Is Errata 109 occurrence related to SPI frequency?

RE: Is Errata 109 occurrence related to SPI frequency?

Kyle Krueger — Fri, 12 Jan 2018 10:25:15 GMT

I wanted to say thanks for the help, but we have not been seeing this issue since reducing the amount of work being done alongside the flash reads and writes. For now I am not sure if this problem has anything to do with Errata 109, but instead could have been an issue with resources.

I will close this issue until we have more time to revisit the builds where this was a problem since some of our changes have proved themselves as an effective workaround.

RE: Is Errata 109 occurrence related to SPI frequency?

Jørgen Holmefjord — Mon, 08 Jan 2018 09:49:40 GMT

It sounds like your approach should work. It would help if you could share some logic traces of the transfer, and also upload your entire SPI related code or the whole project. If you do not want to share it in public, you can create a case on MyPage and link to this thread.

RE: Is Errata 109 occurrence related to SPI frequency?

Kyle Krueger — Wed, 03 Jan 2018 16:30:16 GMT

The receive buffer has a default callback, which manages a queue of SPI commands. Read commands are provided with additional nested function pointers to read out the data (ex. memcopy). This nested function pointer is the last part of the default callback.

At the beginning of each function which uses spiXfer first check a spiBusy flag, if this is true, the command will be ignored, and an error code is returned (to manage a retry). If it is not true, we write true, and proceed to send the command. It will only be marked to false again after the default SPI callback inclusive of the nested function pointer finishes with or without an error.

RE: Is Errata 109 occurrence related to SPI frequency?

Jørgen Holmefjord — Wed, 03 Jan 2018 15:07:09 GMT

How do you read the receive-buffer? Are you using some kind of flag/synchronization mechanism to make sure you do not start a new transfer before the previous is completed?

RE: Is Errata 109 occurrence related to SPI frequency?

Kyle Krueger — Wed, 03 Jan 2018 13:19:25 GMT

I have added information to the question to provide these details. And for the logic analyzer, we do not have one on hand. It would be most convenient if we could work this out without having to go to our other office to use the scope.

RE: Is Errata 109 occurrence related to SPI frequency?

Jørgen Holmefjord — Wed, 03 Jan 2018 11:44:42 GMT

Could you list the part name, or link to datasheet? I assume you are using nRF52832 device, and are using EasyDMA (SPIM), since you reference Errata 109? How do you configure/use SPI (registers directly, HAL, driver, library)? Have you checked the data lines with a logic analyzer, to see if the data is transferred on the bus?

RE: Is Errata 109 occurrence related to SPI frequency?

Kyle Krueger — Wed, 03 Jan 2018 10:43:27 GMT

The specification for the device has only maximum speeds listed per command. For the read and write commands we are using, it has 50 MHz listed, so I do not believe this is the problem here.

Since the time of posting I have also seen the problem with 8 MHz. I have updated the question accordingly.

RE: Is Errata 109 occurrence related to SPI frequency?

Nguyen Hoan Hoang — Tue, 02 Jan 2018 18:43:36 GMT

Have you checked the data sheet of your peripheral to see whether it supports that frequency or not. Some devices work at least 1MHz or more some others at max 1MHz. Make sure you are within range supported by the device.