Hi Shailendra,
You can do this. In the case of a result completion, this is probably done by via a source event or a result event. But in the case of a boundary condition, you need to use a channel event. These are the 3 types of events available ISR flags in our ADC. To set this up, you need to set up a boundary condition. There are 2 global boundaries (GLOBBOUND) available, and 2 group boundaries for each group (GxBOUND) available. Configure your digital result boundary in one of these registers. Next, you need to locate the specific CHCTR register that is tied to the physical channel. You need to tell the channel which boundary conditions, from previous, to look at for upper (BNDSELU) and lower (BNDSELL) boundaries. Select upper and/or lower boundaries. Then, all ADC service requests are a two step setup. You need to enable the event first. CHCTR.CHEVMODE will enable the flag, and it is configurable as an option to your boundary condition. Now you have the boundaries and the flag, but we need to choose a generic service request to target a core service. In the CEVNP0 register, for the specific channel (all channels have 4 bit field) and specific group, you can then tie a specific service request to this boundary event. There are 4 group specific request lines, and 4 general request lines. Once you tie the channel event to a specific service request node, this now maps to a specific SRC_VADC... (register) node where you can configure the type of service (TOS), Priority (SRPN Vector entry), and enable the interrupt(SRE).
