Hi,
After changing another batch of imx6q chip, we found android system cannot boot done, it always hang at:
......
I/Zygote ( 2151): ...preloaded 379 resources in 1771ms.
I/Zygote ( 2151): ...preloaded 31 resources in 9ms.
D/dalvikvm( 2151): GC_EXPLICIT freed 29K, 1% free 6467K/6531K, paused 2ms+2ms
D/dalvikvm( 2151): GC_EXPLICIT freed 10K, 2% free 6457K/6531K, paused 1ms+1ms
D/dalvikvm( 2151): GC_EXPLICIT freed <1K, 2% free 6457K/6531K, paused 2ms+2ms
I/dalvikvm( 2151): System server process 2225 has been created
I/Zygote ( 2151): Accepting command socket connections
D/SystemClock( 2225): Setting time of day to sec=86400
W/SystemServer( 2225): System clock is before 1970; setting to 1970.
the batch number with this issue is:
MCIMX6Q6AVT10AC SBCF1315 KOREA YOCFSBU.
the following chip has no problem:
MCIMX6Q6AVT10AC SBAP1250 KOREA XXAPSBV.
[Update] We used RTC stub instead of SNVS for test, and found system can boot up, but run very slowly. It is almost certainly SNVS is going wrong.
Anybody have any ideas?
Thanks.
解決済! 解決策の投稿を見る。
Yes, the bit1 (SEC_CONFIG[0] )of this register is 0 which means SNVS function is disabled , so that rtc module can’t work as expect. You can blow the right fuse bit on one chip to test if it can fix the issue. Please type “imxotp blow –force 0x2A0302” in u-boot.
Sorry I miss the of the command , should be:
1.MX6Q SABRESD U-Boot > imxotp blow --force 4 0x2A0302
Thank you wery much!
On Tue, Oct 8, 2013 at 10:07 AM, Yibin Gong
SNVS RTC is OK now. Thanks!
BTW:
1. the fuse can be blew several times or only once?
2. how do i blew fuse in mass production? can we distinguish them by P/N?
1. Yes, only fuse once, so please take care of this operation.
2. In my mind, any chip for mass production supposed to be ok from FSL. I guess your chips which not fused are only sample chips? You can confirm it and get more information with your connect window.
Could you please tell me the related sections in reference manual? we need to check other fuses.
I have read Fusemap chapter, but not sure of imxotp register index; I'm not clear the meaning of '4' in "imxopt read 4".
Thanks.
Sorry, I’m not sure the fuse map information can be shared with customer. You can contact some FSL guys who connect with your company(Sales&FAEs) for more information.
Per '4' in "imxopt read 4" you mentioned, you can type “imxotp” in u-boot to get more help information.
We have tried on normal board, and got different result:
MX6Q SABRESD U-Boot > imxotp read 4
Reading fuse at index: 0x4
Fuse at (index: 0x4) value: 0x2A0302
After checking with SW guy, our latest BSP is JB4.2.2_GA.
Please help to update to new version.
Your version is very old.
I am puzzled with your info!
We have tried:
3. JB-422_100 (IMX6_JB422_100_ANDROID_SOURCE)
Which is the latest version in your website.
Do you have the updated version which is not published?
Please let me know the link, thanks.
I believe media scaning only related with PLL or PFD clock source, please check if your simulated RTC driver modified related clock source!
Hope you can solve this issue quickly!