Sheevaplug installer v1.0 could not find serial interface of plug

[donmat]

Hi,

I was able to install install both the FTJAG and USB-serial drivers, and putty in to the plug at 115200bps, 8 data bits, 1 stop bit, with no XON/XOFF. Windows Device Manager also was able to discover USB Serial Converter A & B. I checked "Load VCP" on B as how this tutorial (http://plugcomputer.org/plugwiki/index.php/Installing_Debian_To_Flash#Burn_a_New_Kernel) told me to. It's a great tutorial that doesn't beat around the bush.

I need to flash a new working kernel  (sheeva-with-linux's 2.6.32.2) that is able to mount NTFS. Based on the tutorial I need to upgrade u-boot to version 3.4.19. I choose the TFTP method. After I typed in these commands under u-boot CLI environment the whole thing just went dead. 

   setenv ipaddr 169.254.1.1
   setenv serverip 169.254.78.185
   tftpboot 0x0800000 uboot.bin
   nand erase 0x0 0xa0000
   nand write 0x0800000 0x0 0xa0000
   reset

I then went on to try using sheevaplug installer v1.0, but runme.exe just would not discover the linux plug via serial, the error messages are:

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

Anyone please shed some light.

Don

[donmat]

it worked, sheevaplug_installer could not detect the plug over serial on Windows, I got it working perfectly on Linux though..

[4cx1000a]

I've just spent two days trying to get sheevaplug-installer-1.0 to work on two different computers (one running Ubuntu Hardy Heron, the other running Debian Lenny amd64). It always fails with:

Error: The specified JTAG interface was not found (ft2232)
The following JTAG interfaces are available:
Runtime error, file "/usr/local/share/openocd/scripts/interface/sheevaplug.cfg", line 7:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplugumarc@amphiuma:~/sheeva

Yet according to dmesg, the plug is there:

[  746.108193] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0
[  746.112629] usb 4-1: New USB device found, idVendor=9e88, idProduct=9e8f
[  746.112633] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  746.112636] usb 4-1: Product: SheevaPlug JTAGKey FT2232D B
[  746.112638] usb 4-1: Manufacturer: FTDI
[  746.112640] usb 4-1: SerialNumber: FTSY6XKQ

However, lsusb does not see it:

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 9e88:9e8f 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 045e:0059 Microsoft Corp. Wireless IntelliMouse Explorer
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I am at my wits end. I want to use this plug at a radio station transmitter site, where it has to talk to an RS-232 port on a device called an RBDS generator. The OS in the plug as shipped does not seem to be able to do that, so I'm trying to upgrade to a later version that can.

Does anyone have any ideas?

Thanks,

Rob

[rooster]

I think lsusb did find it:

Bus 004 Device 004: ID 9e88:9e8f 

Are you running a 64bit machine?
You might try the new qt based installer @ http://sourceforge.net/projects/esia/

I have it working on my XP and Ubuntu9.10 32bit machines

[4cx1000a]

Are you running a 64bit machine?
You might try the new qt based installer @ http://sourceforge.net/projects/esia/

One of my machines is 64-bit; unfortunately the one that isn't is running Ubuntu 8.04, and the qt-based installer won't install on it.

I guess the next thing to try is a Windows machine at work.

[4cx1000a]

Well, I tried sheevaplug-installer-1.0 from the Windows machine.

The good news is that it can talk to the plug, which the Linux version could not.

The bad news is that after it was done, I rebooted and got:

4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

I assume this means that whatever the installer loaded into the plug failed some sort of checksum test.

Just for yuks, I restarted the plug after removing the USB stick to see if it was trying to boot from the stick; it wasn't. Whatever it's loading that has the bad checksum is burned into memory.  Did I start with a bad copy of the installer?

[rooster]

I guess that somewhere during the installation an error ocured, can you post the console output?
I would also try the new installer, it has some additional failure checking and gives more information to user if something fails.

[4cx1000a]

Here is what the console says:

        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000

^MReading data from 0x100000 --   0% complete.^MReading data from 0x10a000 --   1% complete.^MReading data from 0x114000 --   2% complete.^MReading data from 0x11e800 --   3% complete.^MReading data from 0x128800 --   4% complete.^MReading data from 0x133000 --   5% complete.^MReading data from 0x13d000 --   6% complete.^MReading data from 0x147800 --   7% complete.^MReading data from 0x151800 --   8% complete.^MReading data from 0x15c000 --   9% complete.^MReading data from 0x166000 --  10% complete.^MReading data from 0x170800 --  11% complete.^MReading data from 0x17a800 --  12% complete.^MReading data from 0x185000 --  13% complete.^MReading data from 0x18f000 --  14% complete.^MReading data from 0x199800 --  15% complete.^MReading data from 0x1a3800 --  16% complete.^MReading data from 0x1ae000 --  17% complete.^MReading data from 0x1b8000 --  18% complete.^MReading data from 0x1c2800 --  19% complete.^MReading data from 0x1cc800 --  20% complete.^MReading data from 0x1d7000 --  21% complete.^MReading data from 0x1e1000 --  22% complete.^MReading data from 0x1eb800 --  23% complete.^MReading data from 0x1f5800 --  24% complete.^MReading data from 0x1ff800 --  25% complete.^MReading data from 0x20a000 --  26% complete.^MReading data from 0x214000 --  27% complete.^MReading data from 0x21e800 --  28% complete.^MReading data from 0x228800 --  29% complete.^MReading data from 0x233000 --  30% complete.^MReading data from 0x23d000 --  31% complete.^MReading data from 0x247800 --  32% complete.^M^MReading data from 0x251800 --  33% complete.^MReading data from 0x25c000 --  34% complete.^MReading data from 0x266000 --  35% complete.^MReading data from 0x270800 --  36% complete.^MReading data from 0x27a800 --  37% complete.^MReading data from 0x285000 --  38% complete.^MReading data from 0x28f000 --  39% complete.^MReading data from 0x299800 --  40% complete.^MReading data from 0x2a3800 --  41% complete.^MReading data from 0x2ae000 --  42% complete.^MReading data from 0x2b8000 --  43% complete.^MReading data from 0x2c2800 --  44% complete.^MReading data from 0x2cc800 --  45% complete.^MReading data from 0x2d7000 --  46% complete.^MReading data from 0x2e1000 --  47% complete.^MReading data from 0x2eb800 --  48% complete.^MReading data from 0x2f5800 --  49% complete.^MReading data from 0x2ff800 --  50% complete.^MReading data from 0x30a000 --  51% complete.^MReading data from 0x314000 --  52% complete.^MReading data from 0x31e800 --  53% complete.^MReading data from 0x328800 --  54% complete.^MReading data from 0x333000 --  55% complete.^MReading data from 0x33d000 --  56% complete.^MReading data from 0x347800 --  57% complete.^MReading data from 0x351800 --  58% complete.^MReading data from 0x35c000 --  59% complete.^MReading data from 0x366000 --  60% complete.^MReading data from 0x370800 --  61% complete.^MReading data from 0x37a800 --  62% complete.^MReading data from 0x385000 --  63% complete.^MReading data from 0x38f000 --  64% complete.^MReading data from 0x399800 --  65% complete.^M^MReading data from 0x3a3800 --  66% complete.^MReading data from 0x3ae000 --  67% complete.^MReading data from 0x3b8000 --  68% complete.^MReading data from 0x3c2800 --  69% complete.^MReading data from 0x3cc800 --  70% complete.^MReading data from 0x3d7000 --  71% complete.^MReading data from 0x3e1000 --  72% complete.^MReading data from 0x3eb800 --  73% complete.^MReading data from 0x3f5800 --  74% complete.^MReading data from 0x3ff800 --  75% complete.^MReading data from 0x40a000 --  76% complete.^MReading data from 0x414000 --  77% complete.^MReading data from 0x41e800 --  78% complete.^MReading data from 0x428800 --  79% complete.^MReading data from 0x433000 --  80% complete.^MReading data from 0x43d000 --  81% complete.^MReading data from 0x447800 --  82% complete.^MReading data from 0x451800 --  83% complete.^MReading data from 0x45c000 --  84% complete.^MReading data from 0x466000 --  85% complete.^MReading data from 0x470800 --  86% complete.^MReading data from 0x47a800 --  87% complete.^MReading data from 0x485000 --  88% complete.^MReading data from 0x48f000 --  89% complete.^MReading data from 0x499800 --  90% complete.^MReading data from 0x4a3800 --  91% complete.^MReading data from 0x4ae000 --  92% complete.^MReading data from 0x4b8000 --  93% complete.^MReading data from 0x4c2800 --  94% complete.^MReading data from 0x4cc800 --  95% complete.^MReading data from 0x4d7000 --  96% complete.^MReading data from 0x4e1000 --  97% complete.^MReading data from 0x4eb800 --  98% complete.^M^MReading data from 0x4f5800 --  99% complete.^MReading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

I've tried three different USB sticks, so that's unlikely to be the problem.

I've run across a couple of references to using tftp instead of a USB stick; are there instructions for that posted anywhere?

[minioak]

Sounds like you haven't set the mainlineLinux u-boot environment setting:

setenv arcNumber 2097
setenv mainlineLinux yes
saveenv

Regards

John