Device not connecting after DFU OTA

RE: Device not connecting after DFU OTA

arjun — Thu, 19 Oct 2017 05:34:33 GMT

Ok. Thanks :-)

RE: Device not connecting after DFU OTA

bjorn-spockeli — Wed, 18 Oct 2017 10:41:18 GMT

Yes, that is because the bootloader in SDK v11.0.0 does not accept signed images. If you want to use signed firmware images you will have to move to SDK v12.3.0, which supports signed images.

RE: Device not connecting after DFU OTA

arjun — Tue, 26 Sep 2017 14:22:41 GMT

Hi Bjorn, is it working??

I have reached a temporary solution. When I am not including the key file in the zip package. its working fine, But when I include the key file , its not working.Could you help with reason..

Thanks

RE: Device not connecting after DFU OTA

arjun — Mon, 25 Sep 2017 09:38:19 GMT

ya, I was able to perform DFU with test images from sdk11.

The nrfutil command I used is as follows- nrfutil dfu genpkg --application hrm.hex --application-version 1 --dev-revision 0xffff --dev-type 0xffff --dfu-ver 0.5 --sd-req 0x81 --key-file hrmkey.pem hrm_dfu.zip

RE: Device not connecting after DFU OTA

bjorn-spockeli — Mon, 25 Sep 2017 08:53:24 GMT

Are you able to perform DFU with the test images from SDK v11? Also could you post the nrfutil command you used to generate the .zip file?

RE: Device not connecting after DFU OTA

arjun — Mon, 25 Sep 2017 05:08:33 GMT

HI Bjorn, I was able to fix the nrfutil v 0.5.2 installation problem. The problem was with the python version. I was using python2.5. When I installed pyhthon2.7, I was able to successfully install the nrfutil.

However after creating the zip file, I am not able to perform DFU operation. When I try to perform DFU, its reaching till "Transmitting firmware update to DFUTarg", but it does not go beyond 0% and disconnects.

For debugging purpose, I compared the init packet of the zip file given in sdk with the one I created. There seemed to be some differences. Could you plz check and let me know.

RE: Device not connecting after DFU OTA

arjun — Fri, 22 Sep 2017 08:32:25 GMT

Yes,I created my own image. I am performing DFU using nrfConnect.

While running, I am getting a linker error "ELF/DWARF", as I mentioned previously. Thus I am unable to run the application.

So I disabled "Include Debug Information" in Options->Linker->Output as suggested in one of the discussions related to ELF/DWARF error. devzone.nordicsemi.com/.../

Still I am facing the same issue and nor am I able to debug.

I followed the following blog - devzone.nordicsemi.com/.../ I have cross-referenced the steps multiple times.Am I missing something??

RE: Device not connecting after DFU OTA

bjorn-spockeli — Fri, 22 Sep 2017 07:49:03 GMT

Did you create your own image or did you use one of the test images in the SDK, if so which image did you use? How did you perferom the DFU, with nrfutil or with one of our mobile apps? Are you able to start a debug session in the bootloader and see if you reach the

nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR);

statment in nrf_dfu_init () in nrf_dfu.c?

RE: Device not connecting after DFU OTA

arjun — Fri, 22 Sep 2017 06:41:44 GMT

Hi Bjorn,

I am now trying to run the secure_ble example in sdk 13. I am able to upload the data over DFU successfully. But after uploading, the device is not coming out of bootloader mode.LED 1 is not glowing, its not advertising..

Even after switching on and switching off, its not advertising. Could it be crashing in the bootloader?

RE: Device not connecting after DFU OTA

arjun — Thu, 21 Sep 2017 12:41:42 GMT

Could you help me with the ELF/DWARF Error.

RE: Device not connecting after DFU OTA

bjorn-spockeli — Thu, 21 Sep 2017 12:12:35 GMT

No, SDK v13.0.0 is in fact better as it is a newer version.

RE: Device not connecting after DFU OTA

arjun — Thu, 21 Sep 2017 12:04:05 GMT

Will it matter, if I use sdk13. When using sdk13, its compiling fine,but while running its giving me error- "ELF/DWARF Error: Unsupported debug_info format version:4"

Failed to load debugee.

RE: Device not connecting after DFU OTA

