• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Bricked Sheevaplug (fixed)  (Read 11698 times)
graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« on: November 10, 2010, 03:54:21 AM »

Tried updating Uboot, followed howto, after reset, nothing.

Minicom output:
_________________________________________________________________________________________

Welcome to minicom 2.4

OPTIONS: I18n                                                                
Compiled on Jun  3 2010, 13:48:00.                                          
Port /dev/ttyUSB1                                                            
                                                                            
Press CTRL-A Z for help o+-----------------------------+                    
                         |                             |                    
                         |  Cannot open /dev/ttyUSB1!  |                    
                         |                             |                    
                         +-----------------------------+
__________________________________________________________________________________________
(Putty stays dead as well, just a green cursor)


Dmesg output:
__________________________________________________________________________________________


[    9.740322] usbcore: registered new interface driver usbserial
[    9.740341] USB Serial support registered for generic
[    9.740377] usbcore: registered new interface driver usbserial_generic
[    9.740380] usbserial: USB Serial Driver core
[    9.756848] USB Serial support registered for FTDI USB Serial Device
[    9.756918] usb 2-1: Ignoring serial port reserved for JTAG
[    9.756958] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[    9.757036] usb 2-1: Detected FT2232C
[    9.757039] usb 2-1: Number of endpoints 2
[    9.757042] usb 2-1: Endpoint 1 MaxPacketSize 64
[    9.757044] usb 2-1: Endpoint 2 MaxPacketSize 64
[    9.757047] usb 2-1: Setting MaxPacketSize 64
[    9.887316] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[    9.887365] usbcore: registered new interface driver ftdi_sio
[    9.887368] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[    9.923754] EDAC MC: Ver: 2.1.0 Oct 16 2010
[   10.020979] EDAC amd64_edac:  Ver: 3.3.0 Oct 16 2010
[   10.069211] EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (0000:00:18.3).
[   10.069219] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
[   10.069221]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
[   10.069223]  (Note that use of the override may cause unknown side effects.)
[   10.069250] amd64_edac: probe of 0000:00:18.2 failed with error -22
[   10.121350] type=1400 audit(1289383442.053:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient3" pid=590 comm="apparmor_parser"
[   10.121696] type=1400 audit(1289383442.053:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=590 comm="apparmor_parser"
[   10.121891] type=1400 audit(1289383442.053:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=590 comm="apparmor_parser"
[   10.238072] ppdev: user-space parallel port driver
[   10.483832] nvidia: module license 'NVIDIA' taints kernel.
[   10.483838] Disabling lock debugging due to kernel taint
[   11.226728] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input3
[   11.320100]   alloc irq_desc for 17 on node 0
[   11.320104]   alloc kstat_irqs on node 0
[   11.320115] ATI IXP AC97 controller 0000:00:14.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[   11.627601] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   11.634475] type=1400 audit(1289383443.563:5): apparmor="STATUS" operation="profile_load" name="/usr/share/gdm/guest-session/Xsession" pid=828 comm="apparmor_parser"
[   11.642752] type=1400 audit(1289383443.573:6): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient3" pid=830 comm="apparmor_parser"
[   11.643104] type=1400 audit(1289383443.573:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=830 comm="apparmor_parser"
[   11.643302] type=1400 audit(1289383443.573:Cool: apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=830 comm="apparmor_parser"
[   11.664869] type=1400 audit(1289383443.593:9): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince" pid=833 comm="apparmor_parser"
[   11.684528] type=1400 audit(1289383443.613:10): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer" pid=833 comm="apparmor_parser"
[   11.702662] type=1400 audit(1289383443.633:11): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-thumbnailer" pid=833 comm="apparmor_parser"
[   12.100749]   alloc irq_desc for 18 on node 0
[   12.100754]   alloc kstat_irqs on node 0
[   12.100765] nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   12.100775] nvidia 0000:01:00.0: setting latency timer to 64
[   12.100781] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   12.101085] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  260.19.06  Mon Sep 13 04:29:19 PDT 2010
[   14.660030] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
[   19.202961] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
[   22.360030] eth0: no IPv6 routers present
[  209.127222] usb 2-1: USB disconnect, address 2
[  209.127438] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[  209.127456] ftdi_sio 2-1:1.1: device disconnected
[  212.070048] usb 2-1: new full speed USB device using ohci_hcd and address 3
[  212.310568] usb 2-1: Ignoring serial port reserved for JTAG
[  212.315594] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[  212.315632] usb 2-1: Detected FT2232C
[  212.315635] usb 2-1: Number of endpoints 2
[  212.315638] usb 2-1: Endpoint 1 MaxPacketSize 64
[  212.315641] usb 2-1: Endpoint 2 MaxPacketSize 64
[  212.315643] usb 2-1: Setting MaxPacketSize 64
[  212.317924] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[  300.455551] usb 2-1: USB disconnect, address 3
[  300.455821] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[  300.455833] ftdi_sio 2-1:1.1: device disconnected
[  312.490039] usb 2-1: new full speed USB device using ohci_hcd and address 4
[  312.730526] usb 2-1: Ignoring serial port reserved for JTAG
[  312.736321] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[  312.736381] usb 2-1: Detected FT2232C
[  312.736384] usb 2-1: Number of endpoints 2
[  312.736387] usb 2-1: Endpoint 1 MaxPacketSize 64
[  312.736390] usb 2-1: Endpoint 2 MaxPacketSize 64
[  312.736392] usb 2-1: Setting MaxPacketSize 64
[  312.737894] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB1
[  557.100036] usb 1-7: new high speed USB device using ehci_hcd and address 4
[  557.180101] hub 1-0:1.0: unable to enumerate USB device on port 7
[  561.180035] usb 1-7: new high speed USB device using ehci_hcd and address 5
[  561.260052] hub 1-0:1.0: unable to enumerate USB device on port 7
[  584.590036] usb 1-7: new high speed USB device using ehci_hcd and address 6
[  584.764407] usb 1-7: device descriptor read/all, error -71
[  584.830045] hub 1-0:1.0: unable to enumerate USB device on port 7
[  587.650081] usb 1-7: new high speed USB device using ehci_hcd and address 8
[  587.812456] scsi5 : usb-storage 1-7:1.0
[  588.811412] scsi 5:0:0:0: Direct-Access     Sony     Storage Media    0100 PQ: 0 ANSI: 0 CCS
[  588.814255] sd 5:0:0:0: Attached scsi generic sg6 type 0
[  588.822655] sd 5:0:0:0: [sdf] 3932160 512-byte logical blocks: (2.01 GB/1.87 GiB)
[  588.823934] sd 5:0:0:0: [sdf] Write Protect is off
[  588.823940] sd 5:0:0:0: [sdf] Mode Sense: 43 00 00 00
[  588.823943] sd 5:0:0:0: [sdf] Assuming drive cache: write through
[  588.828762] sd 5:0:0:0: [sdf] Assuming drive cache: write through
[  588.828773]  sdf: sdf1
[  588.834409] sd 5:0:0:0: [sdf] Assuming drive cache: write through
[  588.834417] sd 5:0:0:0: [sdf] Attached SCSI removable disk
[  728.988649] usb 1-7: USB disconnect, address 8
[ 1166.812256] usb 2-1: USB disconnect, address 4
[ 1166.813387] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 1166.813399] ftdi_sio 2-1:1.1: device disconnected
[ 1169.660033] usb 2-1: new full speed USB device using ohci_hcd and address 5
[ 1169.900169] usb 2-1: Ignoring serial port reserved for JTAG
[ 1169.905174] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[ 1169.905213] usb 2-1: Detected FT2232C
[ 1169.905216] usb 2-1: Number of endpoints 2
[ 1169.905219] usb 2-1: Endpoint 1 MaxPacketSize 64
[ 1169.905222] usb 2-1: Endpoint 2 MaxPacketSize 64
[ 1169.905225] usb 2-1: Setting MaxPacketSize 64
[ 1169.907557] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 1182.542911] usb 2-1: USB disconnect, address 5
[ 1182.543106] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 1182.543123] ftdi_sio 2-1:1.1: device disconnected
[ 1203.380034] usb 2-1: new full speed USB device using ohci_hcd and address 6
[ 1203.620191] usb 2-1: Ignoring serial port reserved for JTAG
[ 1203.626150] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[ 1203.626190] usb 2-1: Detected FT2232C
[ 1203.626193] usb 2-1: Number of endpoints 2
[ 1203.626196] usb 2-1: Endpoint 1 MaxPacketSize 64
[ 1203.626198] usb 2-1: Endpoint 2 MaxPacketSize 64
[ 1203.626201] usb 2-1: Setting MaxPacketSize 64
[ 1203.627818] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
____________________________________________________________________________________________________________

