While we do have an M0062-2, UFS cards are like hens' teeth. Looks like eBay is about the only way to get one; Samsung seems to have stopped making them.

We did notice the SD_UFS_CARD_DET_N signal on J5 pin A12; is it reasonable to assume that we'd need to pull that pin low even if using a UFS chip (rather than a card) in order to signal the presence of the device?

For a carrier board design, we are investigating taking advantage of the UFS1 interface available on J5 of the VOXL2 for additional storage beyond that on board the SOM. Are there any gotchas we should be aware of? Would we need to make any device tree changes if we wanted to use it?

@Vinny It's an Intel I210--should be as vanilla as it gets and well supported by the kernel.

We have an application where we plan to route the PCIe lanes available on J5 to an Ethernet controller on a custom I/O board. However, I've noticed that PCIe support on other cards (M0062, M0090) seems to be dropped during board development--they look like they're designed with supporting PCIe in mind, but USB alternatives seem to be used instead in the final designs. Will we be fighting an uphill battle here if we try to route PCIe from J5?

I also can't rebuild it on my own--the following versions of proprietary binaries are missing from the downloads page (older versions are available):

Missing: apq8096-proprietary_0.0.4.ipk
Missing: qrb5165-proprietary_0.0.3_arm64.deb

I've tried downloading the latest voxl-cross image from developer.modalai.com several times over the past two days, but every time the download fails after around 593 MB is transferred. I'm logged in and have accepted the EULA. Is this a "just me" problem or is there something going on with this file or other large files? A couple smaller files (in the tens of MB range) downloaded fine for me.