And UNbricked again.

In a nutshell:

I followed the instractions here: https://newit.co.uk/forum/index.php?topic=2835

To do that I fired up my Win8, started an Ubuntu in VirtualBox, connected the SheevaPlug's Mini-USB-JTAG to my PC and mapped the USB devices into the VM.

I had to use "sudo screen /dev/ttyUSB0 115200" to connect to the USB device.

As I wanted to reinstall the u-boot version http://people.debian.org/~tbm/u-boot/2011.12-3/sheevaplug/u-boot.kwb I used http://people.debian.org/~tbm/u-boot/2011.12-3/sheevaplug/uboot.elf instead of http://www.downloadsnewit.co.uk/u-boot/recovery/sheevaplug/denx/u-boot.elf

With the result that I could start an u-boot on the Plug, but it didn't recognized any commands (even not "help").

So I switched to NewIT's suggestion about DENX u-boot.elf version and restarted.

Now the plug came up with a 'proper' u-boot. However I downloaded the DENX u-boot.kw version from ~tbm's site and put it onto a pen drive and attached it to the plug.

Then I followed Michael's u-boot USB upgrade instruction at http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html and reset the plug. It came up properly with the environment variables still set to the values before I bricked it.

Booting the plug again it loads it's Debian from SD as before - puh.

I am having a nightmare with a new, external, USB 3TB disk getting to work under linux

Sheevaplug (Linux hardy 2.6.30.2 #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009 armv5tel GNU/Linux)


. When I bought it, it arrived with one 3TB partition with NTFS on and I successfully tested it under Windows
without a problem. When I tried to reformat it into two partitions under linux using fdisk or cfdisk, it only
showed up as a 800 GB disk. After some reading I learned the difference between MBR and GPT partition
tables and that these two utils do not support the required GPT. So I tried to use parted but ran into the following

Warning: /dev/sda contains GPT signatures, indicating that it has a GPT table.  However, it does not
have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a
program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are
now using an msdos partition table.  Is this a GPT partition table?
Yes/No? Yes                                                               
Error: Invalid argument during seek for read on /dev/sda                 
Retry/Ignore/Cancel? I                                                   
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? O                                                             
Backtrace has 0 calls on stack:
                                                                         

You found a bug in GNU Parted! Here's what you have to do:
...   


Then someone recommended that I use gdisk but I cannot work out how to install it - can someone please help! Is there a way to install it with apt-get?
I have downloaded the source and tried to compile it but get several errors which I have put at the end.

Could someone please help get this disk up and working on my Sheevaplug?

Many thanks in advance,

Madmike.


Make error messages:

hardy:~/gptfdisk-0.8.1# make
g++ -Wall -D_FILE_OFFSET_BITS=64 -D USE_UTF16   -c -o gptpart.o gptpart.cc
gptpart.cc:19:28: error: unicode/ustdio.h: No such file or directory
In file included from gptpart.h:22,
                 from gptpart.cc:27:
parttypes.h:7:29: error: unicode/ustream.h: No such file or directory
In file included from gptpart.h:22,
                 from gptpart.cc:27:
parttypes.h:59: error: ‘UnicodeString’ does not name a type
In file included from gptpart.cc:27:
gptpart.h:57: error: ‘UnicodeString’ does not name a type
gptpart.h:64: error: ‘UnicodeString’ does not name a type
gptpart.h:78: error: ISO C++ forbids declaration of ‘UnicodeString’ with no type
gptpart.h:78: error: expected ‘,’ or ‘...’ before ‘&’ token
gptpart.cc:57: error: ‘UnicodeString’ does not name a type
gptpart.cc:73: error: ‘UnicodeString’ does not name a type
gptpart.cc: In member function ‘void GPTPart::SetType(PartType)’:
gptpart.cc:100: error: ‘GetDescription’ was not declared in this scope
gptpart.cc:100: error: ‘class PartType’ has no member named ‘UTypeName’
gptpart.cc: In member function ‘void GPTPart::SetName(const std::string&)’:
gptpart.cc:110: error: ‘UnicodeString’ was not declared in this scope
gptpart.cc: At global scope:
gptpart.cc:115: error: ISO C++ forbids declaration of ‘UnicodeString’ with no type
gptpart.cc:115: error: expected ‘,’ or ‘...’ before ‘&’ token
gptpart.cc: In member function ‘void GPTPart::SetName(int)’:
gptpart.cc:116: error: ‘theName’ was not declared in this scope
gptpart.cc:120: error: ‘UChar’ was not declared in this scope
gptpart.cc:120: error: expected primary-expression before ‘)’ token
gptpart.cc: In member function ‘void GPTPart::ShowSummary(int, uint32_t)’:
gptpart.cc:174: error: ‘UnicodeString’ was not declared in this scope
gptpart.cc:174: error: expected ‘;’ before ‘description’
gptpart.cc:196: error: ‘GetDescription’ was not declared in this scope
gptpart.cc:196: error: ‘description’ was not declared in this scope
gptpart.cc: In member function ‘void GPTPart::ShowDetails(uint32_t)’:
gptpart.cc:228: error: ‘GetDescription’ was not declared in this scope
gptpart.cc: In member function ‘void GPTPart::ChangeType()’:
gptpart.cc:274: error: ‘GetDescription’ was not declared in this scope
gptpart.cc:274: error: ‘GetUTypeName’ was not declared in this scope
make: *** [gptpart.o] Error 1

 

