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

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

squwal — Thu, 09 Sep 2021 09:55:31 GMT

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!

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

Øivind — Thu, 09 Sep 2021 09:43:59 GMT

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

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

squwal — Wed, 08 Sep 2021 12:25:34 GMT

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?

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

Øivind — Wed, 08 Sep 2021 12:02:38 GMT

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.

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

squwal — Wed, 08 Sep 2021 11:22:11 GMT

Both SPIM2 and SPIM4 met the problem.

custom board files? Do you mean the overlay files?

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

Øivind — Wed, 08 Sep 2021 11:17:23 GMT

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?

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

squwal — Wed, 08 Sep 2021 11:02:29 GMT

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?

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

Øivind — Tue, 07 Sep 2021 14:31:26 GMT

There was a change to the disk drivers in zephyr, I think that might be the issue. Try to add:

CONFIG_DISK_DRIVERS=n

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

squwal — Tue, 07 Sep 2021 12:20:04 GMT

Hi Oivind,

Is there any advice for me?

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

squwal — Mon, 06 Sep 2021 11:53:08 GMT

No, I did not change any code, and I use the same board.

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

CONFIG_BOARD_ENABLE_DCDC_APP=y
CONFIG_BOARD_ENABLE_DCDC_NET=y
CONFIG_BOARD_ENABLE_DCDC_HV=y

CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_SMP=y
CONFIG_BT_SIGNING=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DIS=y
CONFIG_BT_ATT_PREPARE_COUNT=5
CONFIG_BT_PRIVACY=y
CONFIG_BT_DEVICE_NAME="Zephyr Peripheral"
CONFIG_BT_DEVICE_APPEARANCE=833
CONFIG_BT_DEVICE_NAME_DYNAMIC=y
CONFIG_BT_DEVICE_NAME_MAX=65
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
CONFIG_BT_SETTINGS=y

CONFIG_NVS=y
CONFIG_SETTINGS=y

CONFIG_DISK_ACCESS=y
CONFIG_LOG=y
CONFIG_FILE_SYSTEM=y
CONFIG_FAT_FILESYSTEM_ELM=y

CONFIG_FPU=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=n
CONFIG_CMSIS_DSP=y
CONFIG_CMSIS_DSP_MATRIX=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_GPIO=n
CONFIG_NRFX_GPIOTE=y
CONFIG_NRFX_DPPI=y
CONFIG_NRFX_SPIM=y
CONFIG_NRFX_SPIM2=y
CONFIG_NRFX_SPIM3=y
CONFIG_NRFX_SPIM4=y

CONFIG_NO_OPTIMIZATIONS=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_NRFX_QSPI=n
CONFIG_LOG_PROCESS_THREAD_SLEEP_MS=100
CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE=128
CONFIG_PPI_TRACE=y
CONFIG_NRFX_TIMER=y
# CONFIG_NRFX_TIMER0 is not set
CONFIG_NRFX_TIMER1=y
CONFIG_NRFX_TIMER2=y
CONFIG_NRFX_PWM=y
CONFIG_NRFX_PWM0=y
CONFIG_NRFX_UARTE=y
CONFIG_NRFX_UARTE0=y
CONFIG_UART_ASYNC_API=y
#CONFIG_UART_0_NRF_UARTE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_0_INTERRUPT_DRIVEN=y
#CONFIG_UART_0_NRF_FLOW_CONTROL=n

CONFIG_SERIAL=n
#
CONFIG_CONSOLE=y
#CONFIG_RTT_CONSOLE=y
CONFIG_LOG_PRINTK=y
#CONFIG_LOG_DEFAULT_LEVEL=4
#CONFIG_USE_SEGGER_RTT=y
#CONFIG_LOG_BACKEND_RTT=y
#CONFIG_LOG_BACKEND_UART=n
#CONFIG_LOG_DEFERRED=n
CONFIG_UART_CONSOLE=n
CONFIG_RTT_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y
#

#i2c
CONFIG_I2C=n
CONFIG_I2C_NRFX=y
CONFIG_I2C_1=y
CONFIG_NRFX_TWIM1=y


CONFIG_HEAP_MEM_POOL_SIZE=65536
CONFIG_MAIN_STACK_SIZE=16384
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=16384
#CONFIG_IDLE_STACK_SIZE = 4096
#CONFIG_PRIVILEGED_STACK_SIZE = 4096
#CONFIG_APPLICATION_WORKQUEUE_STACK_SIZE=4096
#CONFIG_APPLICATION_WORKQUEUE_STACK_SIZE=2048
CONFIG_HW_STACK_PROTECTION=y


#USB related configs
CONFIG_USB=y
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Zephyr MSC sample"
CONFIG_LOG=y
CONFIG_USB_DRIVER_LOG_LEVEL_ERR=y
CONFIG_USB_MASS_STORAGE=y
CONFIG_USB_DEVICE_LOG_LEVEL_ERR=y
CONFIG_USB_MASS_STORAGE_LOG_LEVEL_ERR=y
CONFIG_MASS_STORAGE_DISK_NAME="NAND"

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

Øivind — Mon, 06 Sep 2021 11:17:39 GMT

Hi,

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

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