Need help ragarding MPC8360 Kernel bootup failure

Need help ragarding MPC8360 Kernel bootup failure

[sudheer]

Hello all,

I need help regarding the bootup of linux on MPC8360 MDS Board.

After doing tftp the uImage from u-boot, with the bootm command  the 
kernel gets uncompressed and stops there.
The serial output from kernel could  not be seen.

Source being used:
 uboot - U-Boot-1.1.3
 linux - Linux-2.6.11 supporting mpc8360epb.
board - MPC8360 MDS

The dump is below:

U-Boot 1.1.3 (ppc83xx-20050315-dev) (Dec 14 2005 - 09:37:59) MPC83XX

Clock configuration:
  Coherent System Bus:  264 MHz
  Core:                 528 MHz
  QE:                   396 MHz
  Local Bus Controller: 264 MHz
  Local Bus:             66 MHz
  DDR:                  264 MHz
  DDR Secondary:        264 MHz
  I2C:                  264 MHz
CPU: MPC83xx, Rev: 20 at 528 MHz
Board: Freescale MPC8360EPB
I2C:   ready
DRAM:
   SDRAM on Local Bus: 64 MB
   DDR RAM: 256 MB
FLASH: 16 MB
In:    serial
Out:   serial
Err:   serial
Net:   FSL GETH0
Hit any key to stop autoboot:  0
=> printenv
bootcmd=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrramboot=setenv
bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp
$ramdiskaddr $ramdiskfile;tftp $loarnfsboot=setenv bootargs root=/dev/nfs
rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrbootdelay=6
baudrate=115200
loads_echo=1
ethaddr=00:04:9f:11:22:33
eth1addr=00:E0:0C:00:7D:01
hostname=unknown
loadaddr=200000
netdev=eth0
consoledev=ttyS0
ramdiskaddr=400000
ramdiskfile=ramfs.83xx
ethact=FSL GETH0
filesize=2d030a
fileaddr=20000
gatewayip=192.168.3.1
netmask=255.255.255.0
serverip=192.168.3.81
bootfile=/tftpboot/vmlinux.gz
ipaddr=192.168.3.253
stdin=serial
stdout=serial
stderr=serial

Environment size: 1005/8188 bytes
=> setenv bootargs console=ttyS1 root=/dev/ram
=> tftp 200000 uImage_test
Auto negotiating done
switching to rgmii 100
duplexity: full
mac speed set to: 100
Using FSL GETH0 device
TFTP from server 192.168.3.81; our IP address is 192.168.3.253
Filename 'uImage_test'.
Load address: 0x200000
Loading: #################################################################
         #################################################################
         #################################################################
         #######
done
Bytes transferred = 1033098 (fc38a hex)
=> bootm 200000
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.11.12
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1033034 Bytes = 1008.8 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

 CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline

------------
After Uncompressing kernel, nothing comes onto the minicom.
I have tried the console env in bootargs to ttyS0,  ttyS1, ttyCPM0, ttyCPM1, ttyUCC0. But could not succeed.

Anyone Please help me in this regard.

Thanks & Regards
Sudheer

Re: Need help ragarding MPC8360 Kernel bootup failure

[David Hawkins]

>  CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline

Your minicom is set to 115200, so your U-Boot must be using that,
but you'll need to tell Linux too, try:

console=ttyS0,115200

Dave

Need help on ftp and telnet in my Ramdisk

[Denny]

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

Hi,
 
   1. I copied the ftp and telnet commands to my /bin, and the needed library is also copied to my /lib, but they still don't work so far, can anybody tell me why, thanks!
 
 
logs:
...
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k init
init started:  BusyBox v1.1.3 (2006.06.23-09:32+0000) multi-call binary
Bad inittab entry: :reth0: link is up, 100 FDX
Starting pid 23, console /dev/ttyS1: '/bin/application'
Starting pid 24, console /dev/ttyS1: '/bin/bash'
### Application running ...
bash-3.00# ]
bash: ]: command not found
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# ftp 192.168.65.143
ftp: ftp/tcp: unknown service
bash-3.00# telnet 192.168.65.143
telnet: telnet: bad port
Starting pid 29, console /dev/ttyS1: '/bin/application'
Starting pid 30, console /dev/ttyS1: '/bin/bash'
### Application running ...
Starting pid 33, console /dev/ttyS1: '/bin/bash'
Starting pid 32, console /dev/ttyS1: '/bin/application'
### Application running ...
bash-3.00# 
 
