)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"c5cc1f7653a2a86a70897e3464e4469e12999449","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"66cd099e_c4a177d7","updated":"2026-06-16 08:30:52.000000000","message":"Thanks for this patch.\nI\u0027m not sure we really need to add such new parameter,\nFor me the parsing of DM should not block the target examine.\n- The comments in the code of `check_dbgbase_exists()` already report that the DM can have buggy entries.\n- No other info is taken from DM either if `dbgbase` match or not with the DM entries.\n- Depending on low power modes some entry is not accessible.\n- On ARM DAP we have ROM tables to discover cores, and we have buggy info there too and entry not accessible by low power modes. The target\u0027s `dbgbase` prevails on the ROM table and is mainly used to bypass incorrect ROM contents.\n\nI think we could simply ignore the return value of `check_dbgbase_exists()`, and convert the `LOG_TARGET_ERROR()` in `LOG_TARGET_WARNING()`","commit_id":"34731a56ddd017d6835467b425590f24be86832c"},{"author":{"_account_id":1002315,"name":"liangzhen","email":"zhen.liang@spacemit.com","username":"liangzhen"},"change_message_id":"179336de0046297e49334c59076e5d3677446a99","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"fc39344a_0ce75259","in_reply_to":"66cd099e_c4a177d7","updated":"2026-06-17 06:24:41.000000000","message":"\u003e I think we could simply ignore the return value of check_dbgbase_exists(), and \u003e convert the LOG_TARGET_ERROR() in LOG_TARGET_WARNING()\n\nIt looks good, and I have completed the changes.","commit_id":"34731a56ddd017d6835467b425590f24be86832c"},{"author":{"_account_id":1002315,"name":"liangzhen","email":"zhen.liang@spacemit.com","username":"liangzhen"},"change_message_id":"a40171524c68b4c1d745f85e313f8bffb0ae8738","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c1dfb27d_36156d20","in_reply_to":"fc39344a_0ce75259","updated":"2026-06-17 06:26:28.000000000","message":"Done","commit_id":"34731a56ddd017d6835467b425590f24be86832c"},{"author":{"_account_id":1002047,"name":"Evgeniy Naydanov","email":"eugnay@gmail.com","username":"en-sc"},"change_message_id":"27ef8dc3d3e4f2435add0a6b2fdad6bae7870694","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"ef0e3471_4b29444d","updated":"2026-06-17 11:21:32.000000000","message":"Thanks for the patch!\n\nTBH, I don\u0027t think this is a good solution.\nThe issue is -- `check_dbgbase_exists()` can fail (issuing an error message). This error used to propagate and exit the examination procedure. Now it gets downgraded to a warning.\n\nMoreover, I sink the option to skip the DM address validation is valuable on slow targets (e.g. simulation).\n\nAlso, I\u0027ve posted my overall ideas on the matter in the [GH issue](https://github.com/riscv-collab/riscv-openocd/issues/1147#issuecomment-4729345510). Please, take a look.","commit_id":"43ef19f382ac71c985a269e89a0c22270631b623"}]}