It is said thatNVDS struture data must be written in OTP in production procedure, so I have to burn NVDS data into OTP memory usingSmartSnippets. There is anoffset参数我应该填满,决定燃烧the NVDS data in OTP memory.
my questions is: as far as I am concerned, there is no application code handling the read process of NVDS data from a specific address of OTP memory, therefore, if I burn the NVDS data to offset A or offset B (both in range) of the OTP memory, is there any differences between them?Is it true that the NVDS data will be loaded into RAM correctly inspite of the offset it is in OTP memory?
Eager to hear from you, any advice will be OK.
Hello summer, i have passed this on to our internal team , i hope to get an answer in the next couple of days. BR JE_Dialog
Q.
It is said that NVDS structure data must be written in OTP in production procedure, so I have to burn NVDS data into OTP memory using SmartSnippets. There is an offset parameter, I should fill to decide where to burn the NVDS data in OTP memory.
My questions is: as far as I am concerned, there is no application code handling the read process of NVDS data from a specific address of OTP memory, therefore, if I burn the NVDS data to offset A or offset B (both in range) of the OTP memory, is there any differences between them?
Is it true that the NVDS data will be loaded into RAM correctly, in spite of the offset it is in OTP memory?
A.
The NVDS offset depends of the ROM, so you can’t use any offset.
// NVDS location in FLASH
#ifndef __DA14581__
#define NVDS_FLASH_ADDRESS (0x00000340)
#else
#define NVDS_FLASH_ADDRESS (0x00000350)
#endif
No need to read the NVDS structure from OTP, it’s copied to SYSRAM during OTP mirroring.
The NVDS structure residing in the specific SysRAM address is shared from Application (RAM) and Stack(ROM) code.
So ROM expects to find NVDS data in the specific offset and if they are not there it will read garbage.
HM
Well, but I don't quite understand how should I choose the offset in OTP. What you said above is NVDS FLASH address, which is different from the address the NVDS data is in OTP memory, and it seems that OTP memory starts from 0x40000 according to SmartSnippets, which is not the same as 0x00000000 either.
Could you help me ?
Hello Summer, i am checking (there is a public holiday today in country with SW team). However, i believe that if writing to OTP , the offset is zero (since the boot ROM is always looking for specific , non vairable locations in OTP. We will confirm. BR JE_Dialog
any information for the SW team ?
We are eager to here from you soon, sincerely.
Hi, JE_Dialog, is there any suggestions from the SW team ?
Hi Summer, I'm still checking : it looks like it isn't documented anywhere - we're pretty sure its no offset, but will continue to check. Is this a blocking issue stopping you from moving to production ? BR JE_Dialog
Yes,. by far by now, we can choose not to burn NVDS to OTP to solve this issue, but I want to know the details later.