Michael,

> Okay new problem, Crossworks wants to point to the file
> "$(StudioDir)/targets/flash_placement.xml" I do not want\
> it pointing here, I want it to pointto
"$(ProjectDir)/flash_placement.xml"
> The "Project Manager" will not take my input on this. I like having
> all of the project dependent file in the project dir. This little rule
> makes the guy who come after me life just a little better.

Right click on the placement file and click Import. You can also click on
the project node and use Import Memory Map to break the connection to the
system files. You can break any connection by importing.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!

An Engineer's Guide to the LPC2100 Series

Okay I have the solution to the 2nd problem. I just edited the project file
by hand.

Regards
Michael Freeman

-----Original Message-----
From: l... [mailto:l...]On Behalf Of
Bruce Paterson
Sent: Monday, January 11, 2010 10:34 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using sections

Hmmm. Probably created with 1.7 then moved across to 2.0. Maybe this makes
the difference ?

Cheers,

Bruce
----
--

From: l... [mailto:l...] On Behalf
Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:32 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using sections

Are you using ver 2.0 or was the project created with version 1.7? I am
going keep digging until I crack this nut.

Thanks

Michael Freeman

-----Original Message-----
From: l... [mailto:l...]On Behalf
Of Bruce Paterson
Sent: Monday, January 11, 2010 10:25 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

Odd. I had no problem repointing in Properties to my own modified
flash_placement.xml file. I did this at the Project hierarchy level.

I see I used "$(OutDir)/../build/flash_placement.xml", but I can't
recall why. Perhaps I ran into your problem..

Cheers,

Bruce
----

From: l... [mailto:l...] On Behalf
Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:18 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

I got it. Crossworks uses some XML files to set the locations. It could
use some better documentation. After 30 mins of trial and error I pinned
down what works. I got rid off the linker command line stuff and added these
lines to the file "flash_placement.xml"

Okay new problem, Crossworks wants to point to the file
"$(StudioDir)/targets/flash_placement.xml" I do not want it pointing here, I
want it to point to "$(ProjectDir)/flash_placement.xml" The "Project
Manager" will not take my input on this. I like having all of the project
dependent file in the project dir. This little rule makes the guy who come
after me life just a little better.

Regards,

Michael Freeman
Principal Design Engineer
Update Systems, Inc.

Hmmm. Probably created with 1.7 then moved across to 2.0. Maybe this
makes the difference ?

Cheers,

Bruce

________________________________

From: l... [mailto:l...] On Behalf
Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:32 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

Are you using ver 2.0 or was the project created with version 1.7? I am
going keep digging until I crack this nut.

Thanks

Michael Freeman

-----Original Message-----
From: l... [mailto:l...]On
Behalf Of Bruce Paterson
Sent: Monday, January 11, 2010 10:25 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

Odd. I had no problem repointing in Properties to my own
modified flash_placement.xml file. I did this at the Project hierarchy
level.

I see I used "$(OutDir)/../build/flash_placement.xml", but I
can't recall why. Perhaps I ran into your problem....

Cheers,

Bruce

________________________________
From: l... [mailto:l...]
On Behalf Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:18 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

I got it. Crossworks uses some XML files to set the locations.
It could use some better documentation. After 30 mins of trial and error
I pinned down what works. I got rid off the linker command line stuff
and added these lines to the file "flash_placement.xml"

Okay new problem, Crossworks wants to point to the file
"$(StudioDir)/targets/flash_placement.xml" I do not want it pointing
here, I want it to point to "$(ProjectDir)/flash_placement.xml" The
"Project Manager" will not take my input on this. I like having all of
the project dependent file in the project dir. This little rule makes
the guy who come after me life just a little better.

Regards,

Michael Freeman
Principal Design Engineer
Update Systems, Inc.

Are you using ver 2.0 or was the project created with version 1.7? I am
going keep digging until I crack this nut.

Thanks
Michael Freeman

-----Original Message-----
From: l... [mailto:l...]On Behalf Of
Bruce Paterson
Sent: Monday, January 11, 2010 10:25 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using sections

Odd. I had no problem repointing in Properties to my own modified
flash_placement.xml file. I did this at the Project hierarchy level.

I see I used "$(OutDir)/../build/flash_placement.xml", but I can't recall
why. Perhaps I ran into your problem..

Cheers,

Bruce
----
--

