Does it say RTX5 component itself is missing?
The problem is that the RTOS viewer in the IDE can't get a sensible answer from the RTOS running on the device.
I've encountered this a few times in the past. I think the issue was related to the RTOS failing due to errors in the code. Is the code running as expected when you see this? If you stop the device during debug, where do you stop, and what do you see in the call stack window? (Meaning: do you see what you expect to see?)
If you see a little blue question mark or yellow alert badge on a file icon in the project view, those files need to be updated to match the pack. Right click on the file to open the context menu for the file, which should have an update option. This copies the new version of the file into your project. So if those files were customized (i.e., had user-specific settings), you'll have to re-enter those.
Yes, there were some alert badges in the network components, which I have updated now. The message is gone! There is still on blue question mark over the RTX_Config.h though. This one I cannot update. Is maybe something wrong with the settings?
To be honest, the code is not running as expected at all. I am working on someone else's code and when I directly flash this old code it works. But when I recompile the code it breaks the core functionality. My actual task is to enhance this code, but I am struggling to get back to this working state, which keeps me from progressing.
Great! Per the help (in the File, Group, and Component Attribute Icons section), a blue badge means the changes are related to modified default values and comments, but there are no new settings. You should be able to copy the new version in, unless the file is write-protected.
I don't want to get off-topic here. Hopefully you have the original source (including project files) as well as the working binary image and a good diff tool.
I had this same issue. It was resolved by deleting the <project name>.uvoptx file in the top-level of the project directory. Then, reconfiguring my target options and selecting the desired debugger.
Hope this helps someone else in the future.