DFU without a transport layer

RE: DFU without a transport layer

brooksp — Tue, 30 Jun 2020 13:06:19 GMT

Thanks for replying, Rob. I totally understand, and I'll look into reverse engineering some more. I'm specifically trying to figure out the "Wait until I get a response" part.

RE: DFU without a transport layer

Rob Philip — Mon, 29 Jun 2020 23:36:15 GMT

I ended up reverse engineering what happens with the serial DFU, and then emulated that. My image was on a file system and so I'd read a block, send it to the DFU interface, wait until I got a response and then read & send another block.

I don't work for that company any more and don't have the code available to me, unfortunately, or I'd be more specific.

RE: DFU without a transport layer

brooksp — Mon, 29 Jun 2020 18:17:22 GMT

Hey Rob, I think I'm trying to do something similar to your original post. Did you find out how to send blocking NRF DFU requests, or did you go a different route?

Thanks!

RE: DFU without a transport layer

Rob Philip — Mon, 27 Jan 2020 00:23:07 GMT

I resolved this issue and this ticket can be closed.

RE: DFU without a transport layer

Jimmy Wong — Mon, 15 Apr 2019 16:00:14 GMT

The idea is to skip to use the nrf_dfu_req_handling routine and transport layer. It uses to read the image from the external SPI flash to copy to application region. This is just for the demo source code.

RE: DFU without a transport layer

Rob Philip — Mon, 15 Apr 2019 15:57:10 GMT

I'll have a look in just a minute. Does it still use the DFU code to write/verify the image, or is is a "roll your own" solution?

RE: DFU without a transport layer

Jimmy Wong — Mon, 15 Apr 2019 15:42:29 GMT

You can refer to the example of the SPI bootloader which doesn't have the transport layer for reference.

https://github.com/jimmywong2003/nrf5-external-spi-flash-bootloader