Author Topic: Thought for a debugging interface "uProbe"  (Read 9134 times)

Offline mhoneywill

  • Full Member
  • ***
  • Posts: 173
    • View Profile
Thought for a debugging interface "uProbe"
« on: June 19, 2012, 04:02:36 PM »
Just a thought about a feature to add to utasker, a debug probe that worked in a similar way to the following products


This could connect to the target using any of the following interfaces

serial Uart
SPI or I2c using an FTDI cable (
Comms channel over JTAG (This might be more difficult as it would require hooking into the compiler IDE)

This debug link could be the default way that debug information is reported from uTasker.

I have used a similar UDP only solution for the Rabbit processors, see this link for more details and source maybe the same UDP protocol could be used.

Offline hervé

  • Jr. Member
  • **
  • Posts: 98
    • View Profile
Re: Thought for a debugging interface "uProbe"
« Reply #1 on: July 05, 2012, 08:58:11 AM »

I use similar debug tool, then through UDP packets I can check or change every data zone that the µP can access. I can also call function while the program is running, it is very useful for debbuging : in my case as the board controls fast movement and therefore I cant use breakpoint.
I use the µC/Probe like command to read/write byte,word, or long data at specific address.
I had to have a map file of the variables addresses except for some specific data for which I use a table to reference them : I will fetch the address of this table so I can have access to all variables that are referenced without having to know their absolute address.
For others I use the .Map file generated by the compiler.

On the PC I have a small application that can scan a list of variable in a cyclic manner.
On do this manually.

The code on the target is small and quite generic...