Hi All,
I use OMAP-L138 in our custom board, in the past , we used crystal with 24 MHz like the EVM and the boot sequence was normal like the EVM as :
1 - UBL
2 - UBoot
3- Linux kernal
now we have an issue which is, we move to another HW sample with input crystal 27 MHz , so i started to change the UBL source code to
change the PLL0 and PLL1 settings and then use AISGen tool also i have made the necessary changes in UBoot then refalshing the both UBL +UBoot
I found that the UBL debug messages not appeared on the screen instead , i found output like this ���������������������������������������������
but the strange thing is that , UBoot boots normally but when i try to load linux kernal into memory the Uboot produce the following :
## Booting kernel from Legacy Image at c0700000 ...
Image Name: Linux-2.6.33-rc4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1800268 Bytes = 1.7 MB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
kernel loaded at 0xc0008000, end = 0xc01bf84c
Starting kernel ...
but the kernal not starting !!
so I remove UBL and instead I use UBoot and sign it using the AISGen , trying to re-flash (SPI flash) and boot so it boots successfully
however the same issue happened which is the linux kernal cannot started and UBoot produce the same prints as mentioned.
What does that mean ? .. Is there a specific changes in the linux kernal itself in order to start execute ?
Also, As I can boot using only UBoot , there is no need to use UBL anymore or may be the problem in the kernal related to the problem in using UBoot ?
Thanks in advance for any suggestions.