Help: Linux porting to custom target hw

Help: Linux porting to custom target hw

[Jayanta Das]

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Hello:
 
Can someone point me in the right direction for some good documentation
on the above topic. Following is what I so far have done and what I need
to do.
 
1. Set up host environment based on Fedora Core 4
2. Downloaded 'ppc4xx' tool chain, ELDK and kernel
3. Built U-Boot and uImage
4. Flashed U-Boot on the 2nd flash on the Ocotea board (AMCC440GX
PowerPC)
5. Changed the environment variable for NFS mounted root fs and other
MAC and IP addresses as needed
6. TFTP uImage at 400000
7. bootm and kernel boots all right with root fs mounted on the host
 
I am expecting my hardware based on 440GX end of the month. I told the
HW engineer to follow the peripheral i/f as much possible close to the
ref. design. We are putting 32MB of Flash and 256MB of RAM.
 
I need some guidance so that I can port U-Boot and the kernel (minimal
changes) so that I can bring up the board initially with root fs NFS
minted and later on the RAMDISK.
 
Appreciate the help.
 
Regards.

[-- Attachment #2: Type: text/html, Size: 2863 bytes --]

Help: Linux porting to custom target hw

[Thiago Galesi]

Ok

What is the specific problem you are having?? Based on what you said
all went well, didn't it?

Basically, I think the main thing you have to configure there is flash
location (in the kernel), to be able to use it via MTD.

Booting from NFS or Flash is pretty much effortless, configurable via cmdli=
ne.

Be more specific, so we can help you more...

Thiago

On 5/10/06, Jayanta Das <JDas@alphion.com> wrote:
>
>
> Hello:
>
> Can someone point me in the right direction for some good documentation o=
n
> the above topic. Following is what I so far have done and what I need to =
do.
>
> 1. Set up host environment based on Fedora Core 4
> 2. Downloaded 'ppc4xx' tool chain, ELDK and kernel
> 3. Built U-Boot and uImage
> 4. Flashed U-Boot on the 2nd flash on the Ocotea board (AMCC440GX PowerPC=
)
> 5. Changed the environment variable for NFS mounted root fs and other MAC
> and IP addresses as needed
> 6. TFTP uImage at 400000
> 7. bootm and kernel boots all right with root fs mounted on the host
>
> I am expecting my hardware based on 440GX end of the month. I told the HW
> engineer to follow the peripheral i/f as much possible close to the ref.
> design. We are putting 32MB of Flash and 256MB of RAM.
>
> I need some guidance so that I can port U-Boot and the kernel (minimal
> changes) so that I can bring up the board initially with root fs NFS mint=
ed
> and later on the RAMDISK.
>
> Appreciate the help.
>
> Regards.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>

Help: Linux porting to custom target hw

[Jayanta Das]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

Thanks a lot Thiago.
 
My specific question was what do I need to change in the kernel and
U-Boot source to boot my target HW. Is flash location and the memory map
only thing I need to worry about or I need to do something more. E.g. I
am looking for a document which will specify the LSP specific files.
 
Thanks again for the help.

[-- Attachment #2: Type: text/html, Size: 1007 bytes --]

Help: Linux porting to custom target hw

[Thiago Galesi]

>
> My specific question was what do I need to change in the kernel and U-Boo=
t
> source to boot my target HW. Is flash location and the memory map only th=
ing
> I need to worry about or I need to do something more. E.g. I am looking f=
or
> a document which will specify the LSP specific files.

I'm not very familiar with UBoot but most of the changes will be made
there, not in the kernel (that is, memory size, memory mappings, etc)

AFAIK the only thing you'll have to set up in the kernel is the flash
location, size and configuration (that is, if it is 16 bits, 32 bits,
2x16 bits , etc, etc)

Thiago

Help: Linux porting to custom target hw

[Jayanta Das]

[-- Attachment #1: Type: text/plain, Size: 31 bytes --]

Thiago - thanks for the help.

[-- Attachment #2: Type: text/html, Size: 347 bytes --]