i am seeing a weird behaviour during power cycle test of imx28 board,
in normal room temperature, the power cycle test passed.
on every power up, bootletlog shows this
HTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLFLC
>> TS-BOOTROM - built Dec 22 2016 12:46:40
>> Copyright (c) 2013, Technologic Systems
LLLCFeb 9 201205:04:46
FRAC 0x92925552
memory type is DDR2
Wait for ddr ready 1power 0x00820710
Frac 0x92925552
start change cpu freq
hbus 0x00000003
cpu 0x00010001
start test memory accress
ddr2 0x40000000
finish simple test
LLLLLLLFLCLLJUncompressing Linux... done, booting the kernel.
but at hot chamber power cycle test, at 60 C, the unit freese, not even the kernel loading start,
HTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLFLC
>> TS-BOOTROM - built Dec 22 2016 12:46:40
>> Copyright (c) 2013, Technologic Systems
LLLCFeb 9 201205:04:46
FRAC 0x92925552
memory type is DDR2
Wait for ddr ready 1power 0x00820710
Frac 0x92925552
start change cpu freq
hbus 0x00000003
cpu 0x00010001
start test memory accress
ddr2 0x40000000
finish simple test
LLLLLLLFLCLLJ
the unit is not reboot, its freeze
Any suggestion would be helpful
Further update , things are working normal if I enable, kernel print message. Tested over 300 power cycle test, all were passed
Earlier on freeze failure condition, the kernel print are disabled by passing kernel command argument(quite, konsole=0) for fast boot up unit imx28.
Hello,
What Linux BSP is used in the case?
Regards,
Yuri.
we are using 2.6.35.XX
Is it possible to check Yocto release?
https://www.nxp.com/docs/en/application-note/AN12024.pdf
~Yuri.
Thanks Yuri,
We build a OS using LTIB, we did lot of patches according to our applications requirement, so this time I feel it's not recommend to migrate yocto, may be yes downline we will have too..
I don't know how to figure out freeze in boot loader where ivt-imx28-boot.sb running DDR ram or nand flash where our kernel image is available.
Hello,
It is hard to say what occurs, when kernel print is disabled.
Try JTAG debugging with kernel.
Regards,
Yuri.
Its not even coming only uncompressed the image from nand. after that then kernel printf will come on terminal.
Hello,
When enabled, the ROM will output a single character on the debug UART for every boot command it executes,
with no whitespace between characters. See the table below for the characters output for each command.
Char Command Notes
J Jump After a jump, the application that was jumped to can re-use the memory in on-chip RAM
(which ROM was using), since ROM will not expect this application to return.
This is the key difference between a Call and a Jump, the ROM expects an application,
that was called to return.
C Call ROM expects the application to return.
L Load
F Fill
H Header
T Tag Tag was encountered while parsing
In Your case the problem may be concerned with memory integrity.
Please check memory with a comprehensive test.
Have a great day,
Yuri
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
Hi Yuri
Thanks
Could you please elaborate ?