This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Porting eCos to the Atmel AT91CAP7


Hi John,

Are you able to set breakpoints in any other files? I can understand
that you may have problems with looking up files with Cygwin / Eclipse
but I thought GDB should anyway set the breakpoint but I might be wrong.

You can try to disassemble the code:

arm-elf-objdump -D application.elf > dump_log.txt

and set breakpoints directly at memory location wherever you want in the
vector.S:

break *(address)

Can you set breakpoint with your JTAG debugger directly?

You can also use the CPU IOs to trace the code and find out where it
crashes, by driving some LEDs for instance.

Christophe


-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of John K
Sent: 20. mai 2010 01:17
To: Edgar Grimberg
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Porting eCos to the Atmel AT91CAP7

Edgar,

I am already using the Zylin CDT plug-in. I have tried to set a
breakpoint in vectors.S (per your suggestion I tried adding "break
vectors.S:294" right before "break main" in my initialization script),
but the error on the console reads "No source file named vectors.S."  I
have tried numerous different Source Lookup Paths  in the Debug
Configuration pointing to the eCos sources on my PC, but none of them
find vectors.S.

--John



----- Original Message ----
From: Edgar Grimberg <edgar.grimberg@zylin.com>
To: John K <johnk_dev@yahoo.com>
Cc: ecos-discuss@sourceware.org
Sent: Wed, May 19, 2010 5:19:19 PM
Subject: Re: [ECOS] Porting eCos to the Atmel AT91CAP7

Hello John,

> But
> now I think I'm lost somewhere in vectors.S - when I execute the app,
> it never gets to the breakpoint at main(), my debugger reports "remote
> connection closed", and my board and JTAG debugger get into a funky
> state where I need to cycle power to the board to get out of it.

Most likely you get into an exception that confuses the CPU and the
JTAG. You are not at the stage where you can break in main, there is
still some single stepping to do.
Are you using OpenOCD with your Segger, by any chance? The
initialization scripts for your JTAG debugger might set up some things
in the CPU.

> That
> is where I am stuck now. I have no idea how to figure out what is
going
> wrong.  One thing that might help is if I could set breakpoints within
> vectors.S, but I can't seem to link the eCos source to the Eclipse
> debug session. I have tried all sorts of different path combinations
> within the "Source Lookup Path" of the Eclipse "Debug Configuration" -
> the Eclipse "Problems" tab reports "Unresolved Breakpoint" for
anything I set within vectors.S.

If you are using Windows and Cygwin, you might want to try the
Embedded CDT plugin for Eclipse.

http://opensource.zylin.com/embeddedcdt.html

With that installed, try the gdb console in Eclipse, and set the
breakpoint there :

break vectors.S:line_no

If you feel that you still don't have control over Eclipse, go to
command line GDB until you are done with the assembly code, at least.
Single step (stepi) for as long as you can, insert breakpoints right
after loops.

Regards,
Edgar

> Any suggestions?
>
> Regards,
> John Korsakas
>
>
>
>
> ________________________________
> From: Christophe Coutand <ccoutand@stmi.com>
> To: John K <johnk_dev@yahoo.com>; ecos-discuss@sourceware.org
> Sent: Tue, May 18, 2010 5:38:50 PM
> Subject: RE: [ECOS] Porting eCos to the Atmel AT91CAP7
>
> RE: [ECOS] Porting eCos to the Atmel AT91CAP7
> Hi John,
>
> Just curious, what is actually stopping you in your port?
>
> For consulting, you can check with Zylin.com, I beleive they have an
office in US.
>
> Christophe
>
> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org on behalf of John K
> Sent: Tue 5/18/2010 2:39 PM
> To: ecos-discuss@sourceware.org
> Subject: [ECOS] Porting eCos to the Atmel AT91CAP7
>
> Hi everyone,
>
> We have been working on porting eCos to the Atmel CAP7 processor core
for a couple weeks now (starting out with the AT91CAP7A-STK target
board), and it's going a bit rough. Does anyone else have experience
with this processor or perhaps is also working on a port?
>
> Or maybe one of you has some general experience porting eCos (plus
building & debugging apps with Eclipse) and can be hired as a consultant
to help kick start us? (we've looked at eCosCentric and we were hoping
to find someone in the US that would only charge a one-time consulting
fee rather than royalties). The resulting port would be fed back to the
community.
>
> Regards,
> John
> johnk_dev@yahoo.com
>
>
>
>
> --
> Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
> and search the list archive:
http://ecos.sourceware.org/ml/ecos-discuss
>
>
>
>
> --
> Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
> and search the list archive:
http://ecos.sourceware.org/ml/ecos-discuss
>
>



-- 
Edgar Grimberg
System Developer
Zylin AS

ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
Phone: (+47) 51 63 25 00



      

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]