Download Server/Loader User Manual

Code Composer Studio run). The bootloader routines will now execute towards completing
the routine and the breakpoints we set earlier will be hit. The breakpoint hits are handled by
the OnHitBreakpoint routine. The routine does nothing, it simply waits until all
processors have hit their respective breakpoints.
Finally, the StartDebugging() routine is called. This simple does 2 single steps, which
steps us out of the bootloader routine to the very first C code line after bootloader().
Now close the connection to Code Composer Studio by issuing a call to
CoUninitialize(). The system is now ready for debugging.
Legacy: Class Ccif Interface: parameters
The ccif class is now a legacy interface and will be obsoleted in future. Please use the ‘hesl’
class as described in earlier sections in this Chapter for new projects. The ccif class will
remain supported for some time to support existing applications.
There are no parameters for the ccif class.
Example supporting the ‘-g’ option
The essence of supporting the ‘-g’ option within your own Microsoft Visual C/C++
application is in the following code snippet.
if (net.GetDebugSwitch()) // if user requested to use ‘-g’
{
// Find out the path to the network file. We will
// use spath to set Code Composer's search directory.
if (description_filename[1] == ':')
{
strcpy (spath, description_filename);
Mutilate(spath);
}
else
{
GetCurrentDirectory(256, spath);
}
// Start up Code composer,
if (!cc.StartCodeComposer(spath)) return 0;
// and do a RunFree,
if (cc.RunFree() > 0) return 0;
// We need to give CC some time here to release
// the processors. It's a bit unclear how much time
// is sufficient; and per machine it will differ.
// How to solve this properly?
Sleep(net.GetFactor() * 1000);
if (r == 0) r = net.open ();
if (r == 0) r = net.reset ();
Sleep(100);
// Open all the boards;
// Reset all the boards.
cc.MatchHeronId2CCid(&net);
Sleep(100);
//match CCid with HeronId
52
HUNT ENGINEERING Server/Loader USER MANUAL