Op Thu, 15 Mar 2012 05:03:04 +0100 schreef Przemek Klosowski <przemek@tux.dot.org>:> On Wed, 14 Mar 2012 14:03:32 +0000, Grant Edwards wrote: > >> On 2012-03-14, Tim Wescott <tim@seemywebsite.please> wrote: > >>> There is trace support on every ARM chip made, through the JTAG >>> debugger port. >> >> Not true. In the past, trace support was pretty rare on low-end parts. >> Very few ARM7 parts had trace support -- they only had JTAG. >> Even on the earlier ARM9 parts, many didn't have trace support. > > Am I mistaken in believing that the D in TDMI implies trace support?Yes. Most commercially available ARMv4T ARM7 MCU's were and are ARM7TDMI-S where TDMI = Thumb+Debug+Multiplier+ICE. Apparently 'D' means it has a JTAG TAP-controller with debug extensions (halt command, etc.) Apparently 'I' means the ICEBreaker or EmbeddedICE macrocell which implements watchpoints and a communications channel. In ARM7/9, tracing is typically implemented by an ETM (embedded trace marcocell). -- Gemaakt met Opera's revolutionaire e-mailprogramma: http://www.opera.com/mail/ (Remove the obvious prefix to reply privately.)
ARM GDB debugging.
Started by ●March 13, 2012
Reply by ●March 15, 20122012-03-15
Reply by ●March 15, 20122012-03-15
On Thu, 15 Mar 2012 12:04:46 +0100, "Boudewijn Dijkstra" <sp4mtr4p.boudewijn@indes.com> wrote:>Op Thu, 15 Mar 2012 05:03:04 +0100 schreef Przemek Klosowski ><przemek@tux.dot.org>: >> On Wed, 14 Mar 2012 14:03:32 +0000, Grant Edwards wrote: >> >>> On 2012-03-14, Tim Wescott <tim@seemywebsite.please> wrote: >> >>>> There is trace support on every ARM chip made, through the JTAG >>>> debugger port. >>> >>> Not true. In the past, trace support was pretty rare on low-end parts. >>> Very few ARM7 parts had trace support -- they only had JTAG. >>> Even on the earlier ARM9 parts, many didn't have trace support. >> >> Am I mistaken in believing that the D in TDMI implies trace support? > >Yes. Most commercially available ARMv4T ARM7 MCU's were and are >ARM7TDMI-S where TDMI = Thumb+Debug+Multiplier+ICE. > >Apparently 'D' means it has a JTAG TAP-controller with debug extensions >(halt command, etc.) > >Apparently 'I' means the ICEBreaker or EmbeddedICE macrocell which >implements watchpoints and a communications channel.And the -S suffix indicates that the core IP is Synthesizable (customizable by the mfgr) vice delivered as a netlist "black box." -- Rich Webb Norfolk, VA
Reply by ●March 15, 20122012-03-15
On 2012-03-15, Przemek Klosowski <przemek@tux.dot.org> wrote:> On Wed, 14 Mar 2012 14:03:32 +0000, Grant Edwards wrote: > >> On 2012-03-14, Tim Wescott <tim@seemywebsite.please> wrote: > >>> There is trace support on every ARM chip made, through the JTAG >>> debugger port. >> >> Not true. In the past, trace support was pretty rare on low-end parts. >> Very few ARM7 parts had trace support -- they only had JTAG. >> Even on the earlier ARM9 parts, many didn't have trace support. > > Am I mistaken in believing that the D in TDMI implies trace support?The D stands for "Debug extensions", I'm not sure exactly what that implies, but plenty of TDMI parts didn't have trace support. -- Grant Edwards grant.b.edwards Yow! I'm not an Iranian!! at I voted for Dianne gmail.com Feinstein!!
Reply by ●March 15, 20122012-03-15
On 2012-03-15, David Brown <david@westcontrol.removethisbit.com> wrote:> On 14/03/2012 15:24, Grant Edwards wrote: >> On 2012-03-14, FreeRTOS info<noemail@given.com> wrote: >> >>> It is very rare, unless you work for a tools company, that you would >>> ever actually see the GDB interface, as it will be (effectively) >>> abstracted away by a higher level interface. >> >> By "see the GDB interface" do you mean look at remote protocol >> packets? Or are you saying nobody uses the GDB command line? >> >> If you mean almost nobody messes with the remote protocol packets >> directly, that's probably true. But, I think there are still plenty >> of people that use the gdb command mode. >> > > I like the gdb command line, and use it for several processors. Like > all command lines, it takes a bit longer to learn to use than a nice > gui, but for some uses it is much faster. In particular, it is good for > writing macros for repetitive tasks, or for when you need relatively > little interaction.I too use gdb macros extensively. I can't believe that would willing people sit there and click dozens of buttons and menus and whatnot over and over again instead of typing a single command. I guess that's what happens to you if you were raised on "Windows" -- you just don't know there's a better way. I've written entire board test and programming systems using a small shell script and a handful of gdb macros. I hate to imagine somebody sitting there at a bench doing all that clicking in a GUI. -- Grant Edwards grant.b.edwards Yow! I feel like a wet at parking meter on Darvon! gmail.com