Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problems installing F32C toolchain
12-04-2015, 04:03 PM (This post was last modified: 12-04-2015 04:25 PM by Xark.)
Post: #11
RE: Problems installing F32C toolchain
Hello,

Hmm, interesting. Well, glad you got something to work...

I thought the one I used was FleaFPGA_Uno_revE.ldf with Diamond 3.5.1 64-bit on Windows 7-64 (it is possible older Diamonds might gripe about minor differences in XML project). I'll double check the GitHub matches what I used.

I am curious what errors you are getting (or if it just won't load project)?

-Xark

Hello,

Okay, I double checked GitHub the "FleaFPGA_Uno_revE.ldf" is exactly the one I have been using. AFAICT the "FleaFPGA_Uno_revE.ldf" is basically identical to "project.ldf" with two small exceptions. If it is working for you, I think there is nothing wrong with using "project.ldf" (not as easy to play with IP-Express primitive options but is likely fine for you).

"Project.ldf" is a from slightly older Diamond, but what I am guessing may be your problem is you are not "re-generating" the IP-Express IPX primitives. The "project.ldf" uses pre-generated VHD files (which makes it inconvenient to not be able to use GUI editor on IP options - e.g., change f32c clock speed).

To re-generate primitives from IPX files in the FleaFPGA_Uno_revE.ldf project (or other Diamond projects) do this:

After loading project into Diamond, double-click on "clkgen.ipx" (the PLL used to generate several clocks) and it should pop up a "Lattice FPGA Module - PLL" window. Scroll this down and click "Calculate", then click "Generate", then "Close".

Then do the same for "ddr_out.ipx" (used for "double-data rate" outputs) file to bring up "Lattice FPGA Module - GENERIC_DDR" and click "Generate" and "Close".

After than the design should synthesize (assuming this was your problem). Note that it is "expected" to get some "timing violations" synthesizing f32c for 50Mhz (so kind of "overclocked").

-Xark

P.S. These IPX files are left "non-generated" because that is much better for Git and also it is possible there are legal issues with the generated Lattice IP files. Also pre-generated modules are often not compatible between Diamond releases.
Find all posts by this user
Quote this message in a reply
12-07-2015, 12:18 PM
Post: #12
RE: Problems installing F32C toolchain
Yep, that did it, thanks again Xark. Sorry if that was something I should have already known...still getting my head around this unfamiliar tool chain.
Find all posts by this user
Quote this message in a reply
12-17-2015, 02:23 PM
Post: #13
RE: Problems installing F32C toolchain
Just a quick follow-up for anyone else that reads this, that build does indeed compile and run fine. The only problem I encountered was FleaFPGA-Uno_FLASH.xcf is still pointing to "./project/project_project.jed" instead of "./impl1/FleaFPGA_Uno_rev_E_impl1.jed". Easy fix.

Was very happy to see Hampster's HDMI code in there...I was half-way through trying to get it to work myself when it occurred to me I should probably check f32c.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us | Your Website | Return to Top | Return to Content | Lite (Archive) Mode | RSS Syndication