Offline

As I am new to this site, I am unable to bump old threads. Therefore I create a new one. I just received my freshly bought flashcart, trying to program it using ems-flasher. Compiled under Ubuntu 13.04 GNU/Linux.

johan@crypt:~/Projects/ems-flasher-0.03$ tail -f /var/log/syslog&
[1] 4591
johan@crypt:~/Projects/ems-flasher-0.03$ sudo ./ems-flasher --write lsdj.gb 
Nov 26 11:33:01 crypt kernel: [166453.168511] usb 1-1.2: reset full-speed USB device number 9 using ehci-pci
Could not find/open device, is it plugged in?
Nov 26 11:33:06 crypt kernel: [166458.239807] usb 1-1.2: USB disconnect, device number 9
johan@crypt:~/Projects/ems-flasher-0.03$ Nov 26 11:33:07 crypt kernel: [166458.304794] usb 1-1.2: new full-speed USB device number 10 using ehci-pci
Nov 26 11:33:07 crypt kernel: [166458.393021] usb 1-1.2: New USB device found, idVendor=4670, idProduct=9394
Nov 26 11:33:07 crypt kernel: [166458.393032] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 26 11:33:07 crypt mtp-probe: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Nov 26 11:33:07 crypt mtp-probe: bus: 1, device: 10 was not an MTP device

As you can see above, the device disappears from the system when starting the ems-flasher and shortly after reappears. The device is working, as I am able to flash it using a Windows computer.

Offline
SLC, UT

Obvious solutions: try other USB ports, other cables, etc.

I think you need to give yourself permissions.
Try doing what the FAQ says here: http://lacklustre.net/projects/ems-flasher/faq.html

Offline

Been there done that. smile No sorry, as you see I run as sudo so there is no permission issue. The USB is reset as a result of the command, so obviously I have permission to do nasty things with the USB.

Already tried different ports, but I will try on another computer as well.

Offline
Toronto, Ontario, Canada

What version of libusb package does your computer have installed currently?

Offline
SLC, UT

I would still use the command. Takes about 1 second and at least we'll know.

Offline

I've now added a udev rule as suggested. Now I can reproduce the issue not being sudo. The device is still resetting.

libusb package in use: libusb-1.0-0:amd64

(Please note that it is resetting no matter what command you issue, including --read)

Last edited by johey (Nov 27, 2013 8:56 am)