problem with debugging the GPIO existing code on the stm32L4RG board
Hi Danilo,
Thanks for the response.
For my first issue, I am not understanding the meaning of following sentense “Maybe the connection between your STLink and your target MCU is not ok.” because we only have our target board STM32L476-nucleo board which we have connected with our linux(ubuntu16.04) machine and Ac6 system workbench where we are tried to run/debug the existing c project(Existing example : GPIO IOtoggle). Is STLink any hardware or so to interface this board?
As per your suggestion, we have tried to install STLink utility. Unfortunately, this utility for linux is not available in stm official site(www.stm.com). so we tried to install using github by using following commands:
>> sudo apt-get install libusb-1.0-0-dev
>> git clone https://github.com/texane/stlink stlink.git
>> cd stlink
>> make
but while running the above make command, system is either going to reboot or showing the below error:
/usr/bin/make : 1 : /usr/bin/make : cannot fork
so we could not install the STLink utility successfully. if any solution for this problem, Please let me know.
For second issue: In our debugger setting under debugger tab, following information are mentioned below:
Name : STM32L476RG_NUCLEO Debug
GDB command : ${openstm32_compiler_path}/arm-none-eabi-gdb
openOCD Command : “${openstm32_openocd_path}/openocd”
and so on..
Please refer the attached screenshot for more debug setting information.
Thanks