Hi, I have been successful in performing OTA host firmware updates, however it appears that the notecard is downloading and installing the latest firmware in Notehub to the host mcu on every power cycle, even though it is already installed. This is not ideal for me. I only want the host to do an O…

Taylor, Thank you for your diligence! You have discovered a regression in the firmware. We have a fix, and it will be released very soon with the next LTS release of the firmware. We appreciate the clear framing of the question and detailed information you provided. It helped us reproduce and trac…

Hi Taylor, That sounds frustrating. Can you provide us with some more information? In Notehub, what “Environment Variables” are associated with the device? When you say “power cycle”, do you mean the Notecard, the host or both? Are you able to invite support to your project? Once we have some m…

Hi, Here is a list of the device environment variables: [image] And I think it happens when it is the notecard doing a power cycle because when I press reset on the Swan with the notecarrier still powered via USB, this does not happen. No problem – I just invited support to my project! Thank y…

Thank you for sharing all the information! The environment variables look to be in order, so now I have a couple of questions about the firmware. Our expectation is that the Notecard should remember the environment variable settings, and will not retry the DFU unless they were to change. However, …

I do not have any explicit card.restore requests in my firmware and I don’t have anything that puts my host to sleep, either. I am pretty sure I am doing outboard DFU (ISP) (frankly I am unsure of the difference between those two – please excuse my lack of knowledge there). I followed this tutorial…

This is all good stuff! The DFU code looks fine. If that’s all your are doing for DFU, then you are definitely performing ODFU (standard DFU is very code intensive). Which APIs are you using to manipulation or poll the environment variables? Perhaps that will offer a clue as to what you’re seeing. …

Here is the firmware snippet polling the environment variables: int getSensorInterval() { // sensorIntervalSeconds = sensorIntervalSeconds; J *req = notecard.newRequest("env.get"); if (req != NULL) { JAddStringToObject(req, "name", "sample_rate"); J *rsp = notecard.requestAndResponse(…

I have seen this too, although I haven’t investigated much. Sometimes clicking stop update in notehub stops it looping. But I’ve also connected to the notecarrier with USB and the browser terminal on dev.blues, then issued {"req":"dfu.status","stop":true}

Interesting that you’ve seen this too – thank you for sharing! Perhaps there is some sort of code snippet that could be written to check for dfu.status and depending on what “mode” is, it could then do the update?

Very cool! Thank you! :slight_smile:

OTA DFU Update Happens On Every Power Cycle

Firmware

calcut November 2, 2023, 11:45am 9

while we are debugging ODFU issues, any chance of some love from Blues on this issue? Outboard DFU issue - error: esp: erasing flash failed - #12 by calcut

Topic		Replies	Views
Watchdog for ODFU when disabled? Uncategorized	3	105	February 14, 2025
What happens if I have a fleet `_fw` environment variable and then later add an identical device `_fw` variable? Uncategorized	3	44	October 5, 2026
Dfu.status: firmware update superceded Firmware	3	134	September 25, 2024
Intermittent host ODFU failure: cannot allocate 8192 bytes {memory} Notecard Cellular dfu	4	107	July 23, 2026
Trouble Completing OTA Host MCU (Swan + CircuitPython) Firmware Updates Using Notecard DFU Swan python	8	219	March 15, 2026

OTA DFU Update Happens On Every Power Cycle

Related topics