Trying to get inspired and actually get somewhere with RTDX

It must be at least 2 weeks now that I have been bogged down with this RTDX trouble. If I do not get things happening soon, the end of june deadlines will start to be difficult.

I think that I have to be pretty hard headed and work my way through all the tutorial rather than trying to use a little bit of info in the hope that it will be a shortcut.

I will try to only discuss what I learn from the RTDX debugging tutorial here.

Here is a listing of the files that I am using, the tutorial explanation of them and my interpretation of that:

volume.cdb. This is the configuration file for the project.

I think that this will be the main file that I need to get correct. It has the potential to get the memory mapping set up as well. When it is saved, it creates many other files where I think that my problem lies.

volumecfg.cmd. This linker command file is created when you save the configuration file.

I really don't understand much abou this.

volumecfg.h. This header file is created when you save the configuration file. It includes DSP/BIOS module header files and declares external variables for objects created in the configuration file.

nor this

volumecfg.s28. This assembly file is created when you save the configuration file and contains DSP/BIOS configuration settings.

volumecfg.h28. This header file is created when you save the configuration file and is included by volumecfg.s28.

volumecfg_c.c. This file is created when you save the configuration file. It contains code for Chip Support Library (CSL) structures and settings.

Hopefully I can come back and explain what each of these does a bit better in the future


On page 4, I am back to the problem that I had when I gave up before. They have an excectution graph that has exactly 10 KNL_swi for each processing_SWI.



mine, however is not nearly as nice with the processing_SWI going off all over the place:



I think that hopefully this problem will not affect what I am trying to do. I will continue but keep in mind that this may be the cause of future problems.

I had another thought that this problem may be caused by the ezdsp being connected to the motor interface board. I disconnected it and got the following fom the execution graph:



that is a little more like what I should get.


I should ask Nic what on the board could be affecting it in that way.

I now have a problem that the execution graph is not updating. It sort of works if I start and stop the CPU, however it used to update automatically.

I got the automatic update happening by reopening ccs and reloading the project. However the execution graph still has problems:

in this example, there are too many processing_SWI calls:



in this example, there are too few processing_SWI calls:




I tried "syncronise sliders" in the property page part of the RTA control panel. That did not seem to help.