Is OCRAM non-volitile? Used/Corrupted by boot rom code?

[MikeMelton]

I am looking for a non-volitile storage location to store state information between reboots and power cycles. This is for the OBDS which is a standalone diagnostics program so I am  not concerned with any operating system issues. I am working on a proprietary board running a quad i.mx6.

OCRAM looked like a perfect candidate at first but it appears to be corrupted or reset in the boot cycle.  So my question is: can I stop the OCRAM from being corrupted?   Is it actually non-volitile in the first place?  Is there a better choice for this storage need?   Keep in mind that this is standalone so there is no disk support.

Thanks,

Mike Melton

WinSystems Inc

[AnsonHuang]

Hi,

Which kind of reboot you meant? Reset or power cycle? If the reboot you meant is causing whole board lose power then re-power the board, I think ocram will definitely corrupt. If the reboot you mean is that SOC's power keeps on during reboot, I think we can try warm reset. There are three kinds of reset on our SOC, warm reset, cold reset and POR. Warm reset may keep ocram data, we can try it. Enable warm reset on src scr register, then trigger wdog reset.

[MikeMelton]

Hi Yongcai,

Thanks for your response!  I am concerned with the power cycle case.   So I guess the question is whether the OCRAM is covered by battery backup.  And I think your response said, no it is not.

Any idea of any other storage area on the i.mx6dq that would be able to provide non-volatile storage through a power cycle?  SNVS seems to be more for security....

Thanks,

MIke

[AnsonHuang · Accepted solution]

Hi, Mike

     As far as I know, there is no memory on chip that can be kept during a power cycle, I am afraid you may need to use external memory, such as SD/MMC card, I2C EEPROM or nand/NOR etc...