• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
« previous next »
Author Topic: Installer Error  (Read 1207 times)
byteman
Newbie
*

Karma: 1
Posts: 26


View Profile
« on: January 19, 2010, 09:09:46 AM »
Trying to run the installer 1.0.  Have tried to follow all of the instructions in the wiki and the readme.txt file.  Here's what is happening:

Code:
sudo php runme.php nand

 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_nand:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
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

dmesg:
[2750591.328513] USB Serial support registered for FTDI USB Serial Device
[2750591.328606] usbcore: registered new interface driver ftdi_sio
[2750591.328611] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
[2750616.788025] usb 2-1: new full speed USB device using uhci_hcd and address 17
[2750616.989509] usb 2-1: configuration #1 chosen from 1 choice
[2750616.998504] usb 2-1: Ignoring serial port reserved for JTAG
[2750617.003776] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[2750617.003838] usb 2-1: Detected FT2232C
[2750617.003845] usb 2-1: Number of endpoints 2
[2750617.003849] usb 2-1: Endpoint 1 MaxPacketSize 64
[2750617.003853] usb 2-1: Endpoint 2 MaxPacketSize 64
[2750617.003858] usb 2-1: Setting MaxPacketSize 64
[2750617.010489] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[2751166.706551] usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

 lsusb
Bus 002 Device 017: ID 9e88:9e8f 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 413c:3200 Dell Computer Corp. Mouse
Bus 001 Device 002: ID 0fde:ca01 
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Any suggestions???
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #1 on: January 19, 2010, 09:34:14 AM »
The installer unable to open your /dev/ttyUSB1. please verify you have ftdi-sio module loaded. If you do have the module loaded then verify you have /dev/ttyUSB1, if you do not have /dev/ttyUSB1 then you need to check your sheevaplug's vendor ID and product ID by doing lsusb and find the relevant device.

Good luck Smiley
Logged
Good Luck Smiley

byteman
Newbie
*

Karma: 1
Posts: 26


View Profile
« Reply #2 on: January 19, 2010, 11:26:57 AM »
OK, I had followed the instructions for newer plugs and changed the "openocd/config/board/sheevaplug.cfg" file, but changed it back to agree with my vendor and product id.  Still getting error, but different.   

Code:
sudo php runme.php nand

 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_nand:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: JTAG communication failure: check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Error: unexpected Feroceon EICE version signature
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "openocd/config/board/sheevaplug.cfg", line 21:
     **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug



sudo lsmod |grep ftd
ftdi_sio               52580  1
usbserial              36232  3 ftdi_sio


dmesg (after plug has rebooted)
[2750616.788025] usb 2-1: new full speed USB device using uhci_hcd and address 17
[2750616.989509] usb 2-1: configuration #1 chosen from 1 choice
[2750616.998504] usb 2-1: Ignoring serial port reserved for JTAG
[2750617.003776] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[2750617.003838] usb 2-1: Detected FT2232C
[2750617.003845] usb 2-1: Number of endpoints 2
[2750617.003849] usb 2-1: Endpoint 1 MaxPacketSize 64
[2750617.003853] usb 2-1: Endpoint 2 MaxPacketSize 64
[2750617.003858] usb 2-1: Setting MaxPacketSize 64
[2750617.010489] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[2751166.706551] usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
[2758194.195761] usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
[2758544.996300] usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

The plug reboots immediately upon running "runme.php nand"Huh
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #3 on: January 19, 2010, 12:24:10 PM »
I notice in you dmesg output there is a message
Quote
[2750616.998504] usb 2-1: Ignoring serial port reserved for JTAG
.

May be you can get around by modify runme.php, in it any reference to ttyUSB1 change to ttyUSB0. I think someone in this forum have report they were able to work with ttyUBS0.

Or ther other possiblility is you have the brltty package installed which can cause ttyUSB1 disappearing. you can try to remove the brltty package if this is the case.

Good luck Smiley
Logged
Good Luck Smiley

byteman
Newbie
*

Karma: 1
Posts: 26


View Profile
« Reply #4 on: January 19, 2010, 02:43:31 PM »
Hi pingtoo -

The brltty package is not installed.  And I find no references to ttyUSB0 or ttyUSB1 in the runme.php file???

So I rebooted the host - here's what I get now:

Code:
sudo php runme.php nand
[sudo] password for geoff:

 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)
 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_nand:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:6d:45
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: JTAG communication failure: check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Error: unexpected Feroceon EICE version signature
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "openocd/config/board/sheevaplug.cfg", line 21:
     **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

