7481 - MachXO3/MachXO2: Should PB231101 be followed when using EFB at usermode?

• Related Articles

• 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 ...

• 1702 - MachXO2: Which pin should be used for the EFB SPI clock in a MachXO2 design using the hardened SPI core?<jason.livermore@nsn.com></jason.livermore@nsn.com>

  The MachXO2 has 2 hardened SPI cores tied to the internal FPGA configuration logic. These cores can be accessed through an internal bus interface (wishbone) by instantiating the Embedded Function Block (EFB) element in HDL code. The SPI cores have a ...

• 7336 - Lattice Radiant v2023.2: How to modify I2C slave address or 96-feabits using Pseudo mode?

  Description: Nexus device family has a default I2C slave address of 0x40 and you are allow to modify it based on your requirement. Solution: To permanently modify the I2C address, you can modify the desired value in .fea file and use the Programmer ...

• 7284 - MACHXO3/MACHXO2: What can cause EFB to malfunction in hardware?

  Description: When EFB malfunctions in hardware it is best to check if the EFB is instantiated properly and not optimized. Solution: To workaround this issue, If it is certain that EFB is not optimized, please make sure that GSR is disabled. When GSR ...

• 2123 - MachXO2: Can the user use MachXO2's Embedded Functional Block (EFB) I2C pins&nbsp;(SCL and SDA) to work with soft (NOT EFB) I2C logic?

  Definition: The MachXO2's EFB Primary I2C have dedicated pins. User can't use them for general purpose when enabled for EFB I2C usage, by enabling the Primary I2C Port. However, if the I2C Primary port is not enabled, then the I2C IOs become User ...