You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior, Steps to reproduce and Expected behavior
If I break a PDSC file in my installation, then the RTE model generates an error as one would expect. However, if I load a workspace with an unrelated solution, i.e. the pack isn't needed for that, then loading the solution also shows this error, and the debug button is grayed out.
Reproducer
Break a pack in your installation, e.g. remove a closing tag somewhere in the PDSC file (in my case </sequences>).
Load a solution that doesn't require this pack.
Low priority as this should not happen in reality (feel free to reject). But fixing might help overall robustness.
@brondani, I guess this is related to csolution loading installed packs rather than exclusively the list of packs selected by the current loaded CMSIS Solution. Can we continue processing the faulty installed packs and report the pack as failed to load if the information is explicitly requested?
It's feasible, but it requires some changes. A failure could be ignored when the pack is not explicitly required by the active solution. In other cases it must be distinguished from a missing-pack scenario, otherwise it could incorrectly trigger another mechanism.
The ground change needed is in RteKernel::LoadAndInsertPacks which currently returns immediately when loading a pack fails.
Activity
jkrech commentedon Oct 6, 2026
@brondani, I guess this is related to
csolutionloading installed packs rather than exclusively the list of packs selected by the current loaded CMSIS Solution. Can we continue processing the faulty installed packs and report the pack as failed to load if the information is explicitly requested?brondani commentedon Oct 6, 2026
It's feasible, but it requires some changes. A failure could be ignored when the pack is not explicitly required by the active solution. In other cases it must be distinguished from a missing-pack scenario, otherwise it could incorrectly trigger another mechanism.
The ground change needed is in
RteKernel::LoadAndInsertPackswhich currently returns immediately when loading a pack fails.