Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Apologize for the delay on your update question, but this is a first request to do it via USB. We have examples on how to do over-the-air(OTA) updates. We have focused on this method since we feel it is the most common/practical for IoT devices.
I don't want to be disrespectful but your reply is not satisfactory. Unlike OTA, DFU works with no firmware on the module, and it can be used to load firmware before WiFi works and without interfering with it. How about providing a more useful answer with respect to the BOOT0 and BOOT1 pins? I think they are not exposed in the WICED module, but if that is the case, how can Particle Photon module start in DFU mode?
I think using the OTA firmware as bootloader in the SDK is possible. It just lacks of proper documentation. Sometimes instead of preparing pre-cooked solutions that are supposed to be documentation, it is better to explain how things works, and I don't mean one slide. I believe most developers would rather understand than hacking a "solution" by trial and error. By the way, this comment would apply for many features of the SDK. In the specific case, it would be nice a proper explanation of OTA in contrast or as an alternative to DFU. Sure looking at the source code helps and that is how I learned about many features of the SDK. In any case, I had problems documented in other posts with using OTA, including failing for no apparent reason, failing without reporting and error, failing for too large binaries, and in general obscurity of the process. That is why DFU seems an appealing alternative.
You are right. Ultimately, I ended up customizing the bootloader in the process of liberating ourselves from the Broadcom SDK. It is not software production-ready and I don't understand how anyone can ship products with it.