cross compiling for OMAP2430

cross compiling for OMAP2430

[Budhee Jamaich]

Hello -

I need to cross compile user space applications to OMAP2430.

The applications have standard GNU build scripts (i.e. configure...).

How do I approach this task  ? is it all about finding the right
configure parameters ?

Are there Open Source solutions / papers on the subject or do I have
to purchase commercial environments (...Montavista...) ?

Much Thanks.
Budhee

Re: cross compiling for OMAP2430

[Philip Balister]

Take a look at open embedded. http://www.openembedded.org. I use it to 
create images for the OSK board. Unfortunately, I do not have any 2430 
based hardware to test with.

Philip

Budhee Jamaich wrote:
> Hello -
> 
> I need to cross compile user space applications to OMAP2430.
> 
> The applications have standard GNU build scripts (i.e. configure...).
> 
> How do I approach this task  ? is it all about finding the right
> configure parameters ?
> 
> Are there Open Source solutions / papers on the subject or do I have
> to purchase commercial environments (...Montavista...) ?
> 
> Much Thanks.
> Budhee
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> 

Re: cross compiling for OMAP2430

[Budhee Jamaich]

Hello Philip ^^

On 4/16/07, Philip Balister <philip@balister.org> wrote:
> Budhee Jamaich wrote:
> > I need to cross compile user space applications to OMAP2430.
> > The applications have standard GNU build scripts (i.e. configure...).
> Take a look at open embedded. http://www.openembedded.org. I use it to
> create images for the OSK board. Unfortunately, I do not have any 2430
> based hardware to test with.

Hm. Do I have to use such environment ? Can't I just choose the right
./configure parameter and the application will be built for the target ?

Much Thanks
Budhee

Re: cross compiling for OMAP2430

[nishanth menon]

Hi Budhee,

On 4/16/07, Budhee Jamaich <budheej@gmail.com> wrote:
> Hm. Do I have to use such environment ? Can't I just choose the right
> ./configure parameter and the application will be built for the target ?
you may, but you need to look at a case by case basis. for example, if
u want to cross compile for ARM, busybox will need "make ARCH=ARM
CROSS_COMPILE=arm-none-linux-gnueabi-" etc.. some apps dont know the
existance of CROSS_COMPILE.. and they'd use CC for the same, in which
case u'd have to do "make CC=arm-none-linux-gnueabi-gcc"..

personally, i hand compile most of my own stuff, some places, i'd have
to hack arnd "arm-unaware" apps.. but most places it is
straightforward.

I put some links in this discussion thread:
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008841.html
the compiler link and busybox build info might be useful.

Regards,
Nishanth Menon

RE: cross compiling for OMAP2430

[Kipisz, Steven]

Hi Budhee,
I agree with Nishanth.  I usually try to ./configure --help to see if
cross compiling is available.  If so, you typically do
./configure --target=arm-linux --build=i386-pc-linux --host=arm-linux

Sometimes it works...sometimes it doesnn't.

Another trick is
CC=arm-linux-gcc ./configure

After doing that, check the Makefile to see if CC really is set
correctly.  If all the above fail, then it is time to hand edit
Makefiles or use environments like openembedded.

Steve K.

-----Original Message-----
From: linux-omap-open-source-bounces+s-kipisz2=ti.com@linux.omap.com
[mailto:linux-omap-open-source-bounces+s-kipisz2=ti.com@linux.omap.com]
On Behalf Of nishanth menon
Sent: Tuesday, April 17, 2007 8:16 AM
To: Budhee Jamaich
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: cross compiling for OMAP2430

Hi Budhee,

On 4/16/07, Budhee Jamaich <budheej@gmail.com> wrote:
> Hm. Do I have to use such environment ? Can't I just choose the right
> ./configure parameter and the application will be built for the target
?
you may, but you need to look at a case by case basis. for example, if
u want to cross compile for ARM, busybox will need "make ARCH=ARM
CROSS_COMPILE=arm-none-linux-gnueabi-" etc.. some apps dont know the
existance of CROSS_COMPILE.. and they'd use CC for the same, in which
case u'd have to do "make CC=arm-none-linux-gnueabi-gcc"..

personally, i hand compile most of my own stuff, some places, i'd have
to hack arnd "arm-unaware" apps.. but most places it is
straightforward.

I put some links in this discussion thread:
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/0088
41.html
the compiler link and busybox build info might be useful.

