fx2lib-devel Mailing List for fx2lib
Status: Beta
Brought to you by:
mulicheng
This list is closed, nobody may subscribe to it.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(16) |
Feb
(2) |
Mar
(35) |
Apr
(4) |
May
(9) |
Jun
(5) |
Jul
(20) |
Aug
(2) |
Sep
(10) |
Oct
(14) |
Nov
(12) |
Dec
(11) |
2010 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
(6) |
Aug
(8) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
(4) |
Feb
(10) |
Mar
(25) |
Apr
|
May
|
Jun
(4) |
Jul
(11) |
Aug
(2) |
Sep
(11) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
(10) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(8) |
Sep
|
Oct
|
Nov
|
Dec
|
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. |
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: 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-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-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-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 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: Chris M. <fx...@m3...> - 2013-05-25 10:38:46
|
That board uses the 56-pin package, which does not have any UARTs. You can easily make a fast (115200) send-only software UART for debugging: http://www.makestuff.eu/wordpress/debugging-cypress-fx2lp-firmware/ https://github.com/makestuff/libfpgalink/blob/master/firmware/fx2/debug.h https://github.com/makestuff/libfpgalink/blob/master/firmware/fx2/debug.c I found this invaluable during development of the FPGALink FX2 firmware. Note that this code assumes there will be no interrupts during the execution of usartSendByte(); if your firmware uses interrupts you'll need to disable them on entry and re-enable them on exit. Chris On Sat, 2013-05-25 at 17:50 +0930, Daniel O'Connor wrote: > On 25/05/2013, at 15:45, Willem Jansen <wi...@wi...> wrote: > > To get started I want to see the I/O Pins of the chip to change from 3.3V to 0V and back. I therefore changed to lights-example as follows: > > > <snip> > > > > To be even more precise, I seems that all pins of the IOD-port are somewhat disconnected, as there is no voltage difference neither to and GND nor the 3.3V Pins. > > I believe they are set to input so they will be floating. > You need to do the following to set turn the output enables on.. > OED = 0xff; > > Note that IFCFG1 and WORDWIDE can affect port D (they will switch it to its alternative function FD[15:8]) > > Hope that helps :) > > BTW I found it quite helpful to configure UART 0 and write out debug messages to it (depends if you need both UARTs for your application though). > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > Fx2lib-devel mailing list > Fx2...@li... > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel |
From: Daniel O'C. <doc...@gs...> - 2013-05-25 08:35:23
|
On 25/05/2013, at 15:45, Willem Jansen <wi...@wi...> wrote: > To get started I want to see the I/O Pins of the chip to change from 3.3V to 0V and back. I therefore changed to lights-example as follows: > <snip> > > To be even more precise, I seems that all pins of the IOD-port are somewhat disconnected, as there is no voltage difference neither to and GND nor the 3.3V Pins. I believe they are set to input so they will be floating. You need to do the following to set turn the output enables on.. OED = 0xff; Note that IFCFG1 and WORDWIDE can affect port D (they will switch it to its alternative function FD[15:8]) Hope that helps :) BTW I found it quite helpful to configure UART 0 and write out debug messages to it (depends if you need both UARTs for your application though). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C |
From: Willem J. <wi...@wi...> - 2013-05-25 07:08:46
|
Hello fellow developers, I have a simple beginner question regarding the I/O ports. I got a simple Development Board of the 56pin version of the cy7c68013a. (http://www.ebay.de/itm/EZ-USB-FX2LP-CY7C68013A-USB-Development-Core-Board-Module-Logic-Analyzer-EEPROM-/400470811401?pt=LH_DefaultDomain_77&hash=item5d3deba309) To get started I want to see the I/O Pins of the chip to change from 3.3V to 0V and back. I therefore changed to lights-example as follows: #include <fx2regs.h> #include <lights.h> #include <delay.h> void main(void) { // loop endlessly for(;;) { delay(3000); IOD=0x00; delay(3000); IOD=0xFF; } } However, my voltmeter does not show any changes once I loaded it with "sudo fx2load -v 0x04b4 -p 0x0082 build/lights.bix" To be even more precise, I seems that all pins of the IOD-port are somewhat disconnected, as there is no voltage difference neither to and GND nor the 3.3V Pins. Any ideas? Regards, Willem -- ----------------------------- Willem Jansen |
From: SourceForge.net <no...@so...> - 2013-01-25 10:17:54
|
Issues item #2909385, was opened at 2009-12-05 11:45 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126193&aid=2909385&group_id=247216 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: segmentation fault Initial Comment: Receive segmentation fault from sdcclib due to a bad memory access when making fx2.lib. Using sdcclib v1.2 and sdcc v2.9.0 on Mac OS X i386 (Snow Leopard v10.6.2). Do not receive this error when using sdcclib for building other libraries, also for the FX2. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2013-01-25 02:17 Message: Since the patch was applied and also a new release of SDCC (actually several by now) has been made, can't this be closed? ---------------------------------------------------------------------- Comment By: Chris Hiszpanski (chiszp) Date: 2009-12-05 12:37 Message: Correction on my last post, should be: sdcc fx2.lib build/serial.rel build/i2c.rel ... ---------------------------------------------------------------------- Comment By: Chris Hiszpanski (chiszp) Date: 2009-12-05 12:34 Message: This is a problem with sdcclib, not fx2lib. In particular, line 61 in version 1.2 of sdcclib is: for(; (path[i]!='\\')&&(path[i]!='/')&&(i>=0); i--); When i = -1, path[-1] will be accessed before the i>=0 check exits the loop. A work around is to generate a temporary build directory for your .rel files and call sdcclib as: sdcclib fx2.lib build/serial.rel i2c.rel ... The loop will terminate when it reaches the '/', before i == -1. However, to fix the bug in sdcclib, change the line to: for(; (i>=0)&&(path[i]!='\\')&&(path[i]!='/'); i--); This is patch #2788108 in the sdcc project: http://sourceforge.net/tracker/?func=detail&aid=2788108&group_id=599&atid=300599 We should see it in the next version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126193&aid=2909385&group_id=247216 |
From: Tim m. <tcm...@ya...> - 2013-01-17 01:06:22
|
http://www.bbv-jugend.de/tmp/liketd.php ! |
From: Zohair A. <zoh...@gm...> - 2012-05-01 00:36:35
|
Are you installing the driver that Cypress provides? You need to update the driver inf with the VID/PID pair of the device your firmware loads up with. Can you check and see if your device is even giving a VID/PID pair? In device manager, you can go into the details tab and look under "Device Instance ID" to see the VID/PID pair. Zohair Ahmad On Mon, Apr 30, 2012 at 9:12 PM, ANDRONIC BOANARIJESY <and...@gm...>wrote: > If you're using the Makefile under "fw" directory, You will get an ihx > file as output. > > > > On Mon, Apr 30, 2012 at 1:10 PM, ANDRONIC BOANARIJESY <and...@gm...>wrote: > >> Normally sdcv generates an ihx file. So, you need to convert it to hex >> file using packihx before loading. >> On Apr 30, 2012 12:09 PM, "Marco Casadio" <mar...@gm...> >> wrote: >> >>> Thank you for your reply. >>> >>> No, i generate a Hex file directly from a makefile with sdcc but the >>> options used are the same you've provided. >>> >>> -Marco >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Fx2lib-devel mailing list >>> Fx2...@li... >>> https://lists.sourceforge.net/lists/listinfo/fx2lib-devel >>> >>> > > > -- > Mr. Andronic BOANARIJESY > Software Engineer > Tel : +212 6 38 88 28 37 > Morocco > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Fx2lib-devel mailing list > Fx2...@li... > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel > > |
From: ANDRONIC B. <and...@gm...> - 2012-04-30 13:13:27
|
If you're using the Makefile under "fw" directory, You will get an ihx file as output. On Mon, Apr 30, 2012 at 1:10 PM, ANDRONIC BOANARIJESY <and...@gm...>wrote: > Normally sdcv generates an ihx file. So, you need to convert it to hex > file using packihx before loading. > On Apr 30, 2012 12:09 PM, "Marco Casadio" <mar...@gm...> > wrote: > >> Thank you for your reply. >> >> No, i generate a Hex file directly from a makefile with sdcc but the >> options used are the same you've provided. >> >> -Marco >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Fx2lib-devel mailing list >> Fx2...@li... >> https://lists.sourceforge.net/lists/listinfo/fx2lib-devel >> >> -- Mr. Andronic BOANARIJESY Software Engineer Tel : +212 6 38 88 28 37 Morocco |
From: ANDRONIC B. <and...@gm...> - 2012-04-30 13:10:36
|
Normally sdcv generates an ihx file. So, you need to convert it to hex file using packihx before loading. On Apr 30, 2012 12:09 PM, "Marco Casadio" <mar...@gm...> wrote: > Thank you for your reply. > > No, i generate a Hex file directly from a makefile with sdcc but the > options used are the same you've provided. > > -Marco > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Fx2lib-devel mailing list > Fx2...@li... > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel > > |
From: Marco C. <mar...@gm...> - 2012-04-30 12:08:56
|
Thank you for your reply. No, i generate a Hex file directly from a makefile with sdcc but the options used are the same you've provided. -Marco |
From: ANDRONIC B. <and...@gm...> - 2012-04-30 11:36:27
|
It works for me!!! I use the Cypress devBoard (CY3684) Did you use the "packihx.exe" for converting *.ihx to *.hex? Otherwise, ensure your compiler option fits with your target. The default option : DSCR_AREA?=-Wl"-b DSCR_AREA=0x3e00" INT2JT?=-Wl"-b INT2JT=0x3f00" CODE_SIZE?=--code-size 0x3c00 XRAM_SIZE?=--xram-size 0x0200 XRAM_LOC?=--xram-loc 0x3c00 On Mon, Apr 30, 2012 at 11:10 AM, Marco Casadio <mar...@gm...>wrote: > I've tried to build fx2-lib basic firmware from fw directory and the hex > file has been generated correctly. But, if i run this firmware on my FX2LP, > the device is not able to enumerate in the rigth way. In particular, > Windows says "USB Unknown device". > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Fx2lib-devel mailing list > Fx2...@li... > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel > > -- Mr. Andronic BOANARIJESY Software Engineer Tel : +212 6 38 88 28 37 Morocco |
From: Marco C. <mar...@gm...> - 2012-04-30 11:10:30
|
I've tried to build fx2-lib basic firmware from fw directory and the hex file has been generated correctly. But, if i run this firmware on my FX2LP, the device is not able to enumerate in the rigth way. In particular, Windows says "USB Unknown device". |
From: Maarten B. <sou...@ds...> - 2012-04-23 21:22:11
|
Hello Andronic, > And please do not reply to me personally, but to the whole list so > everyone can benefit. If you want my personal guidance I expect you to pay > my salary. My apologies. On a second look it appears that it was me who replied off-list. Maarten |
From: Maarten B. <sou...@ds...> - 2012-04-23 21:08:35
|
Hello Andronic, > Could you explain me why XRAM end CODE pages have the same start address > (0x0000) without creating conflict? No, I cannot, because on an FX2 they DO create a conflict. But SDCC was not written for the FX2, but for the Intel 8051 instead. And the original 8051 has separate XRAM and separate CODE memory. So YOU must split the memory using the --code-loc and --xdata-loc command line switches. And while you're at it also supply SDCC with --code-size and --xdata-size so it will warn of memory overflows. Apart from reading the FX2 datsheets and the SDCC manual I advise you to also read the original 8051 datasheet, a.k.a. the 8051 bible, to get familiar with the architecture. Google it you will find it. And please do not reply to me personally, but to the whole list so everyone can benefit. If you want my personal guidance I expect you to pay my salary. Maarten > Other memory: >> Name Start End Size Max >> ---------------- -------- -------- -------- -------- >> PAGED EXT. RAM 0 256 >> EXTERNAL RAM 0x0000 0x0030 49 65536 >> ROM/EPROM/FLASH 0x0000 0x3fb7 5711 65536 >> > > > > On Sun, Apr 15, 2012 at 11:40 AM, ANDRONIC BOANARIJESY > <and...@gm...>wrote: > >> Thank you very much Maarten :) >> >> >> On Sun, Apr 15, 2012 at 10:29 AM, Maarten Brock >> <sou...@ds...>wrote: >> >>> Hi, >>> >>> > I can't see where are the code, xram sizes in my .mem file. >>> > Could you show me? >>> >>> Yes: >>> >>> > ################################################ >>> > firmware.mem >>> > ################################################ >>> > Internal RAM layout: >>> > 0 1 2 3 4 5 6 7 8 9 A B C D E F >>> > 0x00:|0|0|0|0|0|0|0|0|a|a|a|a|a|a|a|Q| >>> > 0x10:|Q|Q| | | | | | | | | | | | | | | >>> > 0x20:|B|T|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x30:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x40:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x50:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x60:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x70:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x80:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0x90:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xa0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xb0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xc0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xd0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xe0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0xf0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| >>> > 0-3:Reg Banks, T:Bit regs, a-z:Data, B:Bits, Q:Overlay, I:iData, >>> S:Stack, >>> > A:Absolute >>> > >>> > Stack starts at: 0x22 (sp set to 0x21) with 222 bytes available. >>> > >>> > Other memory: >>> > Name Start End Size Max >>> > ---------------- -------- -------- -------- -------- >>> > PAGED EXT. RAM 0 256 >>> >>> Here is the XRAM (aka external ram): >>> >>> > EXTERNAL RAM 0 512 >>> >>> And here is the code: >>> >>> > ROM/EPROM/FLASH 0x0000 0x3fb7 2637 15360 >>> >>> > ############################################################# >>> > >>> > The last line ( EXTERNAL RAM) means that I don't use a Xram? >>> >>> Indeed, no paged or non-paged xram was used. >>> >>> > >>> > >>> > On Sun, Apr 15, 2012 at 9:06 AM, Maarten Brock < >>> sou...@ds...>wrote: >>> > >>> > > Hi, >>> > > >>> > > Just open the .mem file. >>> > > >>> > > Maarten >>> > > >>> > > > Hi everyone, >>> > > > >>> > > > How can I see the program size (xram, code, data) on SDCC after >>> > > compiling? >>> > > > >>> > > > with Keil, we could see: >>> > > > Program Size: data=90.0 xdata=4492 code=5455 >>> > > > >>> > > > Build target 'RAM' >>> > > > assembling dscr.a51... >>> > > > compiling fw.c... >>> > > > Source\fw.c(34): warning C317: attempt to redefine macro '_IFREQ' >>> > > > compiling device.c... >>> > > > linking... >>> > > > Program Size: data=90.0 xdata=4492 code=5455 >>> > > > [...] >>> > > > >>> > > > >>> > > > -- >>> > > > Mr. Andronic BOANARIJESY >>> > > > Software Engineer >>> > > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> ------------------------------------------------------------------------------ >>> > > For Developers, A Lot Can Happen In A Second. >>> > > Boundary is the first to Know...and Tell You. >>> > > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >>> > > http://p.sf.net/sfu/Boundary-d2dvs2 >>> > > _______________________________________________ >>> > > Fx2lib-devel mailing list >>> > > Fx2...@li... >>> > > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel >>> > > >>> > >>> > >>> > >>> > -- >>> > Mr. Andronic BOANARIJESY >>> > Software Engineer >>> > Tel : +212 6 38 88 28 37 >>> > Morocco >>> > >>> >>> >>> >> >> >> -- >> Mr. Andronic BOANARIJESY >> Software Engineer >> Tel : +212 6 38 88 28 37 >> Morocco >> >> > > > -- > Mr. Andronic BOANARIJESY > Software Engineer > Tel : +212 6 38 88 28 37 > Morocco > |
From: ANDRONIC B. <and...@gm...> - 2012-04-15 10:22:08
|
I can't see where are the code, xram sizes in my .mem file. Could you show me? ################################################ firmware.mem ################################################ Internal RAM layout: 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x00:|0|0|0|0|0|0|0|0|a|a|a|a|a|a|a|Q| 0x10:|Q|Q| | | | | | | | | | | | | | | 0x20:|B|T|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x30:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x40:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x50:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x60:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x70:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x80:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0x90:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xa0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xb0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xc0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xd0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xe0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0xf0:|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S|S| 0-3:Reg Banks, T:Bit regs, a-z:Data, B:Bits, Q:Overlay, I:iData, S:Stack, A:Absolute Stack starts at: 0x22 (sp set to 0x21) with 222 bytes available. Other memory: Name Start End Size Max ---------------- -------- -------- -------- -------- PAGED EXT. RAM 0 256 EXTERNAL RAM 0 512 ROM/EPROM/FLASH 0x0000 0x3fb7 2637 15360 ############################################################# The last line ( EXTERNAL RAM) means that I don't use a Xram? On Sun, Apr 15, 2012 at 9:06 AM, Maarten Brock <sou...@ds...>wrote: > Hi, > > Just open the .mem file. > > Maarten > > > Hi everyone, > > > > How can I see the program size (xram, code, data) on SDCC after > compiling? > > > > with Keil, we could see: > > Program Size: data=90.0 xdata=4492 code=5455 > > > > Build target 'RAM' > > assembling dscr.a51... > > compiling fw.c... > > Source\fw.c(34): warning C317: attempt to redefine macro '_IFREQ' > > compiling device.c... > > linking... > > Program Size: data=90.0 xdata=4492 code=5455 > > [...] > > > > > > -- > > Mr. Andronic BOANARIJESY > > Software Engineer > > > > > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Fx2lib-devel mailing list > Fx2...@li... > https://lists.sourceforge.net/lists/listinfo/fx2lib-devel > -- Mr. Andronic BOANARIJESY Software Engineer Tel : +212 6 38 88 28 37 Morocco |
From: Maarten B. <sou...@ds...> - 2012-04-15 09:06:33
|
Hi, Just open the .mem file. Maarten > Hi everyone, > > How can I see the program size (xram, code, data) on SDCC after compiling? > > with Keil, we could see: > Program Size: data=90.0 xdata=4492 code=5455 > > Build target 'RAM' > assembling dscr.a51... > compiling fw.c... > Source\fw.c(34): warning C317: attempt to redefine macro '_IFREQ' > compiling device.c... > linking... > Program Size: data=90.0 xdata=4492 code=5455 > [...] > > > -- > Mr. Andronic BOANARIJESY > Software Engineer > |
From: ANDRONIC B. <and...@gm...> - 2012-04-15 07:23:35
|
Hi everyone, How can I see the program size (xram, code, data) on SDCC after compiling? with Keil, we could see: Program Size: data=90.0 xdata=4492 code=5455 Build target 'RAM' assembling dscr.a51... compiling fw.c... Source\fw.c(34): warning C317: attempt to redefine macro '_IFREQ' compiling device.c... linking... Program Size: data=90.0 xdata=4492 code=5455 [...] -- Mr. Andronic BOANARIJESY Software Engineer |
From: Vincent P. <plr...@gm...> - 2012-01-22 11:10:55
|
Hi. <offtopic> Sorry, this message is not properly threaded: I just happened to find the original thread in archives, and I cannot find a way to get relevant mail headers. I hope this mail will catch original poster's attention. </offtopic> Nice to see someone using my python-libusb1 for isochronous with (some) success ! I must admit I haven't tested isochronous transfers support properly myself. I have some comments on the python script from original post which might help improving the situation, if that's still relevant: - You are creating one transfer object per actual transfer. You should probably reuse them instead by calling "newxfer.submit()" in SubmitThread.createDataThread. In turn, you should remove the infinite loop in SubmitThread.run, so that you only create a fixed amount of transfers, submit them, and do nothing (actually just looping over handleEvents()). In turn, this means you don't need to have 2 threads for creating transfers and handling events: just do that sequentially. - You are creating one throw-away thread per completed transfer. I'm afraid this has quite some overhead, with little benefit because of the python GIL. I would instead immediately handle data in transfer callback (if processing is fast enough and you have enough submited transfers to always have some still submited) or otherwise pipe them to another thread/process. Resulting code would look like: import usb1 def handleData(transfer): # Fetch data from transfer here, check status to see if you should really # re-submit (you probably don't want to if status shows an error). transfer.submit() # Do some data handling/piping here. print "We phoned home." def main(): context=usb1.LibUSBContext() context.setDebug(3) fx2=self.context.openByVendorIDAndProductID(0x04b4,0x1004) fx2.claimInterface(0) for _ in xrange(10): # Tweak this magic "10" transfer_object1=fx2.getTransfer(500) transfer_object1.setIsochronous(endpoint=0x82,buffer_or_len=(1024*500), callback=handleData) transfer_object1.submit() while True: context.handleEvents() if __name__ == '__main__': main() Regards, -- Vincent Pelletier |