)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1002366,"name":"Liam Fletcher","display_name":"Li-Fletch","email":"liam.fletcher@microchip.com","username":"Li-Fletch","status":"Microchip"},"change_message_id":"e8b01733d1c4e183423a32f71911d092db5ffc03","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"abbcd81f_ba7bc97d","updated":"2025-03-25 11:41:21.000000000","message":"Thank you, I will try it out","commit_id":"36932d0bfe2948645a50aead0ca9b69371a42b88"},{"author":{"_account_id":1002047,"name":"Evgeniy Naydanov","email":"eugnay@gmail.com","username":"en-sc"},"change_message_id":"9fc3a7fb24c54687786d693769a5f3b8c84772b1","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a65bcf65_9280afdc","updated":"2025-03-25 07:04:46.000000000","message":"There is a standard machanism for allowing multiple DMs on a single DMI bus. It is described in [3.1. Debug Module Interface (DMI)] of the spec [1].\n\u003e The DMI uses between 7 and 32 address bits. Each address points at a single 32-bit register that can be read or written. The bottom of the address space is used for the first (and usually only) DM. Extra space can be used for custom debug devices, other cores, additional DMs, etc. If there are additional DMs on this DMI, the base address of the next DM in the DMI address space is given in nextdm.\n\nPlease, consider reusing the standard mechanism in your HW.\n\nIf it\u0027s not possible, consider adapting the support for multiple DMs on a single DMI bus from the RISC-V fork [2]. We can introduce a configuration parameter that will disable the check of `nextdm`.\n\n[1] https://github.com/riscv/riscv-debug-spec/releases/download/1.0/riscv-debug-specification.pdf\n[2] https://github.com/riscv-collab/riscv-openocd/pull/875","commit_id":"36932d0bfe2948645a50aead0ca9b69371a42b88"},{"author":{"_account_id":1002047,"name":"Evgeniy Naydanov","email":"eugnay@gmail.com","username":"en-sc"},"change_message_id":"0f8b14e259bf7b3f0d6f0daf6cf463d10132db5e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ab1c9b4c_ef0aa475","in_reply_to":"84684c2f_fa385927","updated":"2025-05-07 11:05:31.000000000","message":"\u003e ... do I \"abandon the changes\" for this change?\n\nAFAIK, if you are satisfied with the alternative, this is the proper procedure.\n\nE.g.: https://review.openocd.org/c/openocd/+/8812/1#message-91b16829c0840a33e18029c8a3bc70325467c1ec","commit_id":"36932d0bfe2948645a50aead0ca9b69371a42b88"},{"author":{"_account_id":1002366,"name":"Liam Fletcher","display_name":"Li-Fletch","email":"liam.fletcher@microchip.com","username":"Li-Fletch","status":"Microchip"},"change_message_id":"c64e6e6a7a2dc8930c65fd7eeec67455f576b5b8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"84684c2f_fa385927","in_reply_to":"a65bcf65_9280afdc","updated":"2025-05-06 11:37:17.000000000","message":"Thank you for the guidance, very much appreciated. I have submitted a commit/change based on your advice:\nhttps://review.openocd.org/c/openocd/+/8872.\n\nAlso, my apologies I am fairly new to this, I am not familiar with the etiquette, do I \"abandon the changes\" for this change?","commit_id":"36932d0bfe2948645a50aead0ca9b69371a42b88"}]}