Re: [Ltib] MPC8548/8536 targeting Linux 2.6.28 + MPC8536DS (HELP PLEASE)

[Stuart Hughes]

Hi Carolyn,

All the -p does is say "just this package".  The target gets put into
the rootfs NFS area, if you're building a jffs2/ramdisk that will get
rebuilt to include it too.

Regards, Stuart

Reer, Carolyn (SA-1) wrote:
> Stuart:
> I finally got a simple HelloWorld" to run on my target.
> Turns out I was using the wrong gcc.
> I should have been using the powerpc-none-linux-gnuspe-gcc in a
> different DIR and then all the paths were resolved.
> So I guess I am OK targeting MPC 8548 when I really mean MPC 8536. The
> DTB is built for MPC 8536.
> 
> Just one more question:
> Does the embedded application get installed into the Linux image to run
> at boot time?
> $ ./ltib -p helloworld
> Do I build a new image? Or does the '-p' patch the image?
> I found the steps for changing a package on the ltib.org website.
> 
> Next step is adding a daemon.
> Thanks again.
> 
> Carolyn Reer
>  
> 
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden 
> Sent: Thursday, July 29, 2010 2:23 PM
> To: Reer, Carolyn (SA-1)
> Cc: address@hidden
> Subject: Re: [Ltib] MPC8548/8536 targeting Linux 2.6.28 + MPC8536DS
> (HELP PLEASE)
> 
> Hi Carolyn,
> 
> Too many questions at once.  I've tried to answer some in-line
> 
> Reer, Carolyn (SA-1) wrote:
>> Stuart:
>> Are you the same Stuart Hughes of Freescale @ 2005?
>> Just saw that in the LTIB installation that came with MPC8536DS.
>>
> 
> Yes I worked at Freescale, but not since 2009.  I maintain the LTIB
> tool.  The specific BSPs (including kernels) are done by various teams.
> 
>> 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?
>>
> 
> Probably because for that toolchain and/or kernel it's not a valid CPU
> selection.  Generally speaking these come in families so 85xx in this
> case (although that's just a guide).  I suspect in this case this was
> the best optimised too they had for that platform.  If you know the
> toolchain could have better optimisations, you could built it, or ask
> Freescale (or others) to build you one.  A word of caution though, even
> if you did this, it could well be the case that the kernel overrides the
> exact compiler flags to what it thinks is best.  Bottom line, unless you
>  know otherwise, take the default.
> 
> 
>> 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.
>>
> 
> Did you look at the example package for this?
> 
> // leave unpacked so you can tinker with it
> $ ./ltib -p helloworld -m prep
> 
> // build and install on the rootfs, note you can re-run
> // this after edits without rebooting your target it NFS
> $ ./ltib -p helloworld
> 
> 
>> 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.
> 
> See above, you don't need to mess with include paths, they are setup for
> you.
> 
>> 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?
> 
> I don't understand the question.  What do you need them for?  If the
> thing you're building on the target needs them on the target, then the
> thing you're building should enabled them for the target build and
> installed them before 'thing'
> 
> Please tell me what you're trying to actually do and why.  I've no idea
> what you're real objective is here.
> 
>> 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.
>>
> 
> No worries,
> 
>> Carolyn Reer
> 
> I'd remove this, as the internet is crawling with data miners.
> 
> Regards, Stuart
> 
>>
>> -----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
>>>
>>>
>>>
>>> _______________________________________________
>>> LTIB home page: http://ltib.org
>>>
>>> Ltib mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>>
> 
>