-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zephyr UpdateHub sample issues #69297
Comments
Hi @RafalHalik! We appreciate you submitting your first issue for our open-source project. 🌟 Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙 |
@nandojve can you please take a look? |
Hi @RafalHalik, This seems to be related to changes introduced by #50816. We need to understand why this is happening to fix it. |
After the changes introduced by zephyrproject-rtos#50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes zephyrproject-rtos#69297 Signed-off-by: Gerson Fernando Budke <[email protected]>
After the changes introduced by zephyrproject-rtos#50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes zephyrproject-rtos#69297 Signed-off-by: Gerson Fernando Budke <[email protected]>
After the changes introduced by #50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]>
Hi @RafalHalik , With the #72300 the UpdateHub is fully operational again. |
Hey @nandojve That's great news thankyou for looking into this |
Hi @RafalHalik , The backport is already scheduled for 3.5/3.6. I'll add the missing parts and fix commit msgs soon. |
After the changes introduced by zephyrproject-rtos#50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes zephyrproject-rtos#69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 5fb62ca)
This fixes compatibility with recent bootutils API. Fixes zephyrproject-rtos#69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 94cd46d)
This fixes compatibility with recent bootutils API. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 94cd46d)
After the changes introduced by #50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 5fb62ca)
This fixes compatibility with recent bootutils API. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 94cd46d)
After the changes introduced by zephyrproject-rtos#50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes zephyrproject-rtos#69297 Signed-off-by: Gerson Fernando Budke <[email protected]>
After the changes introduced by #50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 5fb62ca)
This fixes compatibility with recent bootutils API. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 94cd46d)
After the changes introduced by #50816 the UpdateHub could not decode anymore the JSON object. This introduce missing parsing definitions to allow JSON parser undertood the correct UpdateHub probe object. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 5fb62ca)
This fixes compatibility with recent bootutils API. Fixes #69297 Signed-off-by: Gerson Fernando Budke <[email protected]> (cherry picked from commit 94cd46d)
I've been working with the OTA updatehub sample built for mimxrt1060_evk.
I've come across some issues with json parse in the mcuboot updatehub agent. When a package is uploaded for a rollout using updatehub-ce in a docker container. The device does a check to pull the update down i get the following error in a minicom terminal window...
minicom -D /dev/ttyACM0
However the update would not fail imedietly but after a minute (interval to check for an update again) it would try pull the meta data about the update once again and fail in the same way.
I decided to by-pass the cleanup that happens if the json parse fails and now all checks to do with meta data from the json parse fail and print their error messages...
and with this change the update fails and doesn't try again after the minute.
To Reproduce
-Following the steps from https://docs.zephyrproject.org/latest/samples/subsys/mgmt/updatehub/README.html
The only difference being building for a mimxrt1060_evk board.
docker run -it -p 8080:8080 -p 5683:5683/udp --rm updatehub/updatehub-ce:latest
localhost:8080
orlocal ip
zephyr-update.pkg
on the updatehub dashboardneed to be commented out, can be found at
~zephyproject/zephyr/subsys/mgmt/updatehub/updatehub.c
I have also check using uhu if my metadata is valid:
Expected behaviour
Impact
Due to this issue I haven't been able to continue on with working with this sample
Environment
The text was updated successfully, but these errors were encountered: