This looks correct - the important bit is that console=ttyO2
Diagnosing why this doesn't come up may be a bit trickier. One thing
that you
can do is to look at the kernel messages (which are not being
printed!). Thankfully,
those are kept buffered in memory and you should be able to print them
manually.
Give these steps a go:
* Boot as you have been, letting it hang after starting the kernel
* Press the RESET button on the PandaBoard
* Break into U-Boot
* Dump the kernel messages via:
U-Boot> md LOG_BUF_ADDRESS
This will display 256 bytes at LOG_BUF_ADDRESS. If you just press
return, you'll
get to see the next 256 bytes, etc. Keep doing this until the
messages stop...
To find the LOG_BUF_ADDRESS, search for __log_buf in the System.map
which was created
when you built your kernel. This will be in your Yocto build tree
.../tmp/work/pandaboard*/linux*/git
(I think - I don't have a build for this machine handy) You'll see
something like this:
$ grep __log_buf tmp/work/panda*/linux*/git/System.map
c06d66e9 b __log_buf
That's a virtual address which corresponds to 0x806d66e9 in physical
RAM. Truncate
the address to a longword value, i.e. 0x806d66e8 - that's LOG_BUF_ADDRESS
See what you get, it may provide a clue where the kernel is crashing.
Everything went ok, except the board doesn't reset when I press the
reset button, or at least I can't see that in the serial console, it
stays stuck at line "booting kernel..."
Radu
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
