Site Home Archive Home FAQ Home How to search the Archive How to Navigate the Archive
Compare FPGA features and resources
Threads starting:
Authors:A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
> "Early Silicon" is my interpretation of ES. To call it "Engineering > Samples" would be misleading. These are full-quality, fully tested and > characterized parts that work over temperature and voltage ranges. Utter bullshit. Usually you write very fair replies but this is just nonsense. I have ES1 and ES4 parts from Xilinx that are only sold as no refunds, no returns, with major components that do not work. They are not full quality at all. These particular Virtex 5 parts may be very good, but it is certainly not true for your entire product range and people should not be mislead in to believing otherwise. > This is Early Silicon, and any design error (and there often is, since > nobody is perfect the first time around) it is described on an errata > sheet. Thus not "full-quality" > Maybe I can help to reduce the usual design-in delay, to your and to > our benefit. What can I say, I made the mistake of not delaying design-in of Virtex 4 FX parts and am still paying the price today. Cheers, JonArticle: 109176
Hi Antti, Antti wrote: > I still wish Xilinx FPGAs would have the config Clock accessible again > as it was with old Xilinx FPGAs ! A little bit of a late response here, but the STARTUP_VIRTEX5 primitive gives you access to both the configuration clock and the internal housekeeping clock. See http://toolbox.xilinx.com/docsan/xilinx82/books/docs/v5ldl/v5ldl.pdf for the full usage in HDL. -mArticle: 109177
I wanted to stress that ES parts are tested and reliable. They do not wear out or slowly go bad on you. The Virtex-4FXES devices had severe functional and parametric (but not "reliability") problems, as covered in the errata sheets. We are all very sorry about this, and we have made sure that the next generation design is far more robust. Peter AlfkeArticle: 109178
Thank you very much, Brian. I have succeeded to write the data to desired location by modifying the linker script. Thank, Cathy.Article: 109179
John McGrath wrote: > Jon Beniston wrote: > > > but it uses verilog at such advanced level that is not supported > > > by Xilinx XST synthesis, e.g. it is only useable with Synplify > > > as synthesis tool > > > > It's about time Xilinx had full Verilog 2001 support really. What year > > is it? > > > > Still, on the plus side, if you do use Synplify, at least the rest of > > your design might work too ;-) > > > > Cheers, > > Jon > > In fairness, the verilog2001 support is not the issue. > The main reason the source did not compile was XST's adherence to some > rules, like naming generate statement begin blocks, etc, and an issue > with using clogb2 in a parameter. > All small issues really - few tweaks here and there, took me a half an > hour to do, and it synthesized! > > This was for a (very) basic configuration, I just tried to synth this > to the slowest speed grade V5, > > Number of Slice Registers: 780 > Number of Slice LUTs: 1174 > Number used as Logic: 1046 > Number used as Memory: 128 > Number used as RAM: 128 > > and it came out at 170MHz (post synth timing only - did not run PAR). > Would be Interesting to see if it works, and with more features turned > on..though I have no time to test it.. > But XST can do it - with relatively small amount of code massaging. I don't understand the idea of using post syn timing. Is that at all accurate? Why not let it do a PAR and see what kind of real results you get? I guess I shouldn't knock post syn timing. The eval I did on my CPU gave pretty close numbers between syn and PAR. I think it actually sped up a little in PAR.Article: 109180
Yes, it can be run via commandline. In the ispLEVER help do a search for 'memedit', this is the memory initialization tool executable. In the search results select 'Running MEMEDIT from the Command Line' to open the MEMEDIT help page. Kevin Antti wrote: > Kevin schrieb: > > > Johannes, > > > > Lattice's current software, ispLEVER 6.0 does offer the ability to > > reinitialize your memory contents without recompiling your design. > > Using the Memory Initialization tool, accessed from the tools menu, a > > new, or modified memory file .mem can be written to the designs > > database file .ncd. After this is done all that needs to be rerun is > > the 'Generate Bitstream Data' process. This feature is only available > > for use on memory blocks that are implemented in the devices EBR blocks > > and created using the software's IPExpress module generation tool. > > is the memory init available from commandline also? > the GUI tool is known to exist for some time, the commandline > bit file merging is far less documented > > AnttiArticle: 109181
Peter Alfke wrote: > I wanted to stress that ES parts are tested and reliable. They do not > wear out or slowly go bad on you. To be fair, I've have no problems with what is isn't listed in the errata. Cheers, JonArticle: 109182
> I don't understand the idea of using post syn timing. Is that at all > accurate? Sometimes it is close, sometimes it is woefully inaccurate. > Why not let it do a PAR and see what kind of real results you get? It's the only way to know. Cheers, JonArticle: 109183
Hi: I'm considering to buy a Dell Precision M90 laptop to replace a regular PC on a cart that was used to wheel around and program various embedded devices. The new laptops of course don't offer old-fashioned ports like parallel and RS-232. Well, some have serial, but the M90 doesn't. I will be getting the docking station which *does* have a parallel and serial port though, so it should be just fine. There is also the option of USB->RS-232 converters. But the dock's parallel port will be critically important to work correctly. I will need to connect to the following devices: Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) Spectrum Digital eZdsp 'F2812 (parallel) Xilinx Parallel Cable IV (parallel) In the future there will likely be a USB JTAG Emulator for the 'F2812, and perhaps I'll upgrade to a better Xilinx cable. Also will probably get into some Xilinx FPGAs and 3rd party development boards, but just need to be sure I can work my present tools. Anyone have any serious problems with Dell laptops for these or other tools? Thanks for input. -- Good day! ________________________________________ Christopher R. Carlen Principal Laser&Electronics Technologist Sandia National Laboratories CA USA crcarleRemoveThis@BOGUSsandia.gov NOTE, delete texts: "RemoveThis" and "BOGUS" from email address to reply.Article: 109184
Hello Chris, > > I'm considering to buy a Dell Precision M90 laptop to replace a regular > PC on a cart that was used to wheel around and program various embedded > devices. > > The new laptops of course don't offer old-fashioned ports like parallel > and RS-232. Well, some have serial, but the M90 doesn't. > > I will be getting the docking station which *does* have a parallel and > serial port though, so it should be just fine. There is also the option > of USB->RS-232 converters. But the dock's parallel port will be > critically important to work correctly. > > I will need to connect to the following devices: > > Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) > > Spectrum Digital eZdsp 'F2812 (parallel) > > Xilinx Parallel Cable IV (parallel) > > In the future there will likely be a USB JTAG Emulator for the 'F2812, > and perhaps I'll upgrade to a better Xilinx cable. Also will probably > get into some Xilinx FPGAs and 3rd party development boards, but just > need to be sure I can work my present tools. > > Anyone have any serious problems with Dell laptops for these or other > tools? > I don't know how their docking stations work but I'd be suspicious. Programmers often bit-bang the parallel port directly and that typically doesn't work if they chose to simply convert USB-parallel in the dock station. My suggestion would be to pay a little more and get a laptop with a genuine parallel port. -- Regards, Joerg http://www.analogconsultants.comArticle: 109185
Bug in saving MSR from within system calls. Sample patch attached that fixes the problem. XMK comes from a time where there was no APU interface or an FPU, which are the only bits of interest in the MSR for each process. The hardware has caught up in the meanwhile :) Vasanth "Andreas Hofmann" <ahofmann@ti.cs.uni-frankfurt.de> wrote in message news:eetohk$3fl$1@tantalos.rbi.informatik.uni-frankfurt.de... > Vasanth Asokan schrieb: > > Hi, > >> Are the fsl() functions being invoked in the same task (after a context >> switch) or in a different task? > > There are two task running: one who invokes the fsl() functions and one > which just spends some CPU time to increment an int value. The latter > task is not necessary, calling sleep() in the task invoking the fsl() > functions leads to similar behaviour because of the context switch to > the idle task. > >> If in a different task - are you enabling the MSR APU bits prior to the >> kernel being initialized? Global processor level initialization (such as >> MSR, caches and other core registers) should happen before >> xilkernel_main(). >> This will convey the user's intent regarding the processor state to the >> kernel and ensure that all subsequent task switches get the same MSR >> value. > > Caches are disabled and APU is enabled in main() prior to invoking > xilkernel_main(). The task invoking the fsl() functions is statically > defined in the static_pthread_table. > > This is the failing code: > > //----------------------------------------------------------------------------- > #include "xmk.h" > #include "xparameters.h" > #include "xbasic_types.h" > #include "xcache_l.h" > #include "xpseudo_asm.h" > #include "stdio.h" > #include "pthread.h" > > void enable_APU() > { > Xuint32 msr_value = mfmsr(); > msr_value |= XREG_MSR_APU_AVAILABLE; > mtmsr(msr_value); > } > > > void* busy() > { > int l = 0; > > while( l < (2 << 2) ) > { > int k = 0; > while( k < (1 << 18) ) > k++; > l++; > } > > return 0; > } > > void* user_main() > { > > pthread_t busy_thread; > pthread_create(&busy_thread, 0, busy, 0); > > print("PPC_CHAT -- Entering user_main() --\r\n"); > > // provoke context switch > yield(); > > enable_APU(); // bit is cleared after context switch! > putfsl(21, 0); > > print("Send succeded.\r\n"); > > volatile int i = -1; > getfsl(i, 0); > > xil_printf("Reply: %d\r\n", i); > > print("PPC_CHAT -- Exiting user_main() --\r\n"); > > return 0; > } > > int main() > { > XCache_DisableICache(); > XCache_DisableDCache(); > > enable_APU(); > > // starting kernel > xilkernel_main(); > > return 0; > } > //----------------------------------------------------------------------------- > > > Regards, > AndreasArticle: 109186
"Chris Carlen" <crcarleRemoveThis@BOGUSsandia.gov> wrote in message news:eev1s101dh2@news3.newsguy.com... > Spectrum Digital eZdsp 'F2812 (parallel) > > Xilinx Parallel Cable IV (parallel) > > In the future there will likely be a USB JTAG Emulator for the 'F2812, and > perhaps I'll upgrade to a better Xilinx cable. Also will probably get > into some Xilinx FPGAs and 3rd party development boards, but just need to > be sure I can work my present tools. > > Anyone have any serious problems with Dell laptops for these or other > tools? Coincidentally only today I was discussing using a Spectrum Digital XDS510PP on a Dell with someone. They were unsuccessful with three different PCMCIA card parallel ports, and they did not have a 'proper' port replicator. By 'proper' I mean a real hardware parallel port appearing at 0x378 on IRQ7. I suggested some workarounds that I have used very successfully on Toshiba laptops for the SD JTAG PP emulator and await the reply. These include moving the phantom internal parallel port to somewhere else (eg, 0x278 or 0x3BC) and sometimes having to hack the .inf file that comes with PCMCIA parallel port adaptors. If the port replicator is a Dell unit designed specifically for the laptop and does _not_ simply replicate parallel ports via a USB port, then you will probably be OK. Forget it if it's a USB-type replicator. Good luck, HowardArticle: 109187
> When I was donwloading bit files to the target FPGA device, the process ran up to around 95% and error message appeared. I have to close the IMPACT program and re-try again. It worked after several times. This happens everytime I download the bit file for the first time. What is the problem? I would guess this is a hardware design issue. The JTAG lines in the hardware are missing terminators, missing buffers, certain chips they are tied to are left unpopulated, or they are longer than the spec. Are you running in bi-directional parallel mode or ECP? What version of ISE? What chipset is the parallel controller on your motherboard? Windows or Linux?Article: 109188
In comp.arch.fpga Joerg <notthisjoergsch@removethispacbell.net> wrote: > My suggestion would be to pay a little more and get a laptop with a > genuine parallel port. PCMCIA Cards might be another option... -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------Article: 109189
Hello Uwe, > >>My suggestion would be to pay a little more and get a laptop with a >>genuine parallel port. > > PCMCIA Cards might be another option... Yes. Although I was cautioned by TI that the MSP430 JTAG programmer might show some quirks if I did that. In the end I switched all tools to USB. -- Regards, Joerg http://www.analogconsultants.comArticle: 109190
On 21 Sep 2006 13:16:08 -0700, "Jon Beniston" <jon@beniston.com> wrote: >> "Early Silicon" is my interpretation of ES. To call it "Engineering >> Samples" would be misleading. These are full-quality, fully tested and >> characterized parts that work over temperature and voltage ranges. > >Utter bullshit. Usually you write very fair replies but this is just >nonsense. I have ES1 and ES4 parts from Xilinx that are only sold as no >refunds, no returns, with major components that do not work. They are >not full quality at all. These particular Virtex 5 parts may be very >good, but it is certainly not true for your entire product range and >people should not be mislead in to believing otherwise. > >> This is Early Silicon, and any design error (and there often is, since >> nobody is perfect the first time around) it is described on an errata >> sheet. > >Thus not "full-quality" > >> Maybe I can help to reduce the usual design-in delay, to your and to >> our benefit. > >What can I say, I made the mistake of not delaying design-in of Virtex >4 FX parts and am still paying the price today. > >Cheers, >Jon I think some slack needs to be cut for Xilinx here :-) At least they are clearly labelling their ES parts (be engineering sample or early silicon) as such. If any of you use an Intel or AMD cpu ;-) go to their respective web sites and look for the errata on the shipping products. Intel's latest cpu has tens of erratas some of which will be fixed in a later stepping. AMD's cpu have around half a dozen which won't be fixed. Anyone who has done any IC development knows how difficult it is to get it right but most of us do, ... eventually.Article: 109191
Joerg wrote: > Hello Chris, > > > > > I'm considering to buy a Dell Precision M90 laptop to replace a regular > > PC on a cart that was used to wheel around and program various embedded > > devices. > > > > The new laptops of course don't offer old-fashioned ports like parallel > > and RS-232. Well, some have serial, but the M90 doesn't. > > > > I will be getting the docking station which *does* have a parallel and > > serial port though, so it should be just fine. There is also the option > > of USB->RS-232 converters. But the dock's parallel port will be > > critically important to work correctly. > > > > I will need to connect to the following devices: > > > > Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) > > > > Spectrum Digital eZdsp 'F2812 (parallel) > > > > Xilinx Parallel Cable IV (parallel) > > > > In the future there will likely be a USB JTAG Emulator for the 'F2812, > > and perhaps I'll upgrade to a better Xilinx cable. Also will probably > > get into some Xilinx FPGAs and 3rd party development boards, but just > > need to be sure I can work my present tools. > > > > Anyone have any serious problems with Dell laptops for these or other > > tools? > > > > I don't know how their docking stations work but I'd be suspicious. > Programmers often bit-bang the parallel port directly and that typically > doesn't work if they chose to simply convert USB-parallel in the dock > station. > > My suggestion would be to pay a little more and get a laptop with a > genuine parallel port. > > -- > Regards, Joerg > > http://www.analogconsultants.com You can get an IBM Thinkpad (I have a P3 1.13Ghz T23, very happy with it). These laptops have very good reputations. The newer models (T60) seems to have dropped the parallel port for the extra vent. But if you don't mind a used/slightly older model you can pick up the Thinkpad T42 which has a parallel port. Also considering that my ol' T23 was released in like 2001 and is still working without any defects is amazing! Built like tanks these laptops are. -IsaacArticle: 109192
I use a dell with docking station for Parallel Cable IV. It works but for some reason you can't undock when the parallel port is used for anything. I had to manual diasble the parallel port in the bios to get a clean undock. So I pitched PC4 and went with a USB cable. -Clark "Chris Carlen" <crcarleRemoveThis@BOGUSsandia.gov> wrote in message news:eev1s101dh2@news3.newsguy.com... > Hi: > > I'm considering to buy a Dell Precision M90 laptop to replace a regular > PC on a cart that was used to wheel around and program various embedded > devices. > > The new laptops of course don't offer old-fashioned ports like parallel > and RS-232. Well, some have serial, but the M90 doesn't. > > I will be getting the docking station which *does* have a parallel and > serial port though, so it should be just fine. There is also the option > of USB->RS-232 converters. But the dock's parallel port will be > critically important to work correctly. > > I will need to connect to the following devices: > > Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) > > Spectrum Digital eZdsp 'F2812 (parallel) > > Xilinx Parallel Cable IV (parallel) > > In the future there will likely be a USB JTAG Emulator for the 'F2812, > and perhaps I'll upgrade to a better Xilinx cable. Also will probably > get into some Xilinx FPGAs and 3rd party development boards, but just > need to be sure I can work my present tools. > > Anyone have any serious problems with Dell laptops for these or other tools? > > > Thanks for input. > > > > -- > Good day! > > ________________________________________ > Christopher R. Carlen > Principal Laser&Electronics Technologist > Sandia National Laboratories CA USA > crcarleRemoveThis@BOGUSsandia.gov > NOTE, delete texts: "RemoveThis" and > "BOGUS" from email address to reply.Article: 109193
Hi Jack, Jack Zkcmbcyk wrote: > I have been working on a design lately where I use a the Xilinx Spartan > 3E starter kit board. I use a logic analyser to check the output on some > signals which are assigned to the boards' J1, J2 and J4 connectors. > Sometimes, I get some of the signals to not even be "connected" on the > external pins. When this happens, I find that going in to the VHDL code and > adding a few changes that are usually never related to the signals I want to > observe in the first palce, fix things for me. Try setting the FPGA Mode jumpers to JTAG. By default I think they are in master serial (to configure from the platform flash parts). A few people have reported problems to me doing JTAG configurations on these boards when the contents of the platform flash PROM does not match the bitstream you are downloading. I also saw this on older V2-1000 boards as well. Hope this helps, JohnArticle: 109194
Hi Chris, Chris Carlen wrote: > I'm considering to buy a Dell Precision M90 laptop to replace a regular > PC on a cart that was used to wheel around and program various embedded > devices. > > The new laptops of course don't offer old-fashioned ports like parallel > and RS-232. Well, some have serial, but the M90 doesn't. I use "the world's most expensive parallel port" (TM) - a Quatech SPP-100 in my Dell Laptop. Paying $200 for a PCMCIA interface + voltage drivers is painful, but the thing works just fine with the Xilinx tools. You do need to override the ECP base address, there's an environment variable you can set. Google comp.arch.fpga's history for this topic, you'll find it discussed at length over the years. Regards, JohnArticle: 109195
Chris Carlen wrote: > Hi: > > I'm considering to buy a Dell Precision M90 laptop to replace a regular > PC on a cart that was used to wheel around and program various embedded > devices. > > The new laptops of course don't offer old-fashioned ports like parallel > and RS-232. Well, some have serial, but the M90 doesn't. > > I will be getting the docking station which *does* have a parallel and > serial port though, so it should be just fine. There is also the option > of USB->RS-232 converters. But the dock's parallel port will be > critically important to work correctly. > > I will need to connect to the following devices: > > Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) > > Spectrum Digital eZdsp 'F2812 (parallel) > > Xilinx Parallel Cable IV (parallel) > > In the future there will likely be a USB JTAG Emulator for the 'F2812, > and perhaps I'll upgrade to a better Xilinx cable. Also will probably > get into some Xilinx FPGAs and 3rd party development boards, but just > need to be sure I can work my present tools. > > Anyone have any serious problems with Dell laptops for these or other > tools? > > > Thanks for input. > I've currently got a Dell D400 which although it has a serial port, does not have a parallel port. The docking station does have the parallel port and I have used without any issues for the entire 3 years I've had it. When I'm away from my docking station I've used a Quatech PCMCIA card to get the parallel port interface and that worked pretty well for the most part, though not as seamlessly as the docking station since it took a little bit of monkeying around to get the right driver. A co-worker of mine has the M90 (or maybe M70?) and I know he does work through the comm port on the docking station and I haven't heard him make any complaints. In fact, he's been quite happy with the performance of his laptop. It runs Linux through VMware faster than his old desktop could run it natively! By the way, USB JTAG emulators for TI DSPs have been out for quite a while. A good low-cost emulator for c2000 DSPs is JTAGjet from Signum. Spectrum Digital also now sells newer versions of the eZdsp with a USB interface rather than the parallel port interface. BradArticle: 109196
Joerg wrote: > I don't know how their docking stations work but I'd be suspicious. > Programmers often bit-bang the parallel port directly and that typically > doesn't work if they chose to simply convert USB-parallel in the dock The dock stations I've seen are generally adapters to buffer the super I/O chip in the laptop. Super I/Os still have legacy ports in them.Article: 109197
Chris Carlen wrote: > Atmel STK500 (RS-232) and JTAG-ICE (USB/RS-232) The STK500 is very well-behaved and works well over USB-to-RS232 adapters. I have a JTAG-ICE mkII and although I can barely get it to work once in a blue moon, it should be equally "easy" to use on your Dell :) > Xilinx Parallel Cable IV (parallel) Upgrade to the DLC9 Platform Cable to work with Xilinx FPGAs. I use two laptops for all my non-day-job embedded work: an Averatec AV3715 (used exclusively for the Xilinx stuff as it has USB 2.0; the laptop is extremely low quality and should be considered a disposable machine) and an HP ZE4805WM. I mainly use MSP430, PowerPC (inside Virtex-4 and also on remote Linux boxes), ARM (I use serial debugging with gdb stubs on the target, though I do own a Macraigor Wiggler) and AVR (via an Olimex USB-to-serial-to-JTAG adapter that looks like a JTAG-ICE mkI).Article: 109198
Howard Long wrote:[edit] > If the port replicator is a Dell unit designed specifically for the laptop > and does _not_ simply replicate parallel ports via a USB port, then you will > probably be OK. Forget it if it's a USB-type replicator. > > Good luck, Howard The tough part is finding out what it has before I buy it. -- Good day! ________________________________________ Christopher R. Carlen Principal Laser&Electronics Technologist Sandia National Laboratories CA USA crcarleRemoveThis@BOGUSsandia.gov NOTE, delete texts: "RemoveThis" and "BOGUS" from email address to reply.Article: 109199
Isaac Bosompem wrote:[edit] > You can get an IBM Thinkpad (I have a P3 1.13Ghz T23, very happy with > it). These laptops have very good reputations. The newer models (T60) > seems to have dropped the parallel port for the extra vent. But if you > don't mind a used/slightly older model you can pick up the Thinkpad T42 > which has a parallel port. Also considering that my ol' T23 was > released in like 2001 and is still working without any defects is > amazing! Built like tanks these laptops are. > > -Isaac Unfortunately, my company has a "permitted" set of laptop models. There are some IBMs and HPs though, so I might take a closer look at those. I have to do some re-thinking about whether I really want to pay for a large screen and do any real work on it, or if it will be just for transferring hex files from my real desktop PC to targets in various labs in my building. If I forego the intention of doing real work on the laptop, then I can consider all 3 makers' products. Hopefully one has a parallel port, but in 2006 I doubt it. -- Good day! ________________________________________ Christopher R. Carlen Principal Laser&Electronics Technologist Sandia National Laboratories CA USA crcarleRemoveThis@BOGUSsandia.gov NOTE, delete texts: "RemoveThis" and "BOGUS" from email address to reply.
Site Home Archive Home FAQ Home How to search the Archive How to Navigate the Archive
Compare FPGA features and resources
Threads starting:
Authors:A B C D E F G H I J K L M N O P Q R S T U V W X Y Z