UpdateHub/community

All your devices, always updated.

tagboxvipul

@tagboxvipul

And also on updatehub CE device is not able to parse metadata.And giving "updatehub: Could not parse json"

Otavio Salvador

@otavio

@tagboxvipul are you using Linux or Zephyr?

tagboxvipul

@tagboxvipul

zephyr

Gerson Fernando Budke

@nandojve

Hi @tagboxvipul , I would like understand better some points:
1) Is this a recent error because you update code? I mean, have you using UpdateHub with success in past and suddenly it started to fail?
2) We need know what Zephyr version you are using + board + connection details (ETH, WIFI, etc).

tagboxvipul

@tagboxvipul

1) We have had trouble with different parts in update hub. Have not managed to successfully run it end to end. Although in parts we have been able to test it

2)1.7.0ncs, custom board with gsm modem

runs on ppp

tagboxvipul

@tagboxvipul

right now it looks like the package's metadata being parsed by probe_cb is failing. reply.max_length and reply.offset are coming out to be equal (456 bytes). hence data being copied tometadata remains empty memcpy(metadata, reply.data ,reply.max_len - reply.offset);

Otavio Salvador

@otavio

@tagboxvipul you can run uhu package metadata to check if it is consistent.

tagboxvipul

@tagboxvipul

@tagboxvipul you can run uhu package metadata to check if it is consistent.
My package metadata looks like this
{
"objects": [
[
{
"filename": "app_update.bin",
"mode": "zephyr",
"sha256sum": "2a6c8d6ed71c2ab293dce3e2ef5dd03d116df387cd43fa161478cf25ffe43ddd",
"size": 328262
}
],
[
{
"filename": "app_update.bin",
"mode": "zephyr",
"sha256sum": "2a6c8d6ed71c2ab293dce3e2ef5dd03d116df387cd43fa161478cf25ffe43ddd",
"size": 328262
}
]
],
"product": "e4d37cfe6ec48a2d069cc0bbb8b078677e9a0d8df3a027c4d8ea131130c4265f",
"supported-hardware": "any",
"version": "3.0.0"
}
Valid metadata.

Otavio Salvador

@otavio

so it looks good. Have you check using latest updatehub-ce?

we did some fixes some weeks ago

@nandojve can you check it too?

tagboxvipul

@tagboxvipul

