Skip to content

[Bug]: PERIPHERAL View shows "No data available" instead of busy #262

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.

Sign up for GitHub

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

Jump to bottom
Open
ReinhardKeil opened this issue May 19, 2025 · 1 comment
Open

[Bug]: PERIPHERAL View shows "No data available" instead of busy #262

ReinhardKeil opened this issue May 19, 2025 · 1 comment
Assignees
@thorstendb-ARM
Labels
CDT.cloud View Extensions Change is required in Eclipse CDT.cloud View Extensions, e.g. Peripheral/Memory Inspector

Comments

@ReinhardKeil
Copy link
Collaborator

Description

The RUN AND DEBUG: PERIPHERAL VIEW shows when you open it "No data available" while it is loading the data.

Image

Instead it should give a busy indicator.

Steps to Reproduce

  1. Use a complex device example, i.e. Alif DualCore and start debug
  2. Open PERIPHERAL VIEW

Expected Behavior

Show Busy instead of No Data Available

Additional Information

No response
@ReinhardKeil ReinhardKeil moved this to Backlog in CMSIS Debugger May 19, 2025
@jreineckearm
Copy link
Collaborator

Created eclipse-cdt-cloud/vscode-peripheral-inspector#65 against Peripheral Inspector.
Can vaguely remember we had something before. But it didn't behave well. Rather a warning that it may not be as much of a low-hanging fruit as it sounds.

@jreineckearm jreineckearm added the CDT.cloud View Extensions Change is required in Eclipse CDT.cloud View Extensions, e.g. Peripheral/Memory Inspector label May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thorstendb-ARM thorstendb-ARM

Labels
CDT.cloud View Extensions Change is required in Eclipse CDT.cloud View Extensions, e.g. Peripheral/Memory Inspector
Projects
CMSIS Debugger
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ReinhardKeil @thorstendb-ARM @jreineckearm