SPI4M errata on nRF53

RE: SPI4M errata on nRF53

Sigurd Hellesvik — Wed, 05 Jun 2024 14:16:33 GMT

I am looking into why this is not included in the nRF Connect SDK now.

For now, i suggest that you disregard my previous comment and then call

*(volatile uint32_t *)0x5000ac04 = 1;

before you enable SPIM4. And then do this when you put SPIM4 to sleep/wake it up with power management. (same register but 0 and 1 as explained in the errata).

Can you try this and see if you still have the SPIM4 issue you are experiencing?

Regards,
Sigurd Hellesvik

RE: SPI4M errata on nRF53

Ahmed Samir — Mon, 03 Jun 2024 16:23:53 GMT

Hi, I'm using SDK v2.4.1, I'm not sure if this is included in that SDK.

Where should I call this function? Once at initialization or before every SPI transaction?

RE: SPI4M errata on nRF53

Sigurd Hellesvik — Mon, 03 Jun 2024 09:34:38 GMT

Hi,

Our HAL has code to add the workaround for this errata automatically:

https://github.com/zephyrproject-rtos/hal_nordic/blob/fc02d66798f691b66bd6b0236e63082a9c498bbf/nrfx/mdk/nrf53_erratas.h#L5301-L5359

Do you see the effects of the errata on your device?

EDIT: I have to correct myself, I cannot see nrf53_errata_135() used anywhere in our driver after all.
Can you try to call the function from your code and see if that helps?

Regards,
Sigurd Hellesvik