• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 336 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem with registry hive

Juergen52081
Prodigy 140 points
Other Parts Discussed in Thread: OMAP3530

Hello.

I use the BSP Version 2.30.00.01 with WEC7.

Now I have the problem, that the registry hive didn't work.

Have anyone a solution for the reg hive in NAND-Flash and booting from NAND-Flash?

When I use the original NAND.REG, I have the following result:

First boot: EBOOT format the flash, after starting the image I change a registry key (touch calibration)

Next boot: WEC7 format the flash and the registry setting is lost

Next boot: EBOOT format the flash and the image is lost.

Please, have anyone a solution or the same problem?

Best regards

Jürgen

  • 0
    Mastermind 9310 points

    Hello,

    The TI Common BSP ver. 2.30.00.01 will automatically format the nandflash and wipe the hive registry when a coldboot is detected on the board. You can disable automatic formatting of the nandflash by setting the "CheckForFormat" registry key to "0" in:

    C:\WINCE700\platform\EVM_OMAP3530\SRC\DRIVERS\BLOCK\nand\nand.reg

    This will prevent the automatic format; however, the hive will still be erased because the OAL will call into the "BSPIoCtlGetHiveCleanFlag" during initialization to determine whether it needs to clean the hive registry or not. You can find this function at:

    \WINCE700\PLATFORM\EVM_OMAP3530\SRC\OAL\OALLIB\ioctl.c

    You will notice that this function queries the COLDBOOT parameter, which will cause the hive to be erased during a coldboot. You need to disable the *pfClean = TRUE from being called using your own mechanism.

    Best Regards,

    Adeneo Support