Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Pin 44 of the Samtec expansion connector for the P-port is p_gpio and used as the default synchronous clock for the GPIF II interface. I was able to measure and confirm this output while modifying the "SlaveFifoAsync" example (adjusted to a 100 MHz output) with the following part of code:
I am now working on GPIO manipulation and have been using the "GpioApp" example as a starting point. However I am not able to get the PCLK to output the same signal I was getting before... it isn't outputting anything at all. I noticed that the "GpioApp" example uses a "gpioClock" and calls the "CyU3PGpioInit" API. Are these configurations somehow interfering with eachother?