• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 623 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.

WEC7 Boot time with AM3517

Michi Yama
Guru 10030 points

Other Parts Discussed in Thread: AM3517

Hi,

My customer is using AM3517 with WEC7 BSP(BSP_WINCE_ARM_A8 02.00.00).

Now customer has one issue "Long boot time".

According to the analysis, AM3517  takes 5seconds waiting in "init.c" source code(SRC\OALLIB\init.c).  As to the source code, it is 100ms waiting, not 5seconds.

The cause is that  "OALStall" function is called without cache-enabled. Customer confirmed that AM3517 waiting time is 100ms if cache is enabled.

How does customer modify BSP source code for fixing this issue?

Please advise me.

the following is environment status.

OS: Windows Embedded Compact 7
BSP: BSP_WINCE_ARM_A8 02.00.00

Source file: SRC\OAL\OALLIB\init.c
Function: OEMInit(）
Internal Function: OALCalibrateSysClk()
Statement: OALStall(100000);

One more question : As to customer's analysis, the value "g_dwMeasuredSysClkFreq" that is calculated by "OALCalibrateSysClk" function is seemed to be not used. Is "OALCalibrateSysClk" function needed in anywhere?

Best regards,

Michi

  • 0
    Guru 10030 points

    Hi,

    I would like to update regarding my question.

    We analyzed the OALCalibrateSysClik" funciton. According to our analyzation, this function make "g_dwMeasuredSysClkFreq" valuables. And this valuables is used for "s_Frequency".

    And "s_Frequency" valuables is used in "OEMProfileTimerEnable(DWORD dwUSecInterval)"....

    As the end reslut, "s_Frequency" valuables is used for "g_pOemGlobal" valuables. "pfnProfileTimerEnable", it is the member valuables of "g_pOemGlobal" struct , it is used for profiler timer interrupt.

    According to MSDN information, the "profiler timer interrupt" in OAL is an option. But this is helpful for timer accuracy increasing.  

    So as a result, "OALCalibrateSysClk" function should not be removed. Is my understanding right?

    If it is so, I would like to know how to enable the cache for "OALCalibrateSysClk" funciton.

    My customer succeeded to cache enable for "OALCalibrateSysClk" function as the below.

     OALCalibrateSysClk() function is moved to the inside of "OALPowerPostInit" of oem_pm.c

    They confirmed this modification makes  100ms wait time by "OALStall" function. Is this modification no problem to other funcition and valuables?

    Please advise me.

    Best regards,

    Michi 

  • 0 in reply to Michi Yama
    Intellectual 630 points

    I have loaded a 4GB SD card with the MLO, EBOOTSD.nb0 and NK.bin that comes with the Demo package "WEC7 BBB 01.05.00", Also I have formatted the card with Fat32 and 4096 byte sectors (using hp foarmat tool), and I have used the TI SD card utility for flashing the SD card, Also I have pushed the user button before power up,
    But noting happens!!!
    I tried without TI Utility and made sd card bootable but no results...
    when I power the board up the leds won't flash, , So I think it's a boot problem, How can I be sure that the MLO is in the first sector of the SD card?
    I have loaded angstrom img succsfuly on BeagleBone Black.

    so please consider the issue and give me the procedure corresponding to this.
    Regards
    aswin pp