Same spi code runs on nrf52840 but does not run on nrf52832

RE: Same spi code runs on nrf52840 but does not run on nrf52832

Einar Thorsrud — Wed, 24 Apr 2024 13:25:36 GMT

Hi,

Yes, the workaround is effective, so with it you can do 1 byte transfers while DMA is enabled. The main thing when using it is tha tyou need to check for every transaction how large it is, and endable ble workaround before a 1 bye transaction, and disable it after (it will cause problems for multi byte transactions).

There are other good reasons for choosing the nRF52840, but this particular issue whould be managable on the nRF52832 as well.

RE: Same spi code runs on nrf52840 but does not run on nrf52832

JasonChen96 — Wed, 24 Apr 2024 00:04:01 GMT

Thanks for your reply.

So while using nRF52832, adopting the SPIM peripheral (with SPI0_USE_EASY_DMA enabled) and applying Errata 58's work around, I can theoretically achieve the same transfer speeds as on the nRF52840?

If so, is this way above a robust way to solve this problem, or I should just choose nRF52840 for relatively high-speed SPI transaction?

RE: Same spi code runs on nrf52840 but does not run on nrf52832

Einar Thorsrud — Tue, 23 Apr 2024 11:48:39 GMT

Hi,

Erratum 58 on the nRF52832 causes problems with 1 byte SPI transactions. The most robust workaround is to disable DMA as you did, as then you are usign the legacy SPI peripheral instead of the SPIM peripheral. As this does not use DMA, the CPU is used for every transfered byte, and the transfer speed is lower. This erratum does not exist on any of the other nRF52 series devices.