5799 - [MachXO3] Lattice Mico32: Why is the Mico32 debugging not working on MachXO3-9400 Development Kit?

• Related Articles

• 7393 - AHB-Lite Bridge IP Cores: Do Lattice AHB-Lite Bridges support write strobes?

  Description: Lattice AHB-Lite Bridge IP Cores are based on AMBA3 specification which does not support write strobes. This applies to the following Bridges IP: AHB-Lite to AXI4 Bridge AXI4-to AHB-Lite Bridge AHB-Lite Interconnect AHB-Lite Feedthrough

• 7608 - Propel Builder: How to export AMBA bus out from Lattice Propel Builder system with a valid memory-mapped address range to the higher-level module.

  The Feedthrough IP allows you to export the specific AMBA bus out from the Lattice Propel Builder system to the higher-level module. Please refer to FPGA-AN-02072-1.0: Lattice RISC-V Embedded Design Guidelines for more information on the application ...

• 1272 - Mico32:  How do I reestablish access to the LatticeMico32 debugger without rebooting?

  The LatticeMico32 debugger is accessed using the Lattice USB download cable. Other Lattice tools like ispVM System, Reveal, and Orcastra also use the USB download cable. During development it is common to build and download new FPGA bitstreams. New ...

• 7406 - RISC-V CPU IP Core: Do Lattice RISC-V supports exception trap handler when writing data to an invalid address?

  Description: RISC-V SM(v1.5)/MC(v2.5) CPUs currently only support trap handler for read access error. When CPU read from an invalid instruction/data address range, it will cause an exception which trigger the trap handler. However, if CPU write to an ...

• 1138 - Mico32: How to compile and link the Mico32 executable code to be either position-independent or relocatable?

  Because the Mico32 compiler does not support the option to generate position-independent code, such as using only relative branch instructions for all code branching, the compiled code will not be position-independent, and it cannot be placed to any ...