What are the issues in moving from the BL51 Linker to LX51? Has anyone out there tried it? What were your experiences? I'd be using it with the Triscend E5 immediately.
the linker lies about the magnitude Bob, Can you please send me an example of where the linker inaccurately reports the size savings so I can figure out what's going on. The linker space savings calculation is based on the code size BEFORE linker optimizations. It should be correct, but if there's a problem we need to get it fixed. Jon
Jon You wanted an example of lies about the amplitude Try \\keil\c51\examples\measure A build with BL51 produces a code length of 7037. A build with LX51 (linker code packing off) produces a length of 7037. A build with LX51 (linker code packing on) produces a length of 6982, and the comment was 7313 reduction 4.6% Inspection of the linker lists files is the next step. This is describe as a linker optimization but is it? (1)It is enabled in the C51 tab of Options for target. (2)It only seems to work when the source is C, rather than assembler. Could you expand the explanation of this feature.