Regards,
Nishanth Menon
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

Re: cross compiling for OMAP2430

[Budhee Jamaich]

Hi Steve and Nishanth,

On 4/17/07, Kipisz, Steven <s-kipisz2@ti.com> wrote:
> Hi Budhee,
> I agree with Nishanth.  I usually try to ./configure --help to see if
> cross compiling is available.  If so, you typically do
> ./configure --target=arm-linux --build=i386-pc-linux --host=arm-linux

can you plz explain what is each flag ? let's say my host (where I compile
the application) is a normal i386 PC, and the target is OMAP2430,
then are these the correct flags ?

> Another trick is
> CC=arm-linux-gcc ./configure

why do I need to use arm-linux-gcc ? can't the standard gcc compile for arm ?

Thank YOu
Budhee

Re: cross compiling for OMAP2430

[nishanth menon]

Hi Budhee,

On 4/17/07, Budhee Jamaich <budheej@gmail.com> wrote:
> can you plz explain what is each flag ?
please read the help: ./configure --help, also google can be pretty
informative in such doubts. :)

>let's say my host (where I compile
> the application) is a normal i386 PC, and the target is OMAP2430,
> then are these the correct flags ?
yup.

> why do I need to use arm-linux-gcc ? can't the standard gcc compile for arm ?
u can if ur gcc generates ARM instructions. please do use google..
that would be more informative.
Regards,
Nishanth Menon

RE: cross compiling for OMAP2430

[Kipisz, Steven]

Use Google.

Also you should get a book or two on Embedded Linux.  The O'Reilly book
with the name something like "Building Embedded Linux Systems" or
another book with a name like "Embedded Linux Primer" that I think is
from Prentice Hall.  I've loaned out mine so I don't have the exact
titles or publishers.

Steve K.

-----Original Message-----
From: Budhee Jamaich [mailto:budheej@gmail.com] 
Sent: Tuesday, April 17, 2007 8:52 AM
To: Kipisz, Steven
Cc: nishanth menon; linux-omap-open-source@linux.omap.com
Subject: Re: cross compiling for OMAP2430

Hi Steve and Nishanth,

On 4/17/07, Kipisz, Steven <s-kipisz2@ti.com> wrote:
> Hi Budhee,
> I agree with Nishanth.  I usually try to ./configure --help to see if
> cross compiling is available.  If so, you typically do
> ./configure --target=arm-linux --build=i386-pc-linux --host=arm-linux

can you plz explain what is each flag ? let's say my host (where I
compile
the application) is a normal i386 PC, and the target is OMAP2430,
then are these the correct flags ?

> Another trick is
> CC=arm-linux-gcc ./configure

why do I need to use arm-linux-gcc ? can't the standard gcc compile for
arm ?

Thank YOu
Budhee

Re: cross compiling for OMAP2430

[Budhee Jamaich]

Thank You Very much !

My company actually bought these two books... still.. I cannot understand
why arm-linux-gcc is needed - can't standard gcc compile for the ARM ?
doesn't gcc have arm code-generator back-end ?
I cannot find this in google...

Thank You
Budhee

Re: cross compiling for OMAP2430

[nishanth menon]

Hi Budhee,
On 4/17/07, Budhee Jamaich <budheej@gmail.com> wrote:
> My company actually bought these two books... still.. I cannot understand
> why arm-linux-gcc is needed - can't standard gcc compile for the ARM ?
> doesn't gcc have arm code-generator back-end ?
> I cannot find this in google...
good place to ask: http://vger.kernel.org/vger-lists.html#linux-gcc

Further, from my brief understanding: it depends on the gcc
distribution you use, each have thier own "pet" patches applied and
may not support all platforms, for example, my RH Fedora5 PC has gcc
v4.1.1, but if i do a "-dumpmachine" it tells me:i386-redhat-linux.
the codesourcery's gcc distrib tells me "arm-none-linux-gnueabi"
Imagine a single gcc distribution supporting ARM,PPC,i386,i686 and all
other numerous versions (dont forget micro-controller ports)... it
will be huge and completely un-necessary in 90% of users. yes, the
backend generator is used for each port providing a uniform interface
for all platforms, but packaging it together.. it depends on the
target audience.

Further, the kernel is also tied with stable version of gcc, so
sometimes, using the old gcc versions or the bleeding edge gcc might
not work..

Regards,
Nishanth Menon

One NAND Booting

