2024-07-29 09:36 AM - edited 2024-07-29 01:22 PM
Edit: I have resolved this by restarting cube. I think the filters were blocking before because the default filters hid some configurations. This time (after reset) when I removed filters, the launch configurations appeared.
Edit 2: Fully solved. When I opened the workspace, cubeIDE renamed all of the projects to be lowercase. The .elf's it was looking for therefore did not exist. I'm not sure why cubeIDE re-named the projects, this causes issues in a few places.
After upgrading STM32CubeIDE from version 1.15 to version 1.16.0, the launch configurations for my project are no longer visible in the Run Configurations dialog. Although the configurations appear in the Project Explorer, attempting to run them results in an internal error.
Steps to Reproduce:
Expected Result: The launch configurations should be visible in the Run Configurations dialog, and running the configuration should execute without errors.
Actual Result:
Error Message:
An internal error occurred during: "Launching <my config name>".
Cannot invoke "org.eclipse.cdt.core.model.ICProject.getProject()" because the return value of "org.eclipse.cdt.debug.core.CDebugUtils.getCProject(org.eclipse.debug.core.ILaunchConfiguration)" is null
Environment:
Additional Information:
Solved! Go to Solution.
2024-07-29 01:23 PM
See edits: This issue was caused by cube re-naming all of my projects when I opened the workspace in cube 1.16. It changed the names from being tile case to all lowercase (from Example to example).
2024-07-29 09:45 AM
Note: even though restarting cube made the configurations visible, I get the same error when trying to use the run configurations.
2024-07-29 01:23 PM
See edits: This issue was caused by cube re-naming all of my projects when I opened the workspace in cube 1.16. It changed the names from being tile case to all lowercase (from Example to example).