Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[csolution] Add system-resources, debug-vars, and debug-sequences to *.cbuild-run.yml for run and debug management #1953

Open
ReinhardKeil opened this issue Feb 7, 2025 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@ReinhardKeil
Copy link
Collaborator

To complete the *.cbuild-run.yml information for pyOCD implement system-resources, debug-vars, and debug-sequences as documented in
https://github.com/ReinhardKeil/cmsis-toolbox/blob/main/docs/Experimental-Features.md#run-and-debug-management

@ReinhardKeil ReinhardKeil added the enhancement New feature or request label Feb 7, 2025
@jkrech jkrech moved this to Todo in CMSIS-Toolbox 2.8.0 Feb 10, 2025
@jkrech jkrech changed the title Implement system-resources, debug-vars, and debug-sequences [csolution] Add system-resources, debug-vars, and debug-sequences to *.cbuild-run.yml for run and debug management Feb 11, 2025
@brondani brondani moved this from Todo to In Progress in CMSIS-Toolbox 2.8.0 Feb 11, 2025
@brondani
Copy link
Collaborator

brondani commented Feb 11, 2025

  1. From https://github.com/ReinhardKeil/cmsis-toolbox/blob/main/docs/Experimental-Features.md#debug-vars:

Additional node vars: is kept to allow for future extensions.

Thinking on future extensions, should debug-vars be an array like this?

debug-vars:
  - vars:
  1. From https://github.com/ReinhardKeil/cmsis-toolbox/blob/main/docs/Experimental-Features.md#system-resources:

It includes memory from the DFP, BSP, and memory: definitions from the csolution.yml file.

The memory definitions from the csolution.yml file as specified here also contains algorithm and it is already listed in cbuild-run under programming algorithm, isn't it inconsistent?

  1. In addition the description and example of system-resources are not aligned. Should it be an array or not?
system-resources:
  - memory:
     - name:

or

system-resources:
  memory:
   - name:

or rather

system-resources:
   - memory: # name
  1. From https://github.com/ReinhardKeil/cmsis-toolbox/blob/main/docs/Experimental-Features.md#debug-vars

Note pname is not required as variables are queried by debug-sequences:. It is enough when these sequences are pname-specific

Actually nothing prevents the use of generic sequences with processor specific debug-vars. Since this is allowed in PDSCs I believe it should be reflected here.

@ReinhardKeil
Copy link
Collaborator Author

@brondani - Here are my answers:

  1. I used your proposal (even when there is currently only one - vars:
  2. Yes this is inconsistent, but it starts in the DFP/BSP where memory and algorithm are disconnected. I believe we should define for external memory an algorithm in the same field.
  3. memory: is now corrected.
  4. In practice debug-vars is not used with pname:. Only an iMX7 has used this feature and a close look shows that this is not required. Recommend to deprecate pname in debug-vars as otherwise the config file management would become even more complicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants