JTAG linked to DEBUG

Hello Toradex team,

I hope you are all doing great! And thank you for your support.



  • Linux verdin-imx8mp-14777482 5.15.129-6.4.0+git.67c3153d20ff #1-TorizonCore SMP PREEMPT Wed Sep 27 12:30:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Images tested:

  • torizon-core-docker-verdin-imx8mp-Tezi_6.4.0+build.5.tar (STABLE Release)

Guest OS:

  • macOS (M1 Pro ARM64)
  • Linux ubuntu (VM x86_64)

We are reviewing our carrier board one more time before launching the next production.

And while I was checking it, I came accross on IC that doesn’t seems necessary for me but I could be wrong, so my question is: do we need to fit the IC34 on our carrier board or it’s not mandatory as you can see on (the right of) the schematic ?

Best Regards,

Our recommended workflow with software does not require the use of JTAG for system bring-up or for debugging the Linux OS/application. However, JTAG can be useful for debugging M core applications. It’s not necessary to route JTAG through a USB-C UART/MPSSE chip. Instead, you can simply install a standard 10-pin header somewhere on the board.

You can entirely omit the use of the FT4232H chip. Please refer to the carrier board design guide for more details. However, we strongly recommend making the USB_1 interface accessible in USB client mode to facilitate module recovery. Additionally, it’s advisable to provide access to UART_3, as it is intended for main OS debug log output and serial console use. To save space and reduce costs, you could opt to install only a header for this purpose. Developers who require this functionality can then use any commercially available TTL to USB serial converter.

If you choose to use the FT4232H IC and wish to keep JTAG signals accessible, then including IC34 is mandatory. This is because the FT4232H operates at 3.3V signal levels, whereas the Verdin module supports only 1.8V levels.

1 Like

Hi @alex.tx,

Thank you for the answer ! It’s super complete and I will remove it and add the pin as you explained.

Best regards,

The design of that schematic was intended to simplify the lives of software engineers. It allows them to directly connect the board to their development machine without the hassle of finding the correct USB to Serial adapter. For your production boards, however, such complexity is definitely unnecessary. End users should not have to worry about program debugging, and if a technician needs to collect a boot log or use a serial console, having a header as a solution is perfectly acceptable. Just make sure it’s placed in an accessible location. If UART_4 is not utilized in your design, I recommend opting for a 2.54 mm header as for UART_3. You can leave it unpopulated; if needed in the future (for instance, if some OS image uses it as a debug console), it can be easily soldered on

1 Like