Hello,
I'm using Segger with the nrf Connect SDK v1.5.1. Before my program's main even calls, the program is getting stuck in the nrf system calls; specifically nvmc_wait() located in system_nrf52.c I've tried on both hardware (BL653) and simulator and both get stuck at the same spot.
Any help would be appreciated, thanks!
I've found a couple things;
For Simulator:
The call stack starts at __start() and after this:
#if defined(CONFIG_PLATFORM_SPECIFIC_INIT)
bl z_platform_init
#endif
The program branches and becomes stuck after void SystemInit() is called and subsequently void nvmc_wait().
For BL653:
The program actually gets stuck at a different point. It's stuck at arch_cpu_atomic_idle() in cpu_idle.S.
It goes to that from the lfclk_spinwait() function in clock_control_nrf.c after this code block.
I thought the reason it might not be working on the BL653 board but working on NRF52833 boards would be because the clock is different, so I changed the configuration around but it is still getting stuck.
I've found a couple things;
For Simulator:
The call stack starts at __start() and after this:
#if defined(CONFIG_PLATFORM_SPECIFIC_INIT)
bl z_platform_init
#endif
The program branches and becomes stuck after void SystemInit() is called and subsequently void nvmc_wait().
For BL653:
The program actually gets stuck at a different point. It's stuck at arch_cpu_atomic_idle() in cpu_idle.S.
It goes to that from the lfclk_spinwait() function in clock_control_nrf.c after this code block.
I thought the reason it might not be working on the BL653 board but working on NRF52833 boards would be because the clock is different, so I changed the configuration around but it is still getting stuck.
