)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1000687,"name":"Tomas Vanek","display_name":"Tomas Vanek","email":"vanekt@fbl.cz","username":"vanekt"},"change_message_id":"5058066fd527144ca8287d7271fa4e50a17e89e9","unresolved":false,"context_lines":[{"line_number":18,"context_line":"in cortex_m_poll()\") proposes a fix for one specific case and only"},{"line_number":19,"context_line":"on cortex_m."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Modify all the examine functions by skipping look-up for the AP if"},{"line_number":22,"context_line":"it was already set in a previous examine; the target\u0027s AP is not"},{"line_number":23,"context_line":"supposed to change during runtime."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Remove the partial fix for cortex_m as it is not needed anymore."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"766dbcf1_e727f4b8","line":22,"range":{"start_line":21,"start_character":36,"end_line":22,"end_character":40},"updated":"2022-12-15 16:50:44.000000000","message":"IMO an important improvement.\nOccasional JTAG/SWD errors or unresponsiveness caused by a deep sleep etc could skip the right AP and continue look-up over all possible 256 APs of ADIv5. Very time consuming and annoying. With the change it cannot happen as soon as the target has been examined.","commit_id":"85e05cd372f9ef85cb9f54ce487af6efb4aa83bb"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"7b447648543162762d3ad5695404443b8cad695a","unresolved":false,"context_lines":[{"line_number":18,"context_line":"in cortex_m_poll()\") proposes a fix for one specific case and only"},{"line_number":19,"context_line":"on cortex_m."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Modify all the examine functions by skipping look-up for the AP if"},{"line_number":22,"context_line":"it was already set in a previous examine; the target\u0027s AP is not"},{"line_number":23,"context_line":"supposed to change during runtime."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Remove the partial fix for cortex_m as it is not needed anymore."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"dc4cd724_b47bb597","line":22,"range":{"start_line":21,"start_character":36,"end_line":22,"end_character":40},"in_reply_to":"766dbcf1_e727f4b8","updated":"2022-12-15 20:52:55.000000000","message":"\u003e ... Very time consuming and annoying. With the change it cannot happen as soon as the target has been examined.\n\nI think we should introduce a target\u0027s flag \"examined_once\" to report that the target property has been read from targets and cached in target struct. This to better explain that we can prevent the time consuming re-read.\nThan the flag \"examined\" could become e.g. \"target_accessible\" to report the current ability to use it. Or it could be moved in target::state, either reusing TARGET_UNKNOWN or, better, adding TARGET_NOT_ACCESSIBLE.","commit_id":"85e05cd372f9ef85cb9f54ce487af6efb4aa83bb"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":1000687,"name":"Tomas Vanek","display_name":"Tomas Vanek","email":"vanekt@fbl.cz","username":"vanekt"},"change_message_id":"5058066fd527144ca8287d7271fa4e50a17e89e9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6b3836bf_d6f83793","updated":"2022-12-15 16:50:44.000000000","message":"Tested on Cortex-M only. No more segmentation faults after momentary SWD disconnections.\nThe change follows the same pattern for all targets, I hope we can assume they would work same way.","commit_id":"85e05cd372f9ef85cb9f54ce487af6efb4aa83bb"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"7b447648543162762d3ad5695404443b8cad695a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8b971bc4_68de7a5d","in_reply_to":"6b3836bf_d6f83793","updated":"2022-12-15 20:52:55.000000000","message":"\u003e Tested on Cortex-M only. No more segmentation faults after momentary SWD disconnections.\n\nThanks\n\n\u003e The change follows the same pattern for all targets, I hope we can assume they would work same way.\n\nActually this modification brings back the behavior before commit 35a503b08d14.\nI haven\u0027t clearly reported it in the commit msg.","commit_id":"85e05cd372f9ef85cb9f54ce487af6efb4aa83bb"}]}