It shows USB0 and USB1 but both unable to.

Now ...

The 1.0 installer is jibberish to me, is there any website that holds my hand and completely explains every single thing I need to do when the blue lighty is not up and running; even videos would be fine.

For instance, I put the files from the installer folder on a usb stick, do I actually copy the folder itself or just the files and put them first place I see when opening frehsly formatted usb stick?

"run php /runme.php" but from where, how when why, if the usb stick is connected to the plug how do I get there?
I installed php5.cli or whatever was needed from what I could see but if Linux does not know where the file is ...

This is driving me insane up to the point that I'll just take a hammer and have 1 minute of fun after having spent days of total aggrevation from morning till evening and that in my holiday.

Edit:

"In order to use Esia you need to make sure that you've updated Uboot" ... OMG, just ridiculous, in order to unbrick you need to first update Uboot, nice one when you cannot serial into Sheeva.
« Last Edit: November 12, 2010, 09:47:51 AM by graviton » Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #1 on: November 10, 2010, 07:26:13 AM »

Did you try to reseat the usb-cable? The USB Port at the Sheeva is VERY unsteady and not every USB-Cable will
connect fine (not even the in the box delivery-cable).

Did you get message that your computer does recognize the conencted USB-Device (Msg in the shell in Linux/dmesg or the
great "BaBim"-Sound in Windows)

