Kinetis K60DN256VQL10 Ethernet and Trace

manu_00 — Thu, 04 Oct 2012 14:57:35 GMT

Hello,

i am a little it confused i realized thatsome of the pins that are neccesary for ethernet (MIIRXD3,MIIRXD2 ) are also neccesary if you want to Trace data (Trace D1 , Trade D2). Could anyone explain me a workaround hoe to connect ethernet MII Phy and the debugging tool at the same time?

Thanks in advance

cheers manu

Re: Kinetis K60DN256VQL10 Ethernet and Trace

egoodii — Thu, 04 Oct 2012 17:02:59 GMT

'Trace' debug pin connections are only used by, well, TRACE debugging options. So firstly you would have to have a trace-enabled tool (like J-Trace) to even expect to do anything with those pin connections. Secondly, while I have such a tool I have found it 'necessary' only once to dig to that detail level; to find an MQX bug. Most problems are not worth forcing yoursellf to deal quite that deeply into cycle watching. We have used MII here and J-Link tools (restricted to the 10-pin debug header) with no other programming/debug limitations. And of course we only use MII when we are forced into it -- RMII is more efficient.

--ERGII

Kinetis MicrocontrollersのトピックRe: Kinetis K60DN256VQL10 Ethernet and Trace

Kinetis K60DN256VQL10 Ethernet and Trace

Re: Kinetis K60DN256VQL10 Ethernet and Trace