Hi
ncs 2.6.1 / toolchain 2.7.0
we have developed a Product using ANNA-B402 (with nRF52833).
Now we made a product variant with nRF52833 WLCSP. Both use the same application-binary (with IO mapping at startup). The application uses mcuboot.
The variant nRF52833 WLCSP does not start, he failed in mcuboot. To find the cause, we made some tests
Application only (without mcuboot, CONFIG_BOOTLOADER_MCUBOOT=n)
nRF52833 WLCSP works well
ANNA works well
Application with mcuboot
ANNA works well
nRF52833 WLCSP works well if we have segger pro connected and made "Debug" or "Attach Debugger to target" or "Debug without flashing"
nRF52833 WLCSP doesnot work standalone (no segger connected, just power cycle)
mcuboot only
ANNA works well
nRF52833 WLCSP works well if we have segger pro connected and made "Debug" or "Attach Ddebugger to target" or "Debug without flashing"
nRF52833 WLCSP doesnot work standalone (no segger connected, just power cycle)
We can not debug with the segger to find the cause (works well when the debugger is connected). We see that mcuboot does not reach the main() from mcuboot.
We use an LED (switch the LED ON at different code lines) to check until which code line the mcuboot will work. We change the LED states with direct write to adresses CNF, DIR, OUT.
When we light on the LED before z_bss_zero(), then the LED will be ON. when we light on the LED after z_bss_zero(), then the LED will stay dark. bss ist at 0x200000e8 / size 0x3928
prep_c.c
void z_arm_prep_c(void)
LED_ON works
z_bss_zero();
LED_ON does not work
Do you have any idea what could be the reason of this ? What can we do to find the cause ? We tried to compare both .conf files, but there are to much entries, maybe you have an idea how an .conf entry can lead to this cause.
Best Regards
Friedrich
