This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Use of Non-Eval Board Custom Hardware

All of our initial BLE project development has been done using a the Nordic nRF5_SDK_15.3.0_59ac345 SDK and 10056 eval board.  Now we have a production board that is based on the eval board but has the following differences:  (1) no reset PB, (2) no SPI flash, and (3) no ext 32K osc

Even after modifying what I believe was a #define for the clock source, my debugger jumps into a SVCALL macro and first gets caught in an assembly code loop looking for a value in SRAM address 0x40000104 to be 1.  Simply put, on the eval board this all works, but on the custom board it does not.  Not sure if this is something related to a need for a new bootloader maybe?

Any insight would be appreciated.

Parents Reply Children
No Data
Related