This resulted in a whitepaper "debugging embedded systems" (http://www.clarinox.com/index.php?id=59).
I am hoping to get some comments from the embedded systems community with permission to publish these on the link (http://www.clarinox.com/index.php?id=4).
So far I have had comments from US, UK and Europe and hope to add some interesting comments from the embedded systems community in Australia.
So far I have had comments from US, UK and Europe and hope to add some interesting comments from the embedded systems community in Australia.
Posts
1 comment:
Hi Trish. I think the quality of the tools can make a difference here.
From my experience with LabVIEW RT projects on the cRIO and cFP platforms, the following things helped get my applications going:
1) System manager - I used this handy tool to monitor memory usage, CPU usage, and VI status during the execution of RT applications.
2) Profile Performance and Memory - Allowed me to get detailed measurements on the timing and memory statistics of VI's in an application.
3) Ability to run in a simulated environment - Quite often software can be simulated on the desktop, to nail a lot of errors before taking the software to the embedded environment.
6) Built-in debugging functionality - Build in debugging code that can be enabled at the pre-processor stage, to assist in event and timing logging etc
Add to this tools I haven't had the opportunity to try yet, such as the RT and Desktop Execution Trace Toolkits.
Post a Comment