XVF3800 - Tuning via i2c on Mac OS (linux, or windows) possible?

[AnkhInnovationsLLC]

Hello,

So we have a custom board here running the XVF3800 and are at the configuration / tuning phase. Essentially, I'd like to use xvf_host with the device over a USB i2c dongle. On our board, we'll turn off i2c master and set the pins floating as to not interfere with the USB i2c dongle.

It looks like i2c control was never compiled in for Mac OS, Linux or Windows as the various i2c libraries are missing. Checking out the git repo, seems like the combination was never implemented: https://github.com/xmos/host_xvf_control

Any plans for it, or would my best bet be to buy a raspberry pi (is the 5 supported?) and go from there.

[xhuw]

Hi, you will probably find it easiest to go the raspberry pi route. As you say, I2C has not been implemented on the host for other platforms and I have not heard any plans to do so.

If this feature is required for your product then you could contact xmos sales and request it.

If you have any other issues, feel free to ask questions here :)

[AnkhInnovationsLLC]

Actually yes 2 questions:

1) Will the Pi 5 work? I'll have to buy one, so buying an old board is never fun. Edit: Seems like it won't work without some work, as the xmos vocal-fusion readme.md here: https://github.com/xmos/vocalfusion-rpi-setup states "NOTE: Host applications and scripts used by the XMOS products support only 32-bit Raspbian systems." and the raspberry pi5 kernel arguments state: "Raspberry Pi 5 only supports a 64-bit kernel, so this parameter has been removed for that device."

2) Do you know the P/N of the header? I'm in Canada right now but the header if I still have it, is in the US. Edit: Seems like it's this https://www.digikey.ca/en/products/deta ... ByEALw_wcB

[xhuw]

1. thanks for clarifying there, I haven't looked into the pi5. Based on what you said I think that it probably wont work out of the box, we have only been testing with pi4.

2. I will check this

[xhuw]

back to this, the link you shared looks good. I can't find the precise part number we have been using, but the one you shared looks suitable.