Hi,
My customer found some board boot fail and stuck at starting kernel.
The fail rate is 3% and we are going to suggest them to review the HW design to avoid timing issue.
Now, they try to skip "recalibrate iodelay" and they said it seems worked.
The following is the related f/w info:
SDK version : processor-sdk-linux-04.01.00
kernel version: Linux version 4.9.41-gc6c5f1afae
BOOT LOADER version: 2017.01-gf8adbe225f
The following is the error log:
U-Boot SPL 2017.01-
DRA722-GP ES2.0
IODELAY: De-isolation of Device IOs failed
Trying to boot from MMC2
U-Boot 2017.01-
CPU : DRA722-GP ES2.0
Model: TI AM572x EVM Rev A3
Board:
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1, OMAP SD/MMC: 2
== data ==
model : not found
serialNum : not found
aGain : not found
irCurrent : not found
yTilt : not found
cmosX : not found
cmosY : not found
yDegUp : not found
yDegDown : not found
FIXA_X : not found
FIXA_Y : not found
focus0D : not found
calDate : not found
swup : not found
rv700 environment
Writing to MMC(1)... done
Writing to redundant MMC(1)... done
Hit any key to stop autoboot: 0
MMC: no card present
switch to partitions #0, OK
mmc1(part 0) is current device
active partition:
1
==>Load Kernel
391736 bytes read in 44 ms (8.5 MiB/s)
SD/MMC found on device 1
** File not found boot.scr **
** File not found uEnv.txt **
3973576 bytes read in 110 ms (34.4 MiB/s)
101626 bytes read in 13 ms (7.5 MiB/s)
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffe4000, end 8ffffcf9 ... OK
Starting kernel ...
Please help to check:
1. Is it OK to skip "recalibrate iodelay" ?
2.They also found when if boot fail at "recalibrate iodelay" and reboot to re-execute "recalibrate iodelay" . And it will boot successfully.
Please help to comment the possible cause.
