Embedded System Switch from 2.6.19.7 to 2.6.30+ No output at all
Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Embedded System Switch from 2.6.19.7 to 2.6.30+ No output at all
Hello Guys,
I hope I'm posting in the correct forum.
I am working with a (specialized) embedded system (NEC VR4133A MIPS CPU)
It is currently running U-Boot 1.3.2 + Linux-Kernel 2.6.19.7.
I am trying to get a kernel >=2.6.30 running on the box.
I do have the source-code and config for the system running on there and i was able to build a running kernel from the sources.
I was also able to port the drivers for the board to 2.6.20.1 and successfully boot it.
Now I'm trying to port the drivers to a kernel >=2.6.30.
With some patching i managed to compile the kernel (actually I'm using 2.6.32.27 for testing) but when i try to boot it through U-Boot, I do not get any (serial-)console output at all after u-boot passes execution to the kernel.
I even put a printk in the very beginning of the setup.c for the board, still nothing.
Right now I'm becoming really frustrated as I'm running out of ideas and I've got no clue how to debug the kernel without even getting any output at all.
I am not even sure how to test if there's something wrong with the console-drivers or if the kernel doesn't boot at all.
I am also wondering if this could be caused by a too old u-boot (even though i don't really get how this could cause a kernel not booting at all when it can successfully boot an older kernel).
I hope someone can point me into the right direction.
I'm using the same config that worked with the 2.6.19 and 2.6.20 Kernels (console=/dev/ttyS1,115200n8).
I also tried ttyS0 - ttyS4 no luck.
Is there a chance the naming has changed in the newer kernel?
If so, how could i find out the new name?
Is there a way to tell the kernel to use all available consoles for output?
As far as i can see i really have no way to tell if the kernel is running because the serial-console (so far) is my only means of communication with the box. (The network-drivers also need to be ported).
Any other suggestions?
Thx,
Chaos
EDIT:
I now put in some lines in my setup.c which (should) switch on all available LEDs, this works for 2.6.19 however in 2.6.32.27 the LEDs don't turn on.
I kind of have the feeling my setup code isn't called at all...
How can i make sure it is being called? Which files need to be changed so the code can be hooked into the kernel?
Last edited by Chaosmaster; 03-24-2011 at 05:20 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.