• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 592 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/AM5728: Boot fails after kernel rebuild

Miguel Duran36
Prodigy 40 points
Part Number: AM5728

Tool/software: Linux

Hello

three days ago I had to rebuild the kernel in order to expand the ttyS ports that the board had available, the default had 6 and I needed the 10.  I did the rebuild in the board (was forced to do it this way, long story), it  took 2 whole days with the board turned on, I was obviously  worried that the AM5728 would burn out so I put a 20 inch fan beside the board. The rebuild ended and I proceed to install it, I tried to reboot thinking it was necessary and thats when things went wrong, the serial debug started outputing garpage characters and did not show the normal power off sequence that normaly does, it finally shut down and when it tried to reboot the board turned off again, now for some reason this happens often, I know through this forum that this is caused  the DEV_ON bit in the PMIC hasn't been set, as I said this happens often so I managed to find a "trick" in order to bypass it without the J5 jumper; if I turned on the board without the SD and after 2 seconds I inserted it the image booted normally, this time I tried to do that but I was surprised that it didn't work, and the next time either. I removed the  SD card turned the board on expecting to see this (example below)

U-Boot SPL 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09) 

DRA752-GP ES2.0
Trying to boot from MMC1
** Unable to use mmc 0:1 for loading the env **
Using default environment
but I was suprised to find that in the serial debug just the next symbol appeared

ø

clearly something was wrong and it after 7 seconds it turned off, that was also a surprise since it normally stayed on with serial debug printing a message of invalid partition and blocking itself there. Now no matter what I do the board doesn´t boot, the serial debug doesn't show anything more thant ø and even when the J5 jumper is on the board doesn't boot.

Did the  AM5728 burned? I tried checking the sd in which the new kernel image was installed through another x15 board and it works fine the serial ports are now from ttyS0 to ttyS9 which means the problem is on my board. The processor still heats up so I take it as a signed that is not burned.

What I could had messed? as I understan the uboot is in the SD and I did not move nothing in eMMC so unless the installing of the kernel somehow managed to corrupt  the eMMC then I can't explain what is happening.

Regards

M