Could you see sheeva as FTDI-Devive in lsusb?
Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #2 on: November 10, 2010, 09:43:05 AM »

hello,

Reseating usb doesn't help, cable is sound, have tested 3 different ones until now, but issue started after trying to update Uboot, last thing I did was reset, after that ... nothing.
Device is listed in dmesg, sometimes as USB0 other times as 1.
USB stick is recognised as well ""[  588.811412] scsi 5:0:0:0: Direct-Access     Sony     Storage Media    0100 PQ: 0 ANSI: 0 CCS""

Problem is that Uboot is screwed up, hardware works but if software is not starting/connecting ...

Don't know about lsusb, device is turned off now.

Only thing I need (for now) is a way to flash Uboot without having to resort to serial connection, I did get an SD card just before with a 1 on 1 copy of fs on NAND.

Am still looking for a decent description on how to do this.

Edit: Thought I'd found a solution @ http://www.plugcomputer.org/plugwiki/index.php/Das_U-boot_plug_support ... again ... use serial to ....

Edit2: ESIA does not recognise the device, obviously because U-boot is ***** up, started to have a look at the 1.0 installer again, 2 minutes and I closed everything, is there no one that can update the readme on this installer or , I'm not going to spend 2 weeks researching something that should take 5 minutes to cli
« Last Edit: November 11, 2010, 12:30:36 PM by graviton » Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #3 on: November 12, 2010, 07:35:54 AM »

So now I switched over to Windows 7 system.
Installed drivers, plugged in serial and started Installer 1.0 after having put all files from the installer folder onto a usb stick and putting it in the usb connection on the Sheeva, then started runme.exe nand from command line.
Then I get this output (devices A, B and the usb device were all recognized by Windows) ...

C:\Users\Eigenaar\Desktop\sheevaplug-installer-v1.0\sheevaplug-installer-v1.0>ru
nme.exe nand

 ****   Preparing environment variables file ...
