• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2
Author Topic: booting image...  (Read 4486 times)
Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« on: August 24, 2009, 04:41:49 PM »

Hey!

after loading the kernel image via tftp into the memory and booting it I only get confusing output like this:

Code:
Marvell>> tftpboot
Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.7
Filename 'uImage'.
Load address: 0x2000000
Loading: ####################################################################
         [...]
         ####
done
Bytes transferred = 2014240 (1ebc20 hex)
Marvell>> bootm 0x2000000

## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18-6plug
   Created:      2009-03-11  18:32:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2014176 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
If)Iyq&'N3
               '8ة9ް))
                           1a9)qyI.X )IyqFN/a@;.3@jLy
                                                                  q6&6
                                                                         "0`) Vrn+V )f&V6  $^II i˯)+XyV6vv      Iq)(y)yqi)i/9VI(/    I9             i))6)iȰiyyaIӨPP I  a)!a 6A)I)      YiȰPЩ&(A)vFؾ)a^^ض!IIN3@ɡ)W5arޱȰPЩ( A)vFX>)a^^X6IIN3ɡ)W5arޱi0Pa.7ѡ}        a       9)N0#)q)a6WWW1W5X^W   'a
                          V&/3        W/3v!
/    9)
fX0`^/^&yyy/3aY^/'Q'^#'Q'^+&'Q'^+&&VVNi&Vz1E$p3
                                                                               V/4W)(    AF      a)V/޶N0h!)&X>)Iyqa)XW/^ ȩii.))q6XW^#     a)V/^ѧi!)'f&FX)Iqy!)i6X^#     a)V/^3o3!)'
    6&X)I)NH f+fP `H `H0yV&P y aȰ'iyӧi+F6 1    Ia     a)N73XX&&     apȶII)I0)yYfnE!I    aI)!iȰVIq)ѦII    IIq9q)aIqI/1ɡ)i/ǩɡѲ59I!)Iq96)y!        ׮9)6IaIiȰP   IIV@qɡI a)!^ )q!   Ȱ'ߩqi6A)W@#   a)V/^6ӧf) )Iq9I)&/.6۱)qY(+&.))!yyEfЩ1     )i0YQQQQQQQQ'!j (V0@X)^)&Vf Ħ  +(V@X)^)&Vf Ħ   +(V3@.        )iȰV&        +i( ^6   a)i0( 'V'@X)Vp^)&
[...]

I tried the newest file from the web as well as the one shiped with the device.

Any ideas?

Thanks!
Pete
Logged

Deviant0ne
Newbie
*

Karma: 0
Posts: 30



View Profile
« Reply #1 on: August 25, 2009, 04:00:38 PM »

I was getting ouput like that when my baud rate was incorrect... I am not sure why you would see normal output then the garbage, though...
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #2 on: August 25, 2009, 10:49:07 PM »

I think you've pegged it, DeviantOne.  The  normal output is the Uboot's.  The corrupted output is the kernel's.

I'd suspect that either the Uboot bootargs_console environment variable is missing or corrupted.  It should be something like:

Code:
bootargs_console=console=ttyS0,115200
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #3 on: August 26, 2009, 10:03:40 AM »

Thanks for your suggestions, but unfortunately the problem still exists.
Maybe the env variables help? although besides the bootargs and bootargs _console variables everything should be set to default (just used resetenv)

Pete

Code:

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootcmd=tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethaddr=00:50:43:a4:0c:38
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
ipaddr=192.168.2.7
serverip=192.168.2.1
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes

« Last Edit: August 27, 2009, 02:43:09 PM by Pete » Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #4 on: August 26, 2009, 10:06:33 AM »

oh, and the ipaddr and serverip is modified, too.
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #5 on: August 31, 2009, 01:26:16 PM »

No more ideas?  Sad
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #6 on: August 31, 2009, 01:38:22 PM »

Sorry, Pete, I've never used tftpboot.  From you later post, it appears your baud rate is being set correctly.

Does the Plug eventually come up, even though it is inaccessible from the console.  (Can you ssh into it after a while?)

If so, log in as root and tell us what the output of "stty -a </dev/ttyS0" is.
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #7 on: September 02, 2009, 11:03:59 AM »

It looks like the plug boots. After a couple of seconds Im also able to ping it. But when I try to establish a ssh connection, I only get a network timeout. Is ssh enabled in the default kernel?
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #8 on: September 02, 2009, 01:03:56 PM »

ssh should be set up by default (although if you are booting tftp, I suppose it depends on the media from which you are booting).  I know nothing about tftp boots, but FWIW, here's some general things I would do:

1.  Can you telnet to port 22 of the Plug?

2.  If you type something on the console, does it produce any sort of response (more gibberish)?

3.  If (2) produces output, I'd try changing the baud rate on your terminal program in order to try to find one that works.

Good luck.
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #9 on: September 03, 2009, 11:32:59 AM »

Hey restamp,

thanks for all your support so far!!! really appreciate it!

the latest progress:
cant connect via telnet and there is not response at all on the console after booting. I think the plug is broken... doing a resetenv and loading a news kernel should work on any plug, right? or is there an even more basic way to start all over than the kernel? Maybe flashing uboot as well? (is this possible without a working kernel?)
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #10 on: September 03, 2009, 01:15:41 PM »

So the Plug doesn't even come up on its internal NAND uImge and root fs anymore?  (I was going on the presumption you were only having trouble with tftp.)  If you know of no way to boot the Plug anymore, I'd run the alpha-6 installer and see if that restores things to some semblance of sanity.

Good luck.
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #11 on: September 05, 2009, 04:33:42 AM »

New development ... in a way...
I ran the alpha-6 install and it looks like it worked properly (no error messages). But the gibberish during the kernel boot is still there :-/

however new is that after the normal booting (no tftp) seems to be done (no new line output) the console reacts to typing on the keyboard (more gibberish). The downside on the other hand is that I cant ping the plug anymore => so no telnet connection (although tftp still works)

Now my conclusion is that because the problem still exists after the alpha-6 install the plug might be broken or the problem is at the host... although I doubt that it is the host (can see the uboot output and pinging the plug doesnt dependent on the host)

Any other ideas? Im thankful for any suggestions

Latest env:
Code:

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions); bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
filesize=1CAE6D
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
ipaddr=192.168.2.1
serverip=192.168.2.1
ethaddr=00:50:43:01:D5:C0
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes


(just changed ipaddr and serverip)
Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #12 on: September 15, 2009, 04:40:07 AM »

out of ideas?
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #13 on: September 15, 2009, 07:04:08 PM »

Basically, yes, I'm out of ideas.  If I understand you correctly, you're say that after alpha-6, you get gibberish from the kernel, but it responds to input on the console with more gibberish.  It surely seems like a mismatched baud rate on the serial console port to me.  I suppose I'd play with setting different baud rates on your console program and seeing if you can find one that works.  If you do, you might be able to make mores sense out of what's happening.

Good luck.
« Last Edit: September 15, 2009, 07:11:16 PM by restamp » Logged

Pete
Newbie
*

Karma: 0
Posts: 11


View Profile
« Reply #14 on: September 26, 2009, 08:06:59 AM »

Had no luck with the baud rate...

I also tried installing the filesystem on a usb stick... but same result. At another forum somebody suggested that the internal flash could be broken. What do you think about that?

Although Im now 5 days past the 30-days warranty, Ill try to get a replacement Thats really my last hope :-/

Thanks again restamp for your help!!
Logged

Pages: [1] 2
Print
Jump to: