...dont know, what your editor shows at 191 --- no AP_NUM
i see:
btw i have no idea, what this means... (backup file , then edit ...maybe as sudo)
i would just try to remove the > if { $ ... < and the else also.
just remains there:
target create $_CHIPNAME.ap2 mem_ap -dap $_CHIPNAME.dap -ap-num 0
swo create $_CHIPNAME.swo -dap $_CHIPNAME.dap -ap-num 0 -baseaddr 0xE00E3000
tpiu create $_CHIPNAME.tpiu -dap $_CHIPNAME.dap -ap-num 0 -baseaddr 0xE00F5000and see, what happens.
after patching out the AP_NUM
I found the steps to upload and debug with a cheap daplink. See my post on imgur (https://imgur.com/a/how-to-use-daplink-cmsis-dap-with-stm32cubeide-OrpcsvX) - or I'll copy paste its contents below:
---
How to use daplink (cmsis-dap) with STM32CubeIDE
You can use a cheap and standard cmsis-dap device to flash and debug stm32 projects within the cube ide. Let's start with a fresh project.
I hook up the dap with 4 wires (vcc, gnd, swdio, swclk) and no reset wire. For this to work without having to constantly manually reset the device, I go to SYS and change Debug mode to Serial Wire. Save and generate code. Build.
Next, we create a file daplink.cfg in the project root. The file should contain:
source [find interface/cmsis-dap.cfg]
adapter speed 1000
transport select swd
source [find target/stm32f1x.cfg]
reset_config none
Now go to Run -> Debug Configurations and create a debug config. Make sure the C/C++ Application field contains our elf file.
The crucial part: on the Debugger tab, we change the probe to OpenOCD, select User Defined script, and use our daplink.cfg.
Click Apply to save our debug config and that should be all. You're now ready to run or debug your code.
QUIRKS: For some reason, ST's openocd scripts leave the mcu paused after detaching the dap. This means every time you Run your code or detach a Debug session, your mcu will need a manual reset.
My workaround for this is to add the following line at the end of daplink.cfg:
lappend pre_shutdown_commands { resume }
