Storing Device Serial/Identifier

RE: Storing Device Serial/Identifier

phipi — Mon, 16 Mar 2020 15:14:51 GMT

The way I've been doing it until now is generating a hex file with the system config data structure located in the PM_MCUBOOT_STORAGE_ADDRESS part of the flash. Then when we load the application we use the --sector-erase option to prevent it from being overwritten.

However, with the changes to the PM this has broken. From what I understand we will need to define static partitions but I haven't had time to explore that yet.

Here's the thread on that: https://devzone.nordicsemi.com/f/nordic-q-a/58945/sdk1-2-nvs-changes.

Good luck 🙂

RE: Storing Device Serial/Identifier

anicare-tero — Mon, 16 Mar 2020 07:19:23 GMT

Hi phipi,

Have you found a way to write to NVS when programming? I heard it could be done via SWD but not sure how.

RE: Storing Device Serial/Identifier

phipi — Wed, 11 Mar 2020 13:18:26 GMT

lol yes that's what I meant. I thought at first maybe it was buried somewhere in the response. No worries :)

RE: Storing Device Serial/Identifier

phipi — Tue, 10 Mar 2020 20:20:31 GMT

Thanks for all the info, I'll see if I can figure that out :)

RE: Storing Device Serial/Identifier

anicare-tero — Tue, 10 Mar 2020 20:16:18 GMT

First I tried things with Zephyr's NVS sample and then imported the code to my project (that is based on Asset Tracker application). Then I wrote hard coded stuff (like serial) to NVS and moved on when they started to work.

I have implemented Serial LTE Modem sample to my project, before the sample was changed from UART interrupt driven to serial sync mode, and without tcpip and any other parts, only the AT host part from that sample. Then I edited it to first comparing the buffer to my custom commands and then to AT commands.

I have successfully managed to write things like serial to NVS from terminal.

I hope you'll get this working and will happily help you more if you need.

EDIT: lol, actually I didn't answer your question. I'm not sure how to write to NVS when programming (do you mean like flashing the device?) or if it's even possible.

RE: Storing Device Serial/Identifier

phipi — Tue, 10 Mar 2020 19:40:07 GMT

I mean I'm able to read/write NVS from the firmware. However, if I want to program a serial number into 100 boards and have the firmware just read that I'm not sure how to write that value to NVS from the host PC while programming the firmware.

RE: Storing Device Serial/Identifier

anicare-tero — Tue, 10 Mar 2020 19:38:40 GMT

Sorry, I don't understand what you are asking.

RE: Storing Device Serial/Identifier

phipi — Tue, 10 Mar 2020 19:22:25 GMT

anicare-tero, do you have a reliable to program these values from command line?

RE: Storing Device Serial/Identifier

phipi — Tue, 03 Mar 2020 16:35:58 GMT

Okay hopefully one of the Nordic guys can chime in if this is the way to use this now, but thanks for the info. I'll give that a shot in the meantime :)

RE: Storing Device Serial/Identifier

anicare-tero — Tue, 03 Mar 2020 16:31:24 GMT

Yes, it's working for me at least.

RE: Storing Device Serial/Identifier

phipi — Tue, 03 Mar 2020 16:29:26 GMT

For use with MCUBOOT?

RE: Storing Device Serial/Identifier

anicare-tero — Tue, 03 Mar 2020 16:01:21 GMT

For me, DT_FLASH_AREA_STORAGE_OFFSET seems to be working fine.

RE: Storing Device Serial/Identifier

phipi — Tue, 03 Mar 2020 14:56:28 GMT

PM_MCUBOOT_STORAGE_ADDRESS and PM_MCUBOOT_STORAGE_ID seem to be no longer defined as of SDK1.2. Is there a new symbol that should be used now?

RE: Storing Device Serial/Identifier

anicare-tero — Tue, 18 Feb 2020 10:49:40 GMT

I'm still getting this error: 'PM_MCUBOOT_STORAGE_ADDRESS' undeclared (first use in this function); did you mean 'PWM_0_BASE_ADDRESS'?

