[christophe]

Seems to be good with this fix.

Thanks

[christophe]

Hi,

Seems working well by replacing the sysprogsUnitTestInterface.c file.

Thanks

 

[christophe]

Hi,

 

With this version, the tracing application “data destination”  is correctly set to “trace memory”, but when i try to compile the unit test, the build still stops on the #error. Here is the build log:

 

[934/945] Building C object esp-idf/SysprogsUnitTestInterface/CMakeFiles/__idf_SysprogsUnitTestInterface.dir/SysprogsUnitTestInterface.c.obj
FAILED: esp-idf/SysprogsUnitTestInterface/CMakeFiles/__idf_SysprogsUnitTestInterface.dir/SysprogsUnitTestInterface.c.obj
C:\SysGCC\esp32\tools\xtensa-esp32-elf\esp-2019r2-8.2.0\xtensa-esp32-elf\bin\xtensa-esp32-elf-gcc.exe -DBUILDING_UNIT_TESTS -DUNITY_INCLUDE_CONFIG_H -Iconfig -IC:/SysGCC/esp32/esp-idf/SysprogsComponents/SysprogsUnitTestInterface -IC:/SysGCC/esp32/esp-idf/v4.2/components/newlib/platform_include -IC:/SysGCC/esp32/esp-idf/v4.2/components/freertos/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/freertos/xtensa/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/heap/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/log/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/lwip/include/apps -IC:/SysGCC/esp32/esp-idf/v4.2/components/lwip/include/apps/sntp -IC:/SysGCC/esp32/esp-idf/v4.2/components/lwip/lwip/src/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/lwip/port/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/lwip/port/esp32/include/arch -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/src/esp32/. -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/src/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_rom/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_common/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_system/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/xtensa/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/xtensa/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/driver/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/driver/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_ringbuf/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/efuse/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/efuse/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/espcoredump/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_timer/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_ipc/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/soc/esp32/. -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/soc/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/soc/soc/esp32/../include -IC:/SysGCC/esp32/esp-idf/v4.2/components/vfs/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_wifi/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_wifi/esp32/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_event/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_netif/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_eth/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/tcpip_adapter/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/app_trace/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/esp_gdbstub/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/unity/include -IC:/SysGCC/esp32/esp-idf/v4.2/components/unity/unity/src -mlongcalls -Wno-frame-address -ffunction-sections -fdata-sections -fstrict-volatile-bitfields -Wall -Werror=all -Wno-error=unused-function -Wno-error=unused-but-set-variable -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wextra -Wno-unused-parameter -Wno-sign-compare -ggdb -Og -std=gnu99 -Wno-old-style-declaration -D_GNU_SOURCE -DIDF_VER=\”v4.2-dev-1995-g636b964c8-dirty\” -DESP_PLATFORM -MD -MT esp-idf/SysprogsUnitTestInterface/CMakeFiles/__idf_SysprogsUnitTestInterface.dir/SysprogsUnitTestInterface.c.obj -MF esp-idf\SysprogsUnitTestInterface\CMakeFiles\__idf_SysprogsUnitTestInterface.dir\SysprogsUnitTestInterface.c.obj.d -o esp-idf/SysprogsUnitTestInterface/CMakeFiles/__idf_SysprogsUnitTestInterface.dir/SysprogsUnitTestInterface.c.obj -c C:/SysGCC/esp32/esp-idf/SysprogsComponents/SysprogsUnitTestInterface/SysprogsUnitTestInterface.c
C:/SysGCC/esp32/esp-idf/SysprogsComponents/SysprogsUnitTestInterface/SysprogsUnitTestInterface.c:8:2: error: #error Please set the Application Level Tracing -> Data Destination setting in ESP-IDF confguration to ‘Trace Memory’
#error Please set the Application Level Tracing -> Data Destination setting in ESP-IDF confguration to ‘Trace Memory’
^~~~~

[christophe]

Could you please update the post title to

[SOLVED] Debugging Microsemi SmartFusion2 with Flashpro device and microsemi custom version of OpenOCD

 

 

 

[christophe]

Great news, it works !

So, when i tried the delay option, I still was on an old 5.3 version. It seems that the delay didn’t work as it should.

