GTM Problems View

The GTM problems manager is responsible to highlight cases in which constraints have not been respected. Typically, these cases occur upon a change in a text field. One such case is when an invalid value is set for one of the CMU dividers. An Input value is invalid! error would occur if a negative value is set for one of the dividers and the code generation would not be triggered.


Figure 1. CMU Error


Figure 2. GTM Problems View

Another example of problem occurrence is when an out of bounds value is set. Therefore, an input larger than the known threshold would trigger a Value out of range error.


Figure 3. CMU Out of range error


Figure 4. GTM Problems View

Another problem which will occur is when ATOM or TOM channels are enabled but there is no clock source enabled in CMU, so the user is informed that a clock source is required, using a specific error for both modules: it should be enabled at least one clock source (0 to 7) from CMU for ATOM and clock source fx from CMU for TOM.


Figure 5. ATOM clock source error


Figure 6. GTM Problems View


Figure 7. TOM clock source error


Figure 8. GTM Problems View