How to debug custom board on SoftConsole?

[mcergun]

I've started working on a new custom board with the mpfs250t. Had been using mpfs-icicle-kit-es with mpfs250-es.
The problem is I can't get the debug working. I can successfully program the eNVM with SoftConsole or FlashPro Express.

What happens:

Here's openocd output:

fpServer v17 waiting for incoming connections on the port 3334 with API v5
Info : 1 xxx microsemi_flashpro_server.c:1751 microsemi_flashpro_initialize() FlashPro ports available: yyy
Info : 2 xxx microsemi_flashpro_server.c:1752 microsemi_flashpro_initialize() FlashPro port selected:   yyy
xPack OpenOCD (Microchip SoftConsole build), x86_64 Open On-Chip Debugger 0.10.0+dev-00859-g95a8cd9b5-dirty (2022-03-15-14:08)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
MPFS
Info : only one transport option; autoselect 'jtag'
Info : Hardware thread awareness created
do_board_reset_init
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : No Embedded FlashPro6 (revision B) devices found
Info : clock speed 6000 kHz
Info : JTAG tap: mpfs.cpu tap/device found: 0x1f81a1cf (mfg: 0x0e7 (GateField), part: 0xf81a, ver: 0x1)
Warn : JTAG tap: mpfs.cpu       UNEXPECTED: 0x1f81a1cf (mfg: 0x0e7 (GateField), part: 0xf81a, ver: 0x1)
Error: JTAG tap: mpfs.cpu expected 1 of 15: 0x0f8581cf (mfg: 0x0e7 (GateField), part: 0xf858, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 2 of 15: 0x0f8781cf (mfg: 0x0e7 (GateField), part: 0xf878, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 3 of 15: 0x0f8771cf (mfg: 0x0e7 (GateField), part: 0xf877, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 4 of 15: 0x0f8181cf (mfg: 0x0e7 (GateField), part: 0xf818, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 5 of 15: 0x0f8381cf (mfg: 0x0e7 (GateField), part: 0xf838, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 6 of 15: 0x0f83c1cf (mfg: 0x0e7 (GateField), part: 0xf83c, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 7 of 15: 0x0f8191cf (mfg: 0x0e7 (GateField), part: 0xf819, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 8 of 15: 0x0f8391cf (mfg: 0x0e7 (GateField), part: 0xf839, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 9 of 15: 0x0f83d1cf (mfg: 0x0e7 (GateField), part: 0xf83d, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 10 of 1: 0x0f81a1cf (mfg: 0x0e7 (GateField), part: 0xf81a, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 11 of 1: 0x0f83a1cf (mfg: 0x0e7 (GateField), part: 0xf83a, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 12 of 1: 0x0f83e1cf (mfg: 0x0e7 (GateField), part: 0xf83e, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 13 of 1: 0x0f81b1cf (mfg: 0x0e7 (GateField), part: 0xf81b, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 14 of 1: 0x0f83b1cf (mfg: 0x0e7 (GateField), part: 0xf83b, ver: 0x0)
Error: JTAG tap: mpfs.cpu expected 15 of 1: 0x0f83f1cf (mfg: 0x0e7 (GateField), part: 0xf83f, ver: 0x0)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : datacount=2 progbufsize=16
Info : Disabling abstract command reads from CSRs.
Info : Core 0 could not be made part of halt group 1.
Info : Examined RISC-V core; found 5 harts
Info :  hart 0: XLEN=64, misa=0x8000000000101105
Info :  hart 1: currently disabled
Info :  hart 2: currently disabled
Info :  hart 3: currently disabled
Info :  hart 4: currently disabled
Info : datacount=2 progbufsize=16
Info : Disabling abstract command reads from CSRs.
Info : Core 1 could not be made part of halt group 1.
Info : Examined RISC-V core; found 5 harts
Info :  hart 0: currently disabled
Info :  hart 1: XLEN=64, misa=0x800000000014112d
Info :  hart 2: currently disabled
Info :  hart 3: currently disabled
Info :  hart 4: currently disabled
Info : datacount=2 progbufsize=16
Info : Disabling abstract command reads from CSRs.
Info : Core 2 could not be made part of halt group 1.
Info : Examined RISC-V core; found 5 harts
Info :  hart 0: currently disabled
Info :  hart 1: currently disabled
Info :  hart 2: XLEN=64, misa=0x800000000014112d
Info :  hart 3: currently disabled
Info :  hart 4: currently disabled
Info : datacount=2 progbufsize=16
Info : Disabling abstract command reads from CSRs.
Info : Core 3 could not be made part of halt group 1.
Info : Examined RISC-V core; found 5 harts
Info :  hart 0: currently disabled
Info :  hart 1: currently disabled
Info :  hart 2: currently disabled
Info :  hart 3: XLEN=64, misa=0x800000000014112d
Info :  hart 4: currently disabled
Info : datacount=2 progbufsize=16
Info : Disabling abstract command reads from CSRs.
Info : Core 4 could not be made part of halt group 1.
Info : Examined RISC-V core; found 5 harts
Info :  hart 0: currently disabled
Info :  hart 1: currently disabled
Info :  hart 2: currently disabled
Info :  hart 3: currently disabled
Info :  hart 4: XLEN=64, misa=0x800000000014112d
Info : Listening on port 3333 for gdb connections
Started by GNU MCU Eclipse
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target mpfs.hart0_e51, state: halted
Info : Disabling abstract command writes to CSRs.
Info : Disabling abstract command writes to CSRs.
Info : Disabling abstract command writes to CSRs.
Info : Disabling abstract command writes to CSRs.
Info : Disabling abstract command writes to CSRs.
Info : dropped 'gdb' connection
shutdown command invoked
fpServer: signal 2 was received, shutting down...

The process is terminated with an error message pop-up. The window details say:

'Launching pfsoc-empty-baremetal Debug' has encountered a problem.
Error in final launch sequence

Error in final launch sequence
  Failed to execute MI Command:
    load D:\\workspace\\Debug\\empty-baremetal.elf
      Error message from debugger back end:
Failed to execute MI Command:
load D:\\workspace\\Debug\\empty-baremetal.elf
Error message from debugger back end:
Load failed
Load failed

What I've tried:

• Updated program scripts as MPFS250T_ES were giving errors with programming as well. Updated values are:

--die MPFS250T
--package FCVG784

• Verified Project and application elf file settings:

empty-baremetal
Debug/empty-baremetal.elf

• Verified openocd location and settings:

c "set DEVICE MPFS"
--file board/microsemi-riscv.cfg

• Verified GDB Session settings:

set mem inaccessible-by-default off
set $target_riscv1=1
set architecture riscv:rv64

• I've made sure that D:\\workspace\\Debug\\empty-baremetal.elf is where the ELF is generated and location is correct.
• Manually started OpenOCD. It does not crash or stop
• Tried to manually start gdb after OpenOCD, but can't set target even though I use the commands I've supplied to the SoftConsole
• Checked .cfg files for debugger. Couldn't find any relevant config related to the chip or routing.

[rockoguido]

Hi... You can bypass SoftConsole for the moment and just test the openocd based connection. The command would look something like this....

C:\Microchip\SC-2022.2-new\openocd\bin>.\openocd.exe --command "set DEVICE MPFS" --file C:\Microchip\SC-2022.2-new\openocd\share\openocd\scripts\board\microsemi-riscv.cfg

I'm assuming you are using an external FP5 or FP6 for the JTAG connection?
Also assuming that this is the same workspace in SoftConsole where you have a successful connection to the Icicle Kit?

Dave