• State Not Answered
  • Replies 8 replies
  • Subscribers 63 subscribers
  • Views 3705 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 123415
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Issue with serial DFU on NRF52

Siva

Hi All,

I am trying to get the serial DFU working with nRF52832 development kit with SDK 13. I am able to get the bootloader flashed and have installed the nrfUtil tool. I followed the exact sequence of the steps mentioned here and got it right until the final step where I am trying to sent the application image to the device. The image transfer doesn't progress from 0% and it finally fails with the below logs: image description

I did some debugging and found that in the "on_packet_received" function, the device is getting an invalid opcode and so its responding with an error. I also tried disabling the HFC in device and the nrfutil tool as mentioned in this thread with no success. Finally I also tried changing the UART Tx/Rx pins to to P[0].3 and P[0].4 with no improvements.

Please let me know if you have some pointers which would help me in debugging this.

Parents
  • 0

    Hi Hung,

    Thanks for your inputs.

    I am stuck with an other issue now. I need to do a hard reset (unplug-plug the USB to serial cable in the nef52 DK) before able to perform a serial DFU. This is an intermittent issue when the softreset using SW5 isn't enough after programming the bootloader and you need to perform a hard reset to get the DFU transfer going.

    I connected a saleae to trace the transfer and could see that a nrfutil is it sending a "\t 1 192" in ascii for which there is no response from the device.

    The LED1 and LED3 is the one normally lit in the bootloader mode but in the instances when the device doesn't respond the LED1 changes LED2 and I can see LED2 and LED3 glowing.

    The steps that I followed is as below:

    1. Flash the SD and the bootloader after a flash erase from nrfGO.
    2. Reset the device using SW5 and transfer the image using nrfUtil
    3. Transfer fails with msg "No ping response" (Not always)
    4. Unplug and plug the cable. Try the DFU now and it works.

    The same happens when I switch back to the bootloader from the application for performing a DFU. The device jumps to the bootloader but the transfer fails with "No ping response"

    Please let me know if you have some pointers for resolving this issue.

Reply
  • 0

    Hi Hung,

    Thanks for your inputs.

    I am stuck with an other issue now. I need to do a hard reset (unplug-plug the USB to serial cable in the nef52 DK) before able to perform a serial DFU. This is an intermittent issue when the softreset using SW5 isn't enough after programming the bootloader and you need to perform a hard reset to get the DFU transfer going.

    I connected a saleae to trace the transfer and could see that a nrfutil is it sending a "\t 1 192" in ascii for which there is no response from the device.

    The LED1 and LED3 is the one normally lit in the bootloader mode but in the instances when the device doesn't respond the LED1 changes LED2 and I can see LED2 and LED3 glowing.

    The steps that I followed is as below:

    1. Flash the SD and the bootloader after a flash erase from nrfGO.
    2. Reset the device using SW5 and transfer the image using nrfUtil
    3. Transfer fails with msg "No ping response" (Not always)
    4. Unplug and plug the cable. Try the DFU now and it works.

    The same happens when I switch back to the bootloader from the application for performing a DFU. The device jumps to the bootloader but the transfer fails with "No ping response"

    Please let me know if you have some pointers for resolving this issue.

Children
No Data
Related