SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
General-purpose inputs are connected to the device GPIO pin mux through an input buffer with an option to directly connect the asynchronous input flowing directly into the ECS or through a ESCSS register pipeline, which can hold the value stable while the value is captured within the ESC. The state of the GPI can be captured based on the following events:
The ESCSS_GPIN_DAT register, containing the contents of the GPIN data, is available for reading from host CPU to allow debug access. Additionally, ESCSS_GPIN_DAT allows CPU writes for being used GPIN override purposes such as in place of using GPIOs.
GPIs are divided into 4 sets: GPI0:7, GPI8:15, GPI16:23, and GPI24:31, for clocking the capture trigger, which means the same capture trigger has to be used for the IOs within a set. Thus, either a bus can be formed out of these or individual IOs which need to be aggregated under common trigger can be combined in one set. This allows limited freedom of trigger selection for inputs. Selection of which Inputs (ESCSS_GPIN_SEL) and outputs (ESCSS_GPOUT_SEL) can be connected to GPIO is possible at each single IO level.
Figure 31-11 shows the integration of the GPI feature.