• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3 4 ... 10
16  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: May 09, 2013, 03:54:26 AM
Just a minor note:

Quote from: odoll
... 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 ...

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 ;-)
17  Linux Stuff / Kernel / Re: Dreamplug - IPTables on: April 29, 2013, 09:55:48 AM
Console access (via JTAG adapter) or are you booting from an SD? If so, mount your SD in another system and fix your config?
18  Hardware and U-Boot firmware / U-Boot stuff / Re: Latest Uboot? on: March 26, 2013, 01:05:42 PM
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.
19  Hardware and U-Boot firmware / U-Boot stuff / Re: Latest Uboot? on: March 26, 2013, 04:28:04 AM
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
20  General Category / General Discussion / Accessing SheevaPlug Serial (JTAG) Console from Windows 8 on: March 25, 2013, 12:52:30 PM
(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.
21  General Category / General Discussion / Re: Accessing SheevaPlug Serial (JTAG) Console from Windows7 on: March 24, 2013, 02:28:06 PM
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.
22  General Category / General Discussion / Re: Accessing SheevaPlug Serial (JTAG) Console from Windows7 on: March 24, 2013, 01:21:29 PM
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 Wink 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.
23  General Category / General Discussion / Re: Accessing SheevaPlug Serial (JTAG) Console from Windows 8 on: March 24, 2013, 12:45:15 PM
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!?!
24  Hardware and U-Boot firmware / U-Boot stuff / Re: Latest Uboot? on: March 22, 2013, 07:27:56 AM
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?!?
25  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: March 20, 2013, 07:40:15 AM
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
26  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: March 20, 2013, 07:04:23 AM
I filed a bug report in the Debian Bug Tracking system so the u-boot maintainer in Debian, Clint Adams, is aware of this issue: http://bugs.debian.org/687006

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 ;-)
27  General Category / General Discussion / Re: Raspberry PI on: September 21, 2012, 11:53:45 AM
outch, sorry to see you're in need to post your advertising here :-(
28  Linux Stuff / General Linux questions / Re: Old Debian on new plug and wrong mac address on: September 06, 2012, 08:39:00 AM
After changing the MAC in U-Boot please also check  /etc/udev/rules.d/70-persistent-net.rules and verify that no spurious mac addresses appear there
29  Hardware and U-Boot firmware / U-Boot stuff / SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: July 17, 2012, 12:25:59 PM
By accident I ran across the new DENX u-boot version 2012.04.01-2 (also for the SheevaPlug) at http://people.debian.org/~tbm/u-boot/2012.04.01-2/sheevaplug/

Being brave I updated my SheevaPlug from 2011.12-3 to 2012.04.01-2, but just to notice, that it wouldn't boot the Debian Squeeze from the SDHC card any longer. Thus it falls back to NAND:

Quote
Marvell>> reset
resetting ...


U-Boot 2012.04.01 (Jun 01 2012 - 02:27:06)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
SDHC found. Card desciption is:
Manufacturer:       0x01, OEM "PA"
Product name:       "SQ04G", revision 7.4
Serial number:      1940688398
Manufacturing date: 7/2011
CRC:                0x00, b0 = 0
mmc1 is available
Loading file "/uImage" from mmc device 0:1 (xxa1)
1431936 bytes read
Loading file "/uInitrd" from mmc device 0:1 (xxa1)
5684091 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel 2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431872 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.38.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2798752 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
[...]

After downgrading to 2011.12-3, everything works again as expected:

Quote
Marvell>> reset
resetting ...


U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
SDHC found. Card desciption is:
Manufacturer:       0x01, OEM "PA"
Product name:       "SQ04G", revision 7.4
Serial number:      1940688398
Manufacturing date: 7/2011
CRC:                0x00, b0 = 0
mmc1 is available
Loading file "/uImage" from mmc device 0:1 (xxa1)
1431936 bytes read
Loading file "/uInitrd" from mmc device 0:1 (xxa1)
5684091 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel 2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431872 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Debian ramdisk 2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5684027 Bytes = 5.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

These are my u-boot environment variables:
Code:
baudrate=115200
bootargs_console=console=ttyS0,115200
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=194.174.11.254:194.174.11.5:194.174.11.1:255.255.255.0:Share:eth0:none
bootcmd=usb start; setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x00800000 0x01100000; run bootcmd_nand
bootcmd_mmc=mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootdelay=3
ethact=egiga0
ethaddr=00:50:43:01:d8:11
serverip=194.174.11.6
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;
30  Hardware and U-Boot firmware / U-Boot stuff / Re: SD card / u-boot problems on: May 21, 2012, 05:55:21 AM
I'v my SP running smotthly from an SD with the latest DENX u-boot. However if you consider a downgrade, please alos consider to take a look at either pingtoo's patched 3.4.27 versions. I think you can find them attached to pingtoo's posts in this forum.
Pages: 1 [2] 3 4 ... 10