1424 - What's the difference between the TraceID and the USERCODE for MACHXO2 device?<br>

• Related Articles

• 3036 - Lattice EPC2/S: Why is the encrypted bitstream not working for Lattice ECP2/S device?<br>

  For the encrypted bitstream to work in LatticeECP2/S device, ensure the following: For power-up, VCC must reach its valid minimum value before powering up VCCAUX (LatticeECP2/M “S” version devices only). Refer to LatticeECP2/M Family Data Sheet for ...

• 534 - MachXO: Why can't I scan or program the MachXO device on the MachXO Mini board after I programmed my pattern into the device?

  The MachXO JTAG pins on the MACHXO Mini board share the same traces with some generic IOs of the MachXO device (as shown on page 4 and page 2 of the schematic). If the new design patterns have signals driving out of these pins, they could potentially ...

• 6511 - All Devices: Are both USERCODE and rollback setting stored in the USERCODE area?

  The Version Rollback Prevention feature is just utilizing the Usercode to track the revision. The only thing user should be aware of is that when Version Rollback Prevention feature is enabled, they have to make sure the value of the usercode is ...

• 1735 - MachXO2: How can we instantiate the TraceID for Lattice&nbsp;MachXO2 in my&nbsp;VHDL RTL?

  You cannot instantiate TraceID directly in your VHDL RTL in your design. You must first instantiate an EFB block and then use either WISHBONE or I2C or SPI protocol to access TraceID. You must remember that only one byte of TraceID is user writable ...

• 6121 - Does the Nexus Platform family have an internal access to the configuration area (ex: USERCODE, Unique ID, CFG0, CFG1, etc)?

  Referring to the Table 6.14 in FPGA-TN-02099 for non-JTAG command table, this is the command sets for all non-JTAG configuration ports including LMMI. The command sequence should be no difference as described in FPGA-TN-02099 for NON-JTAG slave ...