This is the mail archive of the ecos-discuss@sources.redhat.com 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: AT91 ARM Thumb-mode


The plot thickens. I was just able to build (and
execute) in thumb mode with the latest prebuilt
binaries. The only issue I've come across so far in
testing the executable is that after stopping and then
continuing my program with my ICE, I sometimes get
weird results, like:

ASSERT FAIL: <1>dle thread vanished!!!
ASSERT FAIL: <1>                   [397648]
()                                                    
                                             Idle
thread vanished!!!

I think this might be a problem with my ICE, as I
don't see any issues until I stop/continue.

Also, I had to turn off "Use separate interrupt stack"
to get it to build. This might also explain my idle
thread vanishing problem (stack overflow).


--- Jonathan Larmour <jifl at eCosCentric dot com> wrote:
> sensitron medical wrote:
> > compile snippet:
> [snip]
> 
> That command line is fair enough.
> 
> If you were using the current CVS trunk I would
> agree you should be able 
> to get quite far, but the v2.0b1 release had a
> problem that prevented it 
> being compiled for thumb - fixed by this patch but
> only in the CVS trunk: 
>
http://sources.redhat.com/ml/ecos-patches/2003-04/msg00085.html
> 
> If you were using the trunk, you would also see that
> the thumb compiler 
> still isn't necessarily up to scratch:
> 
> arm-elf-gcc -c 
>
-I/home/jlarmour/sourceware/ecos/ecos/obj/arm/pidT/install/include
> 
> -I/home/jlarmour/ecos/packages/kernel/current 
> -I/home/jlarmour/ecos/packages/kernel/current/src 
> -I/home/jlarmour/ecos/packages/kernel/current/tests
> -I. 
> -I/home/jlarmour/ecos/packages/kernel/current/tests/
> -mthumb 
> -mthumb-interwork -Wall -Wpointer-arith
> -Wstrict-prototypes -Winline 
> -Wundef -Woverloaded-virtual -g -O2
> -ffunction-sections -fdata-sections 
> -fno-rtti -fno-exceptions -fvtable-gc
> -finit-priority 
> -Wp,-MD,tests/dhrystone.tmp -o tests/dhrystone.o 
>
/home/jlarmour/ecos/packages/kernel/current/tests/dhrystone.c
>
/home/jlarmour/ecos/packages/kernel/current/tests/dhrystone.c:
> In function 
> `Proc_1':
>
/home/jlarmour/ecos/packages/kernel/current/tests/dhrystone.c:870:
> 
> Internal compiler error in pre_insert_copy_insn, at
> gcse.c:4859
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html>
> for instructions.
> make[1]: *** [tests/dhrystone.d] Error 1
> 
> "Only" a test, sure, but it gives us doubts about
> the compiler's 
> reliability. On the other hand, if anyone reports
> success using GCC 3.2.2 
> or GCC 3.2.3 we would very much like to know about
> it.
> 
> Jifl
> 
> >
>
/ecos-c/ecos-2.0b1/packages/kernel/v2_0b1/src/intr/intr.cxx:668:
> > 
> >>>undefined reference to `hal_disable_interrupts'
> >>
> >>That should have come from vectors.S - there's
> some
> >>thumb only functions 
> >>to do that. Was it definitely compiled in thumb
> >>mode?
> >>
> >>Just thinking of the last message I sent, if
> >>vectors.S was compiled in 
> >>thumb mode, I'm intrigued by the fact you got this
> >>far. What tool versions 
> >>are you using?
> >>
> >>Jifl
> 
> -- 
> eCosCentric    http://www.eCosCentric.com/    The
> eCos and RedBoot experts
> --[ "You can complain because roses have thorns, or
> you ]--
> --[  can rejoice because thorns have roses."
> -Lincoln   ]-- Opinions==mine
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

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


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