Sheeva installer socket error

DanielSjoholm

Newbie

Posts: 10

« on: 20 November 2009, 06:52:30 pm »

So i tried to follow all resources i could find on how to use the sheeva-installer-1.0 utility to change to ubifs (checked your thread here too) and update kernel and what not, but when i came to the final part of actually running it i got this in my face (yes, I'm root, and i ran it as php runme.php nand):

Code:

**** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.3.1 (2009-11-13-14:19)
$URL$
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Error: couldn't bind to socket: Address already in use
**** openocd FAILED
**** Is the mini USB cable connected?
**** Try powering down, then replugging the Sheevaplug

Tried with both the supplied openocd and a fresh from the fedora repositories (which is version 0.3.1), both give me the same issue, and rasing log level to 3 (highest, default is 2), gives me no new information.
I've tried rebooting both my desktop and the sheeva numerous times, tried with and without minicom connected, no change.

Oh - and this interresting snippet turns out in /var/log/messages:

Code:

Nov 20 19:41:51 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

Googling either of my error messages have not yielded any result, and thus i turn to you :p

Regards, Daniel


	Logged

NewIT_Marcus

Administrator
Hero Member

Posts: 960

Re: Sheeva installer socket error

« Reply #1 on: 20 November 2009, 11:54:16 pm »

These are the things that I would try:

1. type php runme.php nand; use reset pin on Sheevaplug; hit Enter a second or two after you reset the plug.

2. Change 2000 kHz to 100 or 500.

3. Reboot the host PC.

As for usb 2-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1 - I get that too, and it works on my (Ubuntu 9.10) host.

I don't know if openocd should be referring to "sockets", so I am surprised by that message. If the above suggestions don't improve matters, you'd better tell us more about the host configuration.


	Logged

DanielSjoholm

Newbie

Posts: 10

Re: Sheeva installer socket error

« Reply #2 on: 21 November 2009, 04:09:18 pm »

For step one, should i still have the terminal up? (The one to interrupt the boot sequence with)
I've tried to reset and then run the script as you said, same error.
I've tried it in the different speeds you said also, no go.
And rebooting.. well, done it a few times (unplugging everything and powering sheeva down etc..), not working.

Host configuration?
Linux dyx2 2.6.27.37-170.2.104.fc10.i686 #1 SMP Mon Oct 12 22:01:53 EDT 2009 i686 athlon i386 GNU/Linux
Fedora 10
libftdi-0.16-4.fc10.i386
openocd-0.3.1-1.fc10.i386

Tried with selinux both on and off, no change, also disabled my local firewall incase it was doing anything funny, nothing.
Not sure what other relevant information would be...

Code:

Nov 21 16:54:59 dyx2 kernel: usb 2-6: new full speed USB device using ohci_hcd and address 5
Nov 21 16:54:59 dyx2 kernel: usb 2-6: configuration #1 chosen from 1 choice
Nov 21 16:54:59 dyx2 kernel: usb 2-6: New USB device found, idVendor=9e88, idProduct=9e8f
Nov 21 16:54:59 dyx2 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 21 16:54:59 dyx2 kernel: usb 2-6: Product: SheevaPlug JTAGKey FT2232D B
Nov 21 16:54:59 dyx2 kernel: usb 2-6: Manufacturer: FTDI
Nov 21 16:54:59 dyx2 kernel: usb 2-6: SerialNumber: FTSFBVPM
Nov 21 16:54:59 dyx2 kernel: usbcore: registered new interface driver usbserial
Nov 21 16:54:59 dyx2 kernel: usbserial: USB Serial support registered for generic
Nov 21 16:54:59 dyx2 kernel: usbcore: registered new interface driver usbserial_generic
Nov 21 16:54:59 dyx2 kernel: usbserial: USB Serial Driver core
Nov 21 16:54:59 dyx2 kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Nov 21 16:54:59 dyx2 kernel: ftdi_sio 2-6:1.0: FTDI USB Serial Device converter detected
Nov 21 16:54:59 dyx2 kernel: ftdi_sio: Detected FT2232C
Nov 21 16:54:59 dyx2 kernel: usb 2-6: FTDI USB Serial Device converter now attached to ttyUSB0
Nov 21 16:54:59 dyx2 kernel: ftdi_sio 2-6:1.1: FTDI USB Serial Device converter detected
Nov 21 16:54:59 dyx2 kernel: ftdi_sio: Detected FT2232C
Nov 21 16:54:59 dyx2 kernel: usb 2-6: FTDI USB Serial Device converter now attached to ttyUSB1
Nov 21 16:54:59 dyx2 kernel: usbcore: registered new interface driver ftdi_sio
Nov 21 16:54:59 dyx2 kernel: ftdi_sio: v1.4.3:USB FTDI Serial Converters Driver
Nov 21 16:57:49 dyx2 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Nov 21 16:57:49 dyx2 kernel: ftdi_sio 2-6:1.0: device disconnected
Nov 21 16:57:49 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:58:44 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:58:51 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:59:14 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:59:36 dyx2 ntpd[2379]: synchronized to 193.10.7.246, stratum 1
Nov 21 16:59:37 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:59:43 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 16:59:48 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:00:53 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:01:43 dyx2 dbus: avc: received setenforce notice (enforcing=0)
Nov 21 17:01:47 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:28 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:37 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:39 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:41 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:43 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:46 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:03:50 dyx2 kernel: usb 2-6: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
Nov 21 17:04:16 dyx2 dbus: avc: received setenforce notice (enforcing=1)

Log of a few attempts (does ttyUSB0 also drop out on your system after a while? I'm unsure if that was when i did the first reset or if it was just a timed event.. My terminal is attached to ttyUSB1 anyway, as USB0 did not seem to work)


	Logged

NewIT_Marcus

Administrator
Hero Member

Posts: 960

Re: Sheeva installer socket error

« Reply #3 on: 21 November 2009, 04:52:12 pm »

Quote from: DanielSjoholm on 21 November 2009, 04:09:18 pm

My reason for suggesting step (1) was that I have run the installer on many plugs, and some of them would only respond to openocd during the early U-Boot phase (ie not if the plug were are at a more advanced stage of boot or login). Terminal being up shouldn't be an issue, although you don't get to see anything in the terminal until after openocd does its thing.

Likewise, because my first plug wouldn't work at 2000 kHz, and I had to ramp it down to 500 kHz, I just left it there and never even tried 200 kHz again., Maybe I should.

Quote from: DanielSjoholm on 21 November 2009, 04:09:18 pm

Host configuration?
Linux dyx2 2.6.27.37-170.2.104.fc10.i686 #1 SMP Mon Oct 12 22:01:53 EDT 2009 i686 athlon i386 GNU/Linux
Fedora 10
libftdi-0.16-4.fc10.i386
openocd-0.3.1-1.fc10.i386

Tried with selinux both on and off, no change, also disabled my local firewall incase it was doing anything funny, nothing.
Not sure what other relevant information would be...

Code:

Are you using the plugcomputer.org "installer", or a hand-built procecedure? Results may well vary according to the version of openocd, certainly in terms of any errors introduced during compilation.

The plugcomputer.org version is rather well tested; I've probably run it over 100 times and I have never seen the error message that you report. I would strongly recommend that you try their build.

Regarding your final question / point - under Ubuntu 9.04, I had 2 devices. There never was any point in establishing a terminal connection to one of them, the device that openocd would be using, since that's not a terminal device. Ubuntu 9.10 is "smart" enough to know this and discard it, leaving just one device. I never noticed either device disappear under either version of Ubuntu, although I was able to trigger the line to be temporarily dropped sometimes when connecting devices to the USB socket (ie a reset / disconnection was being inadvertently triggered).

Some users have reported consistent failures with openocd under one platform, but success under another. Me, I wouldn't want to have to attempt it under Windows, but you might need to try other hosts. I know there was talk of a live CD that would contain a suitable setup for executing openocd, but I think that's all it was - a bright idea, and some talk.


	Logged

DanielSjoholm

Newbie

Posts: 10

Re: Sheeva installer socket error

« Reply #4 on: 22 November 2009, 02:09:23 pm »

Yeah i gave up on my Fedora 10 to do the flashing and tried it on a 9.10 ubuntu system, first flash ended with major issues (it erased block 5-6 and then it went silent for an unknown duration, at least 5 minutes, only to spew up read errors), second flash went OK and I'm now running the new stuff

Now on to getting my own built 31.X kernel on to an SD card and having it boot from there..


« Last Edit: 22 November 2009, 02:12:08 pm by DanielSjoholm »	Logged

NewIT_Marcus

Administrator
Hero Member

Posts: 960

Re: Sheeva installer socket error

« Reply #5 on: 22 November 2009, 02:39:26 pm »

Using openocd for the first time can be a bit intimidating, because you really don't quite know what to expect.

When creating an SD-bootable configuration and using an unformatted SD card, I find that the first attempt doesn't complete. But a second one does. If I run the process using a formatted SD card, it works first time. I wonder if that is the scenario that you encountered. (There's probably a fix that can be applied to this method, but I haven't looked into it at this time).

I'm pleased that you have resolved the problem.


	Logged

Pages: [1]

« previous next »