bjorn-spockeli — Thu, 21 Sep 2017 11:18:09 GMT

Is it an option to move to SDK v12.3.0 ? Then you should be able to use the latest version of nrfutil v3.3.0?

RE: Device not connecting after DFU OTA

arjun — Thu, 21 Sep 2017 09:56:19 GMT

Its still giving the same error.

RE: Device not connecting after DFU OTA

bjorn-spockeli — Thu, 21 Sep 2017 09:34:10 GMT

Try running the pip install -r requirements.txt first.

RE: Device not connecting after DFU OTA

arjun — Thu, 21 Sep 2017 08:46:26 GMT

Its giving error - "No module named py2exe"

RE: Device not connecting after DFU OTA

bjorn-spockeli — Thu, 21 Sep 2017 07:26:49 GMT

Ok, first run pip unistall nrfutil to remove v3.3.0, then install nrfutil v0.5.2 from source, i.e. run the following command in the pc-nrfutil-0_5_2 folder that you unzipped

python setup.py install

after that you should be able to run it from source with this command

python nordicsemi/__main__.py

RE: Device not connecting after DFU OTA

arjun — Thu, 21 Sep 2017 05:40:03 GMT

Hi Bjorn. I am not able to install the nrfutil v 0.5.2. When I am trying to install using pip, it is directly installing nrfutil v 3.3.0. I delete all other nrfutil related files from the system except the nrfutil v 0.5.2. Still I am not able to install.

Whenever I disconnect the internet, and I try to install the nrfutil v0.5.2 by replacing the "nordicsemi" folder in the the python27\lib\sitepackages, I am getting the followuing error- " Could not find a version that satisfies the requirement nrfutil".

RE: Device not connecting after DFU OTA

bjorn-spockeli — Wed, 20 Sep 2017 15:07:48 GMT

The precomiled SDK v11.0.0 bootloader hex is located in SDK_Repository\nRF5_SDK\nRF5_SDK_v11_0_0\examples\dfu\bootloader\hex. You will also have to flash the S132 v2.0.0 Softdevice. The device should advertise as DfuTarg once you reset it.

RE: Device not connecting after DFU OTA

arjun — Wed, 20 Sep 2017 14:59:07 GMT

It seems that still the pre-installed higher versions are working. I will delete all other versions, test it and, let you know.. In the meanwhile could you give me some suggestion about bootloader.

RE: Device not connecting after DFU OTA

bjorn-spockeli — Wed, 20 Sep 2017 14:41:40 GMT

Are you sure that youre using SDK v11.0.0? SDK v11.0.0 and nrfutil v0.5.2 does not support signing keys so you must a newer version if the packet is accepted? What does nrfutil version return?

RE: Device not connecting after DFU OTA

arjun — Wed, 20 Sep 2017 14:40:36 GMT

Could you resolve my one more doubt. Which is the bootloader file that I have to flash in the bootloader region? Is it the hex file given in the bootloader example??

If so, does the hex file code contains only bootloader part or does it also have the application part in it

RE: Device not connecting after DFU OTA

arjun — Wed, 20 Sep 2017 14:34:54 GMT

Ya, I was using nRFGO Studio. Thanks.

This is the command I used to generate the zip file-

nrfutil keys generate hrmkey.pem //for generating the key.

nrfutil pkg generate --hw-version 52 --sd-req 0x81 --application-version 1 --application hrm.hex --key-file hrmkey.pem hrm_dfu.zip

RE: Device not connecting after DFU OTA

bjorn-spockeli — Wed, 20 Sep 2017 13:42:54 GMT

Are you using nRFGo Studio to flash the PCA10036(which should not be used since its the Enginerring version of the nRF52832)? Also can you post the command you used in nrfutil v0.5.2. to generate the .zip file?

RE: Device not connecting after DFU OTA

arjun — Wed, 20 Sep 2017 11:41:09 GMT

I tried with the nrfutil v 0.5.2. I am still facing the same problem.

Meanwhile I have one more doubt.When I am flashing the softdevice and bootloader from 10040 board, I am having no problem, whereas when I am doing the same with the 10036 board, after flashing the softdevice, I am unable to flash bootloader code.It gives the following error, the hex file has data in softdevice region.