Dear Forum Members,
I am writing to seek your assistance regarding an issue I have encountered while developing a program for the ARMCM52 microcontroller using Keil MDK 5.40.
After setting the chip selection to ARMCM52 in my project, I have observed that the F12 functionality, which is used for "Go To Definition of 'XXX'", is not working properly. Keil MDK is displaying the error message "Module error! text completion deactivated."
However, when I switch the project to use the ARMCM55 microcontroller, the F12 functionality for "Go To Definition of 'XXX'" works as expected.
I am using the AC6.22 compiler for this project. Based on my investigation, I believe this issue may be related to either the compiler or the MDK, as the problem seems to be specific to the ARMCM52 chip selection.
I have attached two screenshots to illustrate the issue. The first screenshot shows the F12 functionality for "Go To Definition of 'XXX'" working correctly when the project is set to use the ARMCM55 microcontroller. The second screenshot shows the error message that appears when the project is set to use the ARMCM52 microcontroller.
ARMCM55:
ARMCM52:
I would greatly appreciate if anyone in the forum could provide any insights or suggestions on how to resolve this problem. Your assistance would be invaluable in helping me progress with my project development.
Thank you in advance for your time and support.
Hi kaili,
I had a similar problem, for me the go to definition feature and also the auto complete feature was not working. I also got the error on the bottom left corner (Module error! text completion deactivated).
For me reinstalling µivison in the new default path (localAppdata) and re-download every DFP, compiler version and package that I needed (CMSIS etc.) solved the issue.
Maybe this will help. But I had the problem with the ARM Compiler Version 6, as soon as I switched to version 5, the go to definition feature was working. Sothe behavior is not exactly the same as yours.
This problem only occurred after I switched the selected core type. I tested it on different computers and found that this problem only occurred after using the ARMCM52 core.
Thanks for reporting your observation and the discussion.
I have replicated this result with a simple test project and the ARMCM52 selected.
This now is reported to our Engineering Team. I'll keep this post updated...
It is reassuring to know that the issue has been acknowledged and is now being addressed by your team. I look forward to any updates you may have as the investigation progresses.
Once again, thank you for your time and support. I am grateful for your assistance in helping me resolve this challenge.