• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 91 subscribers
  • Views 1939 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 283324
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nrf52840 errata [198] - data corruption on SPIM3

Dor Sadeh

Hi, I'm using the nrf52840 with Zephyr and I indeed encountered data corruption on SPIM3 transmitted data.

How do I implement the proposed workaround?

"Reserve dedicated RAM AHB slave for the SPIM3 transmit buffer, not overlapping with application data used by the CPU."

Parents
  • 0

    Can you try debugging by setting a breakpoint at where the workaround is called and implemented (nrfx_spim.c, lines 204 and onwards).

    I guess it might also not be related to this erratum. If so I guess we need some more info on what you're doing. Is your project based on any of the sample projects in Zephyr/nRFConnect SDK?

    Best regards,

    Simon

Reply
  • 0

    Can you try debugging by setting a breakpoint at where the workaround is called and implemented (nrfx_spim.c, lines 204 and onwards).

    I guess it might also not be related to this erratum. If so I guess we need some more info on what you're doing. Is your project based on any of the sample projects in Zephyr/nRFConnect SDK?

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    I put a breakpoint to verify that the errata code is executed, and it is.

    My app samples sensors and streams the data to flash. The flash used the spim3.

    The problem did not occur when I moved one of the sensors to work with spim3, and the flash uses spim2.

    Maybe since the sensors sampling uses ppi with short transactions (<10 bytes), and the flash uses long 2KB spi transactions without ppi, the problem does not occur now.

Related
Terms of service