Linux/PROCESSOR-SDK-AM335X: No more output is seen on the console after "Starting Kernel..."

Hi Vishvajeet,

Could you boot with prebuilt images and test the console output.

BR
Tsvetolin Shulev

Hi Cvetolin,
Thanks for your reply,
I just want to know where I can get prebuilt images, actually I tested device with older kernel i.e.linux v3.2 for this console working fine.but for linux v4.4.41 its console gets hang after Starting kernel print.

Regards,
Vishvajeet

Hi Cvetolin,
I tested with the prebuit binary images on EVM-SK board but it gives the same result.
the kernel hangs at following location:

Starting kernel...

Regards,
Vishvajeet.

Hi Cvetolin,
I enabled kernel printk,after this it shows following message on serial terminal.

Starting kernel ...


Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).

Available machine support:

ID (hex) NAME
ffffffff Generic DT based system
ffffffff Generic AM33XX (Flattened Device Tree)

Please check your kernel config and/or bootloader.

Regards,
Vishvajeet

Vishvajeet,

The error message which you observe is due to missing machine name or your machine name no presents in the list of supported machines. See "Error: unrecognized/unsupported machine ID" message in ../linux/arch/arm/kernel/atags_parse.c file.
I suggest you the following tutorial about AM335x Starter Kit ID Memory Programming at:
processors.wiki.ti.com/.../AM335x_Starter_Kit_ID_Memory_Programming
which should help to add board ID information in the EEPROM

BR
Tsvetolin Shulev

Hi Cvetolin,
Thanks for valuable reply,I read given link by you,I have some confusions regarding EEPROM Corruption. beacuse linux v3.2 kernel uImage is properly booting on same board, but if I shifted to upgraded kernel versions(i.e.linux v4.4.41) then this problem occurs. I dont know exactly but if EEPROM gets corrupted then same problem should occur for linux v3.2.
also want to know is their any booting procedure gets changed because I am only using uImage for booting kernel. I am using tftp boot and using following commands in uboot.

set serverip xx.xx.xx.xx (host machine ip addredd)
set ipaddr xx.xx.xx.xx (device ip address)

tftp 0x80100000 uImage (load uImage at 0x80100000)
bootm 0x80100000 (boot from given memory location)

I booted linux kernel v3.2 uImage using above commands,it booted successfully. but if I use kernel v4.2 uImage, it doesnt boot.
it hangs at start kernel. Also I want to know is fdt is playing any role in it.

Regards,
Vishvajeet

I got the same issue, what u got

bootz

Starting kernel ...


Error: unrecognized/unsupported machine ID (r1 = 0x0000157d).

Available machine support:

ID (hex) NAME
ffffffff Generic DT based system
ffffffff Generic DRA72X (Flattened Device Tree)
ffffffff Generic DRA74X (Flattened Device Tree)
ffffffff Generic AM43 (Flattened Device Tree)

I was unable to upload my dtb file. Only option is via SDcard. Did u tried booting via SDcard. If yes, please tell how it worked via SDcard

Hello Madhu Sundar,
I am booting from SD card, I went through same scenario as you, I just want to know uEnv.txt content. I want to verify your boot arguments and its boot command content.

Best Regards,
Vishvajeet

4743.uEnv_uboot.txt

Please find the attached uEnv text file. Thanks for your response

Now i was able to upload both kernel and dtb via xmodem. But still the issues are same

Press SPACE to abort autoboot in 2 seconds
=> bootz 0x80200000 - 0x88000000
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
reserving fdt memory region: addr=88000000 size=9000
Using Device Tree in place at 88000000, end 8800bfff

Starting kernel ...