Bitstream Generation Inquiry / Failure
7496 - Radiant: ERROR <1081326> - Bitstream cannot be generated, either because this device does not support IP Evaluation Mode or the Bitstream Strategy Setting for IP Evaluation Mode is set to False
Description: When generating a bitstream in Radiant, the error below might occur: ERROR <1081326> - Bitstream cannot be generated, either because this device does not support IP Evaluation Mode or the Bitstream Strategy Setting for IP Evaluation Mode ...
6830 - MachXO5D: How is USERCODE stored in MachXO5 JEDEC file?
The MachXO5 JEDEC file should not have the U Field (USERCODE) since the MachXO5 Flash didn't support it. The only USERCODE is supported for MACHXO5 is the SRAM USERCODE, which embedded into the bitstream and config data of the JEDEC files.
4739 - Platform Manager 2 & L-ASC10
In the hex file generated by the Lattice Diamond tool for L-ASC10 device, the line before the last line is the checksum. The following is an example hex file content for L-ASC10 device: 00 e1 FFFFFFFFFFFFFFFF FFFFFFFF4E114E11 4E114E11FC009CC7 ...
1927 - Diamond: How does the user know the mandatory Lattice Diamond files to save so that the user can re-generate the bitstream at a later time?
To save the Lattice Diamond files that are needed to re-generate a bitstream at a later time, use the Project Archiving feature in the main Lattice Diamond window. The Project Archive is a single compressed .zip file that can contain the minimum ...
752 - Lattice Diamond: What are the meanings of the abbreviations in the JEDEC header?
There are a few common abbreviations at the beginning of GAL/CPLD JEDEC files. "QP" means the quantity of pins. This usually is the total number of pins in the package. "QF" is the quantity of fuses. This is the total number of fuses in the device. ...
3748 - Diamond: Why are there bit locations in the readback file that are not equal to zero in the *.msk files?
The bits in mask are AND'ed with the readback file and compared. So only bits that are '1' in mask file need to be compared to verify. Mask files can be generated from Diamond Project Navigator. They are optionally generated by the user from the ...
3570 - ICEcube2: How to program the iCE40 FPGA(CRAM) via Slave SPI interface from a on board MCU with the hex file?
Generate the hex file from iCEcube2 tool ,create the array from hex file and send the array data byte wise similarly as sending bin file as per Slave SPI Configuration Interface procedure is described in TN1248.
3514 - Diamond: Why is there a difference in the bitstream file size with a small logic modification in LatticeECP3?
The bitstream file size increases even with a small modification. The bitstream comprises both fuse data frames (SRAM configuration bits) and EBR initialization information. Fuse data frame size is fixed for the given device irrespective of how huge ...
617 - What is the difference between a .bit file and a .jed file?
A .bit file is used with volatile deivces whereas a .jed file is used with non-volatile devices.
6013 - CrossLink-NX: Why do I get this error in Radiant when programming LIFCL-40: "Verification Error... when Processing function: 'CHECK_ID'"?
If this is Engineering Sample that is for engineering evaluation only, there are some limitations. For software, ES devices are supported by Lattice Radiant 2.0 SP1 Software. Since the bitstream is generated using Radiant 2.1, we need to build a ...
298 - Lattice Diamond: Is there a difference in size between an encrypted and unencrypted FPGA bitstream?
Yes, there is a difference in size between encrypted and unencrypted bitstreams. An encrypted bitstream has additional overhead associated with the bitstream. Therefore an encrypted bitstream's size is slightly larger than an unencrypted bitstream. ...
285 - Lattice Diamond: Can I replace the dummy bits in the LatticeECP3 bitstream header with custom data (revision ID for example)?
Yes, the dummy bits in the LatticeECP3 bitstream header can be used and replaced with custom data. There are two dummy bytes in the beginning of the header that contain all 1s. You can replace these two dummy bytes with custom data in the header. You ...
2504 - Can I use same JEDEC file or bit file to program different speed rating parts?
Solution: Speed rating will define some characteristics of the parts, like how fast the part can run, and if it is commercial or industrial part. So if you want to use same JEDEC or bit file to program different speed rating part, your timing ...
2372 - LatticeECP3: Can the bitstream used for the regular device be programmed in the low power device of LatticeECP3?
Yes. The bit stream formats are the same for the regular LatticeECP3 and the low power LatticeECP3 devices. For example, LFE3-70EA-8TN1156C and the low power version "LFE3-70EA-8LTN1156C" can use the same bitstream file. There is no need to generate ...
6906 - Diamond: How can users accelerate bit file generation?
Multiple-core CPU is better for the compilation process. Users can run multiple Place & Route (PAR) jobs in parallel by using the "Multi-Tasking Node List" strategy setting. User can specify an ASCII-based node list file as input.
6867 - Lattice Radiant: Why is the bitstream file size fixed (ex. Always 1.8Mb) even in small designs for Certus-Pro NX?
Certus Pro-NX, the BIT file size on simplest design is 1.8MB, while for Crosslink-NX it generates 790KB. Whenever design becomes more condensed (especially more usage of EBRs and LRAMs) bitstream size will increase from that 1.8MB. The bitstream size ...
7361 - Radiant: Why does Radiant generate bitstream that contains unusual or garbled characters?
Description: When generating a bitstream on Radiant, there have been reports where the generated bitstream includes unusual or garbled characters that are not appropriate for device programming. Solution: This issue might occur if the project path is ...
6669 - Radiant: How can users obtain a binary file without timestamps from Radiant?
Users can remove the header (together with the timestamp) on the bitstream by entering the command line option e "-q" on the Bitstream Strategy Settings.
6619 - Diamond: How to get the the 32-bit checksum of bitstream file?
The data checksum calculation algorithm is just the sum of all the 1s bit starting from the first to the last bit in the field. The 16-bit checksum is only take the 16-bit LSB value (8-bit words). The 32-bit checksum should take the whole 32-bit ...
6118 - Power Manager: Are LA-ISPPAC-POWR1014-01TN48E and ISPPAC-POWR1014-01TN48I programmable in the same JEDEC file?
Yes, you can use the same JEDEC file generated by ISPPAC-POWR1014-01TN48E to program to LA-ISPPAC-POWR1014-01TN48I or vice versa. The only difference for Automotive and Industrial grade devices is that they have different DEFAULT temperature ranges ...
7058 - Radiant: How to modify majority of the sysConfig settings without the need of performing Place&Route and timing again?
Description: The user can alter the sysConfig settings via bitstream generation command, this can be done using the following methods: Note: In this example, BACKGROUND_RECONFIG was used. Solution: (1) Through Bitstream Strategy Settings Command ...
6508 - Lattice Diamond: What is the behavior of my generated bitstream if i do not have any LSC_SW_XO3D_SECURITY_ENCRYPT feature line in the license file when signing a bitstream?
The bitstream gets generated without any error or warning. If the license feature of LSC_SW_XO3D_SECURITY_ENCRYPT is removed, Bitgen will generate plain a bitstream file, it will ignore the Security setting that is added in the bitstream.
5961 - Lattice Radiant 2.1: How do I generate the bitstream for crosslink-nx with Radiant v2.1?
If the selected device on Radiant is an ES1 device, the bitstream can only be generated on R2.0. R2.1 can only allow bitstream generation for ES2 devices.