26-11-2024, 01:54 PM
Yes, I encountered this, too. But eblink is aware of this. Eblink first checks AP0. This fails, so it retries with AP1.
With -G ap=1 you can configure eblink to directly check AP1. I tried it, but since eblink already works without setting the AP, it didn't change much.
But if you want to use stlink-gdbserver, you have to set the AP to get it to work.
And regarding the JTDO-SWO: I am using a Nucleo board, so this is already wired.
Also, I was trying to connect via SWD, so shouldn't JTDO and SWO be irrelevant for the basic debugging without SWO?
Btw: I am running VSCode with Cortex-Debug and Eblink, so let me know if you encounter any issues with the h5 in the future.
With -G ap=1 you can configure eblink to directly check AP1. I tried it, but since eblink already works without setting the AP, it didn't change much.
But if you want to use stlink-gdbserver, you have to set the AP to get it to work.
And regarding the JTDO-SWO: I am using a Nucleo board, so this is already wired.
Also, I was trying to connect via SWD, so shouldn't JTDO and SWO be irrelevant for the basic debugging without SWO?
Btw: I am running VSCode with Cortex-Debug and Eblink, so let me know if you encounter any issues with the h5 in the future.