• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 74 subscribers
  • Views 2758 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 219978
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How to flash examples to Dongle?

qm3ster

I bought a nRF52840 Dongle, to evaluate the use of nRF52840 for ZigBee purposes.

I have been able to flash such firmwares as \examples\peripheral\blinky\hex\blinky_pca10056_mbr.hex with the nRF Connect Programmer v1.0.1, however no LED flashing took place.

Others, like \examples\zigbee\light_control\light_bulb\hex contain just one layer and I cannot flash them this way, but I have been able  to flash them by doing 

nrfutil pkg generate --debug-mode --hw-version 52 --sd-req 0xAE --application .\nrf52840_xxaa.hex package.zip
nrfutil dfu serial -pkg .\package.zip -p COM12

Again, I get a dead device until I reset to bootloader.

What am I doing wrong?

Also, \examples\zigbee\experimental\cli\cli_agent_router\hex\nrf52840_xxaa.hex should show up as a serial port, right? In order to interact with the CLI?
(Because for me no such thing happens, no USB device until reboot to bootloader)

Parents
  • 0

    Ok, so the Dongle is actually PCA10059.
    PCA10056 also uses the same nRF52840 SoC but is not the dongle.
    Hence, I got the blinking working by flashing `\examples\peripheral\blinky\hex\blinky_pca10059_mbr.hex` with the nRF Connect Programmer graphical app.
    This also worked for some other examples, like the BLE hexes that include a SoftDevice.

    But I can't do the same with the nrfutil, because:

    • I haven't been able to make a "dfu package" that doesn't require any SoftDevice. So if I make one from the blinking example, it demands the soft device be installed. And if I `dfu` it when the requires SoftDevice is available, it just puts the `blinky` `--application` after the SoftDevice, which makes it not work. So, how can I make a `package.zip` that doesn't require any soft device?
    • When doing the same with a BLE example, it puts most of the `hex`'s contents, including a second copy of the SoftDevice, after the existing SoftDevice. Hence, once again the example doesn't work. How would I make it update just the Application sector from the `hex`?
      It is definitely possible, because loading this `hex` in  Programmer graphical application shows me the different sectors separately. (But possibly not implemented yet)
Reply
  • 0

    Ok, so the Dongle is actually PCA10059.
    PCA10056 also uses the same nRF52840 SoC but is not the dongle.
    Hence, I got the blinking working by flashing `\examples\peripheral\blinky\hex\blinky_pca10059_mbr.hex` with the nRF Connect Programmer graphical app.
    This also worked for some other examples, like the BLE hexes that include a SoftDevice.

    But I can't do the same with the nrfutil, because:

    • I haven't been able to make a "dfu package" that doesn't require any SoftDevice. So if I make one from the blinking example, it demands the soft device be installed. And if I `dfu` it when the requires SoftDevice is available, it just puts the `blinky` `--application` after the SoftDevice, which makes it not work. So, how can I make a `package.zip` that doesn't require any soft device?
    • When doing the same with a BLE example, it puts most of the `hex`'s contents, including a second copy of the SoftDevice, after the existing SoftDevice. Hence, once again the example doesn't work. How would I make it update just the Application sector from the `hex`?
      It is definitely possible, because loading this `hex` in  Programmer graphical application shows me the different sectors separately. (But possibly not implemented yet)
Children
Related
Terms of service