Skip to contentSkip to conversation

Improved fxload [Was: Re: fxload devpath]

DISCUSSION Wojciech A. Koszek 3 participants 5 messages Oct 12, 2015 – Oct 19, 2015

lore
Share & tools
lore

Wojciech A. Koszek

author
#0 lore raw

Hello,

In May 2010 I've fixed fxload by adding LibUSB support.

After seeing Carl's e-mail I dug out a patches from backup, and made a repo out of it:

https://github.com/wkoszek/fxload

So basically fxload would gain LibUSB support and much easier usage, since the paths which fxload requires right now change for some devices doing re-enumeration.

Back then I failed to get any replies. Retrying now in hope we could get these fixes into mainline.

Thanks,

Wojciech

Quoted 43 lines · Andrei Borzenkov

12.10.2015 01:29, Carl Karsten пишет:

Quoted 13 lines

man fxload - Firmware download to EZ-USB devices

fxload [ -v ] [ -l ] [ -D devpath ] ...

-D devpath
Specifies the "usbfs" path name for the device in
question, such
as /proc/bus/usb/004/080. This takes precedence over
any DEVICE
environment variable that may be set.

How do I figure out what the devpath is for the device I plugged in?

Quoted 8 lines

or.. how do I know what devnum will get assigned?

The device(s) I am working with:

juser@dc10b:~$ lsusb -s 2:9; lsusb -s 2:10
Bus 002 Device 009: ID 04e2:1410 Exar Corp.
Bus 002 Device 010: ID 1443:0007 Digilent Development board JTAG

Should be /dev/bus/usb/002/010 etc.

Quoted 12 lines

Ubuntu trusty lts
Linux dc10b 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Signature · 6 lines
Carl K
-- 
To unsubscribe from this list: send the line "unsubscribe 
linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 4 lines
To unsubscribe from this list: send the line "unsubscribe 
linux-hotplug" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw

Thank you. I'll try this out in the next day or so.

Quoted 69 lines · Wojciech A. Koszek

Hello,

In May 2010 I've fixed fxload by adding LibUSB support.

After seeing Carl's e-mail I dug out a patches from backup, and made a repo out of it:

https://github.com/wkoszek/fxload

So basically fxload would gain LibUSB support and much easier usage, since the paths which fxload requires right now change for some devices doing re-enumeration.

Back then I failed to get any replies. Retrying now in hope we could get these fixes into mainline.

Thanks,

Wojciech

Quoted 45 lines · Andrei Borzenkov

12.10.2015 01:29, Carl Karsten пишет:

Quoted 14 lines

man fxload - Firmware download to EZ-USB devices

fxload [ -v ] [ -l ] [ -D devpath ] ...

-D devpath
Specifies the "usbfs" path name for the device in
question, such
as /proc/bus/usb/004/080. This takes precedence over any
DEVICE
environment variable that may be set.

How do I figure out what the devpath is for the device I plugged in?

Quoted 8 lines

or.. how do I know what devnum will get assigned?

The device(s) I am working with:

juser@dc10b:~$ lsusb -s 2:9; lsusb -s 2:10
Bus 002 Device 009: ID 04e2:1410 Exar Corp.
Bus 002 Device 010: ID 1443:0007 Digilent Development board JTAG

Should be /dev/bus/usb/002/010 etc.

Quoted 4 lines

Ubuntu trusty lts
Linux dc10b 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Quoted 8 lines

--
Carl K
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Carl K
#2 lore raw
In reply to Wojciech A. Koszek

looks like I need to set LIBUSB_SUPPORT

$ LIBUSB_SUPPORT=1 make

And now it is working as described, which is very nice. +1 mainline

Q: What happens if there are 2 devices plugged in?

I am assuming it uses the first one it finds.
For my usage that is fine.
You might want to add an index or something, although in those cases the person can just use the devpath. I expect most people will be using this from a udev rule that acts on the device being plugged in.

Quoted 69 lines · Wojciech A. Koszek

Hello,

In May 2010 I've fixed fxload by adding LibUSB support.

After seeing Carl's e-mail I dug out a patches from backup, and made a repo out of it:

