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

• Related Articles

• 7053 - Propel: Why I unable to run debugger with Propel SDK on my RISC-V Project?

  Description: 1. RISC-V reset vector is fixed at address 0x00000000, thus instruction memory must start at address 0x0. 2. RISC-V instruction port is a read only port. To run debugger with Propel SDK, the SoC design must support writes to the ...

• 7214 - Avant-E: How to enable RISC-V software debug for Avant-E device

  Description: User is required to implement soft JTAG to enable RISC-V debug in Avant-E early silicon. Solution: Please follow below step to enable debug with Soft-JTAG. The pin assignment is based on Avant-E Evaluation Board. Create an Avant-E RISC-V ...

• 7531 - Propel SDK: How do user change the GNU Language Standard in Lattice Propel SDK.

  User may follow below steps to include desired compiler language standard in Lattice Propel SDK. Open Project Properties: Right-click on your project in the Project Explorer and select Properties. Navigate to C/C++ Build: In the Properties window, ...

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

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