• State Not Answered
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 776 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 250830
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Getting started with Eval board

SidPrice

I have just received my nRF52 development board and I have tried to program one of the pre-bjui;t examples (Blinky). The USB drive on the board appears and if I drag the hex file for the board (10040) onto the drive, the file copies but nothing occurs on the board. The file remains visible until I restart the board.

I was expecting the file to be flashed and the example to run. Pressing buttons does nothing.

Parents
  • 0 in reply to SidPrice

    Hello Sid,

    SidPrice said:
    I am using the examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10040_s132.hex.
    SidPrice said:
    The file stays visible on the drive until I cycle the power, then it is gone. On startup the eval board turns on LED1, it does not blink.

     This is the correct behavior for this example, as can be read in the ble_peripheral Blinky example documentation. It runs a contrary to the usual Blinky applications(which you can try out from the peripheral Blinky example(non BLE, only LEDs) because it includes the use of BLE communication between two devices.
    The way the BLE Blinky examples is set up is to demonstrate the transfer of a button press between devices, one running the BLE peripheral Blinky and one running the BLE central Blinky example.
    Sorry for any confusion this might have caused.

    SidPrice said:
    I see the file copied to the drive. The file stays visible on the drive until I cycle the power, then it is gone.

    This is partially correct - once programmed the file should disappear from the file manager. However, the device should reboot itself within ~5 seconds of the firmware being copied to the JLink.
    Could you try to program the device(drop the .hex file in the JLink file explorer) and then just wait till it resets itself? It should, within a short time after the transfer completes.
    The debugger LED on the DK should also blink, following this.

    Best regards,
    Karl

Reply
  • 0 in reply to SidPrice

    Hello Sid,

    SidPrice said:
    I am using the examples\ble_peripheral\ble_app_blinky\hex\ble_app_blinky_pca10040_s132.hex.
    SidPrice said:
    The file stays visible on the drive until I cycle the power, then it is gone. On startup the eval board turns on LED1, it does not blink.

     This is the correct behavior for this example, as can be read in the ble_peripheral Blinky example documentation. It runs a contrary to the usual Blinky applications(which you can try out from the peripheral Blinky example(non BLE, only LEDs) because it includes the use of BLE communication between two devices.
    The way the BLE Blinky examples is set up is to demonstrate the transfer of a button press between devices, one running the BLE peripheral Blinky and one running the BLE central Blinky example.
    Sorry for any confusion this might have caused.

    SidPrice said:
    I see the file copied to the drive. The file stays visible on the drive until I cycle the power, then it is gone.

    This is partially correct - once programmed the file should disappear from the file manager. However, the device should reboot itself within ~5 seconds of the firmware being copied to the JLink.
    Could you try to program the device(drop the .hex file in the JLink file explorer) and then just wait till it resets itself? It should, within a short time after the transfer completes.
    The debugger LED on the DK should also blink, following this.

    Best regards,
    Karl

Children
No Data
Related
Terms of service