DFU bootloader Serial

RE: DFU bootloader Serial

bjorn-spockeli — Wed, 03 May 2017 14:24:41 GMT

Since you're not using HWFC(which the bootloader is designed for) then you need to send the data at a very low speed in order to avoid overflowing the receive buffer, i've only tested for 9600 baud.

RE: DFU bootloader Serial

Mufasa1 — Wed, 03 May 2017 14:00:55 GMT

Thanks Bjørn. It is working now, but it seems only to work when the baudrate is 9600 and the HWFC is false. If I tried baudrate 38k and HWFC false and it does not work. (the same changes are on dfu_transport_serial.py)

Thanks again :)

RE: DFU bootloader Serial

bjorn-spockeli — Tue, 02 May 2017 11:35:58 GMT

HI Mustafa, I just saw that there is an error in the UART configuration in my answer. It should be NRF_UART_HWFC_DISABLED and not NRF_UART_HWFC_ENABLED, i.e.

nrf_drv_uart_config_t uart_config = NRF_DRV_UART_DEFAULT_CONFIG;

uart_config.pseltxd            = TX_PIN_NUMBER;
uart_config.pselrxd            = RX_PIN_NUMBER;
uart_config.pselcts            = CTS_PIN_NUMBER;
uart_config.pselrts            = RTS_PIN_NUMBER;
uart_config.hwfc               = NRF_UART_HWFC_DISABLED;
uart_config.baudrate           = 2576384; // Corresponds to 9600 baud
uart_config.p_context          = &m_dfu;

RE: DFU bootloader Serial

Mufasa1 — Sat, 29 Apr 2017 01:39:06 GMT

Hi Bjørn, I am still with no luck.

if I let enabled the flow control on dfu_transport_serial.py and bootloader I got the following log:

C:\DesktopHome\Nordic\pc-nrfutil-master>python nordicsemi/__main__.
py dfu serial -pkg 1Normal_HWFC.zip -p COM15
  [####################################]  100%
Device programmed.

If I disable the flow control on dfu_transport_serial.py and bootloader I got the following log:

C:\DesktopHome\Nordic\pc-nrfutil-master>python nordicsemi/__main__.
py dfu serial -pkg 1Normal.zip -p COM15
  [------------------------------------]    0%
Traceback (most recent call last):
  File "nordicsemi/__main__.py", line 681, in <module>
    cli()
  File "C:\Python27\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "C:\Python27\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "C:\Python27\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Python27\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "C:\Python27\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "C:\Python27\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "nordicsemi/__main__.py", line 584, in serial
    dfu.dfu_send_images()
  File "C:\DesktopHome\Nordic\pc-nrfutil-master\nordicsemi\dfu\dfu.
py", line 122, in dfu_send_images
    self._dfu_send_image(self.manifest.application)
  File "C:\DesktopHome\Nordic\pc-nrfutil-master\nordicsemi\dfu\dfu.
py", line 95, in _dfu_send_image
    self.dfu_transport.send_firmware(data)
  File "C:\DesktopHome\Nordic\pc-nrfutil-master\nordicsemi\dfu\dfu_
transport_serial.py", line 277, in send_firmware
    response['crc'] = self.__stream_data(data=data, crc=response['crc'], offset=
i)
  File "C:\DesktopHome\Nordic\pc-nrfutil-master\nordicsemi\dfu\dfu_
transport_serial.py", line 389, in __stream_data
    response = self.__calculate_checksum()
  File "C:\DesktopHome\Nordic\pc-nrfutil-master\nordicsemi\dfu\dfu_
transport_serial.py", line 334, in __calculate_checksum
    (offset, crc) = struct.unpack('<II', bytearray(response))
TypeError: 'NoneType' object is not iterable

at this point I dont know what I am doing wrong. I am compiling after each change dfu_transport_serial.py and verifing it sending printing messages on the command window. I keep the PCA10040 to all the codes, bootloader, app. Does this requiere CTS and RTS pins to works?

In additional I noticed when I disable the flow control on the dfu_transport_serial.py and tried the serial DFU the LED2 and LED 3 turn on and after the it the device restarts and jump to the main aplication.

RE: DFU bootloader Serial

bjorn-spockeli — Fri, 28 Apr 2017 10:52:08 GMT

A additional info I am running the nrfutil from thr souce code calling __main__.py if I made any change to the nrfutil code example disabling/enabling the HWFC does it have any effect calling directly the __main__.py or do I have to compile it before? Yes, you must compile it even though you're running it from source since it uses a static library that must be updated if you modify the source.

RE: DFU bootloader Serial

Mufasa1 — Fri, 28 Apr 2017 08:44:16 GMT

Yes, I did it. I am going to double check again that both app and bootloader have the same pca10040.h file. In case that both are using the same file. I dont know why it does not work on the nRF52 Dk when I changed the Tx/Rx to p03/p04 on the bootloader and app code. A additional info I am running the nrfutil from thr souce code calling main.py if I made any change to the nrfutil code example disabling/enabling the HWFC does it have any effect calling directly the main.py or do I have to compile it before? I tested it using the default Tx/Rx on the DK module and works the serial DFU with no diference. But not when changing the TX/Rx to different pins

RE: DFU bootloader Serial

bjorn-spockeli — Fri, 28 Apr 2017 07:46:37 GMT

@Mufasa1: No, it fully possible to use the Serial Bootloader on custom boards. Are you able to debug your custom board in order to verify that the serial bootloader is running correctly? Have you replaced the pca10040.h file with a custom_board.h file?

RE: DFU bootloader Serial

Mufasa1 — Thu, 27 Apr 2017 20:26:22 GMT

I was wondering if the only way to perform the DFU serial is using a Dev kit Board like the nRF52 DK. or is it possible with a custom hardware? or using a different TX/RX on the Dev kit

RE: DFU bootloader Serial

Mufasa1 — Thu, 27 Apr 2017 14:54:08 GMT

Hi Bjørn, I tried putting tx/rx the p0.3 and p0.04 with no luck. so I opened the shorts on: SB22, SB23, SB24 and SB25 on the nRF52 DK now I am not able to communicate over the Jlink (just as I expected), but I am able to put my device into bootloader from the APP code writing a commad over serial using p0.06, p0.08 with a USB-Serial converter. Still stuck on the percent bar 0%. The Serial DFU only works over the Jlink for me.

Note for my custom board I am not using CTS or RTS. Just TX/RX

RE: DFU bootloader Serial

bjorn-spockeli — Thu, 27 Apr 2017 09:36:37 GMT

The serial bootloader does not advertise on BLE, so thats why you dont see any advertisment packages. I suggest that you change the TX_PIN_NUMBER and RX_PIN_NUMBER to pin P0.03 and P0.04.