> Check your setting in the linker field,
"Use memory layout
> from target dialog", if this field is checked, you need to go
> to "target dialog" to see what the memory layout looks like.
> In the software example, I think all the memory layout is
> defined in the target dialog area that you don't need to do
> that again in the linker field.
>
> If you don't have this field checked, you need to specify your
> own R/O and R/W and/or create a scatter file.
Alex, Tom -
I believe this "problem" came about in the eval version of the latest
Keil SW (I'm seeing the problem in version 3.5). Keil has added
scatter capabilities in the latest rev, but this feature is NOT
supported in the eval tool (makes sense when you think about it). In
the eval tool, you can't toggle the "use memory layout from target
dialog" - it's grey'ed out - so you have to add the R/O and R/W
fields to get things working again.
Again, I believe you should only see this issue in the eval tool.
Regards,
Steve
Reply by armdeveloper●February 3, 20072007-02-03
> If you read all messages from this thread,
you'll find more
> information.
I've read all the posts having 'boot' in the title. If there is
an
answer in there, I've missed it.
> If you are using Keil's examples (as posted
in the NXP website), there
> is some information missing in the linker's configuration to
properly
> create executable files. They compile and link without warning, but
> they don't run once programmed in the MCU.
> The problem is that the Project-> Options ->
Linker -? R/O
> base and R/W base are blank.
> By filling with the correct data (R/0 = 0x00000000
R/W = 0x40000000)
> the examples are compiling and running from the flash of the MCB2360.
I'm running gcc. If you read that thread closely, the OP first had
trouble getting his code to boot at all, and then had problems with
running it. The thread morphed into the later problem after he got it
to boot.
> Mehmet Kurnaz wrote
> "After a little fight i solved the bootloder mode problem by your
helps.But now code doesn't execute."
So what did the bootloader mode have to do with it ? I checked MEMMAP
for both the code that runs and the code that does and it has the same
value (0x01).
What am I missing ?
Reply by ariberospot●February 3, 20072007-02-03
Hi:
If you read all messages from this thread, you'll find more information.
If you are using Keil's examples (as posted in the NXP website), there
is some information missing in the linker's configuration to properly
create executable files. They compile and link without warning, but
they don't run once programmed in the MCU.
The problem is that the Project-> Options -> Linker -? R/O
base and R/W base are blank.
By filling with the correct data (R/0 = 0x00000000 R/W = 0x40000000)
the examples are compiling and running from the flash of the MCB2360.
Regards,
Alex
Reply by armdeveloper●February 2, 20072007-02-02
> Hi again.
> After a little fight i solved the bootloder mode problem by your
> helps.But now code doesn't execute.
What did you find. I may have the same problem. I've got a valid
checksum and my P0.14 pin voltages seem to be OK. What else is there ?
Reply by suvidhk●January 18, 20072007-01-18
Hi Tom ,
The dialog box you are talking is not enabled in evaluation version
atleast and hence the problem !!!
It might be that it works in full version only.
I am yet to install license and hence came across it.
Suvidh
Reply by nxp_apps●January 17, 20072007-01-17
Alex,
Check your setting in the linker field, "Use memory layout
from target dialog", if this field is checked, you need to go
to "target dialog" to see what the memory layout looks like.
In the software example, I think all the memory layout is
defined in the target dialog area that you don't need to do
that again in the linker field.
If you don't have this field checked, you need to specify your
own R/O and R/W and/or create a scatter file.
Regards,
Tom
Reply by ariberospot●January 17, 20072007-01-17
Hi Tom:
I downloaded again the examples from the following location:
And check the projects as they come without any change. The fields in
the Linker are indeed blank. Therefore I didn't accidentally change
them.
I would suggest fix the examples and post them again in the NXP website.
Thanks.
Alex.
Reply by nxp_apps●January 17, 20072007-01-17
Alex,
I am glad that you solved the problem. Thanks, Suvidh!
I am afraid that, somehow, you accidentally cleared
these fields on your local machine, or, this could also
happen if you change the device in the device database and
change back, that uVision may clear these fields and nerve
set it back. In the example software, these are very basic
elements we would never forget to leave blank and post it on
the website without testing. I suggest that you download the
example software from our website again and compare with the
one you have.
Regards,
Tom
Reply by ariberospot●January 17, 20072007-01-17
Hi Suvidh:
Thank you for your answer.
The problem was indeed that the Project-> Options -> Linker -? R/O
base and R/W base were blank.
By filling with the correct data (R/0 = 0x00000000 R/W = 0x40000000)
the examples are compiling and running from the flash of the MCB2360.
So all examples need to be updated to correct this.
It was a little misleading the fact that the USBDev example didn't
compile, but the the GPIO and UART did. The USBDev had BOTH R/O and
R/w blank, but the other examples have only R/W blank.
