********************************************************************************
* Detailed Description:
* A simple example configures eTPU engine B channels 0/1 for GPO/GPI. It is
* needed to connect these pins by wire. Output wave is generated by eTPU GPIO
* output function and inputs are read by fs_etpu_gpio_input_immed function
* latching just current pin state. Pin history is displayed in ISR.
*
* Note: It is needed to configure IGF module, otherwise inputs does not pass
* to eTPU module.
*
* ------------------------------------------------------------------------------
* Test HW: MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C
* MCU: PPC5777CMM03 2N45H CTZZS1521A
* Fsys: PLL1 = core_clk = 264MHz, PLL0 = 192MHz
* Debugger: Lauterbach Trace32
* Target: internal_FLASH
* Terminal: 19200-8-no parity-1 stop bit-no flow control on eSCI_A
* EVB connection: ETPUB0 (PortR P25-1) --> ETPUB1 (PortR P25-0) by wire
*
********************************************************************************
Hello David,
As I know, the input of ETPU channel can be connected from the SDADC valid data flag output or the external pad, we use the SIU_SDETPUA, SIU_SDETPUB, SIU_SDETPUC to choose the connection .You can see the below image:
- I use ETPUA channel 9:
+ In the case 1, ETPUA_9 is connected to the external pad, the pinstate returned by fs_etpu_gpio_pin_history is correct as expected.
+ In the case 2, ETPUA_9 is connected to the SDADC1 data valid flag output, the pinstate returned by fs_etpu_gpio_pin_history always be 0 even though the SDADC1 Conversion Data Valid Event is enabled(CDVEE bit of SDADC_RSER is 1) and Converted Data Valid Flag is 1(CDVF bit of SDADC_SFR is 1). This is wrong. I don't know why.
- The difference between these 2 cases is just SIU_SDETPUA configuraion.
Do you know why?
Regards,
Tam
Sorry, the ETPU channel is ETPUA_15
I tried with 2 cases:
- The ETPUA_15 channel with SDADC2
- The ETPUA_9 channel with SDADC1.
The pinstate always be 0.
Hi, please create new thread here on the community space or new case according to following procedure:
https://community.nxp.com/docs/DOC-329745