[sathish.madhava]

Hi All,
 
I am trying to do One NAND Booting on OMAP2430sdp.
I found that I need to have X-loader image which fits in 1KB of Boot RAM.
Currently the X-loader code i have is around 6KB, can somebody suggest where to get this 1KB size X-loader Code.
 
 
Thanks
-Sathish

RE: cross compiling for OMAP2430

[Woodruff, Richard]

Gcc is a large thing which supports a lot.  The ownership of sub pieces
is distributed around.  You likely find many architectures are not in
phase with each other.  Places where specifications are ambiguous you
will find sub architecture even interpret things differently.  For
example is a 'char' signed or not is different across gcc.  Thus in
practice you will likely  match your tool set with an architecture and
perhaps even a specific kernel version.

Some commercial compilers which have central control do more of what
your imagining.  Even there you likely only get libraries for one
architecture at a time, not for every target.  That is unless you pay
for it.  GCC is free and decentralized. It is impressive in what it can
do given that.

Regards,
Richard W. 

> -----Original Message-----
> From: 
> linux-omap-open-source-bounces+r-woodruff2=ti.com@linux.omap.c
> om 
> [mailto:linux-omap-open-source-bounces+r-woodruff2=ti.com@linu
> x.omap.com] On Behalf Of Budhee Jamaich
> Sent: Tuesday, April 17, 2007 9:30 AM
> To: Kipisz, Steven; nishanth menon
> Cc: linux-omap-open-source@linux.omap.com
> Subject: Re: cross compiling for OMAP2430
> 
> Thank You Very much !
> 
> My company actually bought these two books... still.. I 
> cannot understand why arm-linux-gcc is needed - can't 
> standard gcc compile for the ARM ?
> doesn't gcc have arm code-generator back-end ?
> I cannot find this in google...
> 
> Thank You
> Budhee
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> 

RE: One NAND Booting

[Woodruff, Richard]

> I am trying to do One NAND Booting on OMAP2430sdp.
> I found that I need to have X-loader image which fits in 1KB 
> of Boot RAM.
> Currently the X-loader code i have is around 6KB, can 
> somebody suggest where to get this 1KB size X-loader Code.

You likely don't need this.  The xloading on the TI site can already
boot from OneNAND on the 2430sdp.

Mask ROM code runs and loads code from NAND into SRAM to be executed.
You are limited by your SRAM space (as used by the mask ROM) and block
size of the flash device not the XIP space in the OneNAND.

Regards,
Richard W.

RE: One NAND Booting

[sathish.madhava]

Hi,
My requirement is to use entirely OneNAND and not to use NAND.,
if thats the case how do i fit the X-loader code in 1KB of OneNAND BootRAM area.
 
-Sathish

________________________________

From: Woodruff, Richard [mailto:r-woodruff2@ti.com]
Sent: Tue 4/17/2007 8:55 PM
To: Sathish kumar tekal Sethu madhava rao (WT01 - Wireless Networks and Devices); linux-omap-open-source@linux.omap.com
Subject: RE: One NAND Booting



> I am trying to do One NAND Booting on OMAP2430sdp.
> I found that I need to have X-loader image which fits in 1KB
> of Boot RAM.
> Currently the X-loader code i have is around 6KB, can
> somebody suggest where to get this 1KB size X-loader Code.

You likely don't need this.  The xloading on the TI site can already
boot from OneNAND on the 2430sdp.

Mask ROM code runs and loads code from NAND into SRAM to be executed.
You are limited by your SRAM space (as used by the mask ROM) and block
size of the flash device not the XIP space in the OneNAND.

Regards,
Richard W.

RE: One NAND Booting

[Woodruff, Richard]

Look at the archive for this group.

 

I posted the exact steps for burning into OneNAND such that it boots.
If you follow those you will boot on the SDP as I can today.

 

You are free to create another method if you must, but it doesn't seem
necessary.

 

Regards,

Richard W.

 

________________________________

From: sathish.madhava@wipro.com [mailto:sathish.madhava@wipro.com] 
Sent: Tuesday, April 17, 2007 11:09 AM
To: Woodruff, Richard; linux-omap-open-source@linux.omap.com
Subject: RE: One NAND Booting

 

Hi,

My requirement is to use entirely OneNAND and not to use NAND.,

if thats the case how do i fit the X-loader code in 1KB of OneNAND
BootRAM area.

 

-Sathish

________________________________

