Wondering about "LatticeMico32 Open Source Licensing"

the headers of the latticemico32 verilog source files don't imply changed code may be redistributed: // This confidential and proprietary software may be used only as authorised // by a licensing agreement from Lattice Semiconductor Corporation. // The entire notice above must be reproduced on all authorized copies and // copies may only be made to the extent permitted by a licensing agreement // from Lattice Semiconductor Corporation.

Neither does the Lattice Web site

formatting link
\mico32/mico32opensourcelicensing.cfm talk about code redistribution, also it tells:

Allows the entire user community to identify areas of enhancements and to > help develop higher quality solutions and make modifications

So the only legal way to make a modification available to others is to send the differences to Lattice and hope for inclusion in some next release. Not an option to trust in, when Mico32 on other then Lattice FPGA is one's target!

The software deployment doesn't deploy the license. You can however download it seperate, by trying to download again and mark the license agreement box and save it to a local file. Apendix C, Top 2 however talks about the possibility to redistribute changed code free, in the sense of open source.

What counts?

Bye

--
Uwe Bonnes                bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
 Click to see the full signature
Reply to
Uwe Bonnes
Loading thread data ...

site

formatting link
\

Uwe,

please read Lattice main License, Appendix C

it clearly says ALL FILES GENERATED by Mico32 tools are subject to the open-source licensing, so it over-rides whatever is prefixed into the hdl source code.

you can distribute those files under open-source license, also if modfied and you can distribute you own addons under any license you want

and there is no vendor locking to Lattice, the stuff under lattice opensource license can be implemented for ANY FPGA or ASIC

this is how i read it,

Antti PS there is DDR2 IP Core mico32 so you can use it on Spartan3A starter board :)

Reply to
Antti

If you look at ttp://

formatting link
\ /mico32/mico32peripherals.cfm

you will see the DDR1/DDR2/Tri-Speed MAC/PCI Target 33HHz marked with a star, meaning a seperate license. The verilog directories for these peripherals deployed by the installation also seems to contain only wrappers around EDK specific modules not provided and probably contain a lot of lattice part specific code.

Anyways, looking at the other directories, there only contain few Lattice specific primitives, like IO Buffer, BRAM and FIFO, where it should be not to hard to write wrappers that resolve into other vendors primitives.However Icarus verilog still has some problems withe the present Lattice code. Hopefully stephen, cary and Larry wil care.

Didn't run XST on some directory neither...

--
Uwe Bonnes                bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
 Click to see the full signature
Reply to
Uwe Bonnes

ttp://

formatting link
\/mico32/mico32peripherals.cfm

i did not notice the * but a) if you are student you can use the time limited version b) for commercial use you just need pay license and that it

work well so or so

ah, if you want mico32 with DDR2 on Xilinx? well, you dont expect Lattice to offer that?

as of mico32 with XST, I did that LOOOOONG ago it did take maybe some hour of tweaking. XST doesnt support verilog good enough to synthesize mico32 code

Antti

Reply to
Antti

What is the problem?

Cheers, Jon

Reply to
Jon Beniston

They've only had 7 years to implement Verilog 2001 after all. How hard can it be?

Cheers, Jon

Reply to
Jon Beniston

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.