Pinout Designer Issue - iMX8_WB and 2x Gigabit Ethernet

Technical Support
1

Dear Toradex Team,

I am writing to report an issue encountered while using the Pinout Designer tool to generate a pinout for the iMX8_WB (Apalis iMX8 QuadMax 8GB Wi-Fi / Bluetooth IT) module.

According to the datasheet and comparison chart on the Toradex website, this module supports 2x Gigabit Ethernet. However, when attempting to generate a pinout using the Pinout Designer, I am facing conflicts on pin number 269.

I suspect this might be a bug in the Pinout Designer tool. I would greatly appreciate it if you could investigate this issue and provide a solution or clarification.

I have attached relevant screenshots or information to support my claim.

imagepinout designer
imagepinout designer1851×916 178 KB

1 Like
2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

Thank you for bringing this issue to our attention. When working with the Apalis iMX8 QuadMax 8GB Wi-Fi / Bluetooth IT module and attempting to configure dual Gigabit Ethernet interfaces, it’s crucial to ensure that the pin configuration does not lead to conflicts, especially for critical functions like Ethernet.

The conflict on pin number 269 you’ve encountered could stem from multiple potential causes. It might be a limitation within the Pinout Designer tool’s current logic or database, an actual hardware limitation, or a misunderstanding of the module’s capabilities and pin multiplexing options.

To address this issue, please consider the following steps:

  1. Verify Module Specifications: Double-check the module’s datasheet and hardware reference manual to confirm the pin’s functions and multiplexing options. Ensure that both Gigabit Ethernet interfaces are supported as per the documentation.

  2. Review Pin Multiplexing: For the iMX8QM SoC, certain pins can serve multiple functions. Ensure that the pin configuration you’re attempting does not conflict with other peripheral functions you intend to use.

  3. Alternative Pins: Look for alternative pins that can be used for the second Gigabit Ethernet interface. The SoC might offer flexibility in terms of pin selection for Ethernet PHY interfaces.

  4. Software Configuration: Ensure that your device tree (for Linux) or other relevant configuration files correctly reflect the pin muxing and peripheral setup you intend to use. Incorrect software configuration can sometimes mimic hardware or tool-related issues.

  5. Tool Limitations: Be aware that the Pinout Designer tool might not always reflect the latest hardware capabilities or might have limitations in its current version. While we continuously work to improve our tools, there might be gaps or delays in updating the tool’s database.

If after these steps the issue persists, it might indeed be a limitation or bug within the Pinout Designer tool. While I cannot directly fix the tool, your detailed report, including screenshots and the specific conflict encountered, is invaluable for further investigation and eventual resolution.

In the meantime, manual verification of the pinout and consultation of the module’s comprehensive documentation might be necessary to move forward with your design.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Partner Demo Container - Crank Storyboard | Toradex Developer Center.

3

Hi @workmonesh ,

There is no issue in the pinout designer tool. infact, it is serving the purpose it is made for as it is detecting and showing you the conflict pins.
In your case, pin 269 has functionality for CONN.ENET1.REFCLK_125M and CONN.ENET1.PPS
_25M.
You can deselect CONN.ENET1.PPS if it is not required.
Also, please avoid creating multiple tickets of the same issue.

1 Like