Re: [ECOS] THUMB/eCos application did not run in AT91

[Laurent GONZALEZ <laurent dot gonzalez at silicomp dot fr>]

On Tue, 23 Sep 2003 16:29:23 +0000
Claudio Leonel <cls@elaxys.com.br> wrote:

> Hi all,
> 
> I comented out the lines in vectors.S where the LED macro is and
> eCos compiled OK with thumb mode enabled.
> I coded a test application, compiled it with '-mthumb -mthumb-interwork'
> and linked it OK with libtarget.a
> 
> I loaded the application in the ATMEL EB55 board with gdb/redboot and
> executed 'continue'. The application which should only printf a message
> didn't run and hang. I reloaded the application and set a breakpoint
> in 'main' and got the same result. It seems to get lost before reaching
> 'main'.
> 
> The same application compiled without the thumb options and linked with
> an eCos lib also compiled without the thumb options works OK.
> 
> My setup:
> - Linux 2.4.20
> - arm-elf-gcc v3.2.1 and other gnu tools from eCos v2.0.
> - eCos from CVS (about one week ago)
> - eCos config tool 2.0
> 
> 
> Thanks for any ideas.
> 
>

hello,

what about your redboot ? Are you sure it is compiled with -mthumb-interwork ? I guess that redboot is an arm32 only executable, without interwork support.

Any (diag_)printf or debug session cannot work. Your application can call redboot code, because it uses "bx" instructions, but redboot functions cannot return to the caller with a simple "mov pc,lr" because of the change of instruction set.

Try a simple application that does not uses redboot facilities at all (no printf, no delay, ...). A simple led swing should work.

regards

-- 
GONZALEZ Laurent
Silicomp Research Institute
Tel: 04 76 41 66 98

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