2017-03-03 07:25 AM
I'm using a STM32F7 MCU with a JTAG connection (4-pins used). The schematic is attached. It uses the
http://www.keil.com/support/man/docs/ulinkpro/ulinkpro_jtag_10pin_swm.gif
, and it's connected to a ST-LINK using thehttps://www.olimex.com/Products/ARM/JTAG/ARM-JTAG-20-10/
.The SWD works correctly, but the JTAG can't be connected (I'm using the ST-LINK Utility). Also, I have already used the same schematic for a STM32F2, and it connects successfully using JTAG.
Is there any difference/limitation with the STM32F7 MCU? Any clue of what can happen?
Thank you
#stm32f7 #stlink #jtag-dp #jtag2017-03-04 02:57 PM
Can yout test with another Adapter or with another board? Mostly error are done by the user. Fundamental Errors in crucial of the parts circuit may happen, as with the Ethernet PHY in F767 rev1, but all in all are rather seldom. I suspect JTAG to work on the F767, or otherwise it would be documented in the errate.
2017-03-05 03:08 AM
Is there a specific reason to use JTAG vs SWD? Performance-wise SWD is usually good enough for debugging with 2 or 3 IOs (if SWO printf debug feature is used). Maybe missing pull-ups on JTAG lines?
2017-03-06 04:19 AM
Thank you for the reply.
I've tried with other boards without any success.
2017-03-06 04:24 AM
Thank you for the reply.
There isn't any reason to use JTAG, but I was wondering why it's not working and if there is a hardware error in the design.
The
explains that STM32F7 had internal pull-ups/downs on the JTAG pins, so 'Having embedded pull-ups and pull-downs removes the need to add external resistors'.2017-03-06 04:48 AM
That other boards don't work neither indicates an error on your side...