https://github.com/wkoszek/fxload

So basically fxload would gain LibUSB support and much easier usage, since the paths which fxload requires right now change for some devices doing re-enumeration.

Back then I failed to get any replies. Retrying now in hope we could get these fixes into mainline.

Thanks,

Wojciech

Quoted 45 lines · Andrei Borzenkov

12.10.2015 01:29, Carl Karsten пишет:

Quoted 14 lines

man fxload - Firmware download to EZ-USB devices

fxload [ -v ] [ -l ] [ -D devpath ] ...

-D devpath
Specifies the "usbfs" path name for the device in
question, such
as /proc/bus/usb/004/080. This takes precedence over any
DEVICE
environment variable that may be set.

How do I figure out what the devpath is for the device I plugged in?

Quoted 8 lines

or.. how do I know what devnum will get assigned?

The device(s) I am working with:

juser@dc10b:~$ lsusb -s 2:9; lsusb -s 2:10
Bus 002 Device 009: ID 04e2:1410 Exar Corp.
Bus 002 Device 010: ID 1443:0007 Digilent Development board JTAG

Should be /dev/bus/usb/002/010 etc.

Quoted 4 lines

Ubuntu trusty lts
Linux dc10b 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Quoted 8 lines

--
Carl K
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Carl K
#3 lore raw
In reply to Wojciech A. Koszek
Quoted 7 lines · Wojciech A. Koszek

Hello,

In May 2010 I've fixed fxload by adding LibUSB support.

After seeing Carl's e-mail I dug out a patches from backup, and made a repo out of it:

Quoted 8 lines

https://github.com/wkoszek/fxload

So basically fxload would gain LibUSB support and much easier usage, since the paths which fxload requires right now change for some devices doing re-enumeration.

Back then I failed to get any replies. Retrying now in hope we could get these fixes into mainline.

libusb project shipped with fxload as an example as well. Not so sure which version is better.
https://github.com/libusb/libusb/tree/master/examples

Signature · 1 line
Xiaofan
author
#4 lore raw
In reply to Wojciech A. Koszek

Carl,

Thanks for testing. I gave you the credit for mentioning LIBUSB_SUPPORT=1. I forgot about it.

W.

Quoted 83 lines · Carl Karsten

looks like I need to set LIBUSB_SUPPORT

$ LIBUSB_SUPPORT=1 make

And now it is working as described, which is very nice. +1 mainline

Q: What happens if there are 2 devices plugged in?

I am assuming it uses the first one it finds.
For my usage that is fine.
You might want to add an index or something, although in those cases the person can just use the devpath. I expect most people will be using this from a udev rule that acts on the device being plugged in.

Quoted 64 lines · Wojciech A. Koszek

Hello,

In May 2010 I've fixed fxload by adding LibUSB support.

After seeing Carl's e-mail I dug out a patches from backup, and made a repo out of it:

https://github.com/wkoszek/fxload

So basically fxload would gain LibUSB support and much easier usage, since the paths which fxload requires right now change for some devices doing re-enumeration.

Back then I failed to get any replies. Retrying now in hope we could get these fixes into mainline.

Thanks,

Wojciech

Quoted 41 lines · Andrei Borzenkov

12.10.2015 01:29, Carl Karsten пишет:

Quoted 13 lines

man fxload - Firmware download to EZ-USB devices

fxload [ -v ] [ -l ] [ -D devpath ] ...

-D devpath
Specifies the "usbfs" path name for the device in
question, such
as /proc/bus/usb/004/080. This takes precedence over any
DEVICE
environment variable that may be set.

How do I figure out what the devpath is for the device I plugged in?

Quoted 8 lines

or.. how do I know what devnum will get assigned?

The device(s) I am working with:

juser@dc10b:~$ lsusb -s 2:9; lsusb -s 2:10
Bus 002 Device 009: ID 04e2:1410 Exar Corp.
Bus 002 Device 010: ID 1443:0007 Digilent Development board JTAG

Should be /dev/bus/usb/002/010 etc.

Quoted 4 lines

Ubuntu trusty lts
Linux dc10b 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Quoted 8 lines

--
Carl K
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html