S132 nrfutil DFU package generation

RE: S132 nrfutil DFU package generation

Hung Bui — Wed, 06 Apr 2016 12:52:08 GMT

Hi Cyril,

We found that if you replace "L" with "I" (capital i) at line 82 in nrfhex.py, it should fix the problem. It was due to the difference on python 64-bit and 32-bit. Let us know if it doesn't fix the issue. We have updated the github.

RE: S132 nrfutil DFU package generation

Cyril — Thu, 17 Mar 2016 09:04:19 GMT

I tried with nrfutil.exe, sd_bl.bin is not filled with 0xFF from 0x00 to 0x2000. I upgraded SD+BL OTA. I'll try to look into the python files to fix the issue

RE: S132 nrfutil DFU package generation

Cyril — Wed, 16 Mar 2016 16:55:33 GMT

with nRF52 ?

RE: S132 nrfutil DFU package generation

Hung Bui — Wed, 16 Mar 2016 16:12:31 GMT

This is strange Cyril, I tried with nrfutil.exe on PC and don't have that 0xffff at the first part of the .bin file. I will try to investigate more, maybe it's a bug with the nrfutil on Linux.

RE: S132 nrfutil DFU package generation

Cyril — Wed, 16 Mar 2016 13:49:05 GMT

zip file, without the application dfu.zip

RE: S132 nrfutil DFU package generation

Cyril — Wed, 16 Mar 2016 13:46:50 GMT

I used the hexdump utility on Linux on the sd_bl.bin file generated via nrfutil to see the offset (as you can see in the sample in my post above). I read the memory when I tried to debug the bootloader as it stayed stuck when it verifies if the size of the softdevice is correct, by reading at address 0x5008. I noticed my SD is not actually loaded at the right location in flash. I can upload the zip file without the application binary if you want

RE: S132 nrfutil DFU package generation

Hung Bui — Wed, 16 Mar 2016 11:37:40 GMT

Hi Cyril, How did you do the hexdump to convert the binary file to hex ? Have you tried to do a hex dump after you do DFU on the chip ? I don't think we have that 0x2000 offset with all 0xffff. Could you upload your .zip file that you used ?