- This topic has 1 reply, 1 voice, and was last updated 7 years, 9 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Home › Forums › Mastering STM32 book support forum › Cannot Start Debugger for Section 5.2, Semihosting Example
I cannot start debugger using OpenOCD locally. I cannot uncheck “Start OpenOCD locally” OpenOCD Setup option on Debugger tab of Debug Configurations window because of bug which needs to be fixed in OpenOCD Ver 0.10
This “OpenOCD Remote” bug is described in recent book forum postings.
The example 1 project (stm32nucleo-f446-ex1) compiles with only 1 warning but a “program file does not exist” error is displayed when debugger is run. See Sec5-2_ArmSemihosting.png attachment. When this project example is downloaded to nucleo-f446 board using ST-Link Utility. LED flashing operates continuously. No pushbutton pressing required. The Debug folder tree of project is attached (ex1-DebugFolders.png).
All the ex1 project Debug Configurations window tabs contain the same settings as previous project example (stm32nucleo-f446) described in section 4.3.1
Debugger runs this project using OpenOCD locally and breakpoint stop/resume actions work. Yes, “Enable ARM semihosting” option is checked on Debug Configurations window Startup tab.
What other info or procedure checks are needed to resolve this issue? Thanks.
Larry
A Google search against
“Program File does not exist” while trying to debug with Eclipse OpenOCD
lead to the following page.
http://www.openstm32.org/forumthread2987
The pertinent section is:
For:
Main (tab) => Project (field)
I clicked on the Browse button and selected the project name. Once this was done the elf file path and file name (relative to the Eclipse project) appeared in the C/C++ Application field.
Except the project name was already in the Project: Text Box. Just click the “Search Project…” button (below the “C/C:: Application:” Text Box. The applicable .elf file filename is found and placed in the “C/C:: Application:” Text Box. See attachment (ex1-DebugConfig_MainTab__RevA.png). Apply and Close the Debug Configurations window.
Debugger now runs fine. See attachment (Sec5-2_ArmSemihosting_RevA.png)
Larry