Tool/software:
Posting on customer's behalf
Resetting via JTAG while using openOCD does not work unless a code snippet is added to the ti_k3.cfg file, as indicated in this e2e post. Can you please clarify what this code is doing
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Posting on customer's behalf
Resetting via JTAG while using openOCD does not work unless a code snippet is added to the ti_k3.cfg file, as indicated in this e2e post. Can you please clarify what this code is doing
There is no official support for OpenOCD for AM24 or AM6x family of devices. So the guidance provided below is best effort basis. If you are starting a new development we encourage/recommend that you used the standards CCS IDE and XDS tools as recommended on other related posts on AM6x or AM2x you may come across.
Additional background that may help your specific query
> resetting via openOCD does'nt work unless power AP enabled access to M3. this is the DDAP access for M3, CCS and lauterbach do the same thing but in the background. https://e2e.ti.com/support/processors-group/processors/f/processors-forum/926972/am6526-need-detail-document-regarding-power-ap
This code is still there in upstream openocd https://github.com/openocd-org/openocd/blob/master/tcl/target/ti_k3.cfg#L388 and that gets invoked automatically on gdb attach event https://github.com/openocd-org/openocd/blob/master/tcl/target/ti_k3.cfg#L397 this was done because on HS-FS and HS-SE (field securable and security enabled) variants, We do disable access to the DMSC core.
We are not entirely sure what "reset via jtag" implies here. Are you looking for something like https://github.com/openocd-org/openocd/blob/master/tcl/target/ti_k3.cfg#L539
Hope this helps.
Regards
Mukul