Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

You are viewing a reply to problem with debugging the GPIO existing code on the stm32L4RG board  

problem with debugging the GPIO existing code on the stm32L4RG board

Posted by danilopucci on 2017-08-22 19:39

Hi Neham,

Maybe there’s a relationship between your first issue and the second one.

Your C/C++ Application should be pointing to the .elf file generated on your Debug folder, like this: Debug/YourProjectName.elf

In your case I think is something like: Debug/STM32L476RG_NUCLEO.elf

Clarifying the meaning of “your GDB is not able to find symbols” is that Ac6 STM32 Debugger is GDB, and as you are pointing to a .c file GDB is not finding the debug symbols... The debug symbols is inside .elf file

I think everything should be solved pointing to the right .elf file

Danilo

Reads: 2719
Link
Posted by neham on 2017-08-23 12:25

Hi Dalino,

Thanks a lot.

We are not able to locate .elf file anywhere in our project. After building our project, in debug folder of our project explorer, there are only .mk files but not .elf file. Anyway we searched .elf in our whole project, instead of STM32L476RG_NUCLEO.elf we found STM32L476RG_NUCLEO.elf.launch file in the location “/home/controller/Ac6/SystemWorkbench/STM32Cube_FW_L4_V1.8.0/STM32Cube_FW_L4_V1.8.1/Projects/STM32L476RG-Nucleo/Examples/GPIO/GPIO_EXTI/TrueSTUDIO/STM32L476RG_NUCLEO”.

I dont know why .elf file is not generating after building our project successfully? please suggest

one more thing to clarify, whenever we are building our project, in Debugger configuration under debugger tab, “STM32L476RG_FLASH.ld” file is loaded automatically instead of .elf file. and it is showing the same error - Error in final launch sequence
Failed to execute MI command:
symbol-file /home/controller/Ac6/SystemWorkbench/STM32Cube_FW_L4_V1.8.0/STM32Cube_FW_L4_V1.8.1/Projects/STM32L476RG-Nucleo/Examples/GPIO/GPIO_EXTI/TrueSTUDIO/STM32L476RG_NUCLEO/STM32L476RG_FLASH.ld

Error message from debugger back end:
`/home/controller/Ac6/SystemWorkbench/STM32Cube_FW_L4_V1.8.0/STM32Cube_FW_L4_V1.8.1/Projects/STM32L476RG-Nucleo/Examples/GPIO/GPIO_EXTI/TrueSTUDIO/STM32L476RG_NUCLEO/STM32L476RG_FLASH.ld’: can’t read symbols: File format not recognized.

Please find the attached screenshot of debug folder having only .mk file not .elf file.

Thanks

Screenshot from 2017-08-23 15-55-30.png (247.05 Kb)
Link
Posted by neham on 2017-09-04 09:14

Hi Danilo,

I am not able to locate .elf file in debug folder after running the project.

Please help me with this issue.

Thanks

Link