bootloader_secure_serial and nRFgo Studio not working

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Fri, 16 Jun 2017 07:52:25 GMT

And for the other readers, let's repeat here that you can't use nRFgo Studio but you have to run the programming from command line as:

nrfutil dfu serial -pkg application.zip -p COM# -fc 1 -b 115200

And be sure to generate the application.zip with the private.pem -file which matches the public key compiled into the serial bootloader (located in dfu_public_key.c). See nrfutil documents to find out how to generate the needed public/private key pair.

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Fri, 16 Jun 2017 06:15:31 GMT

No, it did not work without flow control.

RE: bootloader_secure_serial and nRFgo Studio not working

rct42 — Thu, 15 Jun 2017 23:49:22 GMT

@Jarmo, out of curiosity did you happen to have success with this example and modified bootloader without flow control?

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Thu, 15 Jun 2017 12:12:38 GMT

Yep, the CTS pin was connected into a wrong pin of the FTDI module. Now that I connected it into correct RTS pin, I really succeeded to upload a zip file into the pca10040 board! Great! Thanks again :) Now we just need to do the same with our own board...

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Thu, 15 Jun 2017 11:59:11 GMT

Ok, good. Now I tried with flow controls, at least I hope the FTDI module handles them correctly. The result is even worse, bootloader just responds with:

:WARNING:Received unsupported OP code 09
:DEBUG:Sending Response: [0x9, 0x3]

And the nrftool dumps out following:

$ nrfutil dfu serial -pkg ./dfu_test_app_hrm_s132.zip -p COM9 -b 115200 -fc 1
Traceback (most recent call last):
<...trash removed...>
  File "c:\python27\lib\site-packages\nordicsemi\dfu\dfu.py", line 83, in _dfu_send_image
    self.dfu_transport.open()
  File "c:\python27\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 190, in open
    if self.__ping() == False:
  File "c:\python27\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 314, in __ping
    raise NordicSemiException('No ping response')
pc_ble_driver_py.exceptions.NordicSemiException: No ping response

So it does not work, still. Any ideas?

RE: bootloader_secure_serial and nRFgo Studio not working

bjorn-spockeli — Thu, 15 Jun 2017 07:54:01 GMT

No, there is no dependency between the serial bootloader and the S132. The serial bootloader does not enable the SoftDevice or use the sd_flash_-API to write to flash, instead it uses the NVMC directly. So yes, you should be able to use the Serial bootloader from SDK 13 with the S132 v3.0.0 from SDK v12.0.0

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Thu, 15 Jun 2017 07:34:11 GMT

One related question: why there is that dependency between serial bootloader and the s132 soft device? I mean, the serial bootloader is named as "secure_dfu_serial_s132" (sdk 13). If the bootloader really needs the s132 soft device, can we still use sdk 12 version of the s132? Our firmware is compiled against sdk 12 and we don't want to port it for sdk 13 at the moment.

RE: bootloader_secure_serial and nRFgo Studio not working

bjorn-spockeli — Wed, 14 Jun 2017 13:25:15 GMT

Happy to help, let me know how it goes.

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Wed, 14 Jun 2017 12:49:20 GMT

Yep, we have to try with flow controls on. There is no wiring at the moment. Thank you for support!

RE: bootloader_secure_serial and nRFgo Studio not working

bjorn-spockeli — Wed, 14 Jun 2017 12:45:16 GMT

If I perform a Serial DFU using your serialtest.zip and nrfutil v2.3.0 with the following command

nrfutil dfu serial -pkg serialtest.zip -p COM27 -fc 1 -b 115200

then I get the following error

pc_ble_driver_py.exceptions.NordicSemiException: Response Code InvalidObject
Failed to execute script __main__

Which is expected since you've signed the image with your private key and I do not have the corresponding public key in my bootloader. If I generated a new private-public pair and create a new zip with serialtest.hex using the following command

nrfutil pkg generate --application serialtest.hex --application-version 3 --hw-version 52 --sd-req 0x98 --key-file private_key.pem serial_test_pkg.zip

Performing a Serial DFU with the same command as the first time, then the DFU process starts and completes with no errors. Could you try to enable Flow Control?

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Wed, 14 Jun 2017 11:29:04 GMT

Yep, I added those attachments.

RE: bootloader_secure_serial and nRFgo Studio not working

bjorn-spockeli — Wed, 14 Jun 2017 11:19:04 GMT

No, I have not seen that error before. Could you attach the zip file you've generated as well as the hex file to this question so that I can try to reproduce the issue here?

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Wed, 14 Jun 2017 11:01:01 GMT

Now that I changed sd-req into 0x98 to match the soft device in sdk 13.0.0, there is no error in bootloader side, but the nrfutil crashes with the following messages:

$ nrfutil dfu serial -pkg c:/aistin-firmware/core-engine/core-engine.zip -p COM9 -b 115200 -fc 0

Traceback (most recent call last):
<...trash removed...>
  File "c:\python27\lib\site-packages\nordicsemi\dfu\dfu_transport_serial.py", line 347, in __calculate_checksum
    (offset, crc) = struct.unpack('<II', bytearray(response))
TypeError: 'NoneType' object is not iterable

What could be reason for that?

RE: bootloader_secure_serial and nRFgo Studio not working

Jarmo — Wed, 14 Jun 2017 10:55:09 GMT

Yes, I have now tried with the sdk example zip-package using "NRF_DFU_DEBUG_VERSION" of the public key in the bootloader code. Then, I also tried with two self-generated key-pairs, putting the public key into the dfu_public_key.c, and recompiling the bootloader. Then, I generated the package with command:

nrfutil pkg generate --hw-version 52 --sd-req 0x8c --application-version 3 --application _build/application.hex --key-file private.pem application.zip

But with no luck. The result is always as shown above, with pair of unsupported OP codes and failing with "Prevalidate failed!". Well..?

RE: bootloader_secure_serial and nRFgo Studio not working

bjorn-spockeli — Wed, 14 Jun 2017 08:44:27 GMT

Hi Jarmo, nRFGo Studio does not support Secure Serial DFU, it only supports the Legacy Serial DFU. In order to perform Secure Serial DFU you need to use nrfutil v2.3.0, like you did in the EDIT section of your question. The Prevalidate error is caused by the signature of the dfu_test_app_hrm_s132.zip cannot be verified with the public key in the bootloader. Have you created a private-public key pair and replaced the public key in the default bootloader example?