TMS320F28034: IEC60730 question

Hi Emma,

Here are my responses to the questions in the document:

1. You can either determine it experimentally or you can calculate a delay count by looking at what the maximum amount of time it could take for the watchdog to time out. Note that the STL_UTILITY_delay function describes the parameter as: “The number of cycles it takes this function to reach zero when no interrupts are occurring is y = 14x + 32.519, where x is the delay value and y is the cycle delay.”

2. This function configures hardware watchpoints to monitor the stack so that if the stack grows beyond a certain threshold, an interrupt can be generated to alert the application that the end of the stack is being approached and it’s at risk of overflowing. There is an app note that explains use of these watchpoints to monitor the stack: https://www.ti.com/lit/spra820

3. There is a section in the library User Manual document that describes which sections are needed in order to run each test. See the section “External Dependencies” and “4. Linker file” in the list of dependencies.

4. .cdecls functions similarly to a #include. It allows projects that are a mix of assembly and C/C++ share declarations. There’s more info in the Assembly Language Tools guide: https://www.ti.com/lit/pdf/SPRU513. Those _PSA_CRC* symbols are defined by the linker. See the corresponding section in the .cmd file in the screen shot in question #3.

Whitney