Hi John,
> Kris,
>
> Instead of stepping around, why not use objdump on the elf file to
> produce an assembly listing, and take a look at the ordering?
>
> objdump -dSt foo >foo.lst
>
> Be sure to compile your sources with the -g option.
>
> Instead of stepping around, why not use objdump on the elf file to
> produce an assembly listing, and take a look at the ordering?
>
> objdump -dSt foo >foo.lst
>
> Be sure to compile your sources with the -g option.
Because of the confusion reigning, I'm trying it alternating between
HI-TECH C
and also on CrossWorks for ARM.
I'm not proficient with the actual GCC toolchain itself, but I can easily
check the tool to
produce an ASM listing (absolute I hope).
I will investigate this at ASM level when I return to it, and certainly
post my findings here.
On one hand it's like I've already spent way too much time on it ("Don't
muck with it" :-)
but on the other hand it's given me further insight into the
instruction set, the VIC and
other obvious intrinsic issues.
I need to now start re-thinking my tasking, as this project set out to
easily port around between
different MCUs. (before ARM came into ti)
I need to rework my HW abstraction. so other changes can still efficiently
run just as well on MSP430
as on ARM or AVR etc. , it's quite a bit of a challenge.....
-- Kris