Chris Reed

Thanks for the update. It's probably because the TPIU is accessed through APB-AP#2, and is declared on that AP's ROM table (instead of the same ROM table as the CM7)....

> Does fixing this mean a lot of work? Not really sure! The main thing is to ensure the TPIU gets attached to the target node. > ^^ should be...

>^^ should be tpiu What branch/commit are you looking at? It's correct on all of `main`, `develop`, and `feature/debug_sequences`, and the v0.34 release (v0.33.1 was notably different).

Ugh, and I totally missed the error on the next line below… 😅

Actually, the STLink V2J28 and above, including all v3, does allow access of any AP (except the version 2 APs used in ADIv6, required for Cortex-M55 and M85). That's how...

Does this device need to re-enter the debug session via DM-AP after hardware reset? (I hope not… debug logic being reset on hw reset is a Bad Thing imo! 😉...

Btw, if you have a CMSIS-Pack with debug sequences for this device, you can try out the [feature/debug_sequences](https://github.com/flit/pyOCD/tree/feature/debug_sequences) on my work. It's nearly complete and going through extensive testing and...

Fyi, I believe GitHub timed out because the issue comment was so large with the inlined log. It was timing out even as I tried to close the duplicate issues!

The short answer is that Mbed Studio doesn't yet support the LPC1768. It's a known issue but unfortunately hasn't been resolved yet afaik. Are you using the Mbed LPC1768 board?...

Sorry, I can't really answer questions about Mbed Studio since I'm not a member of that team, meaning I don't know what their plans are. I'm looking at LPC1768 support,...