Make DM support CPU with bus width different from core data width#83
Make DM support CPU with bus width different from core data width#83JeanRochCoulon wants to merge 1 commit intopulp-platform:masterfrom
Conversation
CPU with buswidth different from core data width
|
Sorry it is a PR relative to Tag v0.1 and not master ! |
|
Unfortunately, I am still skeptical about the solution here. The debug module should, ideally, support all variations of |
|
Thank you to challenge the PR, it is good for code quality !! To my mind, we are facing to 3 different variables: CORE DATA width, CORE BUS width and DTM width CORE DATA width | CORE BUS width| DTM width
If I remove the trivial and non-applicable cases, it remains 4 cases del cazzo (ask Davide for the italian translation!) In the current DTM github version, DTM looks at DTM width (buswidth variable) to determine the ISA variant (32 or 64 bits). In that case, 5) 6) and 7) are FAILED. This solution is not acceptable for CV32A6. In the PR, DTM looks at CORE DATA width, only 6) is FAILED. I think that 6) corresponds to the case you spoke about. On my side, I have never seen such a case. Would it be acceptable according to you to follow the constraint: COREBUS width always equal to DTM width ? If yes, 5), 7) and 8) would be non-applicable. Kind Regards |
|
Hello, I am trying to use this excellent module in a 64b core, 32b bus SoC. Is there any update in 2024 for if this the correct solution? :) |
|
I was never able to test this configuration so I don't know. |
|
Today the cva6 core can be configured in 32 or 64 bits, while DM works only in 64bits. It seems to work also if I do not stress to much the DM in my product configuration. |
Hi @zarubaf
This PR is relative to the issue #541 of openHWgroup/CVA6
Cheers
Jean-Roch