SPIM failed to read after NRF SDK updated to 1.6.x

[squwal]

Hi all,

I am using NRF5340 in my custom board. The spims are working well, they are developed by nrfx lib in NRF SDK 1.5.1.

However, after I updated my sdk to 1.6.1, the spim cannot read correctly anymore.

The chip id I want to read by spim is supposed to be  "0x1a", but always got "0xff".

So is there any changes between sdk 1.5.1 and 1.6.1 on using spim?

Thanks!

[Øivind]

Hi,

Could you show me the prj.conf of the project?

Did you make any changes, other than updating the SDK version?

[squwal]

Hi Oivind,

Is there any advice for me?

[squwal]

I added CONFIG_DISK_DRIVERS=n to prj.conf, but still got the same result.

It is very strange, because I tested the program (built in sdk v1.6.1) on 5340 DK board, it worked well. The program(built in sdk v1.6.1) failed on my custom board.

But the program(built in sdk 1.5.1) worked well on both 5340 DK and my custom board!

So I really want to know why and what is the different between 1.5.1 and 1.6.1? 

[Øivind]

Does this happen on a specific SPIM instance (SPIM0, SPIM2, SPIM4 etc.) or on every instance?

Since you are using a custom board, you are also using custom board files, correct?

[squwal]

Both SPIM2 and SPIM4 met the problem. 

custom board files? Do you mean the overlay files?

[Øivind]

We strongly recommend that custom boards do not use the default board files in zephyr/boards/arm/nrf5340dk_nrf5340. As these will not reflect any changes you have made on your custom board.

If you are using overlay files to differentiate between the boards, it would be helpful to see these overlays.

[squwal]

The pins I used on my custom board are the same pins on 5340DK board. The other differences between the two boards I guess maybe the power circuit. I use VREGH  for cpu cores and PIOs, and I have checked the high level of pins is 3.3V.

I am not using overlay files yet since the program works well in sdk 1.5.1. And I don't know which file should be modified for my custom board, is there any guide for me?

[Øivind]

Do you have a logic analyzer? It would be great to have some logic traces of the SPI lines on the different applications, both working and non-working.

Which board files to modify depends on what is changed, but the board porting guide should be helpful: developer.nordicsemi.com/.../board_porting.html

[squwal]

We did use a oscilloscope to check the signals of spim lines. In sdk 1.5.1 the signals are correct, and in sdk 1.6.1 there are no output at all. But I can reach the spim interrupt handler and got a NRFX_SPIM_EVENT_DONE event.

I will read the porting guide.

Thank you again!