Help Please! Another Newbie Another Bricked SheevaPlug!

[nut]

Hello folks,

Please help yet another lost sheevaplug newbie!

I think my brand new sheevaplug (NewIT debian squeeze - multi boot esata) is bricked.

I bought it to run Logitech Squeezebox Server and feed music from an external self powered USB HDD to my Squeezebox Touch.

The problems came when I realised my SD card reader would not deal with the  HCSD cards I got from NewIT. I then looked through the Squeezeplug Wiki http://wiki.slimdevices.com/index.php/SqueezePlug and attempted the manual installations.

I slowly but surely got through the Wiki page making the serial connection and installing the various packages and latest versions but realised via my Orange Wireless router (hard wired via the ethernet cable) I had skipped past the "Check U-Boot Version". Upon going back to this step and checking the version I saw that my version was older than the one required for the installation as per the Wiki page.

I downloaded the newer Uboot version and ran the USB install method as per the Wiki page. Upon resetting the Sheevaplug kept freezing at a line that said something like "Sata 0.28" or "esata 0.28" I can't quite remember and didn't get a copy of the line it froze on (sorry I know this isn't much help).

I tried to boot several times each time it froze at the same point and would not proceed. I then tried using other versions of Uboot by stopping it from getting to the bit where it was freezing (pressing enter three times to get the prompt). Finally when using the reset command on one of the versions of u-boot I got nothing, no prompt just black screen in putty and no option to give any commands. If I switch off the Sheevaplug and switch on again nothing happens. I can connect to it in Putty but I cannot type any commands. I have one green light and the other one is out.

I have since found on NewIT website there are uboot versions for download and what might be a version for a sheevaplug with eSata like mine. Is that what caused the freezing, using the wrong uboot driver (the one from the wiki page)


I found the page for the Squeeze installer for use when a sheevaplug is bricked. Is this the only way to get it up and running again? I downloaded the file and unzipped it. The instructions refer to copying the "installer" directory to a FAT32 USB is that just all of the files unzipped? Anyhow the command runme in the dos prompt in my windows XP is not recognised. I can't see a runme file on my computer or in the unzipped files from the squeezepluginstaller. Do I have to install this file? The instructions are quite unclear to me, especially being new to this.


Many thanks if you have been bothered to read this far!

What do I do from here?





Many thanks any help appreciated!

[nut]

An update:


I downloaded runme and copied it to the windows directory. I had been typing the command in the run prompt on the start menu. This time I ran command.com and typed the command in on the dos window.

Microsoft console? opens automatically in windows and shows "console root" with nothing there. In Dos the cursor flases for a while after this giving the impression something is running although the sheevaplug shows no sign of activity at all. Eventually I get the dos prompt back like it has finished although I don't get the beep mentioned in the installer guide. I unplug the serial USB cable plug back in and run Putty. Still black screen, nothing, no prompt.

Please can anyone help me?

[peter a]

sheevaplug is bricked ?.

There is one good thing about the Sheevaplug, it is almost impossible to truly break the device.  
All you need to do a get serial access or use an installer to put things back.
If you haven`t done any hardware damage, then all is never lost !!!.
 
Sorry I`ve never got to the stage where I needed the installer .
I changed the Uboot via tftp , which I was told is the best way to go.
My install is on SD and only use the flash for backups etc


Did you have serial before you had the problems ?
Eg are you using the right coms port or speed  ?

[nut]

Hello, thanks for replying.


Yes I believe I am using the right coms port but I have not changed any speed settings.


I also think that the file runme.exe that I downloaded is totally the wrong file!


I cannot find any information on runme.exe, it is not already on my computer and it is not one of the files that is part of the tar installer package.  

[nut]

I just redownloaded the installer package and I now have runme.exe and the readme file.

Don't know what happened before, I had an entirely different set of files.

Fingers crossed...

[peter a]

You would have problems with other boxes like the lnkstation pro !!!
If you make a mistake it is a brick or hardware mod time !!!!

[nut]

Yes I guess I would be truly stuck. I am a little concerned I am stuck with the Sheevaplug being useless.


I just ran runme.exe nand|mmc and it says (first line)

CRC read error on uboot-env.bin: No error

And freezes there.


I just tried runme.exe nand and I get alot more activity but it all ends with

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


I believe this is a common and very frustrating error from what I have read here today. I have tried unplugging then plugging the Sheevaplug before running the command, resetting the sheevaplug with a paperclip then running the command. Still the same.


Would anyone be so kind to jump in?

[nut]

I noticed this:


  Important Note for Newer Plugs (7/30/09ish)

If you are getting errors when trying to connect to the plug, you may need to change the Vendor and Product IDs in the config (sheevaplug-installer-v1.x\uboot\openocd\config\interface\sheevaplug.cfg ). This is needed if you see the ftdi device and messages as outlined above, but have errors when trying to connect using the runme.sh. You need to change the file so that it contains:

 interface ft2232
 ft2232_layout sheevaplug
 ft2232_vid_pid 0x1c0c 0x0102
 jtag_khz 2000
 #ft2232_vid_pid 0x9e88 0x9e8f
 #ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"



I edited the sheevaplug.cfg file in notepad (windows) and pasted the above over what was in there and re-ran the runme.exe nand. I am still getting the same error.

[peter a]

Yes , it looks like it can`t the serial connection !!!!

Not used the installer , so sorry can`t help you .

[simonbrooke]

Yes I guess I would be truly stuck. I am a little concerned I am stuck with the Sheevaplug being useless.


I just ran runme.exe nand|mmc and it says (first line)

CRC read error on uboot-env.bin: No error

And freezes there.


I just tried runme.exe nand and I get alot more activity but it all ends with

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


I believe this is a common and very frustrating error from what I have read here today. I have tried unplugging then plugging the Sheevaplug before running the command, resetting the sheevaplug with a paperclip then running the command. Still the same.


Would anyone be so kind to jump in?

OK, it sounds like you need a completely different approach. What I did was

(1) plug the SheevaPlug into the mains and into my network switch (assumes you have DHCP running, but most people do these days)
(2) from another machine, run nmap to identify what IP address your SheevaPlug is sitting on:

artisan:~# nmap 192.168.0.0/24

Starting Nmap 4.68 ( http://nmap.org ) at 2010-08-20 15:00 BST
Interesting ports on ubuntu (192.168.0.6):
Not shown: 1711 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
MAC Address: 00:50:43:01:52:1C (Marvell Semiconductor)

Mine self-identifies as 'ubuntu', even though that is no longer its hostname. I expect yours will too. In any case the MAC address will show Marvell Semiconductor, and port 22 (probably only 22, unless you've installed other services) will be open.

(3) ssh in to the port stated:

simon@artisan:~$ ssh 192.168.0.6 -l root
The authenticity of host '192.168.0.6 (192.168.0.6)' can't be established.
RSA key fingerprint is ff:2c:57:5f:f0:7b:ab:3d:95:bb:bc:cf:4d:8f:5f:12.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.6' (RSA) to the list of known hosts.
root@192.168.0.6's password:

The default root password is 'nosoup4u' (BUT CHANGE THIS!)

You now have control of your box.

The only thing that can go wrong with this is if the OS image on the card you've inserted is dodgy, or if the card you've inserted fails fsck (a problem I had), in which case the box will hang in single user mode without starting sshd. However, if this happens, take the card out and power cycle the box, and you'll be fine.

[nut]

Thank you I shall try this later tonight.

I have an Orange Livebox Wireless Router but when I login to the Router I cannot view the IP addresses of the devices connected to it. Does this mean that it doesn't run DHCP and doesn't assign IP Addresses to devices that attach to it?


Thanks.

[NewIT_Marcus]

Hello folks,

Please help yet another lost sheevaplug newbie!

I think my brand new sheevaplug (NewIT debian squeeze - multi boot esata) is bricked.

I bought it to run Logitech Squeezebox Server and feed music from an external self powered USB HDD to my Squeezebox Touch.

The problems came when I realised my SD card reader would not deal with the  HCSD cards I got from NewIT. I then looked through the Squeezeplug Wiki http://wiki.slimdevices.com/index.php/SqueezePlug and attempted the manual installations.

I slowly but surely got through the Wiki page making the serial connection and installing the various packages and latest versions but realised via my Orange Wireless router (hard wired via the ethernet cable) I had skipped past the "Check U-Boot Version". Upon going back to this step and checking the version I saw that my version was older than the one required for the installation as per the Wiki page.

I downloaded the newer Uboot version and ran the USB install method as per the Wiki page. Upon resetting the Sheevaplug kept freezing at a line that said something like "Sata 0.28" or "esata 0.28" I can't quite remember and didn't get a copy of the line it froze on (sorry I know this isn't much help).

I tried to boot several times each time it froze at the same point and would not proceed. I then tried using other versions of Uboot by stopping it from getting to the bit where it was freezing (pressing enter three times to get the prompt). Finally when using the reset command on one of the versions of u-boot I got nothing, no prompt just black screen in putty and no option to give any commands. If I switch off the Sheevaplug and switch on again nothing happens. I can connect to it in Putty but I cannot type any commands. I have one green light and the other one is out.

The final paragraph above is the most relevant to your problem.

If I understand correctly:

• You attempted to install a new version of U-Boot
• You can no longer see the scrolling bootlog (the one that begins with "Marvell U-Boot" in ascii art)

There are several ways to change the U-Boot version; personally we prefer the TFTP method. That, and the USB method require access to the existing U-Boot prompt, ie you must have a working U-Boot installed.

Since it seems that you no longer have a working U-Boot, you are left with the installer method. Solving the messages that you have reported requires that you give more information about your environment - ie is your host PC Windows or Linux; what OS?

The error message you pasted in your post is helpful:

****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

Did you try what it suggests?

[nut]

Hello Marcus, Thank you for jumping in to help!


Yes  the final paragraph is the most relevant and where it all went wrong. I was following the wiki page on setting up Logitech SBS on the Sheevaplug. You are right I do not get the Marvell prompt, when the sheevaplug is reset or turneded off and on nothing is run, nothing happens and there is no prompt to try any commands.


My host computer is Windows XP and I am able to connect via Putty even though I cannot actually do anything. I have tried resetting then running the runme.exe quickly after I have also tried turning it off then doing it as well as unplugging the usb serial cable and plugging back in after reset / switch on. I have tried two different mini USB cables. I have edited the sheevaplug.cfg as per the installer where it notes problems connecting to newer plugs and it now reads:

interface ft2232
 ft2232_layout sheevaplug
 ft2232_vid_pid 0x1c0c 0x0102
 jtag_khz 2000
 #ft2232_vid_pid 0x9e88 0x9e8f
 #ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"


The Sheevaplug I have is (or was!?) a multi boot esata sheevaplug which has one of your 4GB HCSD cards with debian squeeze on it. I also got a spare blank 4GB card if that is of use at all? I also now have a USB HCSD card reader which I picked up today.

[NewIT_Marcus]

Don't be trying anything with the SD card; you need to get the plug back first.

Under Windows the installer instructions are different. Since you can connect via serial or JTAG, but not both. So that's what you need to focus on. When you have that right, the error messages will no longer appear and you should have an activity log to review (don't worry about its contents, it's very technical).

Once you have reflashed U-Boot and the NAND (which will have the same UBIFS file system that we provided), you'll be able to boot to NAND. Your final step will be to set the environment variables to multiboot settings.

[nut]

Under Windows the installer instructions are different. Since you can connect via serial or JTAG, but not both. So that's what you need to focus on.

Please could you elaborate on this as I have spent a good couple of hours going round and round getting the same error. When I google this problem it seems very common but no one really gives any straight answers how to address it. The wiki page seems very difficult I can't really do anymore than run the command the way it is telling me to but it always fails with  that error message. It seems like some folk have abandoned installing from a windows host and had more luck from ubuntu.

I have just installed ubuntu but as I am so new to it I am having great difficulty running runme.php as it keeps telling me I must do it as root.

Thanks.