reading uboot\uboot-env\uboot-dflt.txt
uboot\uboot-env\fw_setenv.exe baudrate 115200
CRC read error on uboot-env.bin: No error
uboot\uboot-env\fw_setenv.exe loads_echo 0
uboot\uboot-env\fw_setenv.exe ipaddr 10.4.50.165
uboot\uboot-env\fw_setenv.exe serverip 10.4.50.5
uboot\uboot-env\fw_setenv.exe rootpath /mnt/ARM_FS/
uboot\uboot-env\fw_setenv.exe netmask 255.255.255.0
uboot\uboot-env\fw_setenv.exe stdin serial
uboot\uboot-env\fw_setenv.exe stdout serial
uboot\uboot-env\fw_setenv.exe stderr serial
uboot\uboot-env\fw_setenv.exe console console=ttyS0,115200 mtdparts=nand_mtd:0xc
0000@0(uboot)ro,0x1ff00000@0x100000(root)
uboot\uboot-env\fw_setenv.exe mainlineLinux no
uboot\uboot-env\fw_setenv.exe CASset min
uboot\uboot-env\fw_setenv.exe enaMonExt no
uboot\uboot-env\fw_setenv.exe enaCpuStream no
uboot\uboot-env\fw_setenv.exe enaWrAllo no
uboot\uboot-env\fw_setenv.exe pexMode RC
uboot\uboot-env\fw_setenv.exe disL2Cache no
uboot\uboot-env\fw_setenv.exe setL2CacheWT yes
uboot\uboot-env\fw_setenv.exe disL2Prefetch yes
uboot\uboot-env\fw_setenv.exe enaICPref yes
uboot\uboot-env\fw_setenv.exe enaDCPref yes
uboot\uboot-env\fw_setenv.exe sata_dma_mode yes
uboot\uboot-env\fw_setenv.exe MALLOC_len 1
uboot\uboot-env\fw_setenv.exe ethprime egiga0
uboot\uboot-env\fw_setenv.exe netbsd_en no
uboot\uboot-env\fw_setenv.exe vxworks_en no
uboot\uboot-env\fw_setenv.exe bootargs_root root=/dev/nfs rw
uboot\uboot-env\fw_setenv.exe bootargs_end :::DB88FXX81:eth0:none
uboot\uboot-env\fw_setenv.exe image_name uImage
uboot\uboot-env\fw_setenv.exe bootcmd tftpboot 0x2000000 $(image_name);setenv bo
otargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):
$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe standalone fsload 0x2000000 $(image_name);setenv b
ootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end
) $(mvPhoneConfig); bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe bootdelay 3
uboot\uboot-env\fw_setenv.exe disaMvPnp no
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:4e:2a:14
uboot\uboot-env\fw_setenv.exe ethmtu 1500
uboot\uboot-env\fw_setenv.exe mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot\uboot-env\fw_setenv.exe mvNetConfig mv_net_config=(00:11:88:0f:62:81,0:1:2
:3),mtu=1500
uboot\uboot-env\fw_setenv.exe usb0Mode host
uboot\uboot-env\fw_setenv.exe yuk_ethaddr 00:00:00:EE:51:81
uboot\uboot-env\fw_setenv.exe nandEcc 1bit
uboot\uboot-env\fw_setenv.exe netretry no
uboot\uboot-env\fw_setenv.exe rcvrip 169.254.100.100
uboot\uboot-env\fw_setenv.exe loadaddr 0x02000000
uboot\uboot-env\fw_setenv.exe autoload no
uboot\uboot-env\fw_setenv.exe enaAutoRecovery yes
uboot\uboot-env\fw_setenv.exe ethact egiga0
reading uboot\uboot-env\uboot-nand-custom.txt
uboot\uboot-env\fw_setenv.exe bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstyp
e=ubifs
uboot\uboot-env\fw_setenv.exe mtdpartitions mtdparts=orion_nand:0x400000@0x10000
0(uImage),0x1fb00000@0x500000(rootfs)
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:01:c1:e6
uboot\uboot-env\fw_setenv.exe real_bootcmd setenv bootargs $(bootargs_console) $
(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000;
bootm 0x00800000
uboot\uboot-env\fw_setenv.exe bootargs_console console=ttyS0,115200
uboot\uboot-env\fw_setenv.exe bootcmd run recover1
uboot\uboot-env\fw_setenv.exe recover1 setenv mainlineLinux yes; setenv arcNumbe
r 2097; setenv bootcmd run recover2; saveenv; reset
uboot\uboot-env\fw_setenv.exe recover2 run recover3; setenv bootcmd $(real_bootc
md); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram
0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
uboot\uboot-env\fw_setenv.exe recover3 run recover4; nand erase clean 0x00100000
 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
uboot\uboot-env\fw_setenv.exe recover4 usb start; fatload usb 0 0x00800000 uImag
e; fatload usb 0 0x01100000 initrd

 ****   Burning uboot and environment variables ... This will take few minutes .
..
 ****   When uboot.bin is written to NAND/SD, Disconnect and connect your mini U
SB cable
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug
Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #4 on: November 12, 2010, 07:59:02 AM »

Without seriell Connection to USB-Port you could only try to manually flash the u-boot via openocd from
the Linux Command-Line.

see Example 2: Reflashing a Bricked U-Boot (Method 1)
at http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux

As netcat I did use telnet on Port 4444 (had to do this with my OpenRD, because my new U-boot
doesnt get the network port up).

openocd and the .cfg and -bin files should be in the same directory.

I did use openocd 0.3.1 in debian squeeze for that.
Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #5 on: November 12, 2010, 08:52:54 AM »

Installer ran, U-boot is working again !!!!! well, still busy copying but what worked was not on Wiki or anything like that grrrrrrrrr

Found a topic (on another computer so cannot link) onhere ...

It states you need to comment out lines 7, 8 and 43, 44 (put /* in beginning of line 7 and */ at the end of line 8, repeat for line 43 and 44) otherwise it will keep stopping with some stupid error in runme.php file and then run it with root account so most people would have to do "su passwd root" first, sudo will not work, after that, run it and it starts !!!!

Courtesy of oncam123, my hero Cheesy
« Last Edit: November 12, 2010, 08:56:13 AM by graviton » Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #6 on: November 12, 2010, 09:47:23 AM »

Sigh ... everything went fine until I changed password for root, now it won't let me in no more, ssh I always get message saying "host key verification failed" via ubuntu host, windows host Putty it says "Access denied"

omg I'm on Azerty keyboard on windows host, ssh'd into it with Ubuntu set as Qwerty or something?Huh

I give up, reinstall again ...
Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #7 on: November 12, 2010, 11:41:50 AM »

Sigh ... everything went fine until I changed password for root, now it won't let me in no more, ssh I always get message saying "host key verification failed" via ubuntu host,

on the Ubuntu computer searc for the file known_hosts and delete the line inside which is for the ip of your sheevaplug.

After deleting the line inside the file save it and try to connect again...
Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #8 on: November 12, 2010, 12:57:08 PM »

Reinstalled Debian Squeeze on SD card ... SAME THING, connection refused, deleted line in .ssh/known_hosts, ssh gets me 'connection refused' and serial gets me 'login failed', found a thread here stating DHCP - Static has something to do with it but I use DHCP...

Sorry for my bad language but this is just a piece of ******************** I can use to put a drink on imo  Angry Angry Angry
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #9 on: November 12, 2010, 06:11:25 PM »

see Example 2: Reflashing a Bricked U-Boot (Method 1)
at http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux
One thing always gets me with this.  You appear to need to run openocd on the system that you are trying to flash.  But it's bricked, so how are you able to boot it to run anything?
Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #10 on: November 13, 2010, 04:57:03 AM »

That was one of my major issues with Sheeva plug, wherever you look, always 'connect to U-boot etc etc' when it is bricked ...
Still a lot to document as far as I can see.

Still not getting IP address, restarted all network devices, blue light burns, serial does show Debian login but that's it.

Just for future reference, Sony 2GB usb stick works as well as mmc 4GB Transcend ...
Seeing that there are so many remarks on usb sticks that don't work, there should be a list for this imo, same for mmc's, issues as well with U-boot/Debian.
« Last Edit: November 13, 2010, 05:00:12 AM by graviton » Logged

graviton
Newbie
*

Karma: 0
Posts: 18


View Profile
« Reply #11 on: November 13, 2010, 05:22:52 AM »

Now when I boot after a reset via serial ... (it aint over yet Wink ) but I did stop autoboot to check things and the ran 'boot'.

## Booting image at 00800000 ...                                               
   Image Name:   Debian kernel                                                 
   Created:      2010-11-12  19:08:01 UTC                                     
   Image Type:   ARM Linux Kernel Image (uncompressed)                         
   Data Size:    1432308 Bytes =  1.4 MB                                       
   Load Address: 00008000                                                     
   Entry Point:  00008000                                                     
   Verifying Checksum ... OK                                                   
OK                                                                             
## Loading Ramdisk Image at 01100000 ...                                       
   Image Name:   Debian ramdisk                                               
   Created:      2010-11-12  19:08:02 UTC                                     
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)                     
   Data Size:    5675841 Bytes =  5.4 MB                                       
   Load Address: 00000000                                                     
   Entry Point:  00000000                                                     
   Verifying Checksum ... OK                                                   
                                                                               