same too me - bricked my test/spare SheevaPlug with the testing version. So my advice: don't give it an additional try ;-)

Luckily my JTAG access is working on W8 now, so I can't try to unbrick (following bigbear59's tutorial http://www.plugcomputer.org/plugforum/index.php?topic=3680

(please also read http://www.plugcomputer.org/plugforum/index.php?topic=6238 first)

!!! SUCCESS !!!

There might be a more straight forward way, but here's how it worked for me

As mentioned in the other thread I amended the "2.08.28 WHQL Certified" INF files with the VID/PID information of the ones in the INF files of the "CDM 2.04.16_SHEEVA" version.

I then disabled the driver signature enforcement in Windows 8 (see http://www.craftedge.com/tutorials/driver_install_windows8/driver_install_win8.html)

After that I manually directed W8 to update the driver from the modified "2.08.28 WHQL Certified" directory for the two unknown devices.

Win complained about the signature, but I confirmed to use that driver.

However the "USB Converter Serial A & B" showed up properly in the HW manager, the newly created COM port was flagged with a failure.

I couldn't get that fixed so I removed the devices and drivers again.

With my 'second' try I picked the "CDM 2.04.16_SHEEVA" drivers (again with disabled the driver signature enforcement).

Again both "USB Converter Serial A & B" showed up, but again an new USB COM port was flagged with a failure.
I picked this device and applied the "2.08.28 WHQL Certified" driver to it and EUREKA, COM9 'arrives'.

W8 reports 2.4.14.0 as the driver version for all the devices.

Tried that one as well - and did it again, just now - maybe still doing something wrong (!?), but no, doesn't work for me. If I unpack the EXE the package contains the same INF-Files as the 2.08.28 ZIP file. BUt my W8 system reports the SheevaPlag devices as

VID_9E88&PID_9E8F&MI_00\6&1D9A809B&0&0000
VID_9E88&PID_9E8F&MI_01\6&1D9A809B&0&0001

which are not included.

@odoll, I had a lot of problems on Win7 trying to update the drivers from the ZIP file.  The installer at http://www.ftdichip.com/Drivers/CDM/CDM20828_Setup.exe worked a lot better.  I removed all instances of the old drivers, removed the JTAG cable, ran the setup and then inserted the JTAG cable.  After checking Windows Update, Windows eventually found the pre-installed drivers.  I do not have Win8 so have not been able to test whether this works.

PS: I sent the following email to Future Technology Devices International Limited (support1@ftdichip.com) in the UK:

Am 24.03.2013 21:14, schrieb odoll:
> To Whom it may concern,
>
> I'm owner of GlobalScale SheevaPlug and was able to use the "FTDI CDM
> Drivers 2.04.16 Revision" driver "CDM 2.04.16_SHEEVA" to access the
> device via JTAG with Windows XP and Windows 7.
>
> However I recently upgraded to Windows 8 Prof 64b and I found the above
> driver no longer working.
>
> Looking for a recent driver I ran into your "CDM 2.08.28 WHQL Certified"
> version, which should support W8, but it doesn't work neither.
>
> Looking into the INF files (and comparing the VID & PID #s) I see the
> new version does not list those related the SheevaPlug any longer.
>
> May I kindly ask if you would be able (and willing to provide a W8
> compatible driver which also still supports the SheevaPlug with the
>
> \VID_9E88&PID_9E8F&MI_00\6&1D9A809B&0&0000
> \VID_9E88&PID_9E8F&MI_01\6&1D9A809B&0&0001
>
> As we still have a big group of people using the SheevaPlug for some
> time I think this would be very much appreciated by the community.

Any idea how to get the driver working with W8 Prof 64b?!

I had JTAG working with W7, but I recently upgraded to W8. As the system found no appropriate driver I was 'clever' enough ;-) to find the site http://www.ftdichip.com/Products/ICs/FT2232D.htm myself and download the file "CDM 2.08.28 WHQL Certified.zip" and tried to apply the drivers from this source.

But again no luck. While further digging into the issue I noticed that the *.inf files in the "CDM 2.04.16_SHEEVA" package also list the devices

ftdibus.inf:
%USB\VID_9E88&PID_9E8F.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F
%USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_00
%USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_01
[...]
USB\VID_9E88&PID_9E8F.DeviceDesc="USB Serial Converter"
USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc="USB Serial Converter A"
USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc="USB Serial Converter B"

ftdiport.inf:
%VID_9E88&PID_9E8F.DeviceDesc%=FtdiPort2232.NT,FTDIBUS\COMPORT&VID_9E88&PID_9E8F
[...]
VID_9E88&PID_9E8F.DeviceDesc="USB Serial Port"


Thinking being 'clever' again I simply added those entries to the *.inf files of the "CDM 2.08.28 WHQL Certified.zip" package.

I seem to be one step further as W8 start the installation of the drivers, now, but it stops a bit later with a message complaining that the hash values of the files don't match (as they may have been [illegally] modified -and the may be right here ;-)

Unfortunately I'm stuck at this point. Any idea who to correct this or how to get hold of a working driver which supports the SheevaPlug and Windows 8!?!

FYI: I just tried to install this following Martins advice and have now bricked my Sheevaplug.