Hi, I have some problem with EVM_3530 + BSP_WINCE_ARM_A8_01_02_00.
The system is freezed when it is booting.
I use kitl to trace the booting, I found it stop when Loading OMAP_EHCIHCD.DLL
How could i investigate this problem?
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.
Hi, I have some problem with EVM_3530 + BSP_WINCE_ARM_A8_01_02_00.
The system is freezed when it is booting.
I use kitl to trace the booting, I found it stop when Loading OMAP_EHCIHCD.DLL
How could i investigate this problem?
More details, I found it is freezed in the funtion "void SOCEhciConfigure(SEHCDPdd * pPddObject)" affter execute
"pOMAP_PRCM_CORE_PRM_REGS->PM_PWSTCTRL_CORE |= (0x01 << 4); "
Yuqing,
Did you download the bootloader which came with (got built) with the 1.02 release? Also, did you erase the blocks (using erase block range command under flash management menu in eboot) before loading the NK.bin?
The above will make sure you have a good starting for the new BSP.
Regards,
Aparna
yongqing,
What 3530 silicon version do you use on your EVM board?
Thanks,
Tao
Hi, Aparna.
Yes, I use the bootloader came with the BSP, the flash stored nothing except the bootloader it self.
Yuqing,
Even if NK.bin is not being written to NAND, could you clear up the flash using erase block range command from eboot (for omap3530, range to be used is 1 to 2047)?
Thanks,
Aparna
Also, are you seeing this issue with the demo image which is part of BSP distribution and on the TI EVM3530?
thanks,
Aparna
I don't have the TI EVM3530, so I can't test the demo image on it.
I run the NK.bin image on my own make EVM.
We are able to provide support only for the TI EVM. If you did not see this issue with a previous version of the BSP but saw it when you upgraded to the newer version, you will have to check the diff in the code and see what could have impacted. You can also look at the release notes of BSP 1.02 which has details about fixes in the new release.
regards,
Aparna
Thanks for your reply, I will check the source code and make sure why this happened.
I have seen the EHCI freeze problem too. Judging by the number of posts others have also. In my case it’s very random and somewhat rare but it seems to stall after the TLL/USB registers are mapped, the USB module clock is enabled and an attempt is made to read the USB modules registers. It’s like the module is off but none of the usual methods work to start it. My last resort was to enable the watchdog timer and do a reset if it stalled. The second time up after a reset it always starts fine. I suspected a silicon bug in the USB’s module startup but I see nothing in the errata even though there seems to be quite a lot of other USB issues. Possibily the low level start up code is missing something and its depending on some randomly set startup register...who knows?