and reply.data from probe_cb is
f0 2b 01 20 c8 01 c8 01 0c aa 04 00 1c 00 aa aa |.+. .... ........
00> 68 45 f9 de 03 23 f6 63 1a 64 9e ab d2 0f 01 b7 |hE...#.c .d......
00> ff 7b 22 6f 62 6a 65 63 74 73 22 3a 20 5b 5b 7b |.{"objec ts": [[{
00> 22 66 69 6c 65 6e 61 6d 65 22 3a 20 22 61 70 70 |"filenam e": "app
00> 5f 75 70 64 61 74 65 2e 62 69 6e 22 2c 20 22 6d |_update. bin", "m
00> 6f 64 65 22 3a 20 22 7a 65 70 68 79 72 22 2c 20 |ode": "z ephyr",
00> 22 73 68 61 32 35 36 73 75 6d 22 3a 20 22 34 34 |"sha256s um": "44
00> 33 65 33 35 30 33 66 62 66 39 32 37 66 64 36 62 |3e3503fb f927fd6b
00> 38 39 65 38 64 66 31 38 61 34 33 34 30 38 35 66 |89e8df18 a434085f
00> 31 64 33 65 39 36 61 39 39 62 39 64 36 39 32 32 |1d3e96a9 9b9d6922
00> 36 63 61 38 30 63 61 63 30 64 61 65 33 61 22 2c |6ca80cac 0dae3a",
00> 20 22 73 69 7a 65 22 3a 20 33 32 38 32 33 32 7d | "size": 328232}
00> 5d 2c 20 5b 7b 22 66 69 6c 65 6e 61 6d 65 22 3a |], [{"fi lename":
00> 20 22 61 70 70 5f 75 70 64 61 74 65 2e 62 69 6e | "app_up date.bin
00> 22 2c 20 22 6d 6f 64 65 22 3a 20 22 7a 65 70 68 |", "mode ": "zeph
00> 79 72 22 2c 20 22 73 68 61 32 35 36 73 75 6d 22 |yr", "sh a256sum"
00> 3a 20 22 34 34 33 65 33 35 30 33 66 62 66 39 32 |: "443e3 503fbf92
00> 37 66 64 36 62 38 39 65 38 64 66 31 38 61 34 33 |7fd6b89e 8df18a43
00> 34 30 38 35 66 31 64 33 65 39 36 61 39 39 62 39 |4085f1d3 e96a99b9
00> 64 36 39 32 32 36 63 61 38 30 63 61 63 30 64 61 |d69226ca 80cac0da
00> 65 33 61 22 2c 20 22 73 69 7a 65 22 3a 20 33 32 |e3a", "s ize": 32
00> 38 32 33 32 7d 5d 5d 2c 20 22 70 72 6f 64 75 63 |8232}]], "produc
00> 74 22 3a 20 22 65 34 64 33 37 63 66 65 36 65 63 |t": "e4d 37cfe6ec
00> 34 38 61 32 64 30 36 39 63 63 30 62 62 62 38 62 |48a2d069 cc0bbb8b
00> 30 37 38 36 37 37 65 39 61 30 64 38 64 66 33 61 |078677e9 a0d8df3a
00> 30 32 37 63 34 64 38 65 61 31 33 31 31 33 30 63 |027c4d8e a131130c
00> 34 32 36 35 66 22 2c 20 22 73 75 70 70 6f 72 74 |4265f", "support
00> 65 64 2d 68 61 72 64 77 61 72 65 22 3a 20 22 61 |ed-hardw are": "a
00> 6e 79 22 2c 20 22 76 65 72 73 69 6f 6e 22 3a 20 |ny", "ve rsion":
00> 22 33 2e 30 2e 30 22 7d a8 73 02 00 00 00 07 61 |"3.0.0"} .s.....a
00> 01 00 00 00 88 c4 00 20 28 2e 01 20 33 72 02 00 |....... (.. 3r..
00> fd 71 02 00 85 f1 03 00 fd 71 02 00 ff 0a 04 00 |.q...... .q......
00> 70 a2 00 20 00 00 00 00 00 00 00 00 63 d7 03 00 |p.. .... ....c...
00> a8 73 02 00 00 00 07 61 01 00 00 00 88 c4 00 20 |.s.....a .......
00> 10 00 00 00 30 2e 01 20 00 00 00 00 88

And reply.max_len = 456 offset len is 456 ,i have done some hack to parse meta data like (memcpy(metadata, reply.data +(32-15),456);) but after this it is failing at

above picture

Gerson Fernando Budke

@nandojve

Hi @tagboxvipul ,
Ok, so you never got UpdateHub to work at least 1 time, right?
I need know Zephyr correct version. I mean, are you using 2.7.0 Release ( I mean the tagged version)? I need know what development board you are using? I need know what modem you are using.

Currently, we have it working with SIMCOM SIM-800 over PPP

Currently Zephyr (at mainline) is changing a lot of things in JSON parser.

Did you follow this tutorial? https://docs.updatehub.io/zephyr-project/zephyr-project-guide/

The easy way to test UpdateHub is using local network with UpdateHub-CE and Ethernet.

Otavio Salvador

@otavio

The upload is likely due do you didn't log in properly.

tagboxvipul

@tagboxvipul

Hi @nandojve It was working earlier for POC we have not tried in production .
1 ) I am working on ncs v2.6.99-ncs1 tag. and harwdare is nrf52840 and quectels EC20 module over PPP
2 )

Currently Zephyr (at mainline) is changing a lot of things in JSON parser.

