• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1296 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.

Persistent registry hive is not working on WEC7 BSP for BeagleBone

Mikael Jansson
Prodigy 30 points

I’m using the TI ARM-A8 BSP v 02.30.00 for BeagleBone and I can’t get the persistent registry hive working. I have selected the catalogue item “Persistent Hive Registry Storage” in platform builder. When the device starts to boot up WEC7 it halts on loading DLL CCFGSVC.DLL, and nothing happens. If I unselect the “Persistent Hive Registry Storage” option it all works fine. What am I missing here?

  • 0
    Prodigy 120 points

    Hi, 

    Did you enable following flags

    PRJ_ENABLE_FSREGHIVE,PRJ_ENABLE_REGFLUSH_THREAD.

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

    Regards,

    Jayaram

  • 0 in reply to Jayaram K S
    Prodigy 30 points

    Hi,

    I looked at the wiki page and according to that page if you are using BSP version 2.x you only need to select the catalogue item for persistent registry. Anyhow looking further down I see that under the SD/MMC section which apply to the BeagleBone it states no such information so I guess that I should follow this implementation instruction? Selecting persistent storage from the catalogue item for the TI EVM AM335x works fine and it also uses SD/MMC, that’s why I’m a little confused by TI's wiki page. Has no one else tried to use persistent registry for the BeagleBone using the latest release from TI ARM-A8 BSP?

    BR,

    Micke

  • 0 in reply to Mikael Jansson
    Prodigy 165 points

    I found that when using Registry Hive, the registry is divided into two sets (Boot Registry and Registry). The Boot Registry is a minimal registry set containing keys necessary to load drivers (eg. SDCard driver etc) in order to load the registry hive from a file system).

    Boot Registry keys must be enclosed within HIVE BOOT SECTION tags in the registry file in order to be loaded in this phase. In this case the SDHC driver (here Hive was stored) is depending on SDBusDriver, Edma and ClientDrivers to load properly. So they also needed to be within HIVE BOOT SECTION tags. "Show built image" provides a nice overview of what is included in The Boot Registry and Registry (after a makeimage)