From: Woodruff, Richard [mailto:r-woodruff2@ti.com]
Sent: Tue 4/17/2007 8:55 PM
To: Sathish kumar tekal Sethu madhava rao (WT01 - Wireless Networks and
Devices); linux-omap-open-source@linux.omap.com
Subject: RE: One NAND Booting

> I am trying to do One NAND Booting on OMAP2430sdp.
> I found that I need to have X-loader image which fits in 1KB
> of Boot RAM.
> Currently the X-loader code i have is around 6KB, can
> somebody suggest where to get this 1KB size X-loader Code.

You likely don't need this.  The xloading on the TI site can already
boot from OneNAND on the 2430sdp.

Mask ROM code runs and loads code from NAND into SRAM to be executed.
You are limited by your SRAM space (as used by the mask ROM) and block
size of the flash device not the XIP space in the OneNAND.

Regards,
Richard W.


The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

www.wipro.com
	

RE: One NAND Booting

[Kyungmin Park]

If you want to boot with OneNAND without other tools such as CSST(?), you can do
it.

You should make a 1KB xloader binary by only initialize the SDRAM in xloader.
The others are done by the second bootloader such as U-Boot.

Now the apollon board based on OMAP2420 boots with this method. Note that it is
not yet tested with omap2430sdp. But I think it's working.

+-----------+-----------+-------------------------------------+
| xloader | dummy | U-boot < (128KB - 2KB)  |
+-----------+-----------+-------------------------------------+
   1KB        1KB

The xloader only does following things.

1. cpu1136 initialization
2. SDRAM initialization (SDRC)
3. copy U-boot to RAM
4. jump to U-boot

Note; you never runs SDRAM initialization in U-boot. it will be hang.

Please refer to this URL.
http://source.mvista.com/git/gitweb.cgi?p=xloader.git;a=summary 

Thank you,
Kyungmin Park

> -----Original Message-----
> From: linux-omap-open-source-bounces@linux.omap.com 
> [mailto:linux-omap-open-source-bounces@linux.omap.com] On 
> Behalf Of Woodruff, Richard
> Sent: Wednesday, April 18, 2007 2:01 AM
> To: sathish.madhava@wipro.com; linux-omap-open-source@linux.omap.com
> Subject: RE: One NAND Booting
> 
> Look at the archive for this group.
> 
>  
> 
> I posted the exact steps for burning into OneNAND such that it boots.
> If you follow those you will boot on the SDP as I can today.
> 
>  
> 
> You are free to create another method if you must, but it doesn't seem
> necessary.
> 
>  
> 
> Regards,
> 
> Richard W.
> 
>  
> 
> ________________________________
> 
> From: sathish.madhava@wipro.com [mailto:sathish.madhava@wipro.com] 
> Sent: Tuesday, April 17, 2007 11:09 AM
> To: Woodruff, Richard; linux-omap-open-source@linux.omap.com
> Subject: RE: One NAND Booting
> 
>  
> 
> Hi,
> 
> My requirement is to use entirely OneNAND and not to use NAND.,
> 
> if thats the case how do i fit the X-loader code in 1KB of OneNAND
> BootRAM area.
> 
>  
> 
> -Sathish
> 
> ________________________________
> 
> From: Woodruff, Richard [mailto:r-woodruff2@ti.com]
> Sent: Tue 4/17/2007 8:55 PM
> To: Sathish kumar tekal Sethu madhava rao (WT01 - Wireless 
> Networks and
> Devices); linux-omap-open-source@linux.omap.com
> Subject: RE: One NAND Booting
> 
> > I am trying to do One NAND Booting on OMAP2430sdp.
> > I found that I need to have X-loader image which fits in 1KB
> > of Boot RAM.
> > Currently the X-loader code i have is around 6KB, can
> > somebody suggest where to get this 1KB size X-loader Code.
> 
> You likely don't need this.  The xloading on the TI site can already
> boot from OneNAND on the 2430sdp.
> 
> Mask ROM code runs and loads code from NAND into SRAM to be executed.
> You are limited by your SRAM space (as used by the mask ROM) and block
> size of the flash device not the XIP space in the OneNAND.
> 
> Regards,
> Richard W.
> 
> 
> The information contained in this electronic message and any 
> attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged 
> information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender 
> immediately and
> destroy all copies of this message and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence 
> of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
> 
> www.wipro.com
> 	
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> 
>