WEC7: Having problems making NAND registry hive persistent in AM35XX BSP

Patrick1

The following snippet from the debug log is causing the problem....we think:

PID:00400002 TID:00510002 FSREG: OEM forcing clean system hive!
PID:00400002 TID:00510002 FSREG: Mounting clean system hive
PID:00400002 TID:00510002 FSREG: Taking down boot registry. Any open keys will
be invalid.
PID:00400002 TID:00510002 FSREG: OEM forcing user hive cleanup!
PID:00400002 TID:00510002 FSVOL: Using system database volume "\Windows\Registry
\default.vol"
PID:00400002 TID:00510002 FSVOL: OEM forcing clean system db volume!

Every time the OS is rebooting it is forcing a fresh copy of the hive to be created rather than using the existing one. This causes the flushed settings to the hive to be lost.

I have tried quite a few steps from this forum and other sources to no avail......A bit of guidance is badly needed in solving this issue.

Thanks

Patrick

over 13 years ago

0 Tao Zhang over 13 years ago

TI__Expert 4155 points

Have you tried warm reset?

Are you booting from SD card or NAND?

Thanks,

Tao

0 Patrick1 over 13 years ago in reply to Tao Zhang

Intellectual 370 points

No I have not tried warm reset.

I am booting from NAND.

0 Tao Zhang over 13 years ago in reply to Patrick1

TI__Expert 4155 points

Please try warm boot using "reboot" command from shell.

Thanks,

Tao

0 Patrick1 over 13 years ago in reply to Tao Zhang

Intellectual 370 points

It does not work for warm reboot.

Warm reboot from the shell is not wired yet but I am using the reset (dev kit) button, not the power switch, as the warm reboot.

0 Madhvi over 13 years ago in reply to Patrick1

TI__Expert 5320 points

Can you tell us which BSP version are you using and what steps did you do to enable Persistent hive registry? Did you take a look at this article:

http://processors.wiki.ti.com/index.php/Persistent_Registry_in_ARM-A8_BSP

Can you check if this setting is present in [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS] (nand.reg)

"CheckForFormat"=dword:0

-Madhvi

0 Tao Zhang over 13 years ago in reply to Patrick1

TI__Expert 4155 points

Is your dev kit from logicPD? If yes, the "Reset" button is still Cold reset.

To verify, you can look at your Eboot boot up log to see if you have following print out.

">>>Forcing cold boot (non-persistent registry and other data will be wiped)"

I did not get your comments : "Warm reboot from the shell is not wired".

TI BSP already provides the warm reboot through "reboot" command .

You can enter the command from "target control" window if your build has KITL enabled.

Or you can open a Telnet session, the command will be : "do reboot"

Thanks,

Tao

0 Patrick1 over 13 years ago in reply to Madhvi

Intellectual 370 points

Yes I did and follow that link in details.

Yes the "CheckForFormat"=dword:0 is set but there is one difference in the file name. You are referencing a file call "nand.reg", my file is "omap_nand.reg".

I do not know if it tells you anything.

0 Patrick1 over 13 years ago in reply to Tao Zhang

Intellectual 370 points

I will verify it tomorrow.

0 Madhvi over 13 years ago in reply to Patrick1

TI__Expert 5320 points

It is omap_nand.reg for AM35x BSP. Sorry for the confusion.

Can you please answer Tao's questions so that we can analyze the issue further?

few more questions/hints:

1. Is a windows folder created under Nand (Mounted_Volume)? If yes, if you enable system and hidden files from the folder options, do you see system.hv file created in this windows folder?

2. if you create a test folder under Mounted_volume, does it survive the reboot?

-Madhvi

0 Patrick1 over 13 years ago in reply to Madhvi

Intellectual 370 points

I will look into all your questions and get back to you tomorrow morning.

0 Patrick1 over 13 years ago in reply to Patrick1

Intellectual 370 points

1.Is your dev kit from logicPD? If yes, the "Reset" button is still Cold reset.

To verify, you can look at your Eboot boot up log to see if you have following print out.

">>>Forcing cold boot (non-persistent registry and other data will be wiped)"

ANSWER: YES to all above

2.Can you check if this setting is present in [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS] (nand.reg)

"CheckForFormat"=dword:0

ANSWER: Yes but my omap_nand.reg file is referencing [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS] and not [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]. Does it make any difference?

3. Is a windows folder created under Nand (Mounted_Volume)? If yes, if you enable system and hidden files from the folder options, do you see system.hv file created in this windows folder?

ANSWER: YES

4.. if you create a test folder under Mounted_volume, does it survive the reboot?

ANSWER: YES

Boot log file is attached2248.Am35X.log

0 Tao Zhang over 13 years ago in reply to Patrick1

TI__Expert 4155 points

>>>ANSWER: Yes but my omap_nand.reg file is referencing [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS] and not [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]. Does it make any difference?

<Tao> In CE6, the profile name is MSFlash, in EC7 the profile name is changed to FlashDisk. There is no difference.

If you create a test folder under "Mounted_Volume\windows" does it survive the reboot?

Thanks,

Tao

0 Patrick1 over 13 years ago in reply to Tao Zhang

Intellectual 370 points

"If you create a test folder under "Mounted_Volume\windows" does it survive the reboot?"

Answer: YES

0 Tao Zhang over 13 years ago in reply to Patrick1

TI__Expert 4155 points

Then could you explain what is the problem you are facing?

The test we normally do is Touchscreen calibration. After calibrate the Touchscreen data, then warm reboot the target, next time when the system boots up, calibration will be skipped. It shows the desktop without calibration.

Thanks,

Tao

0 Patrick1 over 13 years ago in reply to Tao Zhang

Intellectual 370 points

Example: Any changes that are made in Regional Settings are not saved on reboot

Example: If you modify one key or sub key in the registry and reboot, it does not save it.

0 Patrick1 over 13 years ago in reply to Patrick1

Intellectual 370 points

Tao,

Are you able to reproduce this problem? if so, any ideas yet on this issue!

Remember my boot log file is attached.

0 Tao Zhang over 13 years ago in reply to Patrick1

TI__Expert 4155 points

Could you please give warm reboot a try. That is how we test it.

Thanks,

Tao

0 jojo tai over 13 years ago in reply to Tao Zhang

Prodigy 130 points

I have the same problem.

How can i fix it ?

thx.

0 Tao Zhang over 13 years ago in reply to jojo tai

TI__Expert 4155 points

To make NAND hive registry persistent with cold reboot, you can choose one of the methods below:

1) Remove "IOCTL_HAL_GET_HIVE_CLEAN_FLAG" support from ioctl_tab.h

2) If you need other mechanisms other than "clean registry upon cold reboot", then you can modify the implementation of IOCTL_HAL_GET_HIVE_CLEAN_FLAG - BSPIoCtlGetHiveCleanFlag() in am35x_bsp\src\oal\oallib\ioctl.c

Thanks,

Tao

0 jojo tai over 13 years ago in reply to Tao Zhang

Prodigy 130 points

It's work!!!

thx.

Processors

Processors forum

WEC7: Having problems making NAND registry hive persistent in AM35XX BSP