I have defined CONFIG_BOOTLOADER_MCUBOOT=y and added #include <pm_config.h> but it's still not working.

Do I have to use like pm.yml or what is the solution to this? How should I take MCUBOOT_STORAGE to use?

RE: Storing Device Serial/Identifier

JustinApricity — Fri, 31 Jan 2020 19:43:17 GMT

All good now, thanks!

RE: Storing Device Serial/Identifier

jbrzozoski — Fri, 31 Jan 2020 03:07:30 GMT

Try adding:

#include <pm_config.h>

RE: Storing Device Serial/Identifier

JustinApricity — Thu, 30 Jan 2020 22:24:17 GMT

I am trying to use PM_MCUBOOT_STORAGE_ADDRESS in our project instead of DT_FLASH_AREA_STORAGE_OFFSET so that we can retain NVS storage after a FOTA update. However, when building, I get the following error:

'PM_MCUBOOT_STORAGE_ADDRESS' undeclared (first use in this function); did you mean 'PWM_0_BASE_ADDRESS'?

I am setting CONFIG_BOOTLOADER_MCUBOOT=y in the prj.conf, and we are able to do a FOTA.

Here is the init code... this works fine when using DT_FLASH_AREA_STORAGE_OFFSET.

int tk_nv_init(void){

int err = 0;

struct flash_pages_info info;

/* define the nvs file system by settings with:

* sector_size equal to the pagesize,

* 3 sectors

* starting at DT_FLASH_AREA_STORAGE_OFFSET

fs.offset = PM_MCUBOOT_STORAGE_ADDRESS; // was DT_FLASH_AREA_STORAGE_OFFSET (should be PM_MCUBOOT_STORAGE_ADDRESS)

err = flash_get_page_info_by_offs(device_get_binding(DT_FLASH_DEV_NAME), fs.offset, &info); // previous NVS space

if (err) {

printk("Unable to get page info");

return err;

}

fs.sector_size = info.size;

fs.sector_count = 3U;

err = nvs_init(&fs, DT_FLASH_DEV_NAME); // previous NVS space

if (err) {

printk("Flash Init failed\n");

return err;

}

TK_NV_INCR_M(REBOOT_CNT_ID); // Increment the reboot counter

return 0;

}

RE: Storing Device Serial/Identifier

phipi — Thu, 12 Dec 2019 15:45:21 GMT

Thanks for the details. Unfortunately yes, we need to configure the system for things like serial number, battery type, operating mode, etc.

RE: Storing Device Serial/Identifier

jbrzozoski — Wed, 11 Dec 2019 21:45:42 GMT

I'm not sure when that area of flash is or isn't protected. I would expect the JTAG programmer should be able to write there whenever it wants.

In our application, our initial/default values are the same for every unit we program, so we actually hard-coded them into special NVS-reader functions. A factory reset erases the NVS space on our devices, and the reader functions notice that there is no stored value and return the hard-coded initial/default value instead.

Are you using unique or changing initial NVS values for different devices?

RE: Storing Device Serial/Identifier

phipi — Wed, 11 Dec 2019 21:40:36 GMT

jbrzozoski I'm revisiting this now. I am able to read/write NVS at the PM_MCUBOOT_STORAGE_ADDRESS however I'm not sure how to initialize that area of flash. I'd like to include as part of our programming script writing the initial values to PM_MCUBOOT_STORAGE_ADDRESS (0xFC000) but when I try to write a binary there I get an error. I assume the area is protected.

What is the proper way to do this?

RE: Storing Device Serial/Identifier

jbrzozoski — Tue, 27 Aug 2019 19:09:07 GMT

Take a look at the NVS driver that Zephyr provides. There is a sample application over in zephyr/samples/subsys/nvs.

The only issue I bumped into was the flash offset you pass into nvs_init(). The Zephyr sample uses DT_FLASH_AREA_STORAGE_OFFSET, which should work in most cases. Howeverif you are using mcuboot for FOTA updating, that value needs to be PM_MCUBOOT_STORAGE_ADDRESS.