Prev: CMOS Image sensor & Two-wire serial interface
Next: Position independent code with position dependent data ?
From: bigbrownbeastie on 30 Jun 2010 04:43
I had a play around with mine and found an example for your olimex
board in :

Help -> information Centre
Example Project -> NXP -> LPC2106 -> IAR Kickstart card (same as
olimex)

By the way you have described, you have started an ARM project from
scratch and therefore will have ARM defaults or nothing for linker,
flash loader, debugger setup etc. Since ARM is not so well
standardised these settings won’t work for (almost) anyone’s part.
Since you have not said the linker config file, flash loader setting
or debugger setup macro needed it sounds like you are far from setting
up.

As others pointed out it is worth looking at the examples instead of
trying to build from scratch if you are new to a tool chain/
architecture. It will be like trying to jump in to a single seater
race car for the first time and get angry at it for stalling at the
lights.

As far as I know when you single step to the next statement the
debugger then programs in the next expected address in as a breakpoint
(two hardware breakpoints in ARM7). However for some reason actual
program execution does not reach this point, and this is why it
doesn’t halt (just runs and runs until you hit break and the debugger
reads the PC). This also points to the fact that there is an error
with memory locations....... linker

p.s sales is the most powerful guy in the company as he can call on
any resources that breaks down barriers to potential clients
purchasing. You should just simply send him an email with the issue
and ask to pass it to tech support. I would expect they will help you
get the examples up and running as a first step.

From: larwe on 30 Jun 2010 07:31
On Jun 30, 2:00 am, FreeRTOS info <noem...(a)given.com> wrote:

> You don't say which NXP ARM7 you are trying to use though.  Take a look

Actually I did: "Keil MCB2130 (LPC2138) and an Olimex LPC2106"

> Are you using an up to date version of IAR?

Latest version from their website as of two weeks ago.
From: larwe on 30 Jun 2010 07:42
On Jun 30, 4:25 am, Mike Harrison <m...(a)whitewing.co.uk> wrote:

> It definitely does work, but some of the setup is non-obvious and you will struggle to get there
> from a blank project.

This is very strange. According to an earlier message from their tech
support, the linker (inter alia) is aware of what specific device
you've picked for the project, and for instance will automatically
generate the correct bootloader checksum for devices that require it.
The impression I got from his email is that it is largely automated
(which is after all the only reason why I use an IDE - to get running
quickly without manually editing linker scripts and learning command
line switches).

Grr. It Just Worked with RiDE... the Raisonance guys seem to be more
on the ball. The only thing about RiDE is that it only works with the
RLink debugger, or you can build and load a hex file with the chip's
bootloader.

The 32K eval version of IAR would have been all I need, and I have the
right JTAG adapter for it already, which is why I'm taking a second
bite at it.

> A couple of quick things from memory  - ensure the watchdog is disabled, ensure 'use flash loader'
> is set

I don't enable the WDT myself, I didn't see anything in the IDE that
might be enabling it either. Flash loader is checked.
From: bigbrownbeastie on 30 Jun 2010 10:56
Hi, i am using v5.50 and flash loader is selected automatically, but
linker is not. Don’t see why you do not take the advice from others
here and use the prebuilt example with provided linker file,
flashloader, header files, debugger files etc instead of starting with
a blank project.

EWARM will not complain if the chip is full, the IAR linker will
however complain if you try and fit more code then will fit into
the .ROM region.... two different things.

Just because you are not using external flash does not mean you can
use default 'ARM'. Also you may need to modify the linker file
provided for NXP memory for example place a checksum or boot loader in
specific place etc etc real embedded eng need to understand control of
the linker.

p.s some WDT are enabled by default at start-up, not sure that is the
case for your part but could also cause some issues.
From: bigbrownbeastie on 30 Jun 2010 11:01
> 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
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 ?