I dont think there is json parsing issue coap_packet reply data looks like .+.............hE...#.c.d.......{"objects":[[{"filename":"app_update.bin","mode":"zephyr","sha256sum":"443e3503fbf927fd6b89e8df18a434085f1d3e96a99b9d69226ca80cac0dae3a","size":328232}],[{"filename":"app_update.bin","mode":"zephyr","sha256sum":"443e3503fbf927fd6b89e8df18a434085f1d3e96a99b9d69226ca80cac0dae3a","size":328232}]],"product":"e4d37cfe6ec48a2d069cc0bbb8b078677e9a0d8df3a027c4d8ea131130c4265f","supported-hardware":"any","version":"3.0.0"}
Is this data looks like correct but first 32 byte looks weird does is coming from any padding header and due to this i think its failing to memcpy at line memcpy(metadata, reply.data ,reply.max_len - reply.offset);

The easy way to test UpdateHub is using local network with UpdateHub-CE and Ethernet.
right now i dont have hardware setup for this

tagboxvipul

@tagboxvipul

Attahched screenshot shows line number 739 is not able to copy any metadata

tagboxvipul

@tagboxvipul

@nandojve @otavio please help me to solve above issue ASAP

Gerson Fernando Budke

@nandojve

Hi @tagboxvipul , can you check if you have this patch? zephyrproject-rtos/zephyr#37854

I remember that was introduced a regression in Zephyr and I fixed for Zephyr 2.7.0

Since you are entering in production, I strong recommend get an official version like 2.7.0 instead any intermediary like 2..6.99

We try run tests on each final development phase to make sure any new release is without regression.

Gerson Fernando Budke

@nandojve

The UpdateHub Zephyr code base seems to be stable at 2.3, 2.4, 2.7 LTS. Zephyr have tons of changes in 2.5 that compromise many subsystems and majority was fixed at 2.6 for 2.7 release.

tagboxvipul

@tagboxvipul

as i am using nrf connect sdk for zephyr can you help me to point stable version on this repo which is tested

https://github.com/nrfconnect/sdk-zephyr

Gerson Fernando Budke

@nandojve

I see, I think in this case best you can do is simple cherry-pick #37854 change in another local branch to make some tests.

can you help me to point stable version on this repo which is tested

You can find this answer at Zephyr discord channel at Vendors/Nordic

It is very difficult know what is inside a vendor release and best is ask directly to them.

The other think you can try is simple use Zephyr LTS version directly with Zephyr SDK 0.13.1

tagboxvipul

@tagboxvipul

okay thanks alot will try this and let you.

Gerson Fernando Budke

@nandojve

Ok, let us know if you succeed.

tagboxvipul

@tagboxvipul

hey gerson, thanks for the help. after cherry picking updatehub.c the download was succesful. But now I am downloaded image is failing sha validation (see screenshot) with error: updatehub: Firmware - flash validation has failed

We are also raising it with nordic, given we are facing this issue in their mainted fork. But if you have seen this issue please let us know if we need to cherry pick any other module from 2.7.0

Gerson Fernando Budke

@nandojve

Are you with both Download and Storage check enabled, right?

If this is the case, UpdateHub is OK and now there is some issue about write/read at flash.

It will be hard to us follow what is manufacturer branch.

If you not uses something too specific from Nordic, I would encourage you to test directly from Zephyr 2.7.0 LTS version.

youssefchei-xite

@youssefchei-xite

Hello
I'm testing the updatehub using nrf5340dk and quectel BG96 as modem.
I used the zephyr/samples/subsys/mgmt/updatehub sample and I used the updatehub cloud for update (free version for now)
1- I build and flash the version 1.0.0
2-Create and push the update package 2.0.0 to updatehub cloud using https://docs.updatehub.io/zephyr-project/zephyr-project-guide/ , steps: 8-9 then create rollout using step 11
3- start the FOTA using updatehub run command
4- the nrf5340dk connect to updatehub cloud, download the binary and update it after reboot and the firmware 2.0.0 is running.

Then I tested the updatehub with DTLS by including overlay-dtls.conf using the default certificates.
But I always got
[00:02:15.450,164] <err> net_sock_tls: TLS handshake error: -6800
[00:02:15.459,075] <err> updatehub: Could not send request
[00:02:15.473,327] <err> main: Invalid response

Is there a certificate that must upload to updatehub cloud?
Is there any config missing to make the updatehub example connect to updatehub cloud using DTLS ?

Where communities thrive

People

Repo info

Activity