Skip to main content ↑ ↓

Show Posts

This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.

Messages - gebhardt

1
Open Bench Logic Sniffer / Re: fw_update is not working in linux
Hello MickM,

thank you very much for your reply!
Honestly I'm confused about the different fwloader programs.

I'm owning an IR USB Toy.

First I stumbled upon the thread 3697
"fw_update not working in linux or OS X"
Then google lead me to this thread (1628). I did not
realize that this thread treats the Open Bench Logic Sniffer
since its subject "fw_update is not working in linux"
was almost identical and the fw_update cli syntax and the
error messages are identical to the output which I get.

The code that you mention above, compiles to an executable "ols_fwloader"
which has a different command line syntax than fw_update.

How does ols_fwloader relate to fw_loader? Shouldn't I use fw_loader?

Somwhat puzzled, Thomas
2
Open Bench Logic Sniffer / Re: fw_update is not working in linux
Hi,

this is just a me-too post :-( , mentioning that even with the current git

commit ef622b2038dab8eecc85d98a30aeca3130b9d432
Author: Dobrica Pavlinusic <...>
Date:  Mon Apr 1 16:04:05 2013 +0200

source, compiled with

LIBS=-lusb ./configure --with-usb-includes=/usr/include
make

I get the same error as zelea2 .

# ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix /tmp/firmware/USBIRToy.v22.hex
U2IO flash erasing: FAILED.
Device is not found.
Operation aborted.

My OS is ubuntu 12.04 LTS, i386
libusb++-0.1-4c2                              2:0.1.12-20       
libusb++-dev                                  2:0.1.12-20       
libusb-0.1-4                                  2:0.1.12-20       
libusb-1.0-0                                  2:1.0.9~rc3-2ubuntu1
libusb-1.0-0-dev                              2:1.0.9~rc3-2ubuntu1
libusb-dev                                    2:0.1.12-20       
libusbmuxd1                                  1.0.7-2ubuntu0.1   

A system trace reveals an "Inappropriate ioctl" error

open("/dev/bus/usb/003/003", O_RDWR)    = 3
ioctl(3, USBDEVFS_IOCTL or USBDEVFS_IOCTL32, 0xbfb6f1e0) = -1 ENOTTY (Inappropriate ioctl for device)

/dev/bus/usb/003/003 points to:
Bus 003 Device 003: ID 04d8:fd08 Microchip Technology, Inc.

Cheers, Thomas

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01212279440session_write_close ( )...(null):0
20.01252411016ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01252411792Database_MySQL->query( ).../DatabaseHandler.php:119
40.05582550512Database_MySQL->error( ).../Db-mysql.class.php:273