It would be GREAT if the debugger could show the internal timing based on the settings of the processor. Every time we set up a new processor we are forever trying to calculate baud rates, timers rates, input capture compare rates, overflow times etc Why doesnt it just show all this in the debugger
Internal Clock =
Timer X singe clock time =
Baud rate =
ADC Conversion time =
Input/Output Capture singe clock time =
et
All the things the debugger can easily tell you...
If you could set an external xtal setting using some #pragma this would allow the debugger to tell you the same info when the external xtal is setup.
We have been moving a heap of designs from 05 to S08 and there are so many variation and changes its always a 'task' that should really be done for you...
I think beans look after this, but we just use straight c or assembly.
Solved! Go to Solution.
Hello
Well the debugger has no awareness of the way the different devices are working.
So it does not know timing information derived from your current device initialization.
Processor Expert or Device Initialization (if you are using CodeWarrior for MCU) has the knowledge of the internal for all the devices and can calculate the various timing information.
You can submit a Change Request Service Request through our on-line support web site to report you would be interested in such an extension in the debugger.
But keep in mind this is a brand new functionality and a big extension in the debugger. This cannot be implemented quickly.
CrasyCat
Hello
Well the debugger has no awareness of the way the different devices are working.
So it does not know timing information derived from your current device initialization.
Processor Expert or Device Initialization (if you are using CodeWarrior for MCU) has the knowledge of the internal for all the devices and can calculate the various timing information.
You can submit a Change Request Service Request through our on-line support web site to report you would be interested in such an extension in the debugger.
But keep in mind this is a brand new functionality and a big extension in the debugger. This cannot be implemented quickly.
CrasyCat