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 2022.1 and lower versions, see below workaround for the issue:

A. If the user has a C:/Data directory on their PC/Laptop, rename the folder. If none, skip to #B

B. Try these steps:

1. Open Task - Manager and kill cableserver.exe task if exists
2. Open Radiant programmer and download the bitstream into board. (this will create cableserver.exe task again)
3. With programmer opened, go to Propel and open OpenOCD debugger and go to 'CableConn' tab
4. Don't click the 'detect cable' button (this somehow will restart the cableserver.exe) and direct click the 'scan-device' button.

C. Try opening Propel this way:

1. Add one line in launch_propel.cmd (before "start eclipse.exe"), which is under the installation path of Propel.
Ex. C:/lscc/propel/2.2/launch_propel.cmd

set TOOLRTF=YOUR_PROPEL_PATH/sdk
(.e.g set TOOLRTF=D:/lscc/propel/2022.1/sdk in my setup)

Related Articles
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 ...
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 ...
6915 - Propel: Is it possible to do Propel OpenOCD debugging on a device that is part of a JTAG chain?
It is possible to do a Propel OpenOCD debugging on a device that is part of a JTAG chain. An example setup here is with a CertusPro-NX Evaluation Board and a CertusPro-NX Versa Board. The first board is the evaluation board while the second board is ...
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 ...
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 ...

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

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

Related Articles

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?

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

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

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

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