Results 1 to 8 of 8
Thread: Booting linux in PowerPC board
|
Enjoy an ad free experience by logging in. Not a member yet? Register.
|
|
-
11-15-2012 #1
- Join Date
- Nov 2012
- Posts
- 5
Booting linux in PowerPC board
I have a PowerPC COTS board from Embedded Planet.
Using the manual supplied with the board I was able to configure the uboot parameters and load the kernel , ramdisk image and DTB into the flash.
But after booting it with bootargs as root=/dev/ram rw console=ttyS0,115200 nothing appears in my teraterm after uboot messages of loading the kernel,ramdisk and DTB.
Can someone guide me in probing the issue?
-
11-15-2012 #2
- Join Date
- May 2011
- Posts
- 4,353
Hello and welcome!
Originally Posted by guru1132
- So you are saying that text DOES appear in your teraterm (via serial cable) up until a certain point, then nothing more appears?
- Has any login program (e.g, mingetty) been configured on the embedded system to listen on that device? (often defined in /etc/inittab or other rc.init startup file)
- Is there a VGA (or other display) port on the device to which you can connect a monitor to see if there a console is attached there?
-
11-16-2012 #3
- Join Date
- Nov 2012
- Posts
- 5
yes. You are correct.I read somewhere that TEXT is the last Uboot message.I have copied the text below.Am I correct?
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at ffc00000 ...
Image Name: Linux-2.6.36-rc2-ep3.01
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 2038641 Bytes = 1.9 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at f8000000 ...
Image Name: Linux RAMdisk Image
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 4200214 Bytes = 4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at fff00000
Booting using the fdt blob at 0xfff00000
Uncompressing Kernel Image ... OK
Loading Ramdisk to 2fbfe000, end 2ffff716 ... OK
Loading Device Tree to 00ffa000, end 00fff0f6 ... OK I checked that .No getty program is configured.But init is configured to open busybox shell. Does'nt the kernel messages be printed before getty?
Also I tried telnet login by puTTY. I think it doesnot require any getty program.But my puTTY closes after few seconds.
No .there is not any Display port.
Thank YouLast edited by guru1132; 11-16-2012 at 11:21 AM.
-
11-17-2012 #4
- Join Date
- May 2011
- Posts
- 4,353
I'm not sure I understand your question.
No getty program is configured.But init is configured to open busybox shell.
Does'nt the kernel messages be printed before getty?
Redirection over serial is tricky, there are two or three parts. The very first part is the BIOS: some BIOSes allow redirection of the POST over serial port. Forget about that for now. Next comes the boot-loader (grub, lilo, etc.), you can direct that (and thus the kernel boot portion) over a serial device. Lastly comes serial logins to the Linux system, once it is up. This is achieved using one of those getty programs listening on your serial device (ttyS0, ttyUSB0, etc.).
Also I tried telnet login by puTTY. I think it doesnot require any getty program.But my puTTY closes after few seconds.
Code:nmap -n <ip_of_embedded_device>
-
11-20-2012 #5
- Join Date
- Nov 2012
- Posts
- 5
hi
The reason for the issue has been found out.
I have used a 36bit memory map uboot with a 32 bit linux BSP. I have asked the vendor for a 36 bit BSP.
Hope I can boot with the new BSP.
Thanks for your support and guidance.
-
11-20-2012 #6
- Join Date
- May 2011
- Posts
- 4,353
Wouldn't it be easier to use a 32bit memory map uboot and a 32bit linux BSP? Anyway, glad you found the problem and good luck!
If you have more questions/issues regarding this topic, please post them. Otherwise, you can mark this thread as Solved using the Thread Tools at the top of the page.
-
12-13-2012 #7
- Join Date
- Nov 2012
- Posts
- 5
-
12-13-2012 #8
- Join Date
- May 2011
- Posts
- 4,353