7180 - ICE40: Where to find the simulation model for ICE40 SPI/I2C core?

• Related Articles

• 1630 - All FPGAs: How can I obtain a Lattice IP Core pre-compiled simulation library that targets my HDL simulation tool of choice?

  Description: You do not need to obtain a precompiled simulation library for the Lattice IP Core from Lattice. When you configure and generate the Lattice IP Core in IPexpress, the simulation model for the IP core is generated in an "obfuscated" ...

• Modelsim 2020.3: When I tried to simulate the routed design (netlist-Verilog), there were a lot of error messages related to the following: # ** Error (suppressible): (vsim-19) Failed to access library 'ovi_ice' at "ovi_ice". # No such file or directory. (errno = ENOENT)

  Description: When users implement a post-route simulation with iCEcube2 supported modelsim, they are encountering the below library access error: # ** Error (suppressible): (vsim-19) Failed to access library 'ovi_ice' at "ovi_ice". # No such file or ...

• Diamond Programmer: What is the algorithm to verify the SPI flash during SPI flash Erase_Program_Verify in the programmer?

  The Verify function in SPI Flash Erase_Program_Verifty is using data to data byte-to-byte comparison. You can also find the exact algorithm in the *.svp files located in the installation path folder of your diamond ...

• 5383 - Does Lattice provide an RTL model of the L-ASC10 device to be used for simulation?

  A functional simulation model for the L-ASC10 device is already included in the Lattice Diamond Software. From the Start Page tab, click on the Platform Designer User Guide. On page 56 is a guide on simulating Platform Manager 2 designs; this ...

• 1204 - Simulation: Modelsim: Modelsim failed with the error message:"# ** Error: (vsim-3170) Could not find './work.StimModule_Unknown'."<br>

  Description: Modelsim will produce this error when it cannot find a design to be loaded. Error: "# ** Error: (vsim-3170) Could not find './work.StimModule_Unknown'." Workaround: To workaround this, user required to check the module name at the top ...