Hello,
embOS Version 3.60 ships with libraries labeled "A4" and "A5". I guess that these refer to the different CPU-Core architectures - namely ARMv4 and ARMv5.
As the SAM9263 is based on the ARMv5 core, I am trying to use the appropriate embOS version.
However, trying to link with the A5 variant using the latest Yagarto-toolchain fails with the following messages:
c:/programme/yagarto/bin/../lib/gcc/arm-elf/4.2.2/../../../../arm-elf/lib\libc.a(lib_a-div.o) uses FPA instructions, whereas <app> does not
From this the following questions arise:
1. Is it necessary to link with A5 for the SAM9263, or will the A4 version work as well ?
2. Which compiler-switches were used to build the embOS libraries A4 and A5 ?
Besides, my software _seems_ to run on the SAM9263 using the A4 version. Though it does not run stable: it _seems_ that switching tasks _sometimes_ lead to garbled register contents ...
Regard,
Karsten Laux
embOS Version 3.60 ships with libraries labeled "A4" and "A5". I guess that these refer to the different CPU-Core architectures - namely ARMv4 and ARMv5.
As the SAM9263 is based on the ARMv5 core, I am trying to use the appropriate embOS version.
However, trying to link with the A5 variant using the latest Yagarto-toolchain fails with the following messages:
c:/programme/yagarto/bin/../lib/gcc/arm-elf/4.2.2/../../../../arm-elf/lib\libc.a(lib_a-div.o) uses FPA instructions, whereas <app> does not
From this the following questions arise:
1. Is it necessary to link with A5 for the SAM9263, or will the A4 version work as well ?
2. Which compiler-switches were used to build the embOS libraries A4 and A5 ?
Besides, my software _seems_ to run on the SAM9263 using the A4 version. Though it does not run stable: it _seems_ that switching tasks _sometimes_ lead to garbled register contents ...
Regard,
Karsten Laux