6915 - Propel: Is it possible to do Propel OpenOCD debugging on a device that is part of a JTAG chain?

• Related Articles

• 6904 - Propel 2022.1 and below: Why does Propel 2022.1 OpenOCD debug configuration show "+" when scanning the device?

  Description: When doing OpenOCD debug on Propel 2022.1 and lower versions, users might encounter an issue when scanning the device. The device dropdown upon scanning will show the "+" sign only instead of the targeted device. Solution: For Propel ...

• 7502 - Propel SDK GDB OpenOCD Debugger: How do user connect RISC-V debugger to FPGA device without downloading software image?

  This feature is supported in Propel SDK v2024.1, feature describe as "attach to running target" in debugger startup tab. User may refer to below User Guide for more information: Lattice Propel 2024.1 SDK User Guide - FPGA-UG-02211-1.0 - Appendix E. ...

• 6622 - OpenOCD Debug: Err: can not found the device from family database, use default value to access this device. "Info: TAP fpga_spinal.bridge does not have IDCODE."

  Description:User will see this error message on Lattice Propel OpenOCD Debug using LFMXO5-25's RISC V. Solution:As a workaround, user can try the following method: 1. Constraint the Radiant project and make sure no timing errors. 2. Slow down the ...

• 7268 - Propel: What is the workaround for the OpenOCD Debugger Error - Err: can not found the device from device family database, use default value to access this device?

  Description: When you perform an OpenOCD debug session with the MachXO3LF Evaluation Kit, you may encounter the error message below, where the debugger is unable to identify the device family from the database. Device List: LCMXO3LF-9400C:0x612BE043 ...

• 6921 - Propel: What are the ways to initialize the system memory when performing a Propel OpenOCD Debug?

  There are three ways user can do this: 1. Adding the .mem file to the system memory IP.2. Initialize the EBRs of the system memory IP through the ECO editor.3. Do not initialize through IP or EBR. Simply run the OpenOCD debugger. This will ...