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

Nothing happens when I flash a firmware on a custom nrf51822 board

The board is simply an nrf51822 with a crystal and required caps and resistors, without any LEDs. When I try to flash any firmware, I get an OK that the firmware has been flashed BUT there's no sign of a BLE connectivity.

I'm using nRF51822 QFAAG2 on the board. I tried to flash BLE_Connectivity(peripheral) example with S110 from V6, V7 and V8, but nothing happens, I don't see any BLE node from my phone. IS there something I'm missing? I tried different example and I get the same issue.

I'm using the NRF51-DK to program the custom board, and compiling the apps with GCC.

What am I doing wrong? thanks.

Parents
  • You might check that your call to SOFTDEVICE_HANDLER_APPSH_INIT (or SOFTDEVICE_HANDLER_INIT) matches reality. I ran into problems when trying to bring up our custom board because the stock example code--which worked on the nRF51 DK--made use of the 32k LFCLK crystal and our custom board did not have that component.

    The other thing you might check in nRF Studio is that what the JLink device actually sees is your custom board and not the nRF51422 on the development board. It could be that this whole time there's been a connection issue between your custom board and the DK, and what you're actually flashing firmware to is the dev board, not the custom board.

    Other than that, it's hard to say what's going on if you can't get a debugger attached.

Reply
  • You might check that your call to SOFTDEVICE_HANDLER_APPSH_INIT (or SOFTDEVICE_HANDLER_INIT) matches reality. I ran into problems when trying to bring up our custom board because the stock example code--which worked on the nRF51 DK--made use of the 32k LFCLK crystal and our custom board did not have that component.

    The other thing you might check in nRF Studio is that what the JLink device actually sees is your custom board and not the nRF51422 on the development board. It could be that this whole time there's been a connection issue between your custom board and the DK, and what you're actually flashing firmware to is the dev board, not the custom board.

    Other than that, it's hard to say what's going on if you can't get a debugger attached.

Children
No Data
Related