I'm having some trouble getting apps to run as expected on the iMote.
For example, CntToLeds will cycle through the LEDs but Blink will not
work - the LEDs stay white like the mote is initializing and seems to
be stuck in a reset loop. This reset loop occurs virtually all the
time (i've tried several of the demo apps contributed). The firmware
that is flashed to the iMote seems to be erratic.

I've setup the environment as close as possible to the intructions
outlined in contrib/imote/README with the exception of the ARM Linker.
The ADS Tool Chain v1.2 appears to be no longer available from arm.com
for evaluation and has been replaced with the Realview Developer
Suite. This evaluation CD does contain the linker, however it is
marked as version RVCT2.2 [Build 380] Evaluation. Some searching
through ARM's support lead me to a pdf describing changes in the ARM
ABI from v1 to v2 (http://www.arm.com/miscPDFs/8059.pdf), which may
now be the problem. There are two warnings (aside from symbols that
appear to be resolved) that are repeated many times when the linker is
run:

Warning: L6730W: ABI type NUMBER differs from legacy behaviour ARM for
target symbol of relocation 9 from section .text from object
main.exe.o.
Warning: L6318W: main.exe.o(.text) contains branch to a non-code
symbol [Anonymous Symbol].

I've looked both of these up in
http://www.arm.com/support/RVCT22_Errors_and_Warnings.pdf, but I don't
totally understand them and I am not sure how to go about fixing the
problem. Any ideas here would be appreciated.

I have also experimented with the GNU ARM linker from gnuarm.org, but
haven't had any success in correctly mimicking the parameters that are
passed to armlink, or if that's even the right way to go about this. I
would prefer to use the GNU linker if possible. If anyone has
successfully used it, could you please post your Makerules and any
special setup details?

Thanks,
Derek

_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to