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

DFU on nRF Master Control Panel (andriod version)

oceanide

Dear all.

I have some test result on DFU feature. Please any comment on this issue.

test condition

  • Mater control panel (64-bit version)

  • nRFgo studio (64-bit version) : 1.19.0.7

  • Smart Beacon Kit : PCA20006

  • Pre-compiled binary within Smart Beacon Kit v1.1.0

test result

  • With PCA10000 dongle : The DFU is successful with all binaries.

  • nRF Master Control Panel v2.1.1 (android version)

    Only application DFU is successful. The DFU with bootloader and softdevice is NOT successful. Remote DFU Invalid CRC error happen so that I captured log files for two cases.

dfu-android-bootloader-Log 2015-06-01 210155.txt

dfu-android-sd-Log 2015-06-01 210410.txt

BR

oceanide

Parents
  • 0

    @Hung Bui

    When I tried to use your bootloader hex file, it looks like bootloader downloading is done successfully. But, I got a error message as "Error (0x85): GATT ERROR", so I attached a log file.

    log.txt

    When I pressed a button to enter DFU mode again, I never entered into DFU mode and just stayed in normal beacon mode.

    Could you please .dat file for all pre-compiled binaries (softdevice, bootloader, application) of beacon v1.1? I would like to compare if my .dat files are correct or not.

    Thanks in advance

    oceanide

  • 0 in reply to oceanide

    Hi, the Error 0x85 (error 133) happens occasionally sometimes. Also, I think, it may happen when the device is not reachable. If you are dealing with the DFU bootloader from SDK 8+ you should remember that the DFU advertises with an address incremented by 1 when entered with a button (not the buttonless DFU) or in case the softdevice was updated (as it removes the app). This causes a situation when you may send the SD+BL to a device with normal address (when the buttonless update was used) and then an application to a device with address incremented. This issue has been fixed in the new releases of all the Android apps. But it only applies to a situation when you flash SD+BL+App in a single ZIP file after using buttonless update.

    If you want to verify the CRC the best way is to use the nrf utility tool. I gave a link to some documentation above.

Reply
  • 0 in reply to oceanide

    Hi, the Error 0x85 (error 133) happens occasionally sometimes. Also, I think, it may happen when the device is not reachable. If you are dealing with the DFU bootloader from SDK 8+ you should remember that the DFU advertises with an address incremented by 1 when entered with a button (not the buttonless DFU) or in case the softdevice was updated (as it removes the app). This causes a situation when you may send the SD+BL to a device with normal address (when the buttonless update was used) and then an application to a device with address incremented. This issue has been fixed in the new releases of all the Android apps. But it only applies to a situation when you flash SD+BL+App in a single ZIP file after using buttonless update.

    If you want to verify the CRC the best way is to use the nrf utility tool. I gave a link to some documentation above.

Children
No Data
Related
Terms of service