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.
Hello there, I was just wondering if anyone knows how to use the debugging stuff built into the rtx166 full OS ? I'm using the serial port, so the 'status monitor task' seems like a dead idea, and I have no idea how to use the Debug API, because the description in the manual couldn't be any worse! (not even a single example) So anyone out there, have some sample code where you use the Debug API, or maybe some hints? And why doesn't the rtx166 full suppport the same 'kernel aware debugging' as the rtx166 tiny does? (I've got the rtx full.dll) Regards Christian.
Welcome to the club. Keil promised kernal awareness on their evaluation CD when we decided to use RTX full (1999). When downloading to the target, UV always has given an error of 'RTX-FULL.DLL not found' and I was always told by support that it would be available soon. When RTX-FULL.DLL was finally available, we were told we would have to pay for the 'upgrade'. If we treated our customers this way ... So how about Keil fulfilling it's sales promises? Best luck
Bugger... have you ever used the debugging support built into RTX166 Full? The manual mentions the HOOKS build of the OS, but it doesn't say anything about how you link it to your own program, or how you might use the functions... ?