[mc1322x] Using the ROM
Umberto Manzoli
ruytenburch at gmail.com
Thu Jul 30 13:47:41 EDT 2009
Dear Jon,
GCC cannot handle the LLC.a library, as the linker (binutils) cannot
understand R_ARM_THM_PC8 relocations. Usually R_ARM_THM_PC8 relocations are
generated at compile time to use constant values that cannot reside in asm
instructions. These constants are placed in a pool at the end of the
function. R_ARM_THM_PC8 are resolved by compiler and not handled by linker.
We asked Freescale to release the source code, but they answered that the
rom-patching mechanism used by ROM and LLC.a is being covered by some
patents so they are not allowed to distribute source code of LLC.a. Without
some functions - usually not exposed - in LLC.a, ROM functions could not
work or could exhibit wrong behaviour.
Obviously, you can disassemble LLC.a and use the generated assembly code to
replace the library if you are compiling with GCC, as Mariano did with SMAC.
By the way, take care of the software licence shown when Beekit is going to
be installed: it explicitely states that the end-user cannot disassemble any
kind of library. Even if Freescale's library is going to show errors...
2009/7/30 Jon Smirl <jonsmirl at gmail.com>
> What are the problems with using the ROM? Can GCC not link to LLC.a?
> All of the header files appear to be present and all of the routines I
> have checked are documented.
>
> Has anyone filed an SPR and asked for source code to it?
>
> --
> Jon Smirl
> jonsmirl at gmail.com
>
> _______________________________________________
> mc1322x mailing list
> mc1322x at devl.org
> http://devl.org/cgi-bin/mailman/listinfo/mc1322x
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://devl.org/pipermail/mc1322x/attachments/20090730/c74f3d25/attachment.htm>
More information about the mc1322x
mailing list