Lpc2000

Hi,
I am trying to write a bootloader for a development kit based on 
LPC2210. I have read some documents, from which I got to know I had to 
initialize the Flash, ARM, the system clock and the also one UART. 
After that, the bootloader should pass some kernel parameters to boot 
the Linux kernel, and also the Machine Type. Can anyone tell me how to 
abtain the Machine type with a algorithm? Any other method to get it?
And what's the Machine Type of LPC2210?

Please recommend me some useful documents on bootloader, thank you very 
much!

Regards,

Kevin

volunteer_sysu wrote:

>Hi,
>I am trying to write a bootloader for a development kit based on 
>LPC2210. I have read some documents, from which I got to know I had to 
>initialize the Flash, ARM, the system clock and the also one UART. 
>After that, the bootloader should pass some kernel parameters to boot 
>the Linux kernel, and also the Machine Type. Can anyone tell me how to 
>abtain the Machine type with a algorithm? Any other method to get it?
>And what's the Machine Type of LPC2210?
>
>  
>
device_id_t deviceIDs [24] = {
      { 2104, 0xFFF0FF12 },
      { 2105, 0xFFF0FF22 },
      { 2106, 0xFFF0FF32 },
      { 2114, 0x0101FF12 },
      { 2119, 0x0201FF12 },
      { 2124, 0x0101FF13 },
      { 2129, 0x0201FF13 },
      { 2131, 0x0002FF01 },
      { 2132, 0x0002FF11 },
      { 2134, 0x0002FF12 },
      { 2136, 0x0002FF23 },
      { 2138, 0x0002FF25 },
      { 2141, 0x0402FF01 },
      { 2142, 0x0402FF11 },
      { 2144, 0x0402FF12 },
      { 2146, 0x0402FF23 },
      { 2148, 0x0402FF25 },
      { 2194, 0x0301FF13 },
      { 2210, 0x0301FF12 },
      { 2290, 0x0301FF12 },
      { 2212, 0x0401FF12 },
      { 2214, 0x0601FF13 },
      { 2292, 0x0401FF13 },
      { 2294, 0x0501FF13 },
   };

>Please recommend me some useful documents on bootloader, thank you very 
>much!
>
>  
>
Look in the User Manual for the processor of interest.  I wrote my IAP / 
ISP programming utility from the info in the LPC2138 User Manual.  You 
have to tinker with it a bit to see what is the manual is telling you, 
it is not quite intuitive (e.g. it does pass you back ascii chars, not 
binary data bytes).

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Thank you!

Regards,

Kevin

--- In lpc2000@yahoogroups.com, Tom Walsh <tom@...> wrote:
>
> volunteer_sysu wrote:
> 
> >Hi,
> >I am trying to write a bootloader for a development kit based on 
> >LPC2210. I have read some documents, from which I got to know I 
had to 
> >initialize the Flash, ARM, the system clock and the also one 
UART. 
> >After that, the bootloader should pass some kernel parameters to 
boot 
> >the Linux kernel, and also the Machine Type. Can anyone tell me 
how to 
> >abtain the Machine type with a algorithm? Any other method to get 
it?
> >And what's the Machine Type of LPC2210?
> >
> >  
> >
> device_id_t deviceIDs [24] = {
>       { 2104, 0xFFF0FF12 },
>       { 2105, 0xFFF0FF22 },
>       { 2106, 0xFFF0FF32 },
>       { 2114, 0x0101FF12 },
>       { 2119, 0x0201FF12 },
>       { 2124, 0x0101FF13 },
>       { 2129, 0x0201FF13 },
>       { 2131, 0x0002FF01 },
>       { 2132, 0x0002FF11 },
>       { 2134, 0x0002FF12 },
>       { 2136, 0x0002FF23 },
>       { 2138, 0x0002FF25 },
>       { 2141, 0x0402FF01 },
>       { 2142, 0x0402FF11 },
>       { 2144, 0x0402FF12 },
>       { 2146, 0x0402FF23 },
>       { 2148, 0x0402FF25 },
>       { 2194, 0x0301FF13 },
>       { 2210, 0x0301FF12 },
>       { 2290, 0x0301FF12 },
>       { 2212, 0x0401FF12 },
>       { 2214, 0x0601FF13 },
>       { 2292, 0x0401FF13 },
>       { 2294, 0x0501FF13 },
>    };
> 
> >Please recommend me some useful documents on bootloader, thank 
you very 
> >much!
> >
> >  
> >
> Look in the User Manual for the processor of interest.  I wrote my 
IAP / 
> ISP programming utility from the info in the LPC2138 User Manual.  
You 
> have to tinker with it a bit to see what is the manual is telling 
you, 
> it is not quite intuitive (e.g. it does pass you back ascii chars, 
not 

> binary data bytes).
> 
> TomW
> 
> -- 
> Tom Walsh - WN3L - Embedded Systems Consultant
> http://openhardware.net, http://cyberiansoftware.com
> "Windows? No thanks, I have work to do..."
> ----------------------------------------------------
>