From: l... [mailto:l...] On Behalf
Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:18 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using sections

I got it. Crossworks uses some XML files to set the locations. It could
use some better documentation. After 30 mins of trial and error I pinned
down what works. I got rid off the linker command line stuff and added these
lines to the file "flash_placement.xml"

Okay new problem, Crossworks wants to point to the file
"$(StudioDir)/targets/flash_placement.xml" I do not want it pointing here, I
want it to point to "$(ProjectDir)/flash_placement.xml" The "Project
Manager" will not take my input on this. I like having all of the project
dependent file in the project dir. This little rule makes the guy who come
after me life just a little better.

Regards,

Michael Freeman
Principal Design Engineer
Update Systems, Inc.

Odd. I had no problem repointing in Properties to my own modified
flash_placement.xml file. I did this at the Project hierarchy level.

I see I used "$(OutDir)/../build/flash_placement.xml", but I can't
recall why. Perhaps I ran into your problem....

Cheers,

Bruce

________________________________

From: l... [mailto:l...] On Behalf
Of Michael Freeman
Sent: Tuesday, 12 January 2010 3:18 PM
To: l...
Subject: RE: [lpc2000] Crossworks with J-Link loader error using
sections

I got it. Crossworks uses some XML files to set the locations. It could
use some better documentation. After 30 mins of trial and error I pinned
down what works. I got rid off the linker command line stuff and added
these lines to the file "flash_placement.xml"

Okay new problem, Crossworks wants to point to the file
"$(StudioDir)/targets/flash_placement.xml" I do not want it pointing
here, I want it to point to "$(ProjectDir)/flash_placement.xml" The
"Project Manager" will not take my input on this. I like having all of
the project dependent file in the project dir. This little rule makes
the guy who come after me life just a little better.

Regards,

Michael Freeman
Principal Design Engineer
Update Systems, Inc.

I got it. Crossworks uses some XML files to set the locations. It could use
some better documentation. After 30 mins of trial and error I pinned down
what works. I got rid off the linker command line stuff and added these
lines to the file "flash_placement.xml"

Okay new problem, Crossworks wants to point to the file
"$(StudioDir)/targets/flash_placement.xml" I do not want it pointing here, I
want it to point to "$(ProjectDir)/flash_placement.xml" The "Project
Manager" will not take my input on this. I like having all of the project
dependent file in the project dir. This little rule makes the guy who come
after me life just a little better.
Regards,
Michael Freeman
Principal Design Engineer
Update Systems, Inc.
-----Original Message-----
From: l... [mailto:l...]On Behalf Of
Michael Freeman
Sent: Monday, January 11, 2010 9:18 PM
To: l...
Subject: [lpc2000] Crossworks with J-Link loader error using sections

While I am digging on my problem I figure I would throw it out to you guys
too. I am using Crossworks 2.0 and the Segger J-Link tools on a LPC2388. My
project has come along quite nicely until today. I added a SD Card driver
that uses the GPDMA. The DMA uses the USB ram area. I added the following
line of code to my project:

static DWORD DmaBuff[N_BUF][128] __attribute__ ((section(".usbram")));
I added this line to the linker command line settings:

--section-start=.usbram=0x7FD00000

Now here's where the fun starts. I try to run the debugger and the
debugger fails with this error:

Memory erase operation failed: no driver installed for memory range

If I take out the "__attribute__ ((section(".usbram")))" the debugger will
work like a champ. So what am I doing that pisses the debugger off??
Thanks,
Michael Freeman
Principal Design Engineer
Update Systems, Inc.

While I am digging on my problem I figure I would throw it out to you guys
too. I am using Crossworks 2.0 and the Segger J-Link tools on a LPC2388. My
project has come along quite nicely until today. I added a SD Card driver
that uses the GPDMA. The DMA uses the USB ram area. I added the following
line of code to my project:

static DWORD DmaBuff[N_BUF][128] __attribute__ ((section(".usbram")));
I added this line to the linker command line settings:

--section-start=.usbram=0x7FD00000

Now here's where the fun starts. I try to run the debugger and the debugger
fails with this error:

Memory erase operation failed: no driver installed for memory range

If I take out the "__attribute__ ((section(".usbram")))" the debugger will
work like a champ. So what am I doing that pisses the debugger off??
Thanks,
Michael Freeman
Principal Design Engineer
Update Systems, Inc.