Lpc2000

Hi all,

I made a lpc2105 test board. I tied vdd3.3 and v1.8 together and 
provide a 3.3v power suply. Now I can read the part ID and bootloader 
ID. I think it works. But, when I upload a program, I always get the 
message "Code in HEX file exceeds Flash Limitations!" however, the 
ISP Utility still displays an uploading progress bar and then gives 
the successful completion notice. Indeed, nothing is uploaded to the 
chip. The Philips's LPC210X ISP Utility version is 1.0.2 and the 
power Voltage is stable during uploading. The firmware program is got 
from this group and its created HEX file is only 6k(433Bytes after 
loaded into ISP Utility). I compiled it with keil mVision 2. I 
changed the definition ".equ RAM_Limit,  0x40010000" to ".equ 
RAM_Limit,  0x0006000" hoping to reduce the maybe RAM limitation. But 
it doesn't work.
Anybody knows where is the Limitation?
the Crystal is 11.0592MHz and Baudrate is 19200

I will be grateful for any clue.
Best Regards.
Richard.

At 02:28 AM 3/27/04 +0000, you wrote:
>Hi all,
>
>I made a lpc2105 test board. I tied vdd3.3 and v1.8 together and
>provide a 3.3v power suply.

You're running the core at 3.3V?  I did that once by accident and was 
impressed that the chip still ran.  I didn't trust after that of course.

If you are running the core at 3.3V you may no longer have any working 
flash once you attempted to program it (even if it does survive running for 
a period of time).

>Now I can read the part ID and bootloader
>ID. I think it works. But, when I upload a program, I always get the
>message "Code in HEX file exceeds Flash Limitations!" however, the

I don't know where that message is coming from unless hex file you are 
loading isn't doing what you think it is.  Maybe it's located to an invalid 
address?

>ISP Utility still displays an uploading progress bar and then gives
>the successful completion notice. Indeed, nothing is uploaded to the
>chip. The Philips's LPC210X ISP Utility version is 1.0.2 and the
>power Voltage is stable during uploading. The firmware program is got
>from this group and its created HEX file is only 6k(433Bytes after
>loaded into ISP Utility).

What do you mean by "433 bytes after loaded into ISP Utility" ?

>I compiled it with keil mVision 2. I
>changed the definition ".equ RAM_Limit,  0x40010000" to ".equ
>RAM_Limit,  0x0006000" hoping to reduce the maybe RAM limitation. But
>it doesn't work.

This certainly won't help.  From the looks of that, the equate is an 
absolute address and if that's the case the redefinition isn't in the 
address space of any of the micro's memory.

>Anybody knows where is the Limitation?
>the Crystal is 11.0592MHz and Baudrate is 19200

It would effect the flash programming timing if you didn't enter the 
crystal frequency in the ISP SW.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Thanks Robert,
you are right. The flash maybe destroyed by the 3.3v. Now I give the 
chip a 1.8v power and let it run at 1.8v. This time I can upload the 
firmware to the part. Though the message "Code in HEX file exceeds 
Flash Limitations!" still pops up, I think the firmware is uploaded 
into the chip. because I passed the Flash Compare, even I turned off 
the power and then on again. So I guess it do be uploaded.
Thus, I may begin to fine the firmware. But I don't know if my 
firmware executes.
Do you have some start code the simpler the better that only sent a 
string to UART0. this way I can know that the firmware is running.

Best Regards.

richard




