Emulator software for AT91SAM-ICE

Martin Thomas wrote:
> Min Ge wrote:
>> I want to use the Emulator of AT91SAM-ICE, what software I should use
>> for debugging my code.
>
> You can try insight-gdb and the jlinkgdbserver as gdb-server both
> included in WinARM 3/06. Make sure to use the latest driver from Segger.
> The SAM-ICE is basicly an Segger JLINK OEM-version for AT91-only. I have
> not tested this setup myself but there is a report in the AT91.com-forum
> that it works.
>
> Martin Thomas

Thanks for your reply.

One more question. I have alreadly downloaded instight 6.4, but I do not
know how to include it in the WinARM. I Can edit and compile project
under pn in WinARM. But I do not know how to connect to AT91SAM-ICE in
pn. I used to use WinAVR to compile AVR project and debug in AVE studio,
but I do not know when

I use WinARM to compile, what software (Just link AVR Studio) I can use
for connecting to Emulator and debugging. If it is under pn of WinARM.
How to include the insight software? My system is WinXP and I could not
find any install or setup executable file in the insight-6.4.

Thanks again for your help.

Hi Martin Thomas,

Thanks for your help.

I still have problem of debugging with AT91SAM-ICE.

The followings are the related information:
 - WinXP system
 - Use USB to connect AT91SAM-ICE
 - AT91SAM7-EK target board

I installed
 - WinARM (060331)
 - JLink.exe
 - CygWin

The JLink is OK. I can read target board voltage.
What I am doing is:
 - I use Programmer Notepad to comiple files. It is OK
 - Then I run JlinkGDBServer.exe in the directory
       of "C:\WinARM\utils\jlinkgdbserver"
    It displays:
     GDB Server for J-Link V1.00
     GDB Server starting on port 2331
   I keep this window open
 - Then I run arm-elf-insight.exe in the directory of
       C:\WinARM\utils\insight_gdb_6_4_50\bin
   Open Project - "main.elf" file. It is OK
 - In Menu of <file>-<Target settings>
    select Target: Remote/TCP
           Hostname: localhost
           Port: 2331
 - Then in Menu <Run>, click <Connect To Target>
    it idsplays "connection sucessful"
 - Then I click <Run>-<Download>
    It displays "localhost:8888:unknown error"

    GDB cannot connect to the target board using localhost:8888.
    ...

 - I used to set port as 8888. I do not know how to correct it.

 Are my operations correct? Could please tell me what I should do.
 Thanks a lot.

Min Ge

Martin Thomas wrote:
> Programmers Notepad does not have a debugging-interface. You may try
> Eclipse or DevC++ if you whant an IDE with integrated debugging-support.
> Basicly you can use a method like in WinAVR. You create a elf-file with
> debug-information (stabs or dwarf-2). And load this elf-File into
> (insight)-gdb like in AVR-Studio. But there is one major difference.
> AVR-Studio has an integrated hardware-driver for  the JTAG-interface
> (AVR JTAGICE/MKII). For gdb you need an additional software which
> interfaces between gdb and the JTAG-hardware. JLINK-gdb-Server is such a
> software. You may read my small "Wiggler" tutorial on the WinARM-page.
> It basicly describes the method just "replace" OCDRemote by
> Jlinkgdbserver.
>
> Martin Thomas

Hi Martin Thomas,
I still can not solve my problem. Could please give me some idea?
Thanks a lot.

Min Ge

Martin Thomas wrote:
> Please try insight-gdb from gnuarm first. Maybe it's just a problem with
> the program included in WinARM. Michael Fischer's tutorial might be
> useful: http://www.usbdip.de/en/armdev/index.html . It's for other
> JTAG-hardware but you should get the idea. Specific questions about the
> jlinkgdbserver should be asked in the gnuarm yahoo-group since the
> developer of the software reads this forum/newsgroup. I have just
> included it into WinARM since I wanted to test it on my
> development-machine but I have not done this so far.

Hi,

thanks for your help again.

I have already connected My main.elf to the emulator of JTAG-ICES via
Jlink-gdb-servier, and I can run in step in insight. but I can only see
the assembly code instead of my C source code.
I could not make sure whether it is my own code or not.
Is there any settings that is able to change the debugging code to my C
source code? Thanks.