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

Unable to run my program or examples

Hi Nordic developers.

I am developing a custom board using 2 Rigado BMD-300, but I am unable to run my 100% operative program or examples.

At first time I was able to see the rigado DFU service working on thoses chips (it was working) I used nrfjprog --family nrf52 --recover to remove the manufacter firmware then I programmed the Softdevice and the application, but the application does not start.

I was thinking the issue is hardware related, but how is it possible if the manufacter code was working from the first time I powered the devices?

I am able to debugging my code, read back my code from the rigado modules, but no able to start the program.

Info: SDK 12.2 nRF52 (rigado bmd-300), SD: s132, Interface programing: SWD (swdclk, swdio, GND)

Any suggestion?

See you

  • Hi guys. I found the "problem" It was related to the NRF_CLOCK_LFCLKSRC I dont have an external LFCLCK because I dont use it on my software, but seems as the Softdevice uses it. I changed it to NRF_CLOCK_LF_SRC_RC or NRF_CLOCK_LF_SRC_SYNTH and all works pretty good almost the modules does start. The issue now I have is... all are identical hardware (rigado module), but one of thoses modules wont start and it get stuck on "ble_stack_init()" all the others modules works except for one that get stuck there

  • FormerMember
    0 FormerMember

    As LFCLK source, and with low power consumption in mind, I would recommend you to use NRF_CLOCK_LF_SRC_RC instead of NRF_CLOCK_LF_SRC_SYNTH. The reason is that the synthesized clock requires the HFCLK to run when it is in use (which is all the time when the softdevice is enabled).

    On the module that is failing, where in the ble_stack_init() does it fail? Is the chip of the same revision as the other chips?

  • Hi Kristin,

    Yes all the modules are identical, but one module get stuck there, same hardware and same software. The order as I programed each module is the following: Softdevice+Application.

    Could this be a defective module? The weird for me is... I am able to debugging it and when it arrives with the manufacter firmware it was working using a DFU service (I removed it to be able to reprogramming using the Nordic SDK)

  • FormerMember
    0 FormerMember

    Does it work to run the chip in debug mode?

  • No, It does not. I noticed in debug mode it get stuck on ble_stack_init() also I noticed if I call uart_init() before the ble_stack_init() or any other clock related the debug mode get stuck there.

    I moved my uart_init() after the ble_stack_init() and it get stuck on the next clock related function in this case I got stuck now on printf("Start Program\r\n"); -- It happens only on the affected module the others works with no issue.

Related