On the 5.4 R11, I set a delay to somehting like 250ms and it works as expected.

 

So, for people who want to debug Microsemi SmartFusion 2 with VisualGDB :

1. Choose as debug method : Custom GDB Stub
2. point the cutsom OpenOCD.exe in the installation of SoftConsole (dev env by microsemi based on eclipse)
3. add the following command line arg : -c “gdb_port 3333” -f board/microsemi_cortex_m3 -c “set DEVICE M2S090”
4. In the working dir field, set the OpenOCD scripts directory (in the SoftConsole installation dir)

Set the Delay to a 250ms

This configuration allows to debug in internal SRAM (the script configure the VTOR register to the SRAM base address.

Do not forget to use the xxx-sram/ld linker script provided in the SoftConsole Source package.

 

 

 

[christophe]

Hello,

 

I ve already tried the delay option. Whatever the delay i put,  I always get the error message box directly. But when i click on retry,  I can see the delay.

I use a custom gdb stub

[christophe]

The telnet connection succeeded.

As explained in a previous message, we checked that the port is in listening mode when the error message box is dispayed (before pressing any button)

It seems that gdb attempts to connect to the port 3333 a little bit too early.

Is it possible to specify a delay between the execution of openocd and when gdb attempts to connect to it ?

 

 

[christophe]

Hi,

here are 2 files :

abort.txt is the gdb log when i click on the abort button

retry.txt is the log when i click on the retry button

Attachments:

You must be logged in to view attached files.

[christophe]

Hi,

I tried to change the port, and it didn’t solve the issue. So I’ve checked the netstat info at some point (i returned to port 3333 for these tries)

When I start the second time the debug session (when i receive the error message box), the netstat -a returns:

TCP 127.0.0.1:3333  xxxMyPcNamexxx LISTENING

TCP 127.0.0.1:3334  xxxMyPcNamexxx:57364 ESTABLISHED

TCP 127.0.0.1:4444  xxxMyPcNamexxx LISTENING

As soon as i click on the Retry button, i got

TCP 127.0.0.1:3333  xxxMyPcNamexxx LISTENING

TCP 127.0.0.1:3333  xxxMyPcNamexxx:57372 ESTABLISHED

TCP 127.0.0.1:3334  xxxMyPcNamexxx:57364 ESTABLISHED

TCP 127.0.0.1:4444  xxxMyPcNamexxx LISTENING

When I stop the debug session, all the listening ports are properly removed

 

 

 

 

[christophe]

Hello,

I got something. Seems related to underpowering from the jtag cable: removing the 3v3 wire and using the power supply using the USB cable (UART), it seems working well.

 

[christophe]

I’ve checked with another esp32 eval board (based on ESP32-WROVER-B). If I use the built-in JTAG, it works. If i remove the JTAG jumpers and plug my C232HM cable, it also works (without the need of any reset).

But the JTAG debug on the WROOM32 is still stuck!

[christophe]

Working great ! It is now easier to bring back PlatformIO project in VS + VSGdb.

 

Thanks a lot.

[christophe]

Hi,

I’ve tested and it is almost working: the build process takes the default libs first. So, if you want to build a project with a private older library, it takes the local one instead the private one.

It will be great if the build process could take the private one first (or having a checkbox to force to take in account only the private (per-project) ones)

 

 

 

[christophe]

For info (and a kind of feature request) :

I recently try PlatfomIo as VS Code extension to build Arduino projet. The advantage over Arduino IDE and the VisualGDB extension is that PlatformIO is able to manage private Package/libraries stored in specific directory in the project itself. So it is easily possible to have a self-contain project without any trouble of newtest/updated librairies not compatible anymore.

Before building the final sketch, PlatformIO compiles all private libraries (as C lib), and link them to the final compilation.

I will be really happy to have such feature in VisualGDB as well (and enventually the ability to import PlatformIO project directly)

 

 

[christophe]

Hi,

Thanks,  I’ve updated to the latest 2.5.0 Core, but still fails. So, i removed all packages and re-download them, and now, it is working fine. As you said, something was broken somewhere.

[Author]

Posts