How to debug powerquicc using GDB with out USBTAP or CodeWarrior Tap?

[wenlantang]

Have post a question Re: How to debug powerquicc using GDB with out USBTAP or CodeWarrior Tap?, could anyone help?

What's the connection in the picture of WBNR_FTF10_NET_F0676 pasted below? The doc is on 2010 FTF when the CodeWarrior TAP is not introduced yet.

[hwrobel]

The baremetal debug in the gdb stub related picture is not truly bare metal as you already have a gdb stub running on the target. So a minimum amount of setup and interfacing is already done at that time to allow the gdb stub to talk to the rest of the world.

This means that the interface you ask about could be Ethernet or UART or anything that is already set up for the gdb stub to work with. It also means that your system by definition is only partially bare metal.

It is a technically possible but unlikely scenario. If you truly want to go bare metal from the first instruction, you can’t do it as shown, and you have to use a JTAG based probe.

[wenlantang]

Hi Heinz,

Thank you for explanation, your reply looks a better answer than ever.

I do not want to go bare metal, I just want to know is it possible to go without USBTAP or CWTAP? Is this also technically possible but unlikey scenario? A JTAG based proble is still a must?

[hwrobel]

It’s really simple. If you already have software running on the target that implements a gdb stub and the communication link, e.g., Ethernet, then you can debug without a JTAG probe based on the gdb stub capabilities.

If you do not have software running on the target that implements such a gdb stub or the communication link, then you will need a JTAG probe to connect to the target.

[wenlantang]

Thank you, so it is possible to debug without cwtap using GDB, when there is GDB stub on the target.