On board TWRVF65GS10 (MCU) there is K20 JTAG Header. Can I use K20 JTAG Header for programming and debugging of an my own board with the processor Vybrid vf6xx?
Thanks for references!
I read section 7 (Debug Interfaces) of Hardware Development Guide for Vybrid.
I also watched the electric circuit TWR-VF65SG10_SCH.pdf, on which there is 10 pin JTAG port
(J2,Serial Interface, JTAG K20 header).
On my own board (on the model) there is 10 pin JTAG port too, which is connected
to the Vybrid VF6xxx (Vybrid VF6xxx on my own board too).
On the basis these documents I have come to a conclusion, that
I can connect my own board (model) to JTAG K20 header on TWR-VF65GS10, then
connect USB cable to PC and to TWR-VF65GS10 board, after that I can debug and program my own model.
Is it right or not? It seems to me, that in section 7 it is told not concrete.
I would like to know more precisely, yes or not?
Excuse for my English.
Have a great day too.
Hello,
You may look at section 2.4 (Debug interfaces) of TWR-VF65GS10 Tower Module User’s Guide.
< http://www.nxp.com/docs/en/user-guide/TWRVF65GS10UG.pdf >
Three (separate) debugging interfaces are provided on the TWR-VF65GS10 module:
• OpenSDA with CMSIS-DAP on Micro-B OTG USB connector J3 ;
• JTAG on header J5 ;
• ARM ETM (Embedded Trace Macrocell) on connector J11.
The first (OpenSDA with CMSIS-DAP firmware) does not require additional
hardware (probe) for (minimal) debugging.
The second is JTAG approach, that is most powerful, but requires additional
hardware such as DSTREAM of ARM. It allows working in bare metal environment.
For Your board, where there is 10 pin JTAG port, connected to the Vybrid VF6xxx -
the second, JTAG based, approach may be applied. In order to use OpenSDA with CMSIS-DAP on Your board it is necessary to have Kinetis with corresponding firmware (and schematic). If You board is part of Tower system, as the second Vybrid based one - it is possible to rely on existing OpenSDA with CMSIS-DAP,
assuming Your Vybrid code is already working (with help of a JTAG debugger).
Regards,
Yuri.
Thank you very much!
I read section 2.4 and assumed that it is necessary to buy the additional
equipment, but wanted to know precisely.
On our board (bare metal) there are no Kinetis with corresponding firmware
(and schematic) and we have to buy the additional
hardware, to start the Vybrid VF6xxx on the our model.
Thanks, I consider a question solved.
2017-07-20 7:12 GMT+03:00 Yuri <admin@community.nxp.com>:
NXP Community
<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>
Re: Отладка VF6xx
reply from Yuri Muhin
<https://community.nxp.com/people/Yuri?et=watches.email.thread> in *Vybrid
Processors* - View the full discussion
<https://community.nxp.com/message/925924?commentID=925924&et=watches.email.thread#comment-925924>
Hello,
please refer to section 7 (Debug Interfaces) of Hardware Development Guide for Vybrid
Family of MCUs, User’s Guide, Rev. 1, 05/2015.
http://www.nxp.com/docs/en/user-guide/VYBRIDHDUG.pdf
Summary Page :
VF6xx MPUs with ARM Cortex-A5/M4 Core|Vybrid|NXP
Recommended software and tools :
VF6xx MPUs with ARM Cortex-A5/M4 Core|Vybrid|NXP
Have a great day,
Yuri
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------