nRF8001, no CommandResponseEvent

[SYonekura]

Hi, I'm porting the nRF8001 library to a PIC, and now i'm having trouble with the setup process: After i get the DeviceStartedEvent the uC starts to send setup messages, and the nRF8001 is supposed to send CommandResponseEvents.

The problem is that i'm getting messages from the nRF8001 of one 0x01 byte followed by 0x00's with the same lenght of the setup message that i send. I've done a lot of debugging trying to resolve this issue but i can't see what's wrong.

Recently i got a Logic Analyzer (Saleae Logic Pro 8) in order to try to resolve this problem. This screenshots show the problem: ScreenShots.zip

The 8 first screenshots show the transmission of the DeviceStartedEvent from the nFR8001 to the uC. After that, the transmission of the first setup packet is shown (i did not include the rest of the setup packets because it was kinda the same behaviour, the only thing that change is the setup packet that the uC transmits)

If someone could help me to find the cause of this behaviour i'll be much appreciated

[David Edwin]

Typically this issue is caused but the mcu driver not implmenting the REQN and RDYN logic correctly. Look at section 7 of the nRF8001 data sheet. You need to place the REQN low and wait for the RDYN to be low before starting the SPI clock.

Unfortunately I am not able to get the saleae viewer to work on my PC and could not view the capture, can you post few screen shots ?

[SYonekura]

i edited the question and added some screenshots. I think the REQN and RDYN lines perform the handshake correctly.