@ll,

I tried to upgrade my SheevaPlug from Squeeze to Wheezy (using this German Guide http://www.sysadminslife.com/linux/howto-upgrade-debian-6-squeeze-zu-debian-7-wheezy/).

Mostly everything looked promising after the first reboot, except smbd 3.6.6 which crashed and does not come up. (see syslog messages in red below).

As testparm gave a warning about "null passwords = Yes" I disabled this, but smbd won't start (nmbd and winbindd do).

I ran out of ideas and thinking it might be a bug I tried to compile and use version 3.6.15 (following this guide http://verahill.blogspot.de/2012/03/building-and-installing-samba-from.html), but being a Unix n00b I couldn't properly fix the path settings.

I'd appreciate hints ...

May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.289649,  0] lib/fault.c:47(fault_report)
May  9 17:06:45 Share smbd[2430]:   ===============================================================
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.295058,  0] lib/fault.c:48(fault_report)
May  9 17:06:45 Share smbd[2430]:   INTERNAL ERROR: Signal 7 in pid 2430 (3.6.6)
May  9 17:06:45 Share smbd[2430]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.296434,  0] lib/fault.c:50(fault_report)
May  9 17:06:45 Share smbd[2430]:
May  9 17:06:45 Share smbd[2430]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.297702,  0] lib/fault.c:51(fault_report)
May  9 17:06:45 Share smbd[2430]:   ===============================================================
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.298565,  0] lib/util.c:1117(smb_panic)
May  9 17:06:45 Share smbd[2430]:   PANIC (pid 2430): internal error
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.300102,  0] lib/util.c:1221(log_stack_trace)
May  9 17:06:45 Share smbd[2430]:   BACKTRACE: 0 stack frames:
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.302107,  0] lib/util.c:1122(smb_panic)
May  9 17:06:45 Share smbd[2430]:   smb_panic(): calling panic action [/usr/share/samba/panic-action 2430]
May  9 17:06:53 Share smbd[2430]: [2013/05/09 17:06:53.908783,  0] lib/util.c:1130(smb_panic)
May  9 17:06:53 Share smbd[2430]:   smb_panic(): action returned status 0
May  9 17:06:53 Share smbd[2430]: [2013/05/09 17:06:53.909335,  0] lib/fault.c:372(dump_core)
May  9 17:06:53 Share smbd[2430]:   dumping core in /var/log/samba/cores/smbd
May  9 17:06:53 Share smbd[2430]:

BTW: later the year the issue even got worse as the USB drive often wasn't found though rebooting and or resetting the plug. In the end I even electrically connected the outer shield of the USB-plug to the earth cable, which gave some relief.
While I'm currently trying to update my plug from Squeeze to Wheezy I'm playing around with images on different SHDC cards (old Panasonic vs new Transcend). Looking at the various reboots performed during this exercise I notice, that not only the Transcend card is found immediately - usually I have to press the reset button for the Panasonic to be recognized by the plug - but also the USB drive recognition is perfect again with the Transcend, while it's still bad, when the Panasonic is connected.

Strange, but there seems to be some correlation of the recognition with the SD card's brand and the same USB drive!?

Good news: after the upgrade to Wheezy the plug rebooted with the new SD card without me having to push the reset button

Bad news: as with my first attempt to upgrade, smbd does not want to start. I got the below syslog message.

Thus I put back the "Squeeze" card for the moment, leaving the "Wheezy" for trouble shooting with my spare plug.

May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.289649,  0] lib/fault.c:47(fault_report)
May  9 17:06:45 Share smbd[2430]:   ===============================================================
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.295058,  0] lib/fault.c:48(fault_report)
May  9 17:06:45 Share smbd[2430]:   INTERNAL ERROR: Signal 7 in pid 2430 (3.6.6)
May  9 17:06:45 Share smbd[2430]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.296434,  0] lib/fault.c:50(fault_report)
May  9 17:06:45 Share smbd[2430]:
May  9 17:06:45 Share smbd[2430]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.297702,  0] lib/fault.c:51(fault_report)
May  9 17:06:45 Share smbd[2430]:   ===============================================================
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.298565,  0] lib/util.c:1117(smb_panic)
May  9 17:06:45 Share smbd[2430]:   PANIC (pid 2430): internal error
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.300102,  0] lib/util.c:1221(log_stack_trace)
May  9 17:06:45 Share smbd[2430]:   BACKTRACE: 0 stack frames:
May  9 17:06:45 Share smbd[2430]: [2013/05/09 17:06:45.302107,  0] lib/util.c:1122(smb_panic)
May  9 17:06:45 Share smbd[2430]:   smb_panic(): calling panic action [/usr/share/samba/panic-action 2430]
May  9 17:06:53 Share smbd[2430]: [2013/05/09 17:06:53.908783,  0] lib/util.c:1130(smb_panic)
May  9 17:06:53 Share smbd[2430]:   smb_panic(): action returned status 0
May  9 17:06:53 Share smbd[2430]: [2013/05/09 17:06:53.909335,  0] lib/fault.c:372(dump_core)
May  9 17:06:53 Share smbd[2430]:   dumping core in /var/log/samba/cores/smbd
May  9 17:06:53 Share smbd[2430]:

Just a minor note:


Whilst running my second attempt to upgrade my SheevaPlug from Squeeze to Wheezy (using this German Guide http://www.sysadminslife.com/linux/howto-upgrade-debian-6-squeeze-zu-debian-7-wheezy/) though everything looked promising after the first reboot, except the smbd not coming up, I noticed I couldn't make proper images from the Panasonic SD after upgrade as both dd and WinImage complained about I/O errors reading the SDHC card. (Luckily I had a copy of the card from shortly before the upgrade, which I could put onto another spare, but only class 4 Panasonic SDHC).

Thus I decided no longer trusting the old one and  to order a new SHDC (class 10) Transcend and give the upgrade to Wheezy a third try, which I'm currently on now ...

While making another copy of the image to the new SHDC, putting it into the slot, powering the plug and silently starting to count up to ten to when I usually press the reset button, I found the attached USB drive to make the 'proper' I/O noise, showing me, that the image booted without having me to reset the plug :-)

Thus the new Transcend SDHC seems to be more 'recognisable' to the plug that the other SDs I used to far ... to be confirmed in a few ours when I have to do the first reboot after the upgrade ;-)

Console access (via JTAG adapter) or are you booting from an SD? If so, mount your SD in another system and fix your config?

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.

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.

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!?!

As to http://www.plugcomputer.org/plugforum/index.php?topic=6170 I think 2011.12-3 is the last working DENX version.

Though I myself haven't found time to test it, yet, you might give the version at https://doukki.net/plugs/sheevaplug/testing/ a try?!?

PS: just 'found' the test binary here  https://doukki.net/plugs/sheevaplug/testing/

PPS: and just found the link to a "Marvell uboot (3.4.16)" version in the "Linux distributions" section of this forum http://www.plugcomputer.org/plugforum/index.php?topic=6239.msg20460

While following up on this thread and reading the latest info posted to http://bugs.debian.org/687006#20 I see that the same code but translated with another compiler works!? As far as I can see the binary on tbm's site is still the 'faulty' one?

And further reading  http://bugs.debian.org/687006#25 I'd be keen to test the version with the new generic MMC/SDIO driver, as it "fixes an issue with most SDHC cards because of timeout delay" as I seem to suffer from that one as well (after power cycling the plug I have to wait a few seconds and have to press the reset button to get my SD card recognized by the system). Is there already a (publically) available binary (I'm not too good in compling stuff myself ;-)

outch, sorry to see you're in need to post your advertising here :-(