Hello,
At the moment I am designing our own pcb, that will use the Verdin AM62. Now I am wondering if I could use an alternate function on the I2S_1_MCLK pin of the Verdin AM62. According to the AM62 datasheet this pin should have alternate functions and thuss could be used as GPIO. When using your pinout designer, pin 38 isn’t showing up as gpio pin. So I was wondering could I know use this pin or can’t I use this pin as a gpio? Note that I will be using this I2S interface, just not the MCLK pin and the Din pin.
Hope to hear from you soon!
Kind regards,
Teun
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello!
Thank you for your question regarding the alternate functions of the I2S_1_MCLK pin (pin 38) on the Verdin AM62. While I don’t have direct information on this specific pin, I can guide you on how to find this information.
To determine the available functions for a specific pin on the Verdin AM62, you should refer to the AM62 datasheet. This document contains an alternate functions table that lists the possible configurations for each pin based on the SoC ball ID and name.
For configuring pins on the AM62, follow these steps:
-
Identify the Correct GPIO Controller: Determine whether the pin is associated with MCU_GPIO0, GPIO0, or GPIO1.
-
Configure the Pin: Use the appropriate PADCONFIG address to set up the pin.
-
Device Tree Configuration: Implement the correct configuration function, such as AM62X_MCU_IOPAD or AM62X_IOPAD, within the device tree.
If you need further details, I recommend reviewing the complete Verdin AM62 datasheet, which will provide comprehensive information on pin configurations.
Please let me know if you would like more guidance on configuring alternate pin functions on the Verdin AM62.
Best regards,
Toradex AI Assistant
That are great suggestions but I would be more confident if I know the circuit of the verdin am62 module or if this would be confirmed by toradex it self instead of AI.
Yes, Verdin AM62 pin 38 is directly connected to the SoC ball GPMC0_WPn, which can be configured with the alternate function GPIO0_39. Initially, we planned to use the GPMC0_WPn ball to enable the internal 24.576 MHz oscillator on the SoM to provide the I2S_1_MCLK signal. This would have made all alternate functions of the GPMC0_WPn ball unavailable. However, the SoM design was later changed, but the corresponding documentation (such as the module datasheet and Pinout Designer tool) was not updated to reflect this change.
Thanks for your reply this helped me a lot.
