NRF5340 audio keep data through reset

RE: NRF5340 audio keep data through reset

LandyWang — Thu, 31 Aug 2023 06:54:19 GMT

I think I've found the reason for this problem.

In CIS mode, it originally has enable NVS for accessing pairing records, which will conflict with my customized NVS initial code.

I'm working on how to integrate them, and if I have any other questions, I'll post them here again.

Thank you for your assistance.

RE: NRF5340 audio keep data through reset

LandyWang — Thu, 31 Aug 2023 05:46:16 GMT

Thank you for your reply.

I am now using NVS to read and write data, but I have encountered some problems.

Here is my prj.conf and overlay file.

#NVS FLASH
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_NVS_LOG_LEVEL_DBG=y
CONFIG_REBOOT=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

/delete-node/ &storage_partition;

&flash0 {
	partitions {
		/* Set 6KB of storage at the end of 512KB flash */
		storage_partition: partition@fa000 {
			label = "storage";
			reg = <0x000fa000 DT_SIZE_K(6)>;
		};
	};
};

In BIS mode, everything is well. I can use NVS, and audio functions are also normal.

But in CIS mode, the program cannot be executed after burning. It does not boot, and I cannot see the log.

I am confused why this happens, is there a mistake in my settings?

RE: NRF5340 audio keep data through reset

Einar Thorsrud — Wed, 30 Aug 2023 11:52:36 GMT

Hi,

It is possible to write to UICR at run-time (but only from secure mode), and never erase it, as erase of the UICR is only possible together with a full chip erase (erase all). So the UICR is suitable for storing permanent data like serial numbers etc, but not dynamic data. For that you need to use regular flash.

FDS which you refer to is for the nRF5 SDK, but there are equivalent simple file systems available in the nRF Connect SDK. I suggest you take a look at the NVS sample, which demonstrates the use of the NVS subsystem.