--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 02:28 AM 3/27/04 +0000, you wrote:
> >Hi all,
> >
> >I made a lpc2105 test board. I tied vdd3.3 and v1.8 together and
> >provide a 3.3v power suply.
> 
> You're running the core at 3.3V?  I did that once by accident and 
was 
> impressed that the chip still ran.  I didn't trust after that of 
course.
> 
> If you are running the core at 3.3V you may no longer have any 
working 
> flash once you attempted to program it (even if it does survive 
running for 
> a period of time).
> 
> >Now I can read the part ID and bootloader
> >ID. I think it works. But, when I upload a program, I always get 
the
> >message "Code in HEX file exceeds Flash Limitations!" however, the
> 
> I don't know where that message is coming from unless hex file you 
are 
> loading isn't doing what you think it is.  Maybe it's located to an 
invalid 
> address?
> 
> >ISP Utility still displays an uploading progress bar and then gives
> >the successful completion notice. Indeed, nothing is uploaded to 
the
> >chip. The Philips's LPC210X ISP Utility version is 1.0.2 and the
> >power Voltage is stable during uploading. The firmware program is 
got
> >from this group and its created HEX file is only 6k(433Bytes after
> >loaded into ISP Utility).
> 
> What do you mean by "433 bytes after loaded into ISP Utility" ?
> 
> >I compiled it with keil mVision 2. I
> >changed the definition ".equ RAM_Limit,  0x40010000" to ".equ
> >RAM_Limit,  0x0006000" hoping to reduce the maybe RAM limitation. 
But
> >it doesn't work.
> 
> This certainly won't help.  From the looks of that, the equate is 
an 
> absolute address and if that's the case the redefinition isn't in 
the 
> address space of any of the micro's memory.
> 
> >Anybody knows where is the Limitation?
> >the Crystal is 11.0592MHz and Baudrate is 19200
> 
> It would effect the flash programming timing if you didn't enter 
the 
> crystal frequency in the ISP SW.
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to

> chew a radio signal. "
> 
>                          Kelvin Throop, III

At 05:41 AM 3/29/04 +0000, you wrote:
>Thanks Robert,
>you are right. The flash maybe destroyed by the 3.3v. Now I give the
>chip a 1.8v power and let it run at 1.8v. This time I can upload the
>firmware to the part. Though the message "Code in HEX file exceeds
>Flash Limitations!" still pops up, I think the firmware is uploaded
>into the chip. because I passed the Flash Compare, even I turned off
>the power and then on again. So I guess it do be uploaded.
>Thus, I may begin to fine the firmware. But I don't know if my
>firmware executes.
>Do you have some start code the simpler the better that only sent a
>string to UART0. this way I can know that the firmware is running.

I do but it's for a different clock frequency.  Do you have or have access 
to an oscilloscope.  I probably have some pin toggling SW around.  That 
makes for simpler startup and give you a simple debugging tool for later work.

You could then download a known working hex before modifying.  Hmm, I think 
I'll make that available anyway.

Robert


" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Thank you, Robert. Where is it? I have an oscilloscope here and can 
watch the toggled pin wave.
Waiting for you.

Richard



--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 05:41 AM 3/29/04 +0000, you wrote:
> >Thanks Robert,
> >you are right. The flash maybe destroyed by the 3.3v. Now I give 
the
> >chip a 1.8v power and let it run at 1.8v. This time I can upload 
the
> >firmware to the part. Though the message "Code in HEX file exceeds
> >Flash Limitations!" still pops up, I think the firmware is uploaded
> >into the chip. because I passed the Flash Compare, even I turned 
off
> >the power and then on again. So I guess it do be uploaded.
> >Thus, I may begin to fine the firmware. But I don't know if my
> >firmware executes.
> >Do you have some start code the simpler the better that only sent a
> >string to UART0. this way I can know that the firmware is running.
> 
> I do but it's for a different clock frequency.  Do you have or have 
access 
> to an oscilloscope.  I probably have some pin toggling SW around.  
That 
> makes for simpler startup and give you a simple debugging tool for 
later work.
> 
> You could then download a known working hex before modifying.  Hmm, 
I think 
> I'll make that available anyway.
> 
> Robert
> 
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to

> chew a radio signal. "
> 
>                          Kelvin Throop, III

At 04:13 AM 3/30/04 +0000, you wrote:
>Thank you, Robert. Where is it? I have an oscilloscope here and can
>watch the toggled pin wave.
>Waiting for you.

