Selecting toolchains (was Re: [Ltib] MPC8548/8536 targeting Linux 2.6.28 + MPC8536DS (HELPPLEASE))

[Stuart Hughes]

Hi Carolyn,

To set these (yours may differ slightly):

$ ./ltib -m config

scroll down one line past 'Toolchain selection' and press enter.  There
you see which toolchains are selectable for that platform.  On my
current BSP:

│      (X) gcc-4.3.2 eglibc-2.8 multilib PowerPC 4.3-74
       ( ) gcc-4.2.1 eglibc-2.5 multilib PowerPC toolchain
       ( ) Custom

Move the cursor down and select custom and press enter.  You'll then see:

()  Enter the custom toolchain path. (NEW)
()  Enter the toolchain prefix. (NEW)
()  Enter any CFLAGS for gcc/g++

You can then use your down arrow and enter to select each in turn and
fill out.  The help screens give clues as to values.

Note: although many toolchains will work (CodeSourcery, Freescales) some
may not depending on how they're built.

Note also, the toolchain path should be one level above where the
binaries are.  Finally, toolchain prefix should be powerpc-linux-gnu-
i.e. the bit before gcc/g++ etc.


Regards, Stuart


Reer, Carolyn (SA-1) wrote:
> According to http://www.ltib.org/documentation-LtibFaq
> --- Choose your toolchain
> Toolchain (gcc-3.4/glibc-2.3.4 e500 (DPFP))  --->
> (-mcpu=8548 -mhard-float -mfloat-gprs=double) Enter any CFLAGS for gcc
> This entry allows you to choose from the available list of toolchains.
> The choice you make will drive the CFLAGS entry which follows. You may
> of course override the value for CGLAGS. When ltib runs, it will
> download (if required) and install the toolchain you have selected it 
> 
> Note that every platform includes an option to select a custom
> toolchain. This allows you to use most standard cross compilers that are
> your system. The most common use of this option is to test new
> toolchains before wiring them in to the platforms toolchain selection
> list permanently. When using a custom toolchain, you'll be prompted for:
> 
> 
> toolchain path : This is the absolute base path name of your toolchain.
> For instance, if wanted to use:
> /opt/mtwk/usr/local/gcc-3.4.3-glibc-2.3.4/arm-linux/bin/arm-linux-gcc
> the correct entry would be:
> /opt/mtwk/usr/local/gcc-3.4.3-glibc-2.3.4/arm-linux 
> cross tools prefix : This is the value that prefixes all the standard
> toolchain executables for your given cross toolchain. So for the example
> just given, this would be powerpc-linux- 
> CFLAGS : Normally this can be left blank
> 
> How do I set the 'toolchain path' and the 'cross tools prefix'?
> Are these set in the MAKEFILE? Or in the LTIB configuration?
> 
> Carolyn Reer
> 
> 201-405-2992
> 
>  
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This communication is intended only for use by the addressees named
> herein and may contain business confidential and/or legally privileged
> information. If you are not the intended recipient of this e-mail, you
> are hereby notified that any dissemination, distribution, disclosure or
> copying of this e-mail and its contents is strictly prohibited. If you
> have received this e-mail in error, kindly notify the sender by replying
> to this message. In addition, please permanently delete the message and
> any attachments without copying or disclosing the contents. Thank you
> for your cooperation.
> 
> 
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On Behalf Of Reer,
> Carolyn (SA-1)
> Sent: Wednesday, July 28, 2010 12:50 PM
> To: Stuart Hughes
> Cc: address@hidden
> Subject: RE: [Ltib] MPC8548/8536 targeting Linux 2.6.28 + MPC8536DS
> (HELPPLEASE)
> 
> Stuart:
> Are you the same Stuart Hughes of Freescale @ 2005?
> Just saw that in the LTIB installation that came with MPC8536DS.
> 
> I am targeting MPC8536DS. 
> My LTIB configuration is:
> Toolchain (gcc-4.3.2 eglibc-2.8 single library e55v2 toolchain) CFLAGS
> for gcc/g++:
> (-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double) When I
> changed to -mcpu=8536 I received error message from LTIB that
> 8536 is a "Bad value"
> Changed back to 8548, kernel built OK.
> The kernel is selected as (Linux 2.6.28 + MPC8536DS patch)
> Q1) Why can't I select -mcpu=8436?
> 
> At this time, I am just TFTP'ing my kernel image & dtb to RAM and
> booting from there.
> Ultimately we will boot from SD.
> Using NFS my host (Fedora 12) ltib/rootfs directory is mounted as the
> MPC8536 root file system.
> I am trying to build a simple "Hello world" application.
> 
> I was having problems with the include files. The directories under
> /opt/freescale/usr/local/gcc-4.3.74 . . . were mess.
> Had to split and hard code ./gcc and ./as and library and include paths.
> 
> Default wanted to go back to f12 fedora paths.
> Also had to move .h files around to satisfy the compiler. Stdio.h
> couldn't find all its components.
> Q2) I was wondering if I have to split out the linker command also so
> that the gcc-4.3.74 path is used?
> 
> The gcc.log file shows
> --with-gmp=/usr/src/redhat/BUILD/csl-tc-4.3.74/host-libs/usr
> --with-mpfr=/usr/src/redhat/BUILD/csl-tc-4.3.74/host-libs/usr
> --with-cpu=8548 
> 
> Q3) I see the gmp & mpfr rpm files are in ltib subdirectories. F12 won't
> let me install them on the host.
> Do they have to be included in the ltib build? Will this install them on
> my host system?
> 
> Q4) I think I have resolved my 'service' question. Once I can build the
> daemon, I edit the inetd.conf file and restart inetd via kill HUP.
> 
> Thanks for all your help.
> 
> Carolyn Reer
> 
> 201-405-2992
> 
> 
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden
> Sent: Tuesday, July 27, 2010 2:11 PM
> To: Reer, Carolyn (SA-1)
> Cc: address@hidden
> Subject: Re: [Ltib] MPC8548 targeting Linux 2.6.28 + MPC8536DS (HELP
> PLEASE)
> 
> Hi Carolyn,
> 
> What problem are you having? is it with the 8548 or 8536? is it the
> kernel or another package? could you post some output.  Am I right in
> thinking you got the 8536 LTIB and did a -m distclean and are now
> targeting the 8548? If so you're better pulling the latest from LTIB
> CVS, that way at least it's possible this list may be able to help you,
> otherwise you'll need to ask Freescale.
> 
> So far as the autobuilder goes, the output sent to the list is the same
> as that at zee2.com, except there's an expanded full list available
> there, as well as a by-date selection.
> 
> You should never need to run --continue unless developing.
> 
> To start/stop services you configure these with ./ltib --configure and
> use the "Target System Configuration".  Options present depending on the
> packages/options you have selected elsewhere.
> 
> So far as IP tables goes, there's no specific start-up in LTIB for that
> AFAIK.  So you need to add the appropriate iptables config file and run
> iptables restore pointing to it from rc.local.
> 
> Regards, Stuart
> 
> Reer, Carolyn (SA-1) wrote:
>> I am STILL having problems with LTIB and the resultant Linux kernel.
>>
>> My LTIB is dated 13-MAR-09. Came with the Freescale MPC8536DS 
>> development system. I am building for the MPC8548 targeting Linux
> 2.6.28
>> + MPC8536DS patch. Should I download a newer LTIB? I see the
> autobuilder
>> says the MPC8548 builds fail.
>>
>> The autobuilder emails link me to zee2.com which links me back to 
>> ltib.org.
>>
>> I always get some king of build error.
>> I run ./ltib -continue to circumvent as many errors as possible
> although
>> it still aborts prematurely.
>>
>> I have been unsuccessful getting any applications to run on the
> target.
>> Right now I am trying to add a daemon to the system services but don't
> 
>> have a "service" command. I can't use the "iptables" command because I
> 
>> don't have "ip_tables" file. The kernel is able to start inetd,
> syslogd,
>> etc when it boots.
>>
>> What command should I be using to start, stop, restart services ?
>>
>> Carolyn Reer
>>
>> 201-405-2992
>>
>>
>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
>>
>