Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | Executing Code From RAM
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
Executing Code From RAM - mhasson_alpha - Jun 25 14:05:00 2005
Hello,
I'm evaluating the use of LPC2210 for our development. One thing I
couldn't get from the data sheet, is whether the LPC2210 could run out
of RAM. Does Anyone know if there are any issues such as vector table
relocation restriction or any other issues? In the past, I have used
an MMU (on other Processors) to remap address 0 to another physical
address, which would allow me to store the code anywhere in flash, load
it (upon power up) into ram and execute out of ram. This scheme allows
us to:
1) gain execution speed.
2) utilize flash for code and nv data storage.
3) remote upgrade of the code (2 copies).
Any feedback is greatly appreciated!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
I'm evaluating the use of LPC2210 for our development. One thing I
couldn't get from the data sheet, is whether the LPC2210 could run out
of RAM. Does Anyone know if there are any issues such as vector table
relocation restriction or any other issues? In the past, I have used
an MMU (on other Processors) to remap address 0 to another physical
address, which would allow me to store the code anywhere in flash, load
it (upon power up) into ram and execute out of ram. This scheme allows
us to:
1) gain execution speed.
2) utilize flash for code and nv data storage.
3) remote upgrade of the code (2 copies).
Any feedback is greatly appreciated!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Executing Code From RAM - lpc2100_fan - Jun 27 1:33:00 2005
Hi,
first of all executing from RAM definitely possible. Are you talking
internal or external RAM?
If internal, that gives you max. speed, if external it is a little
slower and it needs to be SRAM (not SDRAM).
You might want to look at the latest LPC2220,
http://www.semiconductors.philips.com/pip/LPC2220FBD144.html
it runs up to 75 MHz and has 64K internal SRAM instead of 16k on the
LPC2210 and afaik pricing is a little higher but not much.
This provides the option to have the code that needs to be fast such
as interrupt service routines or algorithms can be located in the
internal SRAM and other code such as uner interface or language
packages or.. can be in an external Flash.
hth, Bob
--- In lpc2000@lpc2..., "mhasson_alpha" <mhasson_alpha@y...>
wrote:
> Hello,
>
> I'm evaluating the use of LPC2210 for our development. One thing I
> couldn't get from the data sheet, is whether the LPC2210 could run out
> of RAM. Does Anyone know if there are any issues such as vector table
> relocation restriction or any other issues? In the past, I have used
> an MMU (on other Processors) to remap address 0 to another physical
> address, which would allow me to store the code anywhere in flash, load
> it (upon power up) into ram and execute out of ram. This scheme allows
> us to:
> 1) gain execution speed.
> 2) utilize flash for code and nv data storage.
> 3) remote upgrade of the code (2 copies).
>
> Any feedback is greatly appreciated!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
first of all executing from RAM definitely possible. Are you talking
internal or external RAM?
If internal, that gives you max. speed, if external it is a little
slower and it needs to be SRAM (not SDRAM).
You might want to look at the latest LPC2220,
http://www.semiconductors.philips.com/pip/LPC2220FBD144.html
it runs up to 75 MHz and has 64K internal SRAM instead of 16k on the
LPC2210 and afaik pricing is a little higher but not much.
This provides the option to have the code that needs to be fast such
as interrupt service routines or algorithms can be located in the
internal SRAM and other code such as uner interface or language
packages or.. can be in an external Flash.
hth, Bob
--- In lpc2000@lpc2..., "mhasson_alpha" <mhasson_alpha@y...>
wrote:
> Hello,
>
> I'm evaluating the use of LPC2210 for our development. One thing I
> couldn't get from the data sheet, is whether the LPC2210 could run out
> of RAM. Does Anyone know if there are any issues such as vector table
> relocation restriction or any other issues? In the past, I have used
> an MMU (on other Processors) to remap address 0 to another physical
> address, which would allow me to store the code anywhere in flash, load
> it (upon power up) into ram and execute out of ram. This scheme allows
> us to:
> 1) gain execution speed.
> 2) utilize flash for code and nv data storage.
> 3) remote upgrade of the code (2 copies).
>
> Any feedback is greatly appreciated!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )