The problem of burning linux2.6 kernel

2005tanze

I downloaded the compiled 2.6 kernel to the 2410 ram to run it, and burned it into the flash to run
Copy linux kernel from 0x00270000 to 0x30008000, size = 0x00200000 ... done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: "noinitrd root=/dev/bon/2 init=/linuxrc console=ttyS0"
MACH_TYPE = 193
NOW, Booting Linux...
Uncompressing Linux................................................ .............
.......... done, booting the kernel.
There is no more, I don't know what's going on, I hope the master will guide you! Thank you!

撒哈拉蚂蚁

console=ttyS0, 9600 Set your baud rate, your kernel has been started, but it cannot be displayed on your terminal, the baud rate does not match the problem

llljklo

I have the same problem.

leonjf

root=/dev/bon/2
~~~~~~~~~~~~~~~~~~~ Maybe the problem lies here.

Guaranteed to burn here?

BTW, how come it looks so weird. What does bon stand for?

死亡之翼狄奥

How do you say booting the kernel has started>
Makes sense on the first floor

Whatleonjfsaid is possible

首席牧师

Yes, the baud rate of your terminal and your hungry kernel do not match!
Change it! Usually 15200~~

geng565784

Generally 15200 or 38400
9600 is impossible

In addition, the kernel in the downloaded ram and the solidified kernel have some changes in the initialization place, right?

winttdown

When you compile the kernel, check to see if your cache is turned on. If it is turned on, turn it off to see if it works. It may be a problem with the design of your board.

鱼语秋雨

How to compile the kernel?
Can I interrupt debugging?

terrycl1

Mine is in Starting network...
I don’t move anymore. I used to be coded. I didn’t touch the kernel burning. I couldn’t do anything about it.