I don't currently have access to the hardware connection between the ST-Link and the board, so, besides from a bad connection, I'm not sure what could be wrong. In short, I'm unable to read or write the MCU, I get 'Can't halt the core', 'Unknown MCU found on target' an...
We find thatSTLINK_DEBUG_APIV3_ENTERis missing. The JTAG_API version is checked for v1 and if that turns out false, v2 is automatically selected. I could imagine this to be a relict from earlier times when STLINK/V3 programmers did not exist. That would also explain why this happens ...
1、点击工具栏中的魔法棒,进入设置界面。 步骤1 2、在device中进行如下设置。 步骤2 3、选择你的芯片型号。 步骤3 4、在Debug中进行如下设置。 步骤4 5、由步骤4进入,并在进行步骤5前,把ST-Link线插上电脑USB端,然后进行如下设置。 步骤5 6、在步骤5的FLASH Download中进行如下设置。 步骤6 7、选择你的...
Reason: (18) Could not verify ST device! Abort connection. Error in initializing ST-LINK device. Reason: (18) Could not verify ST device! Abort connection. The strange thing is I have no issue programming my boards using ST-Link Utility. I thought that maybe t...
0xe0042000 --> The memory register holding the information on the chip ID could not be read. The following problems may lead to this case: This problem is caused by the SWDIO and SWCLK being configured for other purpose (GPIO, etc) other than Serial Wire configuration or Jtag --> A ...
Target not created. Build Time Elapsed: 00:00:05 Load "D:\\u_version projects\\ZET6\\LED_1\\Objects\\LED.axf" ___^ *** error 56: cannot open file Error: Flash Download failed - Could not load file 'D:\u_version projects\ZET6\LED_1\Objects\LED.axf' Flash Load finished at 11...
I would say that buying J-Link to be able to evaluate the IDE is not feasible. Attached are: a. batch file for GDB start (I execute the batch file then Connect to the GDB then start a debug session) b. debug log from GDB c. PC / registers at the end of load / start of ...
Sorry, we tried reproducing it on our hardware (ST-Link v1 and v2) and could not get the problem. It looks like OpenOCD may not fully support st-link v2.1 at this point. Does the Texane/STLink tool work for your hardware? August 3, 2014 at 19:22 #3311 G40 Participant Hello...
After Saving this file (and of course re-booting into unsigned installation mode) I was able to Perform ‘UPDATE DRIVER’ which could now be found and the nucleo board now works. Hope this Helps others Best wishes Martin NB Corrected some spelling typos and added generic HardwareID Note ...
ST-LINK is connected but no board is connected For instance, not using option –d when only SWD pins are connected to the HW. Old ST-LINK_firmware. Reset error. Reset button on board pressed. Target could not be halted. Command error. Application reset error. Version error. Get status ...