Hi Nathan, This is just routing the signal to PRU's Interrupt Controller. [quote userid="581457" url="~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1496514/am263p4-can-xbar-be-used-to-map-adc0_evt1-to-pru_0-interrupt/5761964#5761964"]Register the interrupt in code(You can refer the same adc_soc_rti example for this)[/quote] You don't need to register this interrupt in R5, and you should still be able to get correct results. [quote userid="619313" url="~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1496514/am263p4-can-xbar-be-used-to-map-adc0_evt1-to-pru_0-interrupt/5763188#5763188"]The simple goal for this functionality is to have the PRU handle all functionality associated with the ADC end of conversion. The R5 core can do the setup and initialization of any XBAR or ICSS instances needed, but the implementation should not require intervention of the R5 when the ADC end of conversion occurs. I had hoped that the XBAR could help accomplish this.[/quote] This is exactly what is happening in this scenario. Let me know if you need more information on this! Regards, Akshit
↧