)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"93fa08cc266535aec980f9089c5c89a2fcb5535f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dda2e9e2_4fe4cefa","updated":"2024-12-26 21:21:47.000000000","message":"As discussed on IRC in https://libera.irclog.whitequark.org/openocd/2024-11-26\nthe commit https://review.openocd.org/c/openocd/+/8523\ncan be problematic for people that cannot or doesn\u0027t want to update a 10+ years old ST-Link with a newer post-HLA firmware.\nThis means that while dapdirect offers many advantages wrt HLA, I cannot simply drop HLA on ST-Link! But, I hesitate to fully revert 8523.\n\nI cannot find a simple way to switch at runtime between HLA and dapdirect by checking the ST-Link firmware version, because the TCL conditions about HLA in scripts and the override of Cortex-M with HLA target are done much earlier than the initial communication with ST-Link.\n\nThis series partially address the issue by:\n- using a single transport name \u0027swd\u0027 for \u0027swd\u0027, \u0027hla_swd\u0027 and \u0027dapdirect_swd\u0027 and a single name \u0027jtag\u0027 for \u0027jtag\u0027, \u0027hla_jtag\u0027 and \u0027dapdirect_jtag\u0027;\n- detecting in `interface/stlink.cfg` if another adapter has been already configured before, thus allowing the user to add `-f interface/stlink-hla.cfg` at the beginning of the openocd command-line to use HLA instead of dapdirect.\n\nDo you thing this could be enough to address the backward compatibility?","commit_id":"930868f56cb39cfc8b0ecd738c2fc52121a4765e"}]}