Jake Carter

Should be fixed as of the [Oct 2024 Release](https://github.com/analogdevicesinc/msdk/releases/tag/v2024_10)

I think the PR helps a little bit, but still doesn't really address the root issue that we are not abstracting away this complexity from the user at all. Yes,...

This is a relatively common scenario we should be able to support. It's an issue that's been fixed in the ["V2" version](https://analogdevicesinc.github.io/msdk//USERGUIDE/#spi-v2-library) of the SPI drivers, but most of the...

@BrentK-ADI any success with the V2 drivers?

Thanks @TerryWoo123, it should be relatively straightforward to pull this into the MSDK. There are just a few changes we will need to make: 1. We try to make sure...

> The struct-based API for SPI describes the function of automatically padding the transaction with the appropriate bytes if if rxLen > txLen We have two versions of the SPI...

Yes, the wording and implementation is misleading. Looks like the only time we actually do the automatic padding in "V1" is when `txData` is NULL. (https://github.com/analogdevicesinc/msdk/blob/f2c2c8b03ffb8e92b01947a267c9fe6e18dd5ecc/Libraries/PeriphDrivers/Source/SPI/spi_reva1.c#L737) In which case we...

Agreed. Did some digging and there is a "family code" entry in the USN from the flash info block we can use for this. Just put this together for the...

Hi @buha, I agree. It's been something that I've wanted to address for a while. At the _register_-level, there's going to be unavoidable differences. We generate our register files from...

Thanks, yes it's a good option but we want to avoid overdoing it. It can be difficult for users to port to the new functions, especiallt as they add up...