We are currently using the Verdin iMX8MM Q 2GB IT (V1.1C).
Is it possible to set the module to JTAG boundary scan mode?
The Errata (https://docs.toradex.com/107330-verdin-imx8m-mini-errata.pdf) states (Errata #7) that this mode should be accessible on the new variant. However, as I have seen in the datasheet, the iMX8 pin “BOOT_MODE1” on the Verdin board is pull-downed. Might it be necessary to do something with the 10 test points on the back side of the module?
Click on Instruction and choose EXTEST and “Use safe values from the device BSDL file”
After clicking OK, press Run.
Now can choose a PIN to toggle. Just be aware not to short circuit a PIN on the SOM and/or turn off a PIN which is needed for the Power up of the Soc. For example, we used SODIMM53:i2c2_sda (SoC:D10) and SODIMM55:i2c_scl (SoC: D9), which is safe to use, since these pins have a pull up resistor.
You can use the pin from the Top JTAG Probe tool to be an input or output.
When the PIN is used as an output, you can drive a LED with this.
For Input you can either pull the pin up to 3.3V or GND and readout the value inside the Application.
As I do not have a JTAG, I wasn’t able to test it myself.
Does it help you?
Best regards,
PS: the Verdin iMX8MM Project will be available for 1 year from today.
Can the TP4 really be connected to +3V3? I ask because this pin is connected to the same power domain as the JTAG (NVCC_JTAG) and this domain is +1V8 as far as I know. Or do you have some kind of buffer between?
I have a small follow-up question regarding this topic: Are the other 3 pins (JTAG_MOD, TEST_MODE, GPIO1_IO02) actually wired according to NXP’s boundary-scan specification on the Verdin iMX8M Mini (see picture in the initial question)? Like this:
JTAG_MOD has a 10k pull down resistor and can be controlled through the connection to to TP3.
TEST_MODE is connected to BOOT_MODE1 with a 10k pull down resistor and can be controlled through the connection to TP4.
GPIO1_IO02 is connected to PMIC_WDI and has a 100k pull up resistor to 1.8V.
This has been done to not statically enter the boundary scan mode. From Version 1.1 onward an errata has been issued, which enables you to access the mode via the TPs.
I hope this answers your questions.