[fpc-devel] Is target mips-embedded possible / planned?

Martin Schreiber mse00000 at gmail.com
Thu May 23 12:07:57 CEST 2013

On Thursday 23 May 2013 11:06:52 Michael Schnell wrote:
> On 05/23/2013 10:50 AM, Martin Schreiber wrote:
> > Or the gdbserver runs on the PC and communicates with a debug interface
> > hardware. MSEide uses this approach to debug AVR32 code with the "AVR
> > ONE!" debugger and ARM chips (for example Energy Micro Tiny Gecko) with
> > the Segger J-Link debugger which is built-in in the inexpensive demo
> > board.
> I see.
> I did not  expect that someone would be inclined to go  this way, as you
> need to implement the (published but rather "internal") gdb<->gdbserver
> pipe protocol, and additionally you need to do the arch-dependent
> interpretation in your own software rather than have gdb do this and
> provide the results via it's well-understood command line pipe interface.
> But obviously you did have good reasons to do so. (Can you provide a
> short explanation, why ?)
You misunderstood. The chain is 

> What kind of interface does "AVR ONE!" provide ?

AFAIK debugWIRE, PDI, aWire, JTAG, Nexus.

> Does it come with a 
> gdbserver type of "driver" on the PC ?

> BTW.: can you say anything regarding the PIC32 debugging issue ?
I don't use PIC32, sorry.


More information about the fpc-devel mailing list