nRF52 dfu uart

RE: nRF52 dfu uart

Vidar Berg — Wed, 25 May 2016 14:44:32 GMT

Turns out that there is a know problem with the Segger VCOM on OSX as mentioned here, see "OSX Segger issue". However, it still didn't work after I applied the workarounds here. Could you check if you get the same result?

RE: nRF52 dfu uart

Vidar Berg — Tue, 24 May 2016 15:25:24 GMT

This did not work when I tried it on OSX today, but same version 'util' version is working on windows. I'll have to continue this tomorrow.

RE: nRF52 dfu uart

Justin — Sat, 21 May 2016 18:34:15 GMT

I tried again still no luck:

$ nrfjprog --family nrf52 --program s132_nrf52_2.0.0-7.alpha_softdevice.hex --chiperase
$ nrfjprog --family nrf52 --program ~/Downloads/nrf52832_xxaa.hex --sectorerase
$ nrfjprog --family nrf52 --reset
$ nrfutil dfu serial -p /dev/tty.usbmodem14121 -pkg ~/Downloads/nRF5_SDK_11.0.0-2.alpha_bc3f6a0/examples/dfu/hci_dfu_send_hex/test_images_dual_bank_update_nrf52/dfu_test_app_hrm_s132.zip

RE: nRF52 dfu uart

Vidar Berg — Fri, 20 May 2016 09:27:16 GMT

Try to replace the '--chiperase' option with '--sectorerase'. Otherwise the softdevice will be erased from the device. You need both softdevice and bootloader for DFU to work.

RE: nRF52 dfu uart

Justin — Wed, 18 May 2016 21:23:28 GMT

$ nrfjprog --family nrf52 --program ~/Downloads/nrf52832_xxaa.hex --chiperase
Parsing hex file.
Erasing code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programing device.

$ nrfjprog --family nrf52 --reset
Applying system reset.
Run.

$ nrfutil dfu serial -p /dev/tty.usbmodem14121 -pkg ~/Downloads/nrf5_sdk/examples/dfu/hci_dfu_send_hex/test_images_dual_bank_update_nrf52/dfu_test_app_hrm_s132.zip
Upgrading target on /dev/tty.usbmodem14121 with DFU package /Users/justin/Downloads/nrf5_sdk/examples/dfu/hci_dfu_send_hex/test_images_dual_bank_update_nrf52/dfu_test_app_hrm_s132.zip. Flow control is disabled.
  [------------------------------------]    0%Timed out waiting for acknowledgement from device.


Failed to upgrade target. Error is: No data received on serial port. Not able to proceed.

Possible causes:
- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
- baud rate or flow control is not the same as in the target bootloader.
- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.

RE: nRF52 dfu uart

Justin — Wed, 18 May 2016 21:18:57 GMT

I'm having the same issue both with the hex file you provided and the gcc build from NRF5_SDK 11.

I'm on OSX using nrfutil v0.3.0

$ nrfutil version
nrfutil version 0.3.0

RE: nRF52 dfu uart

Vidar Berg — Wed, 17 Feb 2016 14:46:27 GMT

Unfortunately, the bootlaoder doesn't appear to work when built with GCC in this alpha release. Please try with the attached bootloader that I built with ARMCC and see if you get the same result.

I was able to make it work with the Keil compiled version. Here are the command line arguments I used:

vidar@ubuntu:~/nrfutil/pc-nrfutil/nordicsemi$ sudo python __main__.py dfu serial -p       
/dev/ttyACM0 
-pkg /home/vidar/SDK/nRF5_SDK_11.0.0-
2.alpha_bc3f6a0/examples/dfu/hci_dfu_send_hex/test_images_dual_bank_update_nrf52/dfu_test_app_hrm_s132.zip

Bootloader : nrf52832_xxaa.hex