Prev: CMOS Image sensor & Two-wire serial interface
Next: Position independent code with position dependent data ?
From: bigbrownbeastie on 30 Jun 2010 11:04
the linker file in the LPC2106 project is 'LPC2106_JLink.icf'

i will put my invoice in teh post to you.
From: bigbrownbeastie on 30 Jun 2010 11:12
BTW, why are you using LPC2138 or LPC2106? those parts died out years
ago for new designs

From: larwe on 30 Jun 2010 11:24
On Jun 30, 11:01 am, bigbrownbeastie
<bigbrownbeastiebigbrownf...(a)googlemail.com> wrote:
> > At least I would expect the toolchain to
> > generate executable code that could be flashed into the device
> > externally,
>
> project options -> output converter -> generate additional output

I know how to drive EW thus far (I use it in my day job, for both
MSP430 and ARM, though the ARM projects are admittedly pre-existing,
not hand-built)... You missed the earlier thread I posted on this
topic. The .HEX files generated by this only work in the simulator -
they don't work when loaded onto the target part. And no it is not a
RAM vs ROM startup issue, because the code actually looks OK and is
certainly org'd at the correct address (and verifies OK when read back
from the part).

And I am not compiling for "generic ARM", I realize now you are
operating under a misconception there - I am building for the specific
device. As a rule - I think almost universally - the other toolchains
I use will automatically select a workable linker config when the
device is selected. I asked IAR tech support to provide a list of
exactly what needs to be edited to build a config from scratch, but I
am thinking it is unlikely I'll be buying the product, since it is
unnecessarily difficult to use compared to the competitors.

Note; it is *very* rare that I need to tweak linker settings manually.
In fact since I wrote my first book on the topic, I doubt that I have
had to edit a linker script myself except maybe relocating a couple of
sections to match changes in MMU configuration, which doesn't often
happen. What is it you do that needs so much manual poking?

I think in fact on 8-bit/16-bit projects I have *NEVER* needed to edit
any linker settings manually. And never on 32-bit projects that use a
big OS like Linux, either (assuming I already had a working bootloader
from somewhere). Only on some middle-sized 32-bit projects where I
have had to do some poking with the way the OS is set up, and in
academic projects like my first book.
From: larwe on 30 Jun 2010 11:33
On Jun 30, 11:12 am, bigbrownbeastie
<bigbrownbeastiebigbrownf...(a)googlemail.com> wrote:
> BTW, why are you using LPC2138 or LPC2106? those parts died out years
> ago for new designs

I only need to build about 75 pieces of this product. I happen to have
half-reels of both LPC2103 and LPC2131 lying about, and roughly 100pcs
of the surplus cellphone LCDs that will be used with it. So it will
save me about $1000 to use these surplus parts vs buying current-
production chips. For a product I'm giving away free of charge, why
not use what I can get?

(Besides, those chips are still on NXP's active list and per their
rep, will be available for the foreseeable future).

Silk purse, sow's ear...
From: Chris H on 30 Jun 2010 12:29
In message <d3484abc-ffd5-44ef-8b8b-2f9f46f6993d(a)b35g2000yqi.googlegroup
s.com>, bigbrownbeastie <bigbrownbeastiebigbrownface(a)googlemail.com>
writes
>> At least I would expect the toolchain to
>> generate executable code that could be flashed into the device
>> externally,
>
>project options -> output converter -> generate additional output

Some people know so much they don't read manuals.......

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/



First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: CMOS Image sensor & Two-wire serial interface
Next: Position independent code with position dependent data ?