dmesg
[  272.960025] usb 2-1: new full speed USB device using uhci_hcd and address 2
[  273.162095] usb 2-1: configuration #1 chosen from 1 choice
[  273.261152] usbcore: registered new interface driver usbserial
[  273.261185] USB Serial support registered for generic
[  273.261246] usbcore: registered new interface driver usbserial_generic
[  273.261251] usbserial: USB Serial Driver core
[  273.301182] USB Serial support registered for FTDI USB Serial Device
[  273.301347] usb 2-1: Ignoring serial port reserved for JTAG
[  273.301449] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
[  273.301502] usb 2-1: Detected FT2232C
[  273.301508] usb 2-1: Number of endpoints 2
[  273.301513] usb 2-1: Endpoint 1 MaxPacketSize 64
[  273.301517] usb 2-1: Endpoint 2 MaxPacketSize 64
[  273.301521] usb 2-1: Setting MaxPacketSize 64
[  273.325543] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[  273.325588] usbcore: registered new interface driver ftdi_sio
[  273.325593] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
[  634.352261] usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

What now???
« Last Edit: January 19, 2010, 03:09:41 PM by byteman » Logged

boerner
Jr. Member
**

Karma: 0
Posts: 54


View Profile
« Reply #5 on: January 19, 2010, 03:23:35 PM »
Couple of questions...

What distro are you using?

If you tail /var/log/messages after you plug the Sheeva in via USB do you see anything that indicates it is detected? Sometimes the cable isn't fully seated into the plug itself...
Logged

mhtsaras
Newbie
*

Karma: 0
Posts: 42


View Profile
« Reply #6 on: January 19, 2010, 03:33:03 PM »
All my problems and many error messages like yours, disappeared when I compiled on my host ubuntu pc,the latest openocd.
   
Logged

byteman
Newbie
*

Karma: 1
Posts: 26


View Profile
« Reply #7 on: January 19, 2010, 04:19:26 PM »
Quote from: boerner on January 19, 2010, 03:23:35 PM
Couple of questions...

What distro are you using?

If you tail /var/log/messages after you plug the Sheeva in via USB do you see anything that indicates it is detected? Sometimes the cable isn't fully seated into the plug itself...



Using xubuntu 9.10

Following is the log from unplugging, then plugging back in the Sheeva usb - BTW, the "screen" terminal connects just fine.

Code:
Jan 19 16:12:25 gtnet-server kernel: [ 5112.688086] usb 2-1: USB disconnect, address 2
Jan 19 16:12:25 gtnet-server kernel: [ 5112.688527] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Jan 19 16:12:25 gtnet-server kernel: [ 5112.688556] ftdi_sio 2-1:1.1: device disconnected
Jan 19 16:14:28 gtnet-server kernel: [ 5235.640043] usb 2-1: new full speed USB device using uhci_hcd and address 3
Jan 19 16:14:28 gtnet-server kernel: [ 5235.846111] usb 2-1: configuration #1 chosen from 1 choice
Jan 19 16:14:28 gtnet-server kernel: [ 5235.856138] usb 2-1: Ignoring serial port reserved for JTAG
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861200] ftdi_sio 2-1:1.1: FTDI USB Serial Device converter detected
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861259] usb 2-1: Detected FT2232C
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861265] usb 2-1: Number of endpoints 2
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861270] usb 2-1: Endpoint 1 MaxPacketSize 64
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861274] usb 2-1: Endpoint 2 MaxPacketSize 64
Jan 19 16:14:28 gtnet-server kernel: [ 5235.861278] usb 2-1: Setting MaxPacketSize 64
Jan 19 16:14:28 gtnet-server kernel: [ 5235.866338] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
Logged

byteman
Newbie
*

Karma: 1
Posts: 26


View Profile
« Reply #8 on: January 19, 2010, 04:33:26 PM »
Quote from: mhtsaras on January 19, 2010, 03:33:03 PM
All my problems and many error messages like yours, disappeared when I compiled on my host ubuntu pc,the latest openocd.
   

So I shutdown the "screen" terminal (thought I had tried this both ways) and I compiled openocd-0.3.1 and it worked.  So I don't know which change solved the problem, but I'm happy!

Thanks everyone!
Logged

Pages: [1]
Print
« previous next »
Jump to: