[JoeWright]

Thanks, the path mapping did the trick.  I didn’t really make any changes, just clicked manual then back to default and that was enough to reset it back to normal.

[JoeWright]

I’ve tried downgrading to preview 4, to get back to where I was, but still no joy.  Also, all of my esp32 projects now won’t load properly, clean, etc…

[JoeWright]

Unfortunately the output I posted above is what happens when you do a Clean Solution, and uninstalling and reinstalling the toolchain made no difference.

[JoeWright]

Ok, I will hit the esp32 forum and see if they have any thoughts.

Meanwhile, I’ve tried to go back to rev. 12 of the toolchain but now my project is broken.  The project contents just say ‘Load failed, double-click for details’ (no details on double click), and if I try to clean or rebuild I get:

—— Clean started: Project: Module01, Configuration: Debug VisualGDB ——
VisualGDB: Run “c:\SysGCC\esp32\bin\bash.exe –login -c “export IDF_PATH=/esp-idf/v3.1 && export BATCH_BUILD=1 && export -n PYTHONHOME && export LANG=en_US && cd /E/projects/IMU/ESP32/Test_Projects/Module01 && make clean BUILD_DIR_BASE=’/E/projects/IMU/ESP32/Test_Projects/Module01/Debug’ SDKCONFIG=’/E/projects/IMU/ESP32/Test_Projects/Module01/sdkconfig-debug’ V=0″” in directory “” on local computer
/usr/bin/bash: line 0: cd: /E/projects/IMU/ESP32/Test_Projects/Module01: No such file or directory
————————————————————-
Command exited with code 1
Executable: c:\SysGCC\esp32\bin\bash.exe
Arguments: –login -c “export IDF_PATH=/esp-idf/v3.1 && export BATCH_BUILD=1 && export -n PYTHONHOME && export LANG=en_US && cd /E/projects/IMU/ESP32/Test_Projects/Module01 && make clean BUILD_DIR_BASE=’/E/projects/IMU/ESP32/Test_Projects/Module01/Debug’ SDKCONFIG=’/E/projects/IMU/ESP32/Test_Projects/Module01/sdkconfig-debug’ V=0”
Directory:
VisualGDB: Error: Command-line action failed
========== Clean: 0 succeeded, 1 failed, 0 skipped ==========

 

I can access the visualgdb settings but I don’t know how to correct this corruption.  I’m finding I get a lot of project corruptions with upgrades/downgrades.  Any tips to correct?

[JoeWright]

OK thanks.

[JoeWright]

Ok, thanks, I’ll try and put a bit of flexibility in my design.

I think I saw another post by your team where you recommended the Olimex ARM-USB-OCD-H for esp32.  Is that still a good choice and what configuration of pins worked best for that model?

 

Thanks, Joe

[JoeWright]

I don’t suppose there’s been any updates?

I’m so confused by the ST-Link v2.1 as it doesn’t seem to be sold in the UK, or even listed on the ST website apart from support pages.  I’ve updated the firmware of my two ST-Link v2’s but I can’t use them at the same time with VisualGDB as described above.

I suppose I could try the OpenOCD patches.  What were the issues you were finding with them?

 

Thanks, Joe

[JoeWright]

Ah ok, thanks.

[JoeWright]

Ok, I’ve just changed it to dwarf 2, and it worked.  Then changed it back to gdb optimised and it still worked!  Obviously that tidied up something that a clean and rebuild didn’t.  So all working now, thanks.

Btw, the version of gdb that I’m using is whatever comes with visualgdb.  Wouldn’t know where to start with going to an older version but since its working now, I’ll leave alone.

 

Thanks, Joe

[JoeWright]

Did an ignore and then looked at the gdb session details:

 