I was going to clean this up a little first, but I think you need it more 
than I need to clean it up ;)

http://www.aeolusdevelopment.com/Files/test1.hex

Fairly simple source.

#include "lpc210x.h"

int main( void)
  {
  int out = 0;
  int i;

  PINSEL0 &= 0;
  IODIR |= 0x100;

  while( 1) {
     if( out == 0) {
          out = 1;
          IOSET = 0x100;
          }
      else {
          out = 0;
          IOCLR = 0x100;
          }
      for( i = 0; i < 100000; i++) {
          }
     }
  return( 0);
  }

This is an old hex of mine.  One of the first test ones I used.  I just 
tested it to make sure it works and it produces about a 0.5 Hz square wave 
with a 10MHz clock.  Should be translatable to most compilers.

I'll make a cleaner version available but in the meantime this should run.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

--- In lpc2000@yahoogroups.com, "painfulcn" <painfulcn@y...> wrote:
> Thanks Robert,
> you are right. The flash maybe destroyed by the 3.3v. Now I give 
the 
> chip a 1.8v power and let it run at 1.8v. This time I can upload 
the 
> firmware to the part. Though the message "Code in HEX file exceeds 
> Flash Limitations!" still pops up, I think the firmware is uploaded 
> into the chip. because I passed the Flash Compare, even I turned 
off 
> the power and then on again. So I guess it do be uploaded.

The ISP program discards all code that is out of the address range of 
the microcontroller flash during program and compare. So if you get 
the above warning message it means that at least part of your code 
from the hex file could not be uploaded even if the compare passed.

The HEX file worked. Thank you. This indicates that my board is able 
to run a program. However, your program is too simple to start. I 
added it into my project but it doesn't work. I'm using ADS 1.2. And 
it need some other files such as vector.s, init.s and *.mcp and so 
on. I think I may set these files wrongly. Do you use ADS and have 
the complete code with which I can compile and debug and add some my 
codes. This will be much helpful for me.

best regards,
Richard

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 04:13 AM 3/30/04 +0000, you wrote:
> >Thank you, Robert. Where is it? I have an oscilloscope here and can
> >watch the toggled pin wave.
> >Waiting for you.
> 
> I was going to clean this up a little first, but I think you need 
it more 
> than I need to clean it up ;)
> 
> http://www.aeolusdevelopment.com/Files/test1.hex
> 
> Fairly simple source.
> 
> #include "lpc210x.h"
> 
> int main( void)
>   {
>   int out = 0;
>   int i;
> 
>   PINSEL0 &= 0;
>   IODIR |= 0x100;
> 
>   while( 1) {
>      if( out == 0) {
>           out = 1;
>           IOSET = 0x100;
>           }
>       else {
>           out = 0;
>           IOCLR = 0x100;
>           }
>       for( i = 0; i < 100000; i++) {
>           }
>      }
>   return( 0);
>   }
> 
> This is an old hex of mine.  One of the first test ones I used.  I 
just 
> tested it to make sure it works and it produces about a 0.5 Hz 
square wave 
> with a 10MHz clock.  Should be translatable to most compilers.
> 
> I'll make a cleaner version available but in the meantime this 
should run.
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to

> chew a radio signal. "
> 
>                          Kelvin Throop, III

At 05:52 AM 4/1/04 +0000, you wrote:
>The HEX file worked. Thank you. This indicates that my board is able
>to run a program. However, your program is too simple to start. I
>added it into my project but it doesn't work. I'm using ADS 1.2. And
>it need some other files such as vector.s, init.s and *.mcp and so
>on. I think I may set these files wrongly. Do you use ADS and have
>the complete code with which I can compile and debug and add some my
>codes. This will be much helpful for me.
>
>best regards,
>Richard

Sorry can't help you there.  There are several gcc startup examples around 
(including mine).  Anyone care to pass along an ADS example?

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

