Problem with data sharing

RE: Problem with data sharing

Amanda Hsieh — Mon, 11 Nov 2024 13:34:36 GMT

Hi,

That needs fixing upstream, the fix will be in NCS for the v3.0 release next year.

-Amanda H.

RE: Problem with data sharing

QuentinD — Fri, 08 Nov 2024 09:29:09 GMT

Hi,

OK so it's normal 🙂

But then how to avoid this error? (the loader writes in the shared memory for the 2 images but fails on the second write because these TLVs are already present and therefore it stops loading)

RE: Problem with data sharing

Amanda Hsieh — Thu, 07 Nov 2024 13:39:56 GMT

Hi,

[quote user="QuentinD"]But is it normal that I have 2 images?[/quote]

image 0 is for the app and image 1 is for the b1 (mcuboot) because you have b0.

RE: Problem with data sharing

QuentinD — Wed, 06 Nov 2024 16:13:44 GMT

I copied the configs of this example but I still have the same error (there is just the config "CONFIG_BOOT_VALIDATE_SLOT0=n" that I did not use).

No I have to use the pm_static.yml file to be sure to be able to update the devices in the field.

But I found where the problem is exactly but I do not know how to solve it...

I have the error "SHARED_MEMORY_OVERWRITE" because the boot_add_shared_data() function is called twice. So it writes the data on the first call but, on the 2nd call, since the TLVs have already been written, it returns this error...

It executes this function twice because in "context_boot_go()" it goes through all the images and calls the "boot_add_shared_data()" function for each image.

But is it normal that I have 2 images?

So I see this when I retrieve the images in my project (that the sent image is transferts in "image 0 slot 1" and "image 1 slot 1"):

PS C:\DocTA\Soft\TA-Smart-BT840P> mcumgr -c my_config image list

Images:

image=0 slot=0

version: 2.0.0

bootable: true

flags: active confirmed

hash: 2e7bda6855341724a47a3a31fc9781f0b2c14286dacee41ea540e86e1fdd3cdf

Split status: N/A (0)

PS C:\DocTA\Soft\TA-Smart-BT840P> mcumgr -c my_config image upload Application\TA_Smart\signed_by_mcuboot_and_b0_s1_image.bin -e -n2

45.84 KiB / 45.84 KiB [==============================================================================] 100.00% 2.15 KiB/s 21s

Done

PS C:\DocTA\Soft\TA-Smart-BT840P> mcumgr -c my_config image list

Images:

image=0 slot=0

version: 2.0.0

bootable: true

flags: active confirmed

hash: 2e7bda6855341724a47a3a31fc9781f0b2c14286dacee41ea540e86e1fdd3cdf

image=0 slot=1

version: 0.1.0

bootable: true

flags:

hash: 8b4aa96742d98e55f36a080328a6d260923566033484e514839d84e4fa3f76fc

image=1 slot=1

version: 0.1.0

bootable: true

flags:

hash: 8b4aa96742d98e55f36a080328a6d260923566033484e514839d84e4fa3f76fc

Split status: N/A (0)

RE: Problem with data sharing

Amanda Hsieh — Thu, 31 Oct 2024 19:09:55 GMT

I would suggest to not use the pm_static.yml while developing and use it for updating via DFU stage.

Did you add boards/nrf52840dk_nrf52840.conf? If this still cannot help, please use this mcuboot_data_sharing sample as a base.

RE: Problem with data sharing

QuentinD — Thu, 31 Oct 2024 09:50:14 GMT

Hi,

Yes I had already seen this example but in this example they do not use the pm_static.yml file: is there something I need to write in addition in this file? You do not see anything in my config that can cause this problem?

RE: Problem with data sharing

Amanda Hsieh — Wed, 30 Oct 2024 17:19:42 GMT

Hi,

Check out this mcuboot_data_sharing sample.

Regards,
Amanda H.