Thanks!
- Denny

[-- Attachment #2: Type: text/html, Size: 1803 bytes --]

Need help on adding a command to my ramdi sk

[Denny]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

Hi, 
 
   Since there is no "ldd" command in busybox1.1.3, so I copied it from ELDK4.0 to my bin,
but it didn't work, can anybody tell me how to add a new command to my ramdisk ?
 
bash-3.00# ldd /bin/ftp
sh: applet not found
bash-3.00# 
 
 
- Denny
 
 
 

[-- Attachment #2: Type: text/html, Size: 876 bytes --]

Need help on adding a command to my ramdi sk

[Denny]

[-- Attachment #1: Type: text/plain, Size: 256 bytes --]

 
 

Hi, 
 
   Since there is no "ldd" command in busybox1.1.3, so I copied it from ELDK4.0 to my bin,
but it didn't work, can anybody tell me how to add a new command to my ramdisk ?
 
bash-3.00# ldd /bin/ftp
sh: applet not found
bash-3.00# 
 
 
- Denny
 

[-- Attachment #2: Type: text/html, Size: 889 bytes --]

Need help on ftp and telnet in my Ramdisk

[Denny]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

 
 

Hi,
 
   1. I copied the ftp and telnet commands to my /bin, and the needed library is also copied to my /lib, but they still don't work so far, can anybody tell me why, thanks!
 
 
logs:
...
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k init
init started:  BusyBox v1.1.3 (2006.06.23-09:32+0000) multi-call binary
Bad inittab entry: :reth0: link is up, 100 FDX
Starting pid 23, console /dev/ttyS1: '/bin/application'
Starting pid 24, console /dev/ttyS1: '/bin/bash'
### Application running ...
bash-3.00# ]
bash: ]: command not found
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# 
bash-3.00# ftp 192.168.65.143
ftp: ftp/tcp: unknown service
bash-3.00# telnet 192.168.65.143
telnet: telnet: bad port
Starting pid 29, console /dev/ttyS1: '/bin/application'
Starting pid 30, console /dev/ttyS1: '/bin/bash'
### Application running ...
Starting pid 33, console /dev/ttyS1: '/bin/bash'
Starting pid 32, console /dev/ttyS1: '/bin/application'
### Application running ...
bash-3.00# 
 
Thanks!
- Denny
 

[-- Attachment #2: Type: text/html, Size: 1873 bytes --]

Re: Need help on ftp and telnet in my Ramdisk

[Lee Revell]

On Tue, 2006-06-27 at 09:33 +0800, Denny wrote:
> bash-3.00# ftp 192.168.65.143
> ftp: ftp/tcp: unknown service
> bash-3.00# telnet 192.168.65.143
> telnet: telnet: bad port 

These sound like /etc/services is missing?

Consider adding strace to your build, it saves a LOT of guessing.

Lee

Re: Re: Need help on ftp and telnet in my Ramdisk

[Denny]

[-- Attachment #1: Type: text/plain, Size: 72 bytes --]

Yes, it is the root cause, thanks Lee!
 
Thanks & Regards!
- Denny
 
 
 

[-- Attachment #2: Type: text/html, Size: 611 bytes --]

Re: Need help ragarding MPC8360 Kernel bootup failure - got solved

[sudheer]

Hello All,

I got this problem sorted out.
I have changed the bootargs at u-boot to
setenv bootargs root=/dev/ram rw console=uart,io,0xfe004500
Now i could boot the linux and login.

Thanks & Regards
Sudheer



sudheer wrote:

>Hello all,
>
>I need help regarding the bootup of linux on MPC8360 MDS Board.
>
>After doing tftp the uImage from u-boot, with the bootm command  the 
>kernel gets uncompressed and stops there.
>The serial output from kernel could  not be seen.
>
>Source being used:
> uboot - U-Boot-1.1.3
> linux - Linux-2.6.11 supporting mpc8360epb.
>board - MPC8360 MDS
>
>The dump is below:
>
>U-Boot 1.1.3 (ppc83xx-20050315-dev) (Dec 14 2005 - 09:37:59) MPC83XX
>
>Clock configuration:
>  Coherent System Bus:  264 MHz
>  Core:                 528 MHz
>  QE:                   396 MHz
>  Local Bus Controller: 264 MHz
>  Local Bus:             66 MHz
>  DDR:                  264 MHz
>  DDR Secondary:        264 MHz
>  I2C:                  264 MHz
>CPU: MPC83xx, Rev: 20 at 528 MHz
>Board: Freescale MPC8360EPB
>I2C:   ready
>DRAM:
>   SDRAM on Local Bus: 64 MB
>   DDR RAM: 256 MB
>FLASH: 16 MB
>In:    serial
>Out:   serial
>Err:   serial
>Net:   FSL GETH0
>Hit any key to stop autoboot:  0
>=> printenv
>bootcmd=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
>ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrramboot=setenv
>bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp
>$ramdiskaddr $ramdiskfile;tftp $loarnfsboot=setenv bootargs root=/dev/nfs
>rw nfsroot=$serverip:$rootpath
>ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netrbootdelay=6
>baudrate=115200
>loads_echo=1
>ethaddr=00:04:9f:11:22:33
>eth1addr=00:E0:0C:00:7D:01
>hostname=unknown
>loadaddr=200000
>netdev=eth0
>consoledev=ttyS0
>ramdiskaddr=400000
>ramdiskfile=ramfs.83xx
>ethact=FSL GETH0
>filesize=2d030a
>fileaddr=20000
>gatewayip=192.168.3.1
>netmask=255.255.255.0
>serverip=192.168.3.81
>bootfile=/tftpboot/vmlinux.gz
>ipaddr=192.168.3.253
>stdin=serial
>stdout=serial
>stderr=serial
>
>Environment size: 1005/8188 bytes
>=> setenv bootargs console=ttyS1 root=/dev/ram
>=> tftp 200000 uImage_test
>Auto negotiating done
>switching to rgmii 100
>duplexity: full
>mac speed set to: 100
>Using FSL GETH0 device
>TFTP from server 192.168.3.81; our IP address is 192.168.3.253
>Filename 'uImage_test'.
>Load address: 0x200000
>Loading: #################################################################
>         #################################################################
>         #################################################################
>         #######
>done
>Bytes transferred = 1033098 (fc38a hex)
>=> bootm 200000
>## Booting image at 00200000 ...
>   Image Name:   Linux-2.6.11.12
>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>   Data Size:    1033034 Bytes = 1008.8 kB
>   Load Address: 00000000
>   Entry Point:  00000000
>   Verifying Checksum ... OK
>   Uncompressing Kernel Image ... OK
>
> CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline
>
>------------
>After Uncompressing kernel, nothing comes onto the minicom.
>I have tried the console env in bootargs to ttyS0,  ttyS1, ttyCPM0, ttyCPM1, ttyUCC0. But could not succeed.
>
>Anyone Please help me in this regard.
>
>Thanks & Regards
>Sudheer
>
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>  
>

Can't "up" my eth0

[Denny]

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

Hi,
 
   I am now succefully to bring up my kernel on my PPC440GP custom board, but I failed to up my eth0, the eth0 is link down after the kernel is booting up.
   
   There is no effect, after the command ifconfig eth0 up.
   
   Can anyone tell me what may be the root case, and what reason may cause the eth0 unstable, thanks a lot.
 
    below is my log:
PPC 4xx OCP EMAC driver, version 3.53
mal0: initialized, 4 TX channels, 2 RX channels
zmii0: bridge in RMII mode
eth0: emac0, MAC 00:01:02:54:12:47
eth0: found Generic MII PHY (0x01)
emac1: can't find PHY!
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k init
Starting pid 22, console /dev/teth0: link is down
Starting pid 27, console /dev/ttyS1: '/bin/bash'
Starting pid 26, console /dev/ttyS1: '/bin/application'
### Application running ...
Starting pid 29, console /dev/ttyS1: '/bin/application'
 
Thanks in advance!
- Denny
 
 
 

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]