In XMC1200 and XMC1300, the ADC provide the limit checking feature on the conversion result.
The limit checking mechanism automatically compare the conversion result to the user configurable value.
User can set the upper limit and the lower limit of the boundary.
An event or interrupt can be generate (if enabled) if the conversion result is fall inside or outside the user defined boundary.
If this limit checking features, CPU no longer requires to read every converted result which may not be really useful.
Therefore, is can minimize the CPU load and service the requests only when the result is useful.
The boundary limit value can be set at group-specific boundary register GxBOUND (x = 0 - 1) or from the global boundary register GLOBBOUND
The limit checking mechanism automatically compare the conversion result to the user configurable value.
User can set the upper limit and the lower limit of the boundary.
An event or interrupt can be generate (if enabled) if the conversion result is fall inside or outside the user defined boundary.
If this limit checking features, CPU no longer requires to read every converted result which may not be really useful.
Therefore, is can minimize the CPU load and service the requests only when the result is useful.
The boundary limit value can be set at group-specific boundary register GxBOUND (x = 0 - 1) or from the global boundary register GLOBBOUND
0 Replies