Menu
▾
▴
xc3sprog-users — Generic user and developer list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(6) |
Dec
(1) |
| 2010 |
Jan
(5) |
Feb
(33) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(25) |
Sep
(8) |
Oct
(2) |
Nov
|
Dec
(3) |
| 2012 |
Jan
(2) |
Feb
(22) |
Mar
(1) |
Apr
(8) |
May
(8) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
|
Nov
(9) |
Dec
(5) |
| 2013 |
Jan
|
Feb
(3) |
Mar
(5) |
Apr
(5) |
May
(2) |
Jun
(18) |
Jul
|
Aug
(2) |
Sep
(21) |
Oct
|
Nov
|
Dec
(2) |
| 2014 |
Jan
(6) |
Feb
(6) |
Mar
|
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2015 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
(6) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
(6) |
Dec
(1) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
(5) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-09 21:40:04
|
On Tue, Feb 09, 2010 at 09:28:16PM +0100, Grzegorz Behrens wrote:
> xc3sprog works, with FreeBSD 8 and the Spartan-3 Board 200K from
> Digilent, when this source code (in ioparport.cpp):
>
> if ((status & PCIII_TDO_MASK) && (!(data & PCIII_PROG_EN_N))) {
> fprintf(stderr,"Missing power for Parallel Cable III\n");
> return NO_CABLE;
>
> is commented out.
Thanks a lot Grzegorz for this report!
--
Wojciech A. Koszek
wk...@Fr...
http://FreeBSD.czest.pl/~wkoszek/
|
|
From: Grzegorz B. <grz...@gm...> - 2010-02-09 20:28:23
|
xc3sprog works, with FreeBSD 8 and the Spartan-3 Board 200K from
Digilent, when this source code (in ioparport.cpp):
if ((status & PCIII_TDO_MASK) && (!(data & PCIII_PROG_EN_N))) {
fprintf(stderr,"Missing power for Parallel Cable III\n");
return NO_CABLE;
is commented out.
|
|
From: Uwe B. <bo...@el...> - 2010-02-09 18:47:58
|
>>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes:
Wojciech> Was something wrong with the patch?
Probably lost in work and mail overflow. Can you redo against recent
SVN. Roger started xc3sprog 2004, so start copyright there. Also please
check crosscompiling on Win32, at least with mingw. I don't see uname() in
any mingw header ...
Thanks
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-09 16:05:32
|
On Tue, Feb 09, 2010 at 12:49:34PM +0100, Uwe Bonnes wrote: > >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > > Wojciech> On Mon, Feb 08, 2010 at 09:43:19PM +0100, Uwe Bonnes wrote: > >> >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > >> > Wojciech> xc3sprog project (c) 2005-2010 Uwe Bonnes > Wojciech> bo...@el... WWW: > >> The work was started by Andrew, others dropped in and now most > >> contributions are mine. But that doesn't give me the whole copyright. > > Wojciech> I haven't had a chance to exactly track the version history > Wojciech> and because of not being a copyright expert. Maybe: > > Wojciech> XC3SPROG (c) 2005-2010 xc3sprog project $Rev$ <OS> > > Wojciech> Or whatever else. As long as I can easily distinguish that a > Wojciech> user calls the right program, it's ok. > > Do you have a suggestion for the <OS> printout logic. Otherwise I tried to > implement your suggestions from this mail in rev 434. I tried to be as > explicit as with the error mess Uwe, Was something wrong with the patch? You may want to obtain rev 432 for which my patch was addressed and simply apply it and change printf's. I use uname(3) there and I think it can be used here as well. "FreeBSD" and "Linux" should be enough. Ideally (as I mentioned earlier), your cmake-magic knowledge could be deployed, so that, except pure OS specific string returned from uname(3), you'll also have specific information about cross compilation. Usage is much clearer in my patch. Moreover, it lists -c option, which is missing right now. The reason why I removed verbose notifications as I think they're uncessary, and exceed 80 lines. From r435: ------------------------------------------------------------------------------- "Feedback on success/failure/enhancement requests: http://sourceforge.net/mail/?group_id=170565" "Check Sourceforge for updates: http://sourceforge.net/projects/xc3sprog/develop for updates" Maybe: "In case of problems: http://sf.net/mail/?group_id=170565" And probably only with -v... I think logic present after your patch isn't yet right -- parallel port constructor is always called, which means that my logic circuit for the CNC machine I build here may suddenly, by accident, respond correctly to the "probe" sequence.. My opinion is that under no condition xc3sprog should touch anything, unless stated otherwise. So, IMO (ideal case) the right logic would be: if XC3SPROG_CABLE set Use $XC3SPROG_CABLE. else if -c had some hints Yes, use cable passed from -c. else Inform what to do. Where: - $XC3SPROG_CABLE == "pp:/path/to/dev" -> parallel port backend with /path/to/dev device. - $XC3SPROG_CABLE == "ftdi:vid=<VID>,pid=<PID>,option=..." -> FTDI options Or similar. This would let you to stay away from getenv()s in IOParport.. > Wojciech> This 'usb_control_msg(0x42.1 Unknown error' appears here as > Wojciech> well. BTW, a friend of mine confirmed that he can program his > Wojciech> S3ESK board under his FreeBSD 8 system without a problem with > Wojciech> some of my random notes. > >> I'll look again at the 0x42.1 message again. What Xilinx dobgle is > >> that, what firmware file loaded? > > Wojciech> I have S3ESK board so far. I use its embedded USB JTAG cable > Wojciech> with this firmware: > > I disabled the code so long. It doesn't get work for me and causes problems > for you. Thanks! -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Uwe B. <bo...@el...> - 2010-02-09 11:49:45
|
>>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes:
Wojciech> On Mon, Feb 08, 2010 at 09:43:19PM +0100, Uwe Bonnes wrote:
>> >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes:
>>
Wojciech> xc3sprog project (c) 2005-2010 Uwe Bonnes
Wojciech> bo...@el... WWW:
>> The work was started by Andrew, others dropped in and now most
>> contributions are mine. But that doesn't give me the whole copyright.
Wojciech> I haven't had a chance to exactly track the version history
Wojciech> and because of not being a copyright expert. Maybe:
Wojciech> XC3SPROG (c) 2005-2010 xc3sprog project $Rev$ <OS>
Wojciech> Or whatever else. As long as I can easily distinguish that a
Wojciech> user calls the right program, it's ok.
Do you have a suggestion for the <OS> printout logic. Otherwise I tried to
implement your suggestions from this mail in rev 434. I tried to be as
explicit as with the error mess
Wojciech> This 'usb_control_msg(0x42.1 Unknown error' appears here as
Wojciech> well. BTW, a friend of mine confirmed that he can program his
Wojciech> S3ESK board under his FreeBSD 8 system without a problem with
Wojciech> some of my random notes.
>> I'll look again at the 0x42.1 message again. What Xilinx dobgle is
>> that, what firmware file loaded?
Wojciech> I have S3ESK board so far. I use its embedded USB JTAG cable
Wojciech> with this firmware:
I disabled the code so long. It doesn't get work for me and causes problems
for you.
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-09 02:17:32
|
On Mon, Feb 08, 2010 at 09:43:19PM +0100, Uwe Bonnes wrote: > >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > > Wojciech> xc3sprog project (c) 2005-2010 Uwe Bonnes > Wojciech> bo...@el... WWW: > > The work was started by Andrew, others dropped in and now most contributions > are mine. But that doesn't give me the whole copyright. I haven't had a chance to exactly track the version history and because of not being a copyright expert. Maybe: XC3SPROG (c) 2005-2010 xc3sprog project $Rev$ <OS> Or whatever else. As long as I can easily distinguish that a user calls the right program, it's ok. > > Wojciech> http://sourceforge.net/projects/xc3sprog Release: $Rev: 426 $ > Wojciech> System: FreeBSD(i386): 9.0-CURRENT > > Wojciech> usage: xc3sprog [options] <bitfile> > > I'll consider the usage changes.... How about turning off autodetection? Current situation is that in ~90% cases user gets an error after running xc3sprog without being guilty. Instead of: Could not access parallel device '/dev/parport0': No such file or directory Could not open parallel port (null) It could be: No cable selected. You must use -c option. See xc3sprog -h for more help. > Wojciech> This 'usb_control_msg(0x42.1 Unknown error' appears here as > Wojciech> well. BTW, a friend of mine confirmed that he can program his > Wojciech> S3ESK board under his FreeBSD 8 system without a problem with > Wojciech> some of my random notes. > > I'll look again at the 0x42.1 message again. What Xilinx dobgle is that, > what firmware file loaded? I have S3ESK board so far. I use its embedded USB JTAG cable with this firmware: http://freebsd.czest.pl/~wkoszek/fpga/xusb_emb.hex -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-09 02:17:23
|
This mail should reach a list instead of Uwe personally. ----- Forwarded message from "Wojciech A. Koszek" <wk...@Fr...> ----- To: Uwe Bonnes <bo...@el...> From: "Wojciech A. Koszek" <wk...@Fr...> Date: Tue, 9 Feb 2010 02:35:44 +0100 Subject: Re: [Xc3sprog-users] Bringing FreeBSD support to xc3sprog. User-Agent: Mutt/1.5.17 (2007-11-01) On Mon, Feb 08, 2010 at 09:43:19PM +0100, Uwe Bonnes wrote: > >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > > Wojciech> xc3sprog project (c) 2005-2010 Uwe Bonnes > Wojciech> bo...@el... WWW: > > The work was started by Andrew, others dropped in and now most contributions > are mine. But that doesn't give me the whole copyright. > > Wojciech> http://sourceforge.net/projects/xc3sprog Release: $Rev: 426 $ > Wojciech> System: FreeBSD(i386): 9.0-CURRENT > > Wojciech> usage: xc3sprog [options] <bitfile> > > I'll consider the usage changes.... > > Wojciech> ./xc3sprog -T0 -c xpc > Wojciech> /home/wkoszek/fpga/fbsd-prog/xup-0.0.2/w/wkoszek_leds/leds.bit > Wojciech> Release $Rev: 426 $ Free software: If you contribute nothing, > Wojciech> expect nothing! Please provide feedback on > Wojciech> success/failure/enhancement requests! Check Sourceforge SVN > Wojciech> for updates! usb_control_msg(0x42.1 Unknown error firmware > Wojciech> version = 0x0404 (1028) CPLD version = 0x0012 (18) Reading > Wojciech> ID_CODE 2147483647 times Sending 22 bits IDCODE Commands: > Wojciech> 0x01fe09 Expecting 3 IDCODES : 0x06e5e093 0xf5046093 > Wojciech> 0x41c22093 > > Give the verbose option and you will see lots of dots printed for lots aof > successfill JTAG queue queries. Ops. Sorry for the lack of -v. Once again: Spartan 3e Spartan Kit + embedded JTAG cable and: http://freebsd.czest.pl/~wkoszek/fpga/xusb_emb.hex as a firmware. Now, this is what I noticed: # usbconfig ugen0.1: <OHCI root HUB nVidia> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: <EHCI root HUB nVidia> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: <Optical USB Mouse Logitech> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.2: <USB2.0 Syntek> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.3: <Samsung ML-1610 Series Samsung Electronics Co., Ltd.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.3: <product 0x000d vendor 0x03fd> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON # ./fxload -v -t fx2 -I /compat/linux/opt/Xilinx/11.1/ISE/bin/lin/xusb_emb.hex -D vid=0x3fd,pid=0xd ezusb_libusb_open(106): USB device: VendId: 0x3fd ProdId: 0xd microcontroller type: fx2 single stage: load on-chip memory open RAM hexfile image /compat/linux/opt/Xilinx/11.1/ISE/bin/lin/xusb_emb.hex stop CPU write on-chip, addr 0x1d3d len 10 (0x000a) write on-chip, addr 0x06d9 len 12 (0x000c) [..] write on-chip, addr 0x09d1 len 1 (0x0001) write on-chip, addr 0x0bfd len 79 (0x004f) ... WROTE: 7458 bytes, 85 segments, avg 87 reset CPU # usbconfig ugen0.1: <OHCI root HUB nVidia> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: <EHCI root HUB nVidia> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: <Optical USB Mouse Logitech> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.2: <USB2.0 Syntek> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.3: <Samsung ML-1610 Series Samsung Electronics Co., Ltd.> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.3: <XILINX XILINX> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON # usbconfig -u 1 -a 3 dump_device_desc ugen1.3: <XILINX XILINX> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x03fd idProduct = 0x0008 bcdDevice = 0x0000 iManufacturer = 0x0001 <XILINX > iProduct = 0x0002 <XILINX > iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 Now make couple of silly executions: # ./xc3sprog -v -c xpc xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev$ System: FreeBSD(i386): 9.0-CURRENT usb_control_msg(0x42.1 Unknown error firmware version = 0x0404 (1028) CPLD version = 0x0012 (18) Using built-in device list JTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E JTAG loc.: 0 IDCODE: 0x41c22093 Desc: XC3S500E IR length: 6 JTAG loc.: 1 IDCODE: 0xf5046093 Desc: XCF04S IR length: 8 JTAG loc.: 2 IDCODE: 0x06e5e093 Desc: XC2C64A-VQ44 IR length: 8 USB Read Transactions: 4 Write Transactions: 7 Control Transaction 15 # ./xc3sprog -v -c xpc xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev$ System: FreeBSD(i386): 9.0-CURRENT usb_control_msg(0x42.1 Unknown error firmware version = 0x0404 (1028) CPLD version = 0x0012 (18) Using built-in device list JTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E JTAG loc.: 0 IDCODE: 0x41c22093 Desc: XC3S500E IR length: 6 JTAG loc.: 1 IDCODE: 0xf5046093 Desc: XCF04S IR length: 8 JTAG loc.: 2 IDCODE: 0x06e5e093 Desc: XC2C64A-VQ44 IR length: 8 USB Read Transactions: 4 Write Transactions: 7 Control Transaction 15 # ./xc3sprog -v -c xpc xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev$ System: FreeBSD(i386): 9.0-CURRENT usb_control_msg(0x42.1 Unknown error firmware version = 0x0404 (1028) CPLD version = 0x0012 (18) Using built-in device list JTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E JTAG loc.: 0 IDCODE: 0x41c22093 Desc: XC3S500E IR length: 6 JTAG loc.: 1 IDCODE: 0xf5046093 Desc: XCF04S IR length: 8 JTAG loc.: 2 IDCODE: 0x06e5e093 Desc: XC2C64A-VQ44 IR length: 8 USB Read Transactions: 4 Write Transactions: 7 Control Transaction 15 Now I make -v -T0 test: # ./xc3sprog -v -T0 -c xpc xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev$ System: FreeBSD(i386): 9.0-CURRENT usb_control_msg(0x42.1 Unknown error firmware version = 0x0404 (1028) CPLD version = 0x0012 (18) Using built-in device list JTAG chainpos: 0 Device IDCODE = 0x41c22093 Desc: XC3S500E Reading ID_CODE 2147483647 times Sending 22 bits IDCODE Commands: 0x01fe09 Expecting 3 IDCODES : 0x06e5e093 0xf5046093 0x41c22093.................. Once I try to run JTAG scan I get: # ./xc3sprog -v -c xpc xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev$ System: FreeBSD(i386): 9.0-CURRENT usb_control_msg(0x42.1 Unknown error usb_control_msg(0x28 11) Unknown error Could not find USB dongle 03fd:0008# Could not find USB dongle 03fd:0008# usbconfig -u 1 -a 3 dump_device_desc ugen1.3: <XILINX XILINX> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x03fd idProduct = 0x0008 bcdDevice = 0x0000 iManufacturer = 0x0001 <retrieving string failed> iProduct = 0x0002 <retrieving string failed> iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 This commands takes several seconds to complete, even though the first usbconfig's took a fraction of a second. And this problem with string retrival.. I must reset a board to make it useable. Thanks, -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ ----- End forwarded message ----- -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-08 22:40:34
|
On Mon, Feb 08, 2010 at 08:58:50PM +0000, CeDeROM wrote: > On Mon, Feb 8, 2010 at 8:31 PM, Uwe Bonnes > <bo...@el...> wrote: > > did you read trunk/README, README.Win32 and the other READMEs? > > ... but I have no time right now to doublecheck it ( work rush ...) > > [..] > If you ask why do I use win32 version not FreeBSD, even through I use > FreeBSD commonly on my desktop in everyday life - the answer is simple > - because Xilinx did not release their ISE toolset for FreeBSD, linux > binaries does not work with my fbsd's linux emulation (yet), and what > is most important - I want have proved working configuration to start > messing with emulation or virtual machines on my FreeBSD workstation > :-) I dont like windows, and how things are done in here, I just want > to check what is working, what is not working, why, then create my > working environment on FreeBSD. http://wiki.freebsd.org/FreeBSD_Xilinx -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Uwe B. <bo...@el...> - 2010-02-08 21:21:39
|
>>>>> "CeDeROM" == CeDeROM <tom...@gm...> writes:
CeDeROM> On Mon, Feb 8, 2010 at 8:31 PM, Uwe Bonnes
CeDeROM> <bo...@el...> wrote:
>> did you read trunk/README, README.Win32 and the other READMEs?
>> ... but I have no time right now to doublecheck it ( work rush ...)
>>
>> Do you have libusb-win32 installed? Does libusb recognise the FT2232?
>> B.t.w. didn't you start with FreeBSD? Why did you switch?
CeDeROM> Yes, I have read readmes, I can read ;] Yes, I do have
But I still have not seen the exact commandline you use.
>From what I understand you try to use a JtagKey with VID=0x0403
PID=0xCFF8. I have not yet done any coding for ID 403/cff8, so no wonder
that it doesn't work yet. I'll try to code a path for ID 403/cff8 the next
days.
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: CeDeROM <tom...@gm...> - 2010-02-08 20:58:57
|
On Mon, Feb 8, 2010 at 8:31 PM, Uwe Bonnes <bo...@el...> wrote: > did you read trunk/README, README.Win32 and the other READMEs? > ... but I have no time right now to doublecheck it ( work rush ...) > > Do you have libusb-win32 installed? Does libusb recognise the FT2232? > B.t.w. didn't you start with FreeBSD? Why did you switch? Yes, I have read readmes, I can read ;] Yes, I do have libusb0.dll in my windows directory installed with libusb-win32-filter-bin-0.1.12.2.exe installer. Yes, the TestLibUsb-win program shows my cable as bus-0/\\.\libusb0-002-0x0403-0xcff8 0403/CFF8 Yes, I have my cable Amontec JTAGkey2P installed and working with UrJTAG. No, my cable is not detected with xc3sprogs, what I get is: "(...) No dongle found Could not open parallel port (null)" This is why I was asking you for a working invocation of the xc3sprog on your machine - to exclude possibility that I have missed some commandline switch. If you need any additional information please let me know :-) If you ask why do I use win32 version not FreeBSD, even through I use FreeBSD commonly on my desktop in everyday life - the answer is simple - because Xilinx did not release their ISE toolset for FreeBSD, linux binaries does not work with my fbsd's linux emulation (yet), and what is most important - I want have proved working configuration to start messing with emulation or virtual machines on my FreeBSD workstation :-) I dont like windows, and how things are done in here, I just want to check what is working, what is not working, why, then create my working environment on FreeBSD. Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info |
|
From: Uwe B. <bo...@el...> - 2010-02-08 20:43:29
|
>>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes:
Wojciech> xc3sprog project (c) 2005-2010 Uwe Bonnes
Wojciech> bo...@el... WWW:
The work was started by Andrew, others dropped in and now most contributions
are mine. But that doesn't give me the whole copyright.
Wojciech> http://sourceforge.net/projects/xc3sprog Release: $Rev: 426 $
Wojciech> System: FreeBSD(i386): 9.0-CURRENT
Wojciech> usage: xc3sprog [options] <bitfile>
I'll consider the usage changes....
Wojciech> ./xc3sprog -T0 -c xpc
Wojciech> /home/wkoszek/fpga/fbsd-prog/xup-0.0.2/w/wkoszek_leds/leds.bit
Wojciech> Release $Rev: 426 $ Free software: If you contribute nothing,
Wojciech> expect nothing! Please provide feedback on
Wojciech> success/failure/enhancement requests! Check Sourceforge SVN
Wojciech> for updates! usb_control_msg(0x42.1 Unknown error firmware
Wojciech> version = 0x0404 (1028) CPLD version = 0x0012 (18) Reading
Wojciech> ID_CODE 2147483647 times Sending 22 bits IDCODE Commands:
Wojciech> 0x01fe09 Expecting 3 IDCODES : 0x06e5e093 0xf5046093
Wojciech> 0x41c22093
Give the verbose option and you will see lots of dots printed for lots aof
successfill JTAG queue queries.
Wojciech> This 'usb_control_msg(0x42.1 Unknown error' appears here as
Wojciech> well. BTW, a friend of mine confirmed that he can program his
Wojciech> S3ESK board under his FreeBSD 8 system without a problem with
Wojciech> some of my random notes.
I'll look again at the 0x42.1 message again. What Xilinx dobgle is that,
what firmware file loaded?
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: Uwe B. <bo...@el...> - 2010-02-08 20:31:56
|
>>>>> "CeDeROM" == CeDeROM <tom...@gm...> writes:
CeDeROM> Hello Uwe! On Mon, Feb 8, 2010 at 11:54 AM, Uwe Bonnes
CeDeROM> <bo...@el...> wrote:
>> For me and some coworkers, xc3sprog works with SPI flash and S33. I
>> tested with FT2232 cable and on windows too. So if you have an error
>> report or enhancement request, please, be explicit.
>>
>> For me it looks like people didn't notice the bscan_bpi subdirectory
>> and the need to load the bscan_bpi bitmap first.
CeDeROM> Uwe, this is good information that S33 flashing works - could
CeDeROM> you please send me your full commandline invocation of the
CeDeROM> Intel S33 programming via FT2232 cable? My version of xc3sprogs
CeDeROM> (fresh win32 binary downloaded from the project site) did not
CeDeROM> recognise any usable cable... but I have no time right now to
CeDeROM> doublecheck it (university rush, next week Ill get to it). The
CeDeROM> documentation says that I need libusb to crompile the software,
CeDeROM> there are some cable specific switches in help list, but I
CeDeROM> could not find any switch to select my FT2232 cable - are there
CeDeROM> any, or it should be defected automaticaly? I am a bit confised
CeDeROM> :-) If you send me and example invocation I will know what is
CeDeROM> working. Thank you in advance!
Tomek,
did you read trunk/README, README.Win32 and the other READMEs?
... but I have no time right now to doublecheck it ( work rush ...)
Do you have libusb-win32 installed? Does libusb recognise the FT2232?
B.t.w. didn't you start with FreeBSD? Why did you switch?
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: CeDeROM <tom...@gm...> - 2010-02-08 20:11:33
|
Hello Uwe! On Mon, Feb 8, 2010 at 11:54 AM, Uwe Bonnes <bo...@el...> wrote: > For me and some coworkers, xc3sprog works with SPI flash and S33. I tested > with FT2232 cable and on windows too. So if you have an error report or > enhancement request, please, be explicit. > > For me it looks like people didn't notice the bscan_bpi subdirectory and > the need to load the bscan_bpi bitmap first. Uwe, this is good information that S33 flashing works - could you please send me your full commandline invocation of the Intel S33 programming via FT2232 cable? My version of xc3sprogs (fresh win32 binary downloaded from the project site) did not recognise any usable cable... but I have no time right now to doublecheck it (university rush, next week Ill get to it). The documentation says that I need libusb to crompile the software, there are some cable specific switches in help list, but I could not find any switch to select my FT2232 cable - are there any, or it should be defected automaticaly? I am a bit confised :-) If you send me and example invocation I will know what is working. Thank you in advance! Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-08 19:26:21
|
On Tue, Jan 19, 2010 at 05:15:01PM +0100, Uwe Bonnes wrote: > >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > > ... > Wojciech> Before I prepare a port of xc3sprog for FreeBSD, I'll probably > Wojciech> send you some more stuff. I want your xc3sprog to be > Wojciech> identified well (Author+project URL), so that there is no > Wojciech> confusion with Andrew Rogers' stuff and XUP code. > > Wojciech> Do they have something which your code doesn't have? > > I started from Rogers sources, so everything should be included. > > XUP uses a different firmware for the DLC9/10 dongles. No need for the a > different firmware with kawk's reverse engineering the Xilinx protocoll. I > didn't check if they added anythging else. > > >> I added the errno.h in the FreeBSD conditional path. (Rev 428) > >> > >> A CMAKE Toolchain File is only needed for crosscompiling. Did you > >> crosscompile? Or does CMAKE not work appropriate on FreeBSD? It's > >> added as Rev 429. > > Wojciech> I just assumed you pick one CMAKE file for one family of > Wojciech> systems. Can you use this string (system name) in the xc3sprog > Wojciech> output somehow? > > Normally you start "cmake" and it should configure for the running > system. Toolchainfiles only needed for crosscompiling. As I run on Suse > 64-bit, I needed the Toolchain-SUSE32.cmake to compile the 32-bit binary. Sorry for delay. Indeed 'cmake' works for me. I don't have a setup to try cross-compilation out.. Don't remove the file yet -- I'll keep you posted. Andrew Rogers, XUP people and your code share the same name. So if I say "xc3sprog" to someone new with those projects, we'll probably pick Andrew's code. My idea is to modify existing "hello message": Free software: If you contribute nothing, expect nothing! Please provide feedback on success/failure/enhancement requests! Check Sourceforge SVN for updates! To something more meaningful. Ideally, xc3sprog program would become 'xilprog' or similar to cut off the historical baggage, but it's probably too late. To help a bit, I propose this patch: http://freebsd.czest.pl/~wkoszek/fpga/xc3sprog.1.patch (hand-edited patch against revision 426). It generates: xc3sprog project (c) 2005-2010 Uwe Bonnes bo...@el... WWW: http://sourceforge.net/projects/xc3sprog Release: $Rev: 426 $ System: FreeBSD(i386): 9.0-CURRENT usage: xc3sprog [options] <bitfile> Possible options: -h Print this help. -c Choose programmer type [pp|ftdi|fx2|xpc]. -C Verify device against file (no programming). -e file EEPROM file. -f file File with fuse bits. -i Input file format (BIT|BIN|MCS|MCSREV|HEX). -I Work on connected SPI Flash (ISF Mode). (after 'bscan_spi' bitfile for device has been loaded). -j Detect JTAG chain, nothing else (default action). -L Program lockbits if defined in fusefile. -m <dir> Directory with XC2C mapfiles. -o Output file format (BIT|BIN|MCS|MCSREV|HEX). -p Possition in the JTAG chain. -r Read from device and write to file. -T val Test chain 'val' times (0 = forever) or 10000 times default. In ISF Mode, test the SPI connection. -v Verbose output. Programmer specific options: -d (pp only ) Parallel port device. -t (xpc only ) NONE or INT (Internal Chain , not for DLC10)) -s num (ftdi/fx only) Serial number string. -t type (ftdi/fx only) Type can be [NONE|IKDA|OLIMEX|FTDI_JTAG|AMONTEC]. -P pid (ftdi/fx only) Product ID. -S desc (ftdi/fx only) Product ID string. -V vid (ftdi/fx only) Vendor ID. Apart from that, it removes redundant ":" after 'T' and removes 'D' from getopt(), which isn't supported. I'd also stay away from falling back to parallel port and all sorts of autodetection. No -c given should be considered a mistake, IMO. > ... > Wojciech> At home I'll just comment it out and perform some tests with > Wojciech> small/big bitfiles and see if everything is more broken. > > Look at the -T0 option to keep JTAG busy. This is what I did: wkoszek@laptop:/media/Multimedia/fpga/XC3SPROG/xc3sprog/trunk/build# ./xc3sprog -T0 -c xpc /home/wkoszek/fpga/fbsd-prog/xup-0.0.2/w/wkoszek_leds/leds.bit Release $Rev: 426 $ Free software: If you contribute nothing, expect nothing! Please provide feedback on success/failure/enhancement requests! Check Sourceforge SVN for updates! usb_control_msg(0x42.1 Unknown error firmware version = 0x0404 (1028) CPLD version = 0x0012 (18) Reading ID_CODE 2147483647 times Sending 22 bits IDCODE Commands: 0x01fe09 Expecting 3 IDCODES : 0x06e5e093 0xf5046093 0x41c22093 This 'usb_control_msg(0x42.1 Unknown error' appears here as well. BTW, a friend of mine confirmed that he can program his S3ESK board under his FreeBSD 8 system without a problem with some of my random notes. -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Uwe B. <bo...@el...> - 2010-02-08 11:55:07
|
>>>>> "CeDeROM" == CeDeROM <tom...@gm...> writes:
CeDeROM> Hello Wojciech! 2010/2/8 Wojciech A. Koszek
CeDeROM> <wk...@fr...>:
>>> Did anyone manage to program Intel S33 SPI Flash, or BPI Flash
>>> memory on Xilinx's Spartan 3A-DSP board?
>> Don't you want to use Xilinx ISE IDE?
CeDeROM> 1. I dont have Xilinx platform cable, but FT2232C/H, so I
CeDeROM> cannot use it directly from ISE... 2. Official Xilinx IDE
CeDeROM> called ISE does not and will not support SPI S33 Flash memory
CeDeROM> that resides on this Xilinx DevelKit - their solution is to
CeDeROM> replace chip into a Numonyx one. 3. I cannot program BPI
CeDeROM> because there is no support in Xilinx ISE for BPI :\ 4. I have
CeDeROM> managed to produce SVF file and upload it into RAM
CeDeROM> configuration memory in FPGA devoce (XC3SD1800A).
CeDeROM> I think I have to write my own IP-Core to support both of these
CeDeROM> memories and add this functionality to UrJTAG - just wanted to
CeDeROM> ask in here to make sure. But first I have to verify if PROM
CeDeROM> file produced for M25P64 is the same as it would be for
CeDeROM> S33... otherwise there is no way to produce S33 PROM file from
CeDeROM> Xilinx ISE to program official Xilinx DevelKit :-(
For me and some coworkers, xc3sprog works with SPI flash and S33. I tested
with FT2232 cable and on windows too. So if you have an error report or
enhancement request, please, be explicit.
For me it looks like people didn't notice the bscan_bpi subdirectory and
the need to load the bscan_bpi bitmap first.
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: CeDeROM <tom...@gm...> - 2010-02-08 08:05:00
|
Hello Wojciech! 2010/2/8 Wojciech A. Koszek <wk...@fr...>: >> Did anyone manage to program Intel S33 SPI Flash, or BPI Flash memory >> on Xilinx's Spartan 3A-DSP board? > > Don't you want to use Xilinx ISE IDE? 1. I dont have Xilinx platform cable, but FT2232C/H, so I cannot use it directly from ISE... 2. Official Xilinx IDE called ISE does not and will not support SPI S33 Flash memory that resides on this Xilinx DevelKit - their solution is to replace chip into a Numonyx one. 3. I cannot program BPI because there is no support in Xilinx ISE for BPI :\ 4. I have managed to produce SVF file and upload it into RAM configuration memory in FPGA devoce (XC3SD1800A). I think I have to write my own IP-Core to support both of these memories and add this functionality to UrJTAG - just wanted to ask in here to make sure. But first I have to verify if PROM file produced for M25P64 is the same as it would be for S33... otherwise there is no way to produce S33 PROM file from Xilinx ISE to program official Xilinx DevelKit :-( Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-08 02:25:05
|
On Sun, Jan 31, 2010 at 10:14:35PM +0000, CeDeROM wrote: > Hello world! > > Did anyone manage to program Intel S33 SPI Flash, or BPI Flash memory > on Xilinx's Spartan 3A-DSP board? > Why usb cablel is not available by default on windows version? > Anyone knows good/any solution to build Verilog/VHDL code into bitfile > on FreeBSD? Don't you want to use Xilinx ISE IDE? -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-02 10:42:31
|
On Tue, Feb 02, 2010 at 10:56:03AM +0100, Uwe Bonnes wrote: > >>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes: > > Wojciech> On Mon, Feb 01, 2010 at 10:39:10PM +0000, CeDeROM wrote: > >> Hello Uwe! > >> > >> On Mon, Feb 1, 2010 at 9:31 AM, Uwe Bonnes > >> <bo...@el...> wrote: > I tested reading > >> the ADSP board when adapting the SPI code. There is no BPI > code > >> yet, but contributions are welcome. I did not test write the S33 on > >> > the ADSP, but i think I tested on other boards. What did you do? > >> What didn't > work as expected? > > Wojciech> [..] > >> > The DLC9/10 needs firmware that is installed when the impact > >> driver is > installed. > >> > >> Im using FT2232 and FT2232H based cables - none of them was detected > >> on the binary for win32. Are they supported off the box or I must > >> recompile? Has anyone managed to run xc3sprogs on FreeBSD? > > Wojciech> With Spartan 3E Starter Kit it works with its internal USB > Wojciech> JTAG stuff on FreeBSD-9 CURRENT. > > Wojciech> I have FTDI-based ARM JTAG debugger, which is Amontec cable > Wojciech> clone, and since Amontec advertises possibility of replaying > Wojciech> SVFs via their device, it might be possible here as well. > > Wojciech> There were some problems with parallel cable and I've sent a > Wojciech> report to this list. Hopefully we'll be able to see it > Wojciech> shortly, as it's waiting for a moderator. > > The list maintainer didn't answer yet. Probably I'll have to make an > takeover, but give us some timne... > > Wojciech, as I told Tomek your reports aren't very exact. Please tell > Tomek: Your report isn't exact. You don't tell > - what version of xc3sprog you use > - who you invoked xc3sprog > - how the dongle or it's USB device is recognized by the OS > - whether you checked user access to the device > - what output you got > - what you expected > - what you didn't like/understand with that output > - what Readme you have reads > - whether you loaded the bscan_spi bitmap before writing to the SPI flash > ... I don't know which report do you refer to here. My report mailed to you privately contains all this information. Have you read it? -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: Uwe B. <bo...@el...> - 2010-02-02 09:56:27
|
>>>>> "Wojciech" == Wojciech A Koszek <wk...@Fr...> writes:
Wojciech> On Mon, Feb 01, 2010 at 10:39:10PM +0000, CeDeROM wrote:
>> Hello Uwe!
>>
>> On Mon, Feb 1, 2010 at 9:31 AM, Uwe Bonnes
>> <bo...@el...> wrote: > I tested reading
>> the ADSP board when adapting the SPI code. There is no BPI > code
>> yet, but contributions are welcome. I did not test write the S33 on
>> > the ADSP, but i think I tested on other boards. What did you do?
>> What didn't > work as expected?
Wojciech> [..]
>> > The DLC9/10 needs firmware that is installed when the impact
>> driver is > installed.
>>
>> Im using FT2232 and FT2232H based cables - none of them was detected
>> on the binary for win32. Are they supported off the box or I must
>> recompile? Has anyone managed to run xc3sprogs on FreeBSD?
Wojciech> With Spartan 3E Starter Kit it works with its internal USB
Wojciech> JTAG stuff on FreeBSD-9 CURRENT.
Wojciech> I have FTDI-based ARM JTAG debugger, which is Amontec cable
Wojciech> clone, and since Amontec advertises possibility of replaying
Wojciech> SVFs via their device, it might be possible here as well.
Wojciech> There were some problems with parallel cable and I've sent a
Wojciech> report to this list. Hopefully we'll be able to see it
Wojciech> shortly, as it's waiting for a moderator.
The list maintainer didn't answer yet. Probably I'll have to make an
takeover, but give us some timne...
Wojciech, as I told Tomek your reports aren't very exact. Please tell
Tomek: Your report isn't exact. You don't tell
- what version of xc3sprog you use
- who you invoked xc3sprog
- how the dongle or it's USB device is recognized by the OS
- whether you checked user access to the device
- what output you got
- what you expected
- what you didn't like/understand with that output
- what Readme you have reads
- whether you loaded the bscan_spi bitmap before writing to the SPI flash
...
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: Uwe B. <bo...@el...> - 2010-02-02 09:51:02
|
>>>>> "CeDeROM" == CeDeROM <tom...@gm...> writes:
CeDeROM> Hello (Czesc) Wojciech! :-) 2010/2/1 Wojciech A. Koszek
CeDeROM> <wk...@fr...>:
>> With Spartan 3E Starter Kit it works with its internal USB JTAG stuff
>> on FreeBSD-9 CURRENT.
CeDeROM> Mmm, good to know another low level BSD user! :-) Im working on
CeDeROM> 8.0-RELEASE, did not try to compile xc3sprog as I need to
CeDeROM> finish some other work before, but Ive modified a bit PONG demo
CeDeROM> from Spartan 3E to test my Spartan 3A-DSP. What kind of memory
CeDeROM> resides on 3E board - it it S33 SPI Intel Flash? Did you manage
CeDeROM> to generate prom file and upload it into that flash memory?
It's nice to see discussion on this mailing list
CeDeROM> How about port for xc3sprog? :-)
CeDeROM> Sorry for the question, but is xc3sprog mentioned to be
CeDeROM> standalone application? Wouldn't be more convenient to add its
CeDeROM> functinoality into UrJTAG? ;P
xc3sprog is standalone, controlled by the commandline and easily usable in
makefiles.
Urjtag has abother scope. xc3sprog provides the programming algos for known
devices, while urjtag plays SVF produces in some other way.
>> I have FTDI-based ARM JTAG debugger, which is Amontec cable clone,
>> and since Amontec advertises possibility of replaying SVFs via their
>> device, it might be possible here as well.
Tomek: Your report isn't exact. You don't tell
- what version of xc3sprog you use
- who you invoked xc3sprog
- how the dongle or it's USB device is recognized by the OS
- whether you checked user access to the device
- what output you got
- what you expected
- what you didn't like/understand with that output
- what Readme you have reads
- whether you loaded the bscan_spi bitmap before writing to the SPI flash
...
Pleasetry the examples given in .../trunk/README and give annotated feedback.
CeDeROM> Yes, Ive got both of them - Amontec JTAGkey2P and
CeDeROM> ARM-USB-OCD. There are some issues with JTAGkey2P and FreeBSD
CeDeROM> as it uses FT2232H and our system still use 0.14 libftdi - Ive
CeDeROM> noticed maintainer for update :-) Ive managed to play SVF with
CeDeROM> both cables under win32.
SVF player can only report that something got wrong, a real programmer can
give more hints.
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: CeDeROM <tom...@gm...> - 2010-02-01 23:18:41
|
Hello (Czesc) Wojciech! :-) 2010/2/1 Wojciech A. Koszek <wk...@fr...>: > With Spartan 3E Starter Kit it works with its internal USB JTAG stuff > on FreeBSD-9 CURRENT. Mmm, good to know another low level BSD user! :-) Im working on 8.0-RELEASE, did not try to compile xc3sprog as I need to finish some other work before, but Ive modified a bit PONG demo from Spartan 3E to test my Spartan 3A-DSP. What kind of memory resides on 3E board - it it S33 SPI Intel Flash? Did you manage to generate prom file and upload it into that flash memory? How about port for xc3sprog? :-) Sorry for the question, but is xc3sprog mentioned to be standalone application? Wouldn't be more convenient to add its functinoality into UrJTAG? ;P > I have FTDI-based ARM JTAG debugger, which is Amontec cable clone, and since > Amontec advertises possibility of replaying SVFs via their device, it might be > possible here as well. Yes, Ive got both of them - Amontec JTAGkey2P and ARM-USB-OCD. There are some issues with JTAGkey2P and FreeBSD as it uses FT2232H and our system still use 0.14 libftdi - Ive noticed maintainer for update :-) Ive managed to play SVF with both cables under win32. > There were some problems with parallel cable and I've sent a report > to this list. Hopefully we'll be able to see it shortly, as it's > waiting for a moderator. Parallel cables are simple to build and so it is nice to have them, however almost no modern computer have them onboard anymore - this is why Ive switched to USB and most generic FT2232 ones. Best regards, Tomek Cedro -- CeDeROM, http://www.tomek.cedro.info |
|
From: Wojciech A. K. <wk...@Fr...> - 2010-02-01 22:51:22
|
On Mon, Feb 01, 2010 at 10:39:10PM +0000, CeDeROM wrote: > Hello Uwe! > > On Mon, Feb 1, 2010 at 9:31 AM, Uwe Bonnes > <bo...@el...> wrote: > > I tested reading the ADSP board when adapting the SPI code. There is no BPI > > code yet, but contributions are welcome. I did not test write the S33 on > > the ADSP, but i think I tested on other boards. What did you do? What didn't > > work as expected? [..] > > > The DLC9/10 needs firmware that is installed when the impact driver is > > installed. > > Im using FT2232 and FT2232H based cables - none of them was detected > on the binary for win32. Are they supported off the box or I must > recompile? > Has anyone managed to run xc3sprogs on FreeBSD? With Spartan 3E Starter Kit it works with its internal USB JTAG stuff on FreeBSD-9 CURRENT. I have FTDI-based ARM JTAG debugger, which is Amontec cable clone, and since Amontec advertises possibility of replaying SVFs via their device, it might be possible here as well. There were some problems with parallel cable and I've sent a report to this list. Hopefully we'll be able to see it shortly, as it's waiting for a moderator. -- Wojciech A. Koszek wk...@Fr... http://FreeBSD.czest.pl/~wkoszek/ |
|
From: CeDeROM <tom...@gm...> - 2010-02-01 22:39:18
|
Hello Uwe! On Mon, Feb 1, 2010 at 9:31 AM, Uwe Bonnes <bo...@el...> wrote: > I tested reading the ADSP board when adapting the SPI code. There is no BPI > code yet, but contributions are welcome. I did not test write the S33 on > the ADSP, but i think I tested on other boards. What did you do? What didn't > work as expected? I was trying to generate bitstream of my project with ISE (most recent one 11.4 i think), but no S33 is on the list - Xilinx sux ass in this matter - I have chosen M25P64 as a replacement from Numonyx, then generated SVF file and then played that SVF file with UrJTAG. Loading file into Flash takes a long time and fails. Uploading bitstream directly into FPGA works fine, and project works until power is on. I am wondering if the prom file is wrong, or programming the flash fails. I think that there is no communication with flash, as its content remains after playing SVF containing "erase-write-verify" cycle... so I am lookins some other tools to program that S33 memory, or BPI memory instead :-) I could use my JTAG adapter as ISP programmer directly on the Flash Chip, but using FPGA-JTAG seems more versatile, especialy if no SPI pinout is available on the PCB... Maybe the core uploaded into FPGA for programming the flash use some different programming algorithm, but as I have seen on the M25P64 document page thet are almost compatibile, except the mass/block erase available on S33. > The DLC9/10 needs firmware that is installed when the impact driver is > installed. Im using FT2232 and FT2232H based cables - none of them was detected on the binary for win32. Are they supported off the box or I must recompile? Has anyone managed to run xc3sprogs on FreeBSD? Best regards, Tomek -- CeDeROM, http://www.tomek.cedro.info |
|
From: Uwe B. <bo...@el...> - 2010-02-01 09:31:49
|
>>>>> "CeDeROM" == CeDeROM <tom...@gm...> writes:
CeDeROM> Hello world! Did anyone manage to program Intel S33 SPI Flash,
CeDeROM> or BPI Flash memory on Xilinx's Spartan 3A-DSP board? Why usb
CeDeROM> cablel is not available by default on windows version? Anyone
CeDeROM> knows good/any solution to build Verilog/VHDL code into bitfile
CeDeROM> on FreeBSD?
Well,
I tested reading the ADSP board when adapting the SPI code. There is no BPI
code yet, but contributions are welcome. I did not test write the S33 on
the ADSP, but i think I tested on other boards. What did you do? What didn't
work as expected?
The DLC9/10 needs firmware that is installed when the impact driver is
installed.
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: CeDeROM <tom...@gm...> - 2010-01-31 22:14:42
|
Hello world! Did anyone manage to program Intel S33 SPI Flash, or BPI Flash memory on Xilinx's Spartan 3A-DSP board? Why usb cablel is not available by default on windows version? Anyone knows good/any solution to build Verilog/VHDL code into bitfile on FreeBSD? Best regards, Tomek Cedro -- CeDeROM, http://www.tomek.cedro.info |
4 messages has been excluded from this view by a project administrator.
