We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
http://www.keil.com/update/relnotes/uv4.htm
In the release notes for uVision 4.60, at the bottom, there is a blurb:
" The Keil RT-Agent is deprecated in this release. The MDK-ARM component RT-Agent component in folder ..\ARM\RT Agent\ is no longer actively maintained. The component is shipped "as is" an no updates or bug fixes will be provided. All files in this folder and subfolders are included for compatibility in this release but will be removed from the product in future releases. "
I am not sure I understand the implications. With future releases, are the debug->OS support-> trace options going away? With future releases, is the serial redirect to a console going away?
Is there some new functionality that supersedes RT Agent and we should be migrating too? I know RT Agent is a pain to get working, but when it works it is very nice. It seems like a step backwards to pull it out of the tool, unless there is something better and easier for Keil to support.
-Steve
The RT Agent is only relevant on ARM9, the Cortex has the ITM for semi-hosting etc.
In my experience the RT Agent was flakey and Keil haven't fixed any of the problems that I reported months ago. I think it was written by a 3rd party.
In summary if you wish to use semi-hosting on the ARM9 with MDK-ARM V4.60 or later then don't expect RT Agent to work, it might if you're lucky.
I am disappointed by Keil's decision.
I got RT Agent working on NXP LPC23xx series devices. These are ARM7. It worked very well about 2 years ago, but with the later releases parts began flying off the spokes. The event viewer (task switching) pane does not work with 4.53 and newer unless you turn off the "one ELF section per function" feature in the C compiler tab for your project. The compiler tosses the RTAgent sections as part of optimization!
The event switching and task monitoring is really helpful. Likewise the live update of your watch variables while the program is running. Brian at Keil indicates that with the Cortex M series processors, the RT Agent is not needed. I will be validating this on a new design and I will update this thread. I still hope to convince them not to kill the RTAgent from a functional perspective, as I have about 8 designs with RT Agent embedded that are still in production. I don't want to have to hold onto an old version of the tool just to use RTAgent.
I can confirm that RT Agent is not needed for Cortex M. You can do everything RT Agent did and more. Even better if you use ULINK Pro instead of ULink2.
It would be encouraging to see the bad decisions such as this be reconsidered and their products to be actually well tested prior to release.
RT agent has been working great on the ARM7 (str731) for watch purposes except when the ULINK2 firmware update broke it for a few weeks about a year ago.
I recently sent in a letter detailing the simulation speed degrading with each MDK release and the continuous introduction of new problems with each MDK release.
I got a couple of replies, one indicating to download the new 4.60 and see if it would fix anything: Compiler -> "internal fault" please contact vendor.
I have been told than a nasty sim script compile bug will be fixed in MDK 5.00 - whenever that will come out.
One really should not have to file support tickets with each new release but that is the norm for the last year or two.