Nora-B126

[Petar02]

Hi everyone,

I have a problem with flashing code to Nora-B126, when i press flash in Visual Studio Code everything works fine. I got: 

Parsing image file.
Verifying programming.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050249959 flashed successfully.

But on actual board nothing happens ( i flashed a simple ble code). Does anyone know whats the problem.

Here is my prj.conf 

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_ZEPHYR_NUS=n
CONFIG_BT_DEVICE_NAME="My_nRF_Device"

CONFIG_LOG=y
CONFIG_LOG_BUFFER_SIZE=16384
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

and also i have built it for nrf5340dk_cpuapp_ns.

[Samruddhi Jadhav]

Hi,

Could you please clarify a bit more about your process here? What exactly is the outcome you are expecting? Have you previously worked with UART logs and are you expecting to see these? Also, are you able to check the status of the application so whether it has crashed or not? A suggestion here would be to connect a debugger. 

[Petar02]

Hi,

The expected outcome is that the LED should turn on/blink and the device should start BLE advertising.

I have not checked UART logs yet, because the flashing process completes successfully without errors. The same application code worked on the C212 NORA-B126 board. The only difference now seems to be that on this board I may need to use the internal LF oscillator, so I added:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

On the C212 NORA-B126 board this was not required.

At the moment it looks like the firmware is “phantom flashed”: the programming tool reports that flashing was successful, but the application behaves as if the code was not actually running at all. The LED does not indicate activity and BLE advertising does not start.

I have not yet connected a debugger to check whether the application crashes or stops before reaching main(), but that will be my next step.