Debugging remote target

Debugging remote target

[Dale Lee]

Hi Support

We are currently running Insight debugger on an i686 Host to remotely 
debug an ARM Target using JLink.
Both Target and Host are running Linux.

     Host (Linux i686 PC) <==  JTAG (JLink) ==> Target (ARM9) ATMEL91SAM9261
                                                   Ethernet
1. I configure the Insight by running ./configure
2. I followed instructions indicated on 'Section 2.1 Building and 
Installing.
3. When insight is invoked, I can  access the register values currently 
in the target.
4. Why is the registers shown as  i686 PC ( ) format INSTEAD of the ARM 
format (pc, cspr, r1, r2, r3...)
when issue the gdb command

    gdb > info registers

5. Even though I am executing insight on the i686 "host" to remotely 
debug the ARM target
I can only see the register in format for i686 PC and NOT for ARM which 
I want.

What do I need to do to make the insight debugger report the arm 
registers correctly?

Thanks
Dale

Re: Debugging remote target

[Keith Seitz]

Dale Lee wrote:

> What do I need to do to make the insight debugger report the arm 
> registers correctly?

You need to tell the build that you want a debugger that runs (hosted) 
on i686, but targets ARM. See configure's "--target" option.

I don't know the exact triple used for your ARM cpu, there are a number 
of ways to find out. Easiest, what is the name of your compiler 
(assuming gcc). If it's "foo-bar-baz-gcc" (or perhaps just 
"foo-bar-gcc"), then your build --target is "foo-bar-baz" (or perhaps 
simply "foo-bar").

If you're not using gcc, you can look in src/gdb/configure.tgt for a 
suitable target triple for your target. Otherwise, your best bet is to 
search or ask the gdb mailing list for assistance.

Keith