forum

Has anyone else had issues with OTA sketch updates? I can only successful push a sketch OTA update if I first push a bootloader OTA update. I tried this with multiple Z_Wave controllers (Zooz Hat and Zooz USB), multiple Raspberry PIs using Home Assistant. I've tried many combinations of service button and reset sequences and no luck with Parameter 20 set to 1. The only way to get a sketch to update OTA is to OTA update the bootloader each time.

Hardware:
Z-Uno2

Make sure to select the chip #1.

Bootloader is #0,
Sketch is #1

Yep, I picked the correct chip number.

Here's what I need someone to confirm:

1) Burn OTA Bootloader Chip #0 - Successful
2) Burn OTA Sketch Chip #1 - Successful
3) Try and Burn OTA Sketch again on Chip #1 (with or without an update) - Unsuccessful
5) Burn OTA Bootloader Chip #0 again - Successful
6) Burn OTA Sketch Chip #1 - Successful

Seem like anytime I want to update the Sketch OTA, I first need to burn the bootloader. So I'm able to remotely update the device, I just doesn't make sense that I need to re-burn the bootloader each time. It seems like the Uno2 needs to be in a "idle" state or some state that pauses the sketch.

It should work without the necessity to upgrade the bootloader again (unless the new sketch was compiled using a newer toolchain).

We will check it.

kreienhe wrote: ↑

14 Jan 2024 04:13

Has anyone else had issues with OTA sketch updates? I can only successful push a sketch OTA update if I first push a bootloader OTA update.

Hello.
What version of Z-Uno firmware are you using?

I'm using v3.0.10 on the Z-Uno2

I have the White "LED_BUILITIN" blinking in my sketch that I see blinking before the Sketch OTA update. Right near the end of the OTA Sketch update, I see the blinking stop. Suggesting the sketch has stopped. I see a few Red and Green blinks then the White led goes on solid. The Sketch firmware doesn't see to update or respond to the controller which eventually will timeout. Again, this is doing a sketch OTA update without doing a firmware OTA update first.

I'm attaching the Z-Wave JS log

The firmware with fragment size 535 is the sketch with Chip 1 selected.
The firmware with fragment size 4773 is the bootloader with Chip 0 selected.

kreienhe wrote: ↑

20 Jan 2024 22:00

I'm using v3.0.10 on the Z-Uno2

Yes, there is such a problem in v3.0.10.
I suggest updating to v3.0.12 beta or waiting for the release version if this problem is not critical.

I have a few questions:

• What are the differences between the ZUNO_TC_BETA files and the ZUNO_CORE_BETA releases files?

• Which of the Beta versions should I try (including the version and build number) to fix the OTA sketch update issue?

What is the difference between the bootloaders contained within these versions?
What version of the bootloader should I try including the version and build number?

TC is the toolchain (compiler) and Core is the code to be compiled with your sketch.

Bootloaders are for different hardware. The toolchain will pick up the right one. Or open the build_md.json to see the description. You need the HW704.