VisualGDB is licensed to Joe Wright
C:\SysGCC\arm-eabi\bin\arm-eabi-gdb.exe –interpreter mi E:\projects\IMU\STM32_Projects\Handle_6\VisualGDB\Debug\Handle_6
-gdb-version
=thread-group-added,id=”i1″
~”GNU gdb (GDB) 8.0.1\n”
~”Copyright (C) 2017 Free Software Foundation, Inc.\n”
~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
~”This GDB was configured as \”–host=i686-w64-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”
This GDB was configured as “–host=i686-w64-mingw32 –target=arm-eabi”.
Type “show configuration” for configuration details.
~”\nFor bug reporting instructions, please see:\n”
~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/&gt;.
~”For help, type \”help\”.\n”
~”Type \”apropos word\” to search for commands related to \”word\”…\n”
~”Reading symbols from E:\\projects\\IMU\\STM32_Projects\\Handle_6\\VisualGDB\\Debug\\Handle_6…”
~”done.\n”
~”GNU gdb (GDB) 8.0.1\n”
~”Copyright (C) 2017 Free Software Foundation, Inc.\n”
~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
~”This GDB was configured as \”–host=i686-w64-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”
This GDB was configured as “–host=i686-w64-mingw32 –target=arm-eabi”.
Type “show configuration” for configuration details.
~”\nFor bug reporting instructions, please see:\n”
~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/&gt;.
~”For help, type \”help\”.\n”
~”Type \”apropos word\” to search for commands related to \”word\”.\n”
^done
-list-features
^done,features=[“frozen-varobjs”,”pending-breakpoints”,”thread-info”,”data-read-memory-bytes”,”breakpoint-notifications”,”ada-task-info”,”language-option”,”info-gdb-mi-command”,”undefined-command-error-code”,”exec-run-start-option”]
-gdb-set disassembly-flavor intel
^error,msg=”No symbol \”disassembly\” in current context.”
-gdb-set print demangle off
^done
-break-insert -f main
^done,bkpt={number=”1″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x08013302″,func=”main()”,file=”Src/main.cpp”,fullname=”E:\\projects\\IMU\\STM32_Projects\\Handle_6\\Src\\main.cpp”,line=”219″,thread-groups=[“i1″],times=”0″,original-location=”main”}
set remotetimeout 60
&”set remotetimeout 60\n”
=cmd-param-changed,param=”remotetimeout”,value=”60″
^done
target remote :55440
&”target remote :55440\n”
~”Remote debugging using :55440\n”
=thread-group-started,id=”i1″,pid=”42000″
=thread-created,id=”1″,group-id=”i1″
~”../../gdb-8.0.1/gdb/frame.c:542: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed’ failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? ”
../../gdb-8.0.1/gdb/frame.c:542: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed’ failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session?
~”(y or n) [answered Y; input not from terminal]\n”
&”\nThis is a bug, please report it.”
&” For instructions, see:\n<http://www.gnu.org/software/gdb/bugs/&gt;.”
&”\n\n”
~”../../gdb-8.0.1/gdb/frame.c:542: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed’ failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreate a core file of GDB? ”
../../gdb-8.0.1/gdb/frame.c:542: internal-error: frame_id get_frame_id(frame_info*): Assertion `stashed’ failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB?
~”(y or n) [answered Y; input not from terminal]\n”
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application’s support team for more information.

[JoeWright]

No, I did a full reboot but it did not help.  Loading up the two different projects – one works, one doesn’t.  Went in and checked the gdb settings were the same and they were (as far as I can tell).  Have also tried switching off the firewall but that didn’t work either.

[JoeWright]

Ok, thanks.  Yes, it looks like a newlib-nano limitation indeed.

[JoeWright]

Hi, the problem is that with the new gpdsc importer, it guarantees you’re going to get conflicts.  The solution is to remove all the cubemx sources and headers referenced in the generated project, delete the include folder additions in the project settings, and enable the embedded frameworks in visualgdb.

That is more work than it used to be, when using the import from source files, adding the inc folder, and selecting the choice of embedded frameworks.

Attached is an example of an imported project (along with the cubemx base.ioc and base.gpdsc files).  The only other thing I did was enable the Fast Semihosting, which gives rise to the clash with _isatty.

I think if the gpdsc importer is going to be useful, it needs to detect and override the sources of the embedded frameworks coming from cubemx.  Or is there something that can be put in for the alternative firmware location in cubemx?  As I see it, cubemx firmware and visualgdb firmware use different folder structures so I’m not sure what I would put in that field.

Thanks, Joe

Attachments:

You must be logged in to view attached files.

[JoeWright]

Hi, yes that’s what’s happening.  I’ll try and upload a bit later.

My temporary solution was to remove the embedded framework references as you said, but then I ran into that problem with the Fast Semihosting framework as it was conflicting with the cubemx refs for _isatty

[JoeWright]

I guess using the new import option, the firmware location needs to be specified.  But the folder structure for STM32CubeMX (…\Repository\STM32Cube_FW_F3_V1.9.0) is somewhat different to the visualGDB one (…\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\STM32F3xxxx\).

So I’m not sure what to put in there.

[Author]

Posts