Starting kernel ...                                                           
                                                                               
Uncompressing Linux... done, booting the kernel.                               
                                                                               
Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).                 
                                                                               
Available machine support:                                                     
                                                                               
ID (hex)        NAME                                                           
00000690        Marvell DB-88F6281-BP Development Board                       
00000691        Marvell RD-88F6192-NAS Development Board                       
00000692        Marvell RD-88F6281 Reference Board                             
0000078c        Marvell 88F6281 GTW GE Board                                   
00000a76        Marvell eSATA SheevaPlug Reference Board                       
00000831        Marvell SheevaPlug Reference Board                             
00000a63        Marvell GuruPlug Reference Board                               
0000085b        QNAP TS-119/TS-219                                             
000009c6        QNAP TS-41x                                                   
00000bb6        Seagate FreeAgent DockStar                                     
00000b44        Marvell OpenRD Ultimate Board                                 
00000939        Marvell OpenRD Client Board                                   
00000915        Marvell OpenRD Base Board                                     
00000b1e        HP t5325 Thin Client                                           
                                                                               
Please check your kernel config and/or bootloader.

Edit:
Marvell>> setenv arcNumber 2097
Marvell>> setenv mainlineLinux yes
Marvell>> saveenv
Marvell>> reset

fixed that one as well, now I can logon serial and Sheeva gets DHCP again, now for ssh Cheesy