ADS 1.2 example uploaded. Please refer to test1.zip in the Files area.

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 05:52 AM 4/1/04 +0000, you wrote:
> >The HEX file worked. Thank you. This indicates that my board is 
able
> >to run a program. However, your program is too simple to start. I
> >added it into my project but it doesn't work. I'm using ADS 1.2. 
And
> >it need some other files such as vector.s, init.s and *.mcp and so
> >on. I think I may set these files wrongly. Do you use ADS and have
> >the complete code with which I can compile and debug and add some 
my
> >codes. This will be much helpful for me.
> >
> >best regards,
> >Richard
> 
> Sorry can't help you there.  There are several gcc startup examples 
around 
> (including mine).  Anyone care to pass along an ADS example?
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to

> chew a radio signal. "
> 
>                          Kelvin Throop, III

Thanks millions. I downloaded the example and tried it on my board. 
It worked very well. 

Best Regards
Richard

--- In lpc2000@yahoogroups.com, "lpc2100" <lpc2100@y...> wrote:
> ADS 1.2 example uploaded. Please refer to test1.zip in the Files 
area.
> 
> --- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
> wrote:
> > At 05:52 AM 4/1/04 +0000, you wrote:
> > >The HEX file worked. Thank you. This indicates that my board is 
> able
> > >to run a program. However, your program is too simple to start. I
> > >added it into my project but it doesn't work. I'm using ADS 1.2. 
> And
> > >it need some other files such as vector.s, init.s and *.mcp and 
so
> > >on. I think I may set these files wrongly. Do you use ADS and 
have
> > >the complete code with which I can compile and debug and add 
some 
> my
> > >codes. This will be much helpful for me.
> > >
> > >best regards,
> > >Richard
> > 
> > Sorry can't help you there.  There are several gcc startup 
examples 
> around 
> > (including mine).  Anyone care to pass along an ADS example?
> > 
> > Robert
> > 
> > " 'Freedom' has no meaning of itself.  There are always 
> restrictions,
> > be they legal, genetic, or physical.  If you don't believe me, 
try 

> to
> > chew a radio signal. "
> > 
> >                          Kelvin Throop, III

Hello,

thanks a lot for the ADS 1.2 example. I tried to use it and it works
on my board. I use it to debug out of RAM - so I changed the linker
settings. Debugging without interrupts works very good but interrupts
cannot be used. I think I need an other statup-code which installs the
interrupt-vectors to the beginning of the RAM and do a remap to put
them to the correct address. Is this correct? As I am not very
familiar in assembler I wasn't able so far to build a working startup
code by my self.

Does anyone have a startup code for debugging out of RAM with the
correct set interrupt vectors for use with the Toolset "ARM ADS 1.2"?

Best regards,

Markus


--- In lpc2000@yahoogroups.com, "lpc2100" <lpc2100@y...> wrote:
> ADS 1.2 example uploaded. Please refer to test1.zip in the Files
area.
> 
> --- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
> wrote:
> > At 05:52 AM 4/1/04 +0000, you wrote:
> > >The HEX file worked. Thank you. This indicates that my board is 
> able
> > >to run a program. However, your program is too simple to start. I
> > >added it into my project but it doesn't work. I'm using ADS 1.2. 
> And
> > >it need some other files such as vector.s, init.s and *.mcp and
so
> > >on. I think I may set these files wrongly. Do you use ADS and
have
> > >the complete code with which I can compile and debug and add
some 
> my
> > >codes. This will be much helpful for me.
> > >
> > >best regards,
> > >Richard
> > 
> > Sorry can't help you there.  There are several gcc startup
examples 
> around 
> > (including mine).  Anyone care to pass along an ADS example?
> > 
> > Robert
> > 
> > " 'Freedom' has no meaning of itself.  There are always 
> restrictions,
> > be they legal, genetic, or physical.  If you don't believe me,
try 

> to
> > chew a radio signal. "
> > 
> >                          Kelvin Throop, III