Thread: [Fx2lib-devel] FX2 Firmware device descriptor read/64, error -110
Status: Beta
Brought to you by:
mulicheng
Menu
▾
▴
fx2lib-devel
|
From: Christoph K. <chr...@we...> - 2014-08-13 11:53:34
|
Hi everyone,
I am new to the Cypress FX2 and USB development. Using Linux Mint 17.
I compiled the example firmware.
With cyc2fxprog it downloads to the fx2.
When I run it, I receive the following Kernel Error:
Aug 13 13:10:14 workstation kernel: [17091.746996] usb 1-1: new
high-speed USB device number 35 using ehci-pci
Aug 13 13:10:29 workstation kernel: [17106.846587] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:10:44 workstation kernel: [17122.050051] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:10:44 workstation kernel: [17122.265909] usb 1-1: new
high-speed USB device number 36 using ehci-pci
Aug 13 13:10:59 workstation kernel: [17137.365421] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:11:14 workstation kernel: [17152.568983] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:11:15 workstation kernel: [17152.784822] usb 1-1: new
high-speed USB device number 37 using ehci-pci
Aug 13 13:11:20 workstation kernel: [17157.800814] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:25 workstation kernel: [17162.916650] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:25 workstation kernel: [17163.132336] usb 1-1: new
high-speed USB device number 38 using ehci-pci
Aug 13 13:11:30 workstation kernel: [17168.148372] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:35 workstation kernel: [17173.264055] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:35 workstation kernel: [17173.367771] hub 1-0:1.0: unable
to enumerate USB device on port 1
Aug 13 13:11:36 workstation kernel: [17173.683559] usb 4-1: new
full-speed USB device number 10 using ohci-pci
Aug 13 13:11:51 workstation kernel: [17188.807165] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:06 workstation kernel: [17204.034600] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:06 workstation kernel: [17204.274435] usb 4-1: new
full-speed USB device number 11 using ohci-pci
Aug 13 13:12:21 workstation kernel: [17219.397975] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:37 workstation kernel: [17234.625482] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:37 workstation kernel: [17234.865358] usb 4-1: new
full-speed USB device number 12 using ohci-pci
Aug 13 13:12:42 workstation kernel: [17239.882243] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:47 workstation kernel: [17244.997856] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:47 workstation kernel: [17245.236756] usb 4-1: new
full-speed USB device number 13 using ohci-pci
Aug 13 13:12:52 workstation kernel: [17250.253374] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:57 workstation kernel: [17255.369012] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:57 workstation kernel: [17255.472389] hub 4-0:1.0: unable
to enumerate USB device on port 1
Google told me, error -110 means something aboult not enough power for
the usb device.
So I experimented with the values for
.db 0xE0 ; attrs = bus powered, no wakeup
.db 0x00 ; max power = 100ma
but nothing changed.
I also tried to download the firmware with fxload.
But here I receive the error:
fxload -vvv -t fx2 -D /dev/bus/usb/001/039 -I build/firmware.ihx
microcontroller type: fx2
single stage: load on-chip memory
open RAM hexfile image build/firmware.ihx
stop CPU
** LINE: :040000000201B9320E
** LINE: :01000B0032C2
write on-chip, addr 0x0000 len 4 (0x0004)
... ... ...
can't write 188 bytes external memory at 0x3e00
unable to download build/firmware.ihx
What am I doing wrong?
Where can I find a mapping between error description and numercial error
code?
All I found until now are error codes without number.
Best Regards,
Ck
|
|
From: Christoph K. <chr...@we...> - 2014-08-13 11:49:52
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everyone,
I am new to the Cypress FX2 and USB development. Using Linux Mint 17.
I compiled the example firmware.
With cyc2fxprog it downloads to the fx2.
When I run it, I receive the following Kernel Error:
Aug 13 13:10:14 workstation kernel: [17091.746996] usb 1-1: new
high-speed USB device number 35 using ehci-pci
Aug 13 13:10:29 workstation kernel: [17106.846587] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:10:44 workstation kernel: [17122.050051] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:10:44 workstation kernel: [17122.265909] usb 1-1: new
high-speed USB device number 36 using ehci-pci
Aug 13 13:10:59 workstation kernel: [17137.365421] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:11:14 workstation kernel: [17152.568983] usb 1-1: device
descriptor read/64, error -110
Aug 13 13:11:15 workstation kernel: [17152.784822] usb 1-1: new
high-speed USB device number 37 using ehci-pci
Aug 13 13:11:20 workstation kernel: [17157.800814] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:25 workstation kernel: [17162.916650] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:25 workstation kernel: [17163.132336] usb 1-1: new
high-speed USB device number 38 using ehci-pci
Aug 13 13:11:30 workstation kernel: [17168.148372] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:35 workstation kernel: [17173.264055] usb 1-1: device
descriptor read/8, error -110
Aug 13 13:11:35 workstation kernel: [17173.367771] hub 1-0:1.0: unable
to enumerate USB device on port 1
Aug 13 13:11:36 workstation kernel: [17173.683559] usb 4-1: new
full-speed USB device number 10 using ohci-pci
Aug 13 13:11:51 workstation kernel: [17188.807165] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:06 workstation kernel: [17204.034600] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:06 workstation kernel: [17204.274435] usb 4-1: new
full-speed USB device number 11 using ohci-pci
Aug 13 13:12:21 workstation kernel: [17219.397975] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:37 workstation kernel: [17234.625482] usb 4-1: device
descriptor read/64, error -110
Aug 13 13:12:37 workstation kernel: [17234.865358] usb 4-1: new
full-speed USB device number 12 using ohci-pci
Aug 13 13:12:42 workstation kernel: [17239.882243] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:47 workstation kernel: [17244.997856] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:47 workstation kernel: [17245.236756] usb 4-1: new
full-speed USB device number 13 using ohci-pci
Aug 13 13:12:52 workstation kernel: [17250.253374] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:57 workstation kernel: [17255.369012] usb 4-1: device
descriptor read/8, error -110
Aug 13 13:12:57 workstation kernel: [17255.472389] hub 4-0:1.0: unable
to enumerate USB device on port 1
Google told me, error -110 means something aboult not enough power for
the usb device.
So I experimented with the values for
.db 0xE0 ; attrs = bus powered, no wakeup
.db 0x00 ; max power = 100ma
but nothing changed.
I also tried to download the firmware with fxload.
But here I receive the error:
fxload -vvv -t fx2 -D /dev/bus/usb/001/039 -I build/firmware.ihx
microcontroller type: fx2
single stage: load on-chip memory
open RAM hexfile image build/firmware.ihx
stop CPU
** LINE: :040000000201B9320E
** LINE: :01000B0032C2
write on-chip, addr 0x0000 len 4 (0x0004)
... ... ...
can't write 188 bytes external memory at 0x3e00
unable to download build/firmware.ihx
What am I doing wrong?
Where can I find a mapping between error description and numercial error
code?
All I found until now are error codes without number.
Best Regards,
Ck
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJT61DNAAoJEHW4vNfjUxtPh0gIAIeaLy0qQC9E4YIEGSwZTMJM
COeEkS6AjuDmSD2kZynHuN71twabnSyC57Dt1fP2tA+7s8uOz5+gQGgUuViuY3u5
OM9b1KHu6kdC8w4GHf+0sD9BSmO2HbkIxw5KoARS0UwGV5qFiLYG3ALZ8jKn7YtN
WLFOHkirR6xyHLj7FSQdY6F7LoQETqjtRoxWFbyeGQ9sT+8scbwxYWi/pq5QCaOS
LwwKh6yErsUR7u94sub1NuRXIOfiS3HWuVD94NcyRHwk8FkU3Ykf13v2TQgFQ/gA
ep0+3gSAeH+R7e4fkwBXPmy4hxrcjaTN6j9xuMMoHhR3E1t7FdP3HuLu1MwjXeo=
=kBAC
-----END PGP SIGNATURE-----
|
|
From: Dennis M. <djm...@gm...> - 2014-08-13 14:14:48
|
On 8/13/14, 5:53 AM, Christoph Kuhr wrote: > > Google told me, error -110 means something aboult not enough power for > the usb device. > So I experimented with the values for > .db 0xE0 ; attrs = bus powered, no wakeup > .db 0x00 ; max power = 100ma > > but nothing changed. If it is a power problem, that likely means the device is really having issues with too much power or not enough power or whatever. Whatever you put in the descriptor is only a hint to the software on the computer but it's up to the device to actually obey that hint. > > > > I also tried to download the firmware with fxload. > But here I receive the error: > > fxload -vvv -t fx2 -D /dev/bus/usb/001/039 -I build/firmware.ihx > > microcontroller type: fx2 > single stage: load on-chip memory > open RAM hexfile image build/firmware.ihx > stop CPU > ** LINE: :040000000201B9320E > ** LINE: :01000B0032C2 > write on-chip, addr 0x0000 len 4 (0x0004) > ... ... ... > can't write 188 bytes external memory at 0x3e00 > unable to download build/firmware.ihx > > What am I doing wrong? > > > Where can I find a mapping between error description and numercial error > code? > All I found until now are error codes without number. Are you using libusb-1.0? At least for libusb errors you can look at the libusb header. http://www.libusb.org/browser/libusb/libusb/libusb.h For kernel errors you'll have to look which module produced the error and look at the kernel sources for your distro. If you look in the fx2lib examples you can see how loading is actually done and perhaps check any errors about what might be going on. https://github.com/djmuhlestein/fx2lib/blob/master/examples/fx2/cpp/fx2.cpp That uses libusb-0.1 though and is pretty outdated. As far as fx2lib goes, it's firmware is as good/stable as ever but I haven't spent time maintaining any driver support at the fx2lib level. I am still working on drivers that work both with the fx2 and the fx3 device though. https://github.com/ubixum/nitro The driver layer of the nitro package has the utilities to load firmware on both devices. It may or may not be useful but you could check the src/*usb* files to get a better explanation of what is going on. Anyway, if you post a dropbox link or gist or whatever with your fx2lib firmware perhaps I could download it to a known working device and see what's might be going on. -Dennis |
|
From: Christoph K. <chr...@we...> - 2014-08-13 19:13:09
|
Hi, thanks for your quick reply.
When I attach the device, the factory firmware is loaded, so I dont
think that there is a physical power problem, or am I wrong?
On 13.08.2014 16:14, Dennis Muhlestein wrote:
> Anyway, if you post a dropbox link or gist or whatever with your fx2lib
> firmware perhaps I could download it to a known working device and see
> what's might be going on.
>
I just typed make with what is in the git repository ("fx2lib/fw").
Ck
|
|
From: Dennis M. <djm...@gm...> - 2014-08-14 00:55:29
|
On 8/13/14, 1:12 PM, Christoph Kuhr wrote:
> Hi, thanks for your quick reply.
>
> When I attach the device, the factory firmware is loaded, so I dont
> think that there is a physical power problem, or am I wrong?
Yes you should be able to see the default Cypress device w/ lsusb if no
firmware is loaded on the device.
>
>
> On 13.08.2014 16:14, Dennis Muhlestein wrote:
>> Anyway, if you post a dropbox link or gist or whatever with your fx2lib
>> firmware perhaps I could download it to a known working device and see
>> what's might be going on.
>>
> I just typed make with what is in the git repository ("fx2lib/fw").
Are you loading the ihx file?
|
|
From: Christoph K. <chr...@we...> - 2014-08-14 10:27:30
|
Hi,
>> I just typed make with what is in the git repository ("fx2lib/fw").
>
> Are you loading the ihx file?
Yes I am.
|
|
From: Dennis M. <djm...@gm...> - 2014-08-16 21:30:42
|
On 8/14/14, 4:27 AM, Christoph Kuhr wrote:
> Hi,
>
>
>
>>> I just typed make with what is in the git repository ("fx2lib/fw").
>>
>> Are you loading the ihx file?
> Yes I am.
>
Do you have a Cypress FX2 devel board? If I recall all the examples
work out of the box on the devel board so that might be a way to
compare. If you're using the stock firmware and the device operates
correctly I can't think of what else might be wrong.
|
|
From: Dennis M. <djm...@gm...> - 2014-08-19 13:05:29
|
On 8/16/14, 3:30 PM, Dennis Muhlestein wrote:
> On 8/14/14, 4:27 AM, Christoph Kuhr wrote:
>> Hi,
>>
>>
>>
>>>> I just typed make with what is in the git repository ("fx2lib/fw").
>>>
>>> Are you loading the ihx file?
>> Yes I am.
>>
Jessy Exum emailed me off list he'd like to reply but he hasn't quite
worked out replying to the list yet. He mentioned you're trying to load
the code as an fx2 part (which has 1/2 the code space) but it's an fx2lp.
I personally haven't used fxload. In fact I haven't used the cypress
tools much either. I used the driver or a derivative of it from the
examples directory. That's probably why I didn't notice the issue.
Thanks Jessy for pointing that out.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X