Edit:
Sorry for all this editing and talking about different stuff ...
Turns out that Debian did not install openssh  Shocked so the guy that wrote the tutorial on how to install Debian should change this Wink
« Last Edit: November 13, 2010, 05:37:12 AM by graviton » Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #12 on: November 13, 2010, 06:19:24 AM »

]One thing always gets me with this.  You appear to need to run openocd on the system that you are trying to flash.  But it's bricked, so how are you able to boot it to run anything?
No  Cheesy you didnt run opencd on the sheevaplug, but on another Linux-computer and the sheevaplug is connected to this computer as a USB-device.
So this should also work if the sheevaplug is bricked.
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #13 on: November 13, 2010, 11:57:45 AM »

...So this should also work if the sheevaplug is bricked.
Thanks - it occurred to me later than I'd got the wrong idea about openocd and that it runs over the USB/JTag/ftdi interface - not directly to NAND...
I do have some questions about u-boot in general, though - but that's for later, once I sort out what I wish to know.
Logged

Dammuozz
Newbie
*

Karma: 0
Posts: 41


View Profile
« Reply #14 on: November 29, 2010, 01:21:58 AM »

wonderful! I've been trying to unbrick my sheevaplug for ages!!!! obviously with no success....

I must say I agree with you when you say readmes and all the documentation about openOCD and installer-scripts stuff are way too much complicated and can't tell you what to do!!!

I'll give another try using your configuration with openocd and debian sqeeze....If you have any tips please do help me... Smiley

I gave up unbricking my sheeva but your story it's the proof that "it can be done!!"... Tongue



dammuozz
Logged

Pages: [1]
Print
Jump to: