Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

About the S132 SDK 17.0.2 DFU

I've been develop the other MCU;s DFU driver for the nrf52832 recently, and I ran into several problems.

The first I show you my DFU step in the RTL8720( Be the central to update the peripheral (NRF52832) ), which I

referenced the IOS DFU Library, Android DFU Library and the nRF5 SDK Doc.

test condition:

  • SD:                                     S132
  • Peripheral:                          nRF52832-QFAA 
  • Central:                               RTL8720DN
  • Firmware generator:           nrfutil
  • Each data obj:                    4KB
  • Each frame sent size:         20 bytes
  • Notify receipt num:              220

Put aside the errors in transmission, ignore the repetitive firmware:

  1. set notify receipt
  2. create data object
  3. send block
  4. wait notify
  5. send block
  6. repeat until all data was sent
  7. cal crc32
  8. excute

When I was sent the first block, I recieved the nofity: 0x60 0x03 0x03.

Which steps I was wrong, please advise.

Thank you!

Parents
  • Hello,

    When I was sent the first block, I recieved the nofity: 0x60 0x03 0x03.

    The value 0x60 means this notification is a response to a request, where the following byte, 0x3 (NRF_DFU_OP_CRC_GET), is the request was in response to.   And the final byte is the is the response code (NRF_DFU_RES_CODE_INVALID_PARAMETER).

    But I don't understand why the bootloader would return this error for the CRC request. What happens if you set the packet receipt notification to '0', do you get the same error?

    Best regards,

    Vidar

Reply
  • Hello,

    When I was sent the first block, I recieved the nofity: 0x60 0x03 0x03.

    The value 0x60 means this notification is a response to a request, where the following byte, 0x3 (NRF_DFU_OP_CRC_GET), is the request was in response to.   And the final byte is the is the response code (NRF_DFU_RES_CODE_INVALID_PARAMETER).

    But I don't understand why the bootloader would return this error for the CRC request. What happens if you set the packet receipt notification to '0', do you get the same error?

    Best regards,

    Vidar

Children
Related