Custom Search
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
langwadt@fonz.dk wrote: > On Jun 18, 6:01 pm, carlton...@gmail.com wrote: >> Hi Gabor, >> >> If I understand your approach correctly, you are using the higher clock rate further into the chain. As such, your approach with detecting the rising edge makes perfect sense. There is no need for the second register set. >> >> What I was referring to had the presumption that it is/was desired to transition to the slower clock. For example, perhaps right after the de-serializer. Because the de-serializer is always working when the link is active and because there is a phase shift relative to the slower clock, it is necessary to additionally register right after the de-serializer to permit alignment to the slower clock while at the same time not dropping or losing anything. >> >> Also note, that my comment about the DCM was backwards. I meant to mention a 1:7 not 7:1. For some reason I got on a 7:1 track. Woops. To pull off a 1:7 will require 2 DCMs. The first operates in a mode to permit a lower (than 32MHz) CLKIN frequency but outputs (a) a CLKFX higher frequency clock compatible with the second DCM and (b) a regenerated slower clock. The second DCM receives the now compatible clock from the first DCM and creates the final overall 1:7. >> >> Regards, >> Carlton > > can't you just generate the 7x clock with clkfx of single dcm? > > shift data and clock in to regsister on that 7x clk, look for the > transition > on clock move the right bits from the shifter to a register > generate your slow clock with a divider aligned with the data update > > -Lasse First, you really only need 3.5x rather than 7x if you use both clock edges. Second, a DCM is a bad choice because it cannot both multiply the clock by a number (other than 1 or 2) and also phase shift the clock to line up with the data eye. A PLL can multiply and phase shift at the same time. Cascading DCM's to get the phase shift is a poor choice because the FX output of the DCM adds a lot of jitter, making the second DCM prone to losing lock. You might be able to work around the phase shift problem using the IDELAY components of each input, though. -- GaborArticle: 153876
I am using EDK 14.1 and a Spartan-6 FPGA (potentially changing FPGAs in the future to the Artix 7 or Kintex 7). I am trying to figure out a way that I could output the data from the MicroBlaze to a VHDL module and also the reverse transfer. This way I can capture the data, use it in some calculations, and then also pass it back to the MicroBlaze for further use. I am new to Embedded Design and MicroBlaze, so any help that anyone may have would be greatly appreciated. If anyone has other options for transferring data between the MicroBlaze and my VHDL modules, I am looking for something that would allow me to transfer data using a 32- bit wide bus at the fastest speed the FPGA will allow me to clock at. - RobertArticle: 153877
>I am using EDK 14.1 and a Spartan-6 FPGA (potentially changing FPGAs >in the future to the Artix 7 or Kintex 7). I am trying to figure out >a way that I could output the data from the MicroBlaze to a VHDL >module and also the reverse transfer. This way I can capture the >data, use it in some calculations, and then also pass it back to the >MicroBlaze for further use. > >I am new to Embedded Design and MicroBlaze, so any help that anyone >may have would be greatly appreciated. If anyone has other options >for transferring data between the MicroBlaze and my VHDL modules, I am >looking for something that would allow me to transfer data using a 32- >bit wide bus at the fastest speed the FPGA will allow me to clock at. > >- Robert > All you need to do is create a custom AXI IP module that will interface between your IP and the Microblaze. There is a wizard that will do this for you. Jon --------------------------------------- Posted through http://www.FPGARelated.comArticle: 153878
On Jun 19, 8:59=A0pm, Gabor <ga...@szakacs.invalid> wrote: > langw...@fonz.dk wrote: > > On Jun 18, 6:01 pm, carlton...@gmail.com wrote: > >> Hi Gabor, > > >> If I understand your approach correctly, you are using the higher cloc= k rate further into the chain. As such, your approach with detecting the ri= sing edge makes perfect sense. There is no need for the second register set= . > > >> What I was referring to had the presumption that it is/was desired to = transition to the slower clock. For example, perhaps right after the de-ser= ializer. Because the de-serializer is always working when the link is activ= e and because there is a phase shift relative to the slower clock, it is ne= cessary to additionally register right after the de-serializer to permit al= ignment to the slower clock while at the same time not dropping or losing a= nything. > > >> Also note, that my comment about the DCM was backwards. I meant to men= tion a 1:7 not 7:1. For some reason I got on a 7:1 track. Woops. To pull of= f a 1:7 =A0will require 2 DCMs. The first operates in a mode to permit a lo= wer (than 32MHz) CLKIN frequency but outputs (a) a CLKFX higher frequency c= lock compatible with the second DCM and (b) a regenerated slower clock. The= second DCM receives the now compatible clock from the first DCM and create= s the final overall 1:7. > > >> Regards, > >> Carlton > > > can't you just generate the 7x clock with clkfx of single dcm? > > > shift data and clock in to regsister on that 7x clk, look for the > > transition > > on clock move the right bits from the shifter to a register > > generate your slow clock with a divider aligned with the data update > > > -Lasse > > First, you really only need 3.5x rather than 7x if you use both clock > edges. =A0Second, a DCM is a bad choice because it cannot both multiply > the clock by a number (other than 1 or 2) and also phase shift the > clock to line up with the data eye. =A0A PLL can multiply and phase > shift at the same time. =A0Cascading DCM's to get the phase shift is > a poor choice because the FX output of the DCM adds a lot of jitter, > making the second DCM prone to losing lock. =A0You might be able to > work around the phase shift problem using the IDELAY components of > each input, though. > agreed, my thinking was assuming the eye doesn't move around too much you would only have to calibrate the idelay once. but I'm not sure that theres a guarantee the fx output will always have the same phase alignment with regards to input when you don't have feedback -LasseArticle: 153879
On Tuesday, June 19, 2012 4:27:27 PM UTC-4, maxascent wrote: > >I am using EDK 14.1 and a Spartan-6 FPGA (potentially changing FPGAs > >in the future to the Artix 7 or Kintex 7). I am trying to figure out > >a way that I could output the data from the MicroBlaze to a VHDL > >module and also the reverse transfer. This way I can capture the > >data, use it in some calculations, and then also pass it back to the > >MicroBlaze for further use. > > > >I am new to Embedded Design and MicroBlaze, so any help that anyone > >may have would be greatly appreciated. If anyone has other options > >for transferring data between the MicroBlaze and my VHDL modules, I am > >looking for something that would allow me to transfer data using a 32- > >bit wide bus at the fastest speed the FPGA will allow me to clock at. > > > >- Robert > > >=20 > All you need to do is create a custom AXI IP module that will interface > between your IP and the Microblaze. There is a wizard that will do this f= or > you. >=20 > Jon =20 > =09 > --------------------------------------- =09 > Posted through http://www.FPGARelated.com Thank you Jon for your reply, but I am still a little confused. I have not= iced that there are IP modules for BRAM, GPIO, and even FSL...but I am unsu= re as to which one to choose. I have tried adding the FSL IP module into m= y design, but when I do, I don't see how to connect it to anything so that = data can be transferred to and from the MicroBlaze? Are there any helpful = guides that you know of that could possibly walk me through some of these m= ethods? - RobertArticle: 153880
On Wed, 20 Jun 2012 06:25:12 -0700, robert.higginbotham0 wrote: > On Tuesday, June 19, 2012 4:27:27 PM UTC-4, maxascent wrote: >> >I am using EDK 14.1 and a Spartan-6 FPGA (potentially changing FPGAs >> >in the future to the Artix 7 or Kintex 7). I am trying to figure out >> >a way that I could output the data from the MicroBlaze to a VHDL >> >module and also the reverse transfer. This way I can capture the >> >data, use it in some calculations, and then also pass it back to the >> >MicroBlaze for further use. >> > >> >I am new to Embedded Design and MicroBlaze, so any help that anyone >> >may have would be greatly appreciated. If anyone has other options >> >for transferring data between the MicroBlaze and my VHDL modules, I am >> >looking for something that would allow me to transfer data using a 32- >> >bit wide bus at the fastest speed the FPGA will allow me to clock at. >> > >> >- Robert >> > >> > >> All you need to do is create a custom AXI IP module that will interface >> between your IP and the Microblaze. There is a wizard that will do this >> for you. >> >> Jon >> >> --------------------------------------- >> Posted through http://www.FPGARelated.com > > > > Thank you Jon for your reply, but I am still a little confused. I have > noticed that there are IP modules for BRAM, GPIO, and even FSL...but I > am unsure as to which one to choose. I have tried adding the FSL IP > module into my design, but when I do, I don't see how to connect it to > anything so that data can be transferred to and from the MicroBlaze? > Are there any helpful guides that you know of that could possibly walk > me through some of these methods? > > - Robert All I know about the Microblaze is that it's a synthesizable microprocessor, so take this with an appropriate-sized grain of salt: I expect that the most convenient and commonly used way of connecting to the Microblaze core is going to be as a memory-mapped peripheral. So at some point you need to learn how to make ports on your VHDL module appear to the Microblaze as a memory location (or you need to dig around and find out if there's a tutorial or wizard that will help you out). Whether you want to configure things so that your interface has the Microblaze pounding away at one memory location, or several, or whether you want to augment the interface between the Microblaze and your logic with a bit of block RAM that's configured as dual-port memory, is a decision that you'll have to make. Ultimately, though, I think the best way you have of making your logic go "zing!" in response to something the processor does is to have logic registers show up in the Microblaze's memory map. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.comArticle: 153881
Lasse, The preferred way to do the clock derivation would be as Gabor suggests, us= e a PLL. Unfortunately for the OP, V4 only has DCMs. The reason for the 2 cascaded DCMs is because the OP has a desired clock re= lationship which is out of bounds for a single DCM. The OP's desired link c= lock frequency is something less than 32MHz. Which means that the first DCM needs to be a maximum range setup DCM. Problem is, the maximum range DCM ca= nnot directly derive a 3.5x or 7x clock based upon the limited input clock = frequency. So for the first DCM, the clk2x output is used to double the=20 frequency of the link clock frequency. The clk2x clock frequency is now of a value whereby a maximum frequency set= up DCM can be used to derive the overall 3.5x or 7x clock by using the clkf= x and setting M and D to values which provide the overall desired frequency= . As far as phase relationship on this second DCM, if clk0 is piped back to c= lkfb, clkfx is supposed to be aligned to the clk0 but with the twist that i= t is every D clkin cycles. If clk0 is aligned to clkin, clkfx should also b= e aligned to clkin. Gabor is right, that depending upon arrangement of the 2 cascaded DCMs it i= s possible that the jitter can be out of limits. Generally speaking, it is = when clkfx is cascaded or clkfx is part of the feedback path where problems= can begin to arise. I believe however that the above implementation is ok = with respect to jitter being within limits because clkfx is only used as a final output and is not being fed back into the cascaded DCMs. Regards, CarltonArticle: 153882
Robert, Guessing from the limited details you provided, it sounds as if you are goi= ng to be trading a reasonable amount of data between the microblaze and you= r VHDL module. GPIO is likely not sufficient. BRAM (dual port setup) may be possible, howe= ver you would still need to implement the handshaking between the microblaz= e and your VHDL module. FSL sounds like it may be a possible candidate or a= t least give you an idea of how it can be done. Check out the FSL core datasheet DS449 and the application note XAPP529. Th= is should give you an idea in a general sense how it's done. From there you= should be able to arrive at what best suites the needs of your application= . Regards, CarltonArticle: 153883
On Jun 20, 7:08=A0pm, carlton...@gmail.com wrote: > Lasse, > > The preferred way to do the clock derivation would be as Gabor suggests, = use a PLL. Unfortunately for the OP, V4 only has DCMs. > > The reason for the 2 cascaded DCMs is because the OP has a desired clock = relationship which is out of bounds for a single DCM. The OP's desired link= clock frequency is something less than 32MHz. Which means that the first D= CM > needs to be a maximum range setup DCM. Problem is, the maximum range DCM = cannot directly derive a 3.5x or 7x clock based upon the limited input cloc= k frequency. So for the first DCM, the clk2x output is used to double the > frequency of the link clock frequency. > > The clk2x clock frequency is now of a value whereby a maximum frequency s= etup DCM can be used to derive the overall 3.5x or 7x clock by using the cl= kfx and setting M and D to values which provide the overall desired frequen= cy. > > As far as phase relationship on this second DCM, if clk0 is piped back to= clkfb, clkfx is supposed to be aligned to the clk0 but with the twist that= it is every D clkin cycles. If clk0 is aligned to clkin, clkfx should also= be aligned to clkin. > > Gabor is right, that depending upon arrangement of the 2 cascaded DCMs it= is possible that the jitter can be out of limits. Generally speaking, it i= s when clkfx is cascaded or clkfx is part of the feedback path where proble= ms can begin to arise. I believe however that the above implementation is o= k with respect to jitter being within limits because clkfx is only used > as a final output and is not being fed back into the cascaded DCMs. > > Regards, > Carlton by why not just use the clk fx directly? as far as I can tell it can do 7x might even go crazy and try 14x and use both edges via input ddr flops, that way you get 4x data rate sampling and realign at every edge which is how most full-speed usb devices do it -LasseArticle: 153884
What you need to do is to look at doing the tutorial that Xilinx provide with EDK. Its called concepts tools and techniques. Basically Microblaze can use either a PLB or AXI bus. The AXI bus is the newer standard and so that one would be the best to use. Xilinx provide a wizard that creates an interface bewteen the AXI bus and your IP. So you don't even have to know how AXI works. You just get a set of standard signals which are a write and read data path. But just have a look at some of the Xilinx docs as this should make things clearer. Jon --------------------------------------- Posted through http://www.FPGARelated.comArticle: 153885
can i have ur vhdl code ...wid appreciate it a lot ... thanx in advance. my gmail:zakaria.nits@gmail.comArticle: 153886
Thank you to everyone for your replies! This gives me some great information to look over and figure this out. Thanks again for your help! - Robert On Wednesday, June 20, 2012 3:00:28 PM UTC-4, maxascent wrote: > What you need to do is to look at doing the tutorial that Xilinx provide > with EDK. Its called concepts tools and techniques. Basically Microblaze > can use either a PLB or AXI bus. The AXI bus is the newer standard and so > that one would be the best to use. Xilinx provide a wizard that creates an > interface bewteen the AXI bus and your IP. So you don't even have to know > how AXI works. You just get a set of standard signals which are a write and > read data path. But just have a look at some of the Xilinx docs as this > should make things clearer. > > Jon > > --------------------------------------- > Posted through http://www.FPGARelated.com On Wednesday, June 20, 2012 3:00:28 PM UTC-4, maxascent wrote: > What you need to do is to look at doing the tutorial that Xilinx provide > with EDK. Its called concepts tools and techniques. Basically Microblaze > can use either a PLB or AXI bus. The AXI bus is the newer standard and so > that one would be the best to use. Xilinx provide a wizard that creates an > interface bewteen the AXI bus and your IP. So you don't even have to know > how AXI works. You just get a set of standard signals which are a write and > read data path. But just have a look at some of the Xilinx docs as this > should make things clearer. > > Jon > > --------------------------------------- > Posted through http://www.FPGARelated.comArticle: 153887
Carlton, I have tried finding the XAPP529 pdf from Xilinx, but it always comes up wi= th a "Bad encrypt dictionary" message. Would you be able to email me the d= ocument if you have it? Also, I noticed in the FSL Core Datasheet (acquire= d through XPS 14.1) that the FSL is not supported by the 7-Series FPGAs, si= nce I am looking to migrate to that from my Spartan6, do you have another s= uggestion/option for me in lieu of the FSL? - Robert (robert.higginbotham0@gmail.com) On Wednesday, June 20, 2012 1:27:47 PM UTC-4, carlt...@gmail.com wrote: > Robert, >=20 > Guessing from the limited details you provided, it sounds as if you are g= oing to be trading a reasonable amount of data between the microblaze and y= our VHDL module. >=20 > GPIO is likely not sufficient. BRAM (dual port setup) may be possible, ho= wever you would still need to implement the handshaking between the microbl= aze and your VHDL module. FSL sounds like it may be a possible candidate or= at least give you an idea of how it can be done. >=20 > Check out the FSL core datasheet DS449 and the application note XAPP529. = This should give you an idea in a general sense how it's done. From there y= ou should be able to arrive at what best suites the needs of your applicati= on. >=20 > Regards, > CarltonArticle: 153888
On Jun 21, 2:44=A0pm, RHigginbotham <robert.higginboth...@gmail.com> wrote: > Carlton, > > I have tried finding the XAPP529 pdf from Xilinx, but it always comes up = with a "Bad encrypt dictionary" message. =A0Would you be able to email me t= he document if you have it? =A0Also, I noticed in the FSL Core Datasheet (a= cquired through XPS 14.1) that the FSL is not supported by the 7-Series FPG= As, since I am looking to migrate to that from my Spartan6, do you have ano= ther suggestion/option for me in lieu of the FSL? > > - Robert (robert.higginboth...@gmail.com) > > > > > > > > On Wednesday, June 20, 2012 1:27:47 PM UTC-4, carlt...@gmail.com wrote: > > Robert, > > > Guessing from the limited details you provided, it sounds as if you are= going to be trading a reasonable amount of data between the microblaze and= your VHDL module. > > > GPIO is likely not sufficient. BRAM (dual port setup) may be possible, = however you would still need to implement the handshaking between the micro= blaze and your VHDL module. FSL sounds like it may be a possible candidate = or at least give you an idea of how it can be done. > > > Check out the FSL core datasheet DS449 and the application note XAPP529= . This should give you an idea in a general sense how it's done. From there= you should be able to arrive at what best suites the needs of your applica= tion. > > > Regards, > > Carlton I think that message is usually an indication that your reader is not sufficiently current. Try updating and opening the document again. RickArticle: 153889
RHigginbotham <robert.higginbotham0@gmail.com> writes: > Carlton, > > I have tried finding the XAPP529 pdf from Xilinx, but it always comes > up with a "Bad encrypt dictionary" message. Would you be able to > email me the document if you have it? Also, I noticed in the FSL Core > Datasheet (acquired through XPS 14.1) that the FSL is not supported by > the 7-Series FPGAs, since I am looking to migrate to that from my > Spartan6, do you have another suggestion/option for me in lieu of the > FSL? > AXI4-stream replaces FSL. The AXI docs are in UG761. As an aside - you might want to install the DocNav from Xilinx - that keeps all their docs together and updated: http://myfpgablog.blogspot.co.uk/2011/03/xilinx-document-navigator-is-live.html Cheers, Martin -- martin.j.thompson@trw.com TRW Conekt - Consultancy in Engineering, Knowledge and Technology http://www.conekt.co.uk/capabilities/39-electronic-hardwareArticle: 153890
Martin Thompson wrote: > > As an aside - you might want to install the DocNav from Xilinx - that > keeps all their docs together and updated: > > http://myfpgablog.blogspot.co.uk/2011/03/xilinx-document-navigator-is-live.html Thank you! Thank you! Thank you! I regard finding / tracking Xilinx documents with the same level of enthusiasm as a trip to the dentist. This program will make my life easier. PeteArticle: 153891
If a design has differential inputs, but the synthesis tool did not infer differential input buffers IBUFDS on Xilinx FPGA for them, IBUFs are inferred instead. What will be the impact to the implementation? Thanks!Article: 153892
Hi everybody, I am Philippe Faes, founder of Sigasi. Sigasi sells a design entry and code comprehension tool for VHDL. Many users of Altera Quartus have asked us if Sigasi plugs in to Quartus. We have been working on integrating our tool with Quartus. Today, we are ready to allow selected users to use a beta version. If you are interested, please visit: http://bit.ly/sigasi-quartus-beta best regards PhilippeArticle: 153893
>If a design has differential inputs, but the synthesis tool did not infer differential input buffers IBUFDS on Xilinx FPGA for them, IBUFs are inferred instead. What will be the impact to the implementation? Thanks! > Try it! If Mapping fails, you will have to instantialte them somewhere appropriate. --------------------------------------- Posted through http://www.FPGARelated.comArticle: 153894
pfraser <pete_fraser@comcast.net> writes: > Martin Thompson wrote: > >> >> As an aside - you might want to install the DocNav from Xilinx - that >> keeps all their docs together and updated: >> >> http://myfpgablog.blogspot.co.uk/2011/03/xilinx-document-navigator-is-live.html > > Thank you! Thank you! Thank you! You're welcome :) > I regard finding / tracking Xilinx documents with the same level > of enthusiasm as a trip to the dentist. > Yes, it can be a bit like that can't it? Cheers, Martin -- martin.j.thompson@trw.com TRW Conekt - Consultancy in Engineering, Knowledge and Technology http://www.conekt.co.uk/capabilities/39-electronic-hardwareArticle: 153895
Hi Lasse, The problem is that the OP desires an incoming frequency less than 32MHz. This means the maximum-range type of DCM has to be used in order to accept = the less than 32MHz clock input. The tradeoff is that the clkfx is restrict= ed to what frequencies can be generated. In this case the upper limit on cl= kfx is < 3.5x and also 7x for a maximum-range type DCM. To illustrate the limit, try creating a DCM which uses the clkfx in the cor= e generator for a V-4 target. Use an input frequency < 32MHz. Regards, CarltonArticle: 153896
Firstly, unless there is some newer info out there, I believe that per the = Xilinx HDL libraries guide, an IBUFDS must be instantiated and cannot be in= ferred. The IBUFDS primitive and its functionality is located up in the I/O= cell and performs the differential to single ended conversion directly.=20 I will presume that your code to infer the differential to single-ended con= version matches the functionality of the IBUFDS logic table in the HDL libr= ary guide. As such with the IBUFs at the I/O cell, the synthesizer will the= n try to replicate the functionality using logic cell(s). A significant per= formance hit will occur do to the delays. These delays will change from ite= ration to iteration as well. Also there will be more susceptibility to glit= ching because it will be more challenging to match the routing of the two s= ignals in and amongst the logic cell fabric. Regards, CarltonArticle: 153897
>>Hi all >>I got stuck with my design. I'm planning to use microblaze in ML505 board >>to read my full custom chip output and display to hyperterminal. >>I've found one tutorial about read DIP switch using microblaze, but here >I >>want the output of my external chip to be read by microblaze. >>I'm confused of the device_ID that I should use in my programming so that >>the microbalze can read the signal. >> >>FYI, I want to test my chip by driven the input signal using test vector >>that I've designed using VHDL in Virtex-5(ML505)and the test vector >output >>will be the input of my chip. Then my chip will produce the output and >>display at hyperterminal using microblaze. >> >>Hope somebody can help me with this. >>Thanks > >What is the interface of the "full custon chip" that you want to read? >Or is it just a bunch of signals? > > >--------------------------------------- >Posted through http://www.FPGARelated.com Hi my interface is a test vector generator(vhdl file) to generate the 2 input of 8-bit to my full custom chip. output of my chip will be read again and compare with expected result and also to display at hyperterminal. Actually i want to make this simple, but this is the only plan I have to display the output by using microblaze. Do you have any idea to solve my prob?Thanks. --------------------------------------- Posted through http://www.FPGARelated.comArticle: 153898
>>>Hi all >>>I got stuck with my design. I'm planning to use microblaze in ML505 >board >>>to read my full custom chip output and display to hyperterminal. >>>I've found one tutorial about read DIP switch using microblaze, but here >>I >>>want the output of my external chip to be read by microblaze. >>>I'm confused of the device_ID that I should use in my programming so >that >>>the microbalze can read the signal. >>> >>>FYI, I want to test my chip by driven the input signal using test vector >>>that I've designed using VHDL in Virtex-5(ML505)and the test vector >>output >>>will be the input of my chip. Then my chip will produce the output and >>>display at hyperterminal using microblaze. >>> >>>Hope somebody can help me with this. >>>Thanks >> >>What is the interface of the "full custon chip" that you want to read? >>Or is it just a bunch of signals? >> > >Hi >my interface is a test vector generator(vhdl file) to generate the 2 input >of 8-bit to my full custom chip. output of my chip will be read again and >compare with expected result and also to display at hyperterminal. >Actually i want to make this simple, but this is the only plan I have to >display the output by using microblaze. >Do you have any idea to solve my prob?Thanks. > Does the phrase "sledgehammer to crack a nut" mean anything to you? Unless you are allergic to HDLs, it is time to learn digital design and Verilog or VHDL. --------------------------------------- Posted through http://www.FPGARelated.comArticle: 153899
I had MXE (Modelsim Xilinx Edition) running successfully under Wine until recently. However, following a lot of changes, I 've just re-installed it, and can't get vsim running. My setup is SL(/RHEL)6, 64-bit, wine 1.2.3. I've installed MXE-III Starter, for both VHDL and Verilog. When I run vsim I get a pop-up with a long message which starts: 'can't read "view_master": no such variable when executing "GUIMAIN"...' The problem is in the tcl start-up (tcl/vsim/vsim). Anyone else seen this? Any ideas? Thanks.
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