thingy53: Firmware update using MCUboot bootloader

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Fri, 31 Mar 2023 13:04:29 GMT

Hello Abhijith,

Thank you very much for your support and time spent on this case.

Indeed hopefully it might be useful for other users.

Have a great day

RE: thingy53: Firmware update using MCUboot bootloader

Menon — Fri, 31 Mar 2023 12:52:37 GMT

Hello,

Glad to hear that it worked. iOS stores some old connection configuration of peripheral and will be expecting a same old configuration next time you connect. I have seen something similar with Thingy53.

But thank you for sharing the details here, will be useful for some other users.

Kind Regards,

Abhijith

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Fri, 31 Mar 2023 07:29:44 GMT

This morning I read about this post ( When do you get the "peer removed pairing information" error? ) about the "peer removed pairing information".

I deleted the existing Bluetooth bond between my iPhone and Thingy53 in bluetooth settings, then everything is working back to normal.

However it looks like the nRF programmer 3.0.8 update on windows was fully necessary for the MCU bootloader to work correctly.

Now it is time to exploit the BT mesh sensor model, I might come back with some questions on this model 🙂

Thank You !

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Thu, 30 Mar 2023 11:34:52 GMT

This morning there has been an update of nRF programmer for desktop (on windows) 3.0.8.

Things are working better but still not completely.

With this new version, now I can upload the pre-compiled firmwares and Thingy53 is now recognized in apps, though not working as expected.

My observations:

1) Uploading (with MCU bootloader via USB & nRF programmer windows) edge_impulse_1.0.0_thingy53_nrf5340.zip

Upload is successful. Thingy53 is recognized in nRF EdgeImpulse App (cf. 2 screenshots below), but with failure message when trying to connect: « peer removed pairing information ».

In addition, any update with nRF programmer on iOS is not working, as seen on 3 screenshots below.

2) Uploading (with MCU bootloader via USB & nRF programmer windows) matter_weather_station_2.0.2_thingy53_nrf5340.zip

Upload is successful with nRF programmer windows. Blue led is blinking.

In addition Thingy53 is visible in nRF Programmer iOS as MatterWeather.

From there I can update via BLE with iOS nRF programmer (which was not working with EdgeImpulse above..). For instance I update the firmware with BT mesh sensors server (this reason why I bought Thingy53). Device is now seen in app as Mesh Sensor.

BUT, unfortunately even though the Mesh sensor is recognized i provisionning process in nRF Mesh App, I am unable to connect to the device. Status stays to connecting without connecting.

3) other observations.

I noticed that the only pre-compiled firmware (uploaded with nRF Programmer windows via MCU bootloader) that allow me after to update firmware in iOS nRF Programmer is MatterWeather.

All the other pre-compiled firmwares, there is an error when trying to update in iOS nRF programmer "Device capabilities not supported".

I also tried to upload the other BTmesh firmwares, namely:

- mesh_light_1.0.0_thingy53_nrf5340.zip

- mesh_light_ctrl_1.0.0_thingy53_nrf5340.zip

- mesh_light_switch_1.0.0_thingy53_nrf5340.zip

I can see Thingy 53 as MeshLight, Mesh Light Fixture, Mesh Light Switch respectively in nRF Mesh App but the device is unable to be provisionned.

I would be so happy to be able to run again the sensor model on Thingy53, so that I can practise the sensors models.

Thanks again for any help on that topic.

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Wed, 29 Mar 2023 14:47:22 GMT

I forget also to mention that as you suggested I uploaded the peripheral lbs sample but thingy53 is not visible as Nordic_LBS.

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Wed, 29 Mar 2023 14:44:43 GMT

Dear Abhijith,

Thank you very much for your help.

Indeed it looks a good idea to check whether it is not a name problem.

So I have uploaded the Edge impulse firmware (edge_impulse_1.0.0_thingy53_nrf5340.zip) to the thingy53 as you may see on pictures below :

The upload looks good, and at the end of it, I can see Application: Thingy53 instead of bootloader.

Then I am looking for a Thingy (or any other name) in Edge Impulse App, but not found :

Also I am looking for thingy in nRF Programmer on iOS, but I cannot see any name.

In addition I tried to update on all nearby devices with n/a names also, but still.

Would Thingy 53 be slightly capricious :) ?

RE: thingy53: Firmware update using MCUboot bootloader

Menon — Wed, 29 Mar 2023 13:16:12 GMT

Hello,

[quote user=""]Thingy in nRF app[/quote]

Is it because the precompiled files will change the name of the thingy after doing an update. For eg: If you are uploading the peripheral lbs sample then thingy53 will be visible as Nordic_LBS.

Could you once try with nRF programmer app for uploading the Edge impulse firmware to the thingy53? You can follow this.

Kind Regards,

Abhijith

RE: thingy53: Firmware update using MCUboot bootloader

BesbarJB — Wed, 29 Mar 2023 07:55:08 GMT

I tried this morning again. It is still not working.

However I have built the blinky example (with nRF SDK in VS code, using thingy53_nrf5340_cpuapp as target board) and upload the resulting dfu_application.zip to thingy53.

Now the led blinks indeed.

So I wonder why this is not working with other softwares.