Hi Richard,
Referring to this and your earlier question. Here's some advice.
Before you start any of this you have to figure out whether or not
anything you want to use is legally restricted by Freescale. I assume
you have copy of their BSP. If so then you have all the parts you need
to achieve this in your local environment. If you wanted to get this
into the public CVS, you'd have to check with Freescale. Ideally you'd
get them to push the platform out (at least the GPP content).
Alternatively if someone authoritative there says it's okay to publicly
distribute all components of that BSP, and you can get that CC'd to the
list, then it would be possible to include this on the public project
(not withstanding time available to do it).
Note: they can't place restrictions on any GPL (etc) code they have
released to you in the ISO image (for example u-boot/kernel patches).
What they can restrict though is any of their original content that is
not covered by a license that allows you free public re-distribution.
Sorry I can't be more definitive, but I'm not a lawyer and it really
does depend what's in there (I don't know). Aside from the legal side
of it, out of courtesy it's best to email them and try to get them to
help you. I doubt they're really trying to restrict things, I suspect
it's more a question of it not being on their radar to get stuff pushed out.
To integrate the new platform you need to:
* Add the config/platform/_imx53_ platform to a current CVS copy of
the LTIB sources
* Add any new global spec files into the appropriate
dist/lfs-5.1/xxx/ area. You can tell which ones may be missing
when you try to build the BSP, it will complain that it can't find
the spec file if it's missing
* Add any missing BSP content to /opt/freescale/pkgs. To figure out
what GPP/PPP content you're missing run the command: ./ltib
--dltest it will tell you what is not on the GPP. You can then
copy the missing files from your BSP ISO image (pkgs directory) to
/opt/freescale/pkgs (or /opt/ltib/pkgs, they're both in the search
path).
Regards, Stuart
On 30/08/12 02:29, Bair, Richard wrote:
********************************************************************************************************************
1) This is the uboot error I get by just copying the imx directory to the CVS
tree:
Processing: u-boot
====================
Build path taken because: no prebuilt rpm,
Testing network connectivity for gpp
OK GPP: is available
Try u-boot-2009.08.tar.bz2.md5 from the GPP
21:04:08 URL:http://bitshrine.org/gpp/u-boot-2009.08.tar.bz2.md5 [56/56] ->
"u-boot-2009.08.tar.bz2.md5" [1]
Try u-boot-2009.08.tar.bz2 from the GPP
21:05:06 URL:http://bitshrine.org/gpp/u-boot-2009.08.tar.bz2 [8736849/8736849] ->
"u-boot-2009.08.tar.bz2" [1]
Try u-boot-v2009.08-imx_11.09.01.tar.bz2.md5 from the GPP
http://bitshrine.org/gpp/u-boot-v2009.08-imx_11.09.01.tar.bz2.md5:
21:05:06 ERROR 404: Not Found.
Try u-boot-v2009.08-imx_11.09.01.tar.bz2 from the GPP
http://bitshrine.org/gpp/u-boot-v2009.08-imx_11.09.01.tar.bz2:
21:05:07 ERROR 404: Not Found.
Can't get: u-boot-v2009.08-imx_11.09.01.tar.bz2 at ./ltib line 834.
f_buildrpms() returned an error, exiting
traceback:
main:580
Started: Wed Aug 29 21:01:27 2012
Ended: Wed Aug 29 21:05:07 2012
Elapsed: 220 seconds
VERSION : 11.4.1
CVS_VERSION : $Revision: 1.88 $ (Savannah)
PLATFORM : imx51
GNUTARCH : arm
TOOLCHAIN : tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm
TOOLCHAIN_CFLAGS : -O2 -fsigned-char -mfloat-abi=softfp -mfpu=vfp
These packages failed to build:
u-boot
********************************************************************************************************************
2) Next I copy from BSP packages directory (uboot and kernel files) to the CVS
tree (Sources) and I u-boot appear to build and the kernel bulds for quite some
time prior to failing with the following message:
Assembler messages:
Error: unknown architecture `armv7-a'
Error: unrecognized option -march=armv7-a
make[2]: *** [scripts/mod/empty.o] Error 1
make[2]: *** Waiting for unfinished jobs....
HOSTCC scripts/genksyms/parse.o
HOSTLD scripts/genksyms/genksyms
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
error: Bad exit status from /home/rich/imx53/ltib/tmp/rpm-tmp.3262 (%build)
RPM build errors:
Bad exit status from /home/rich/imx53/ltib/tmp/rpm-tmp.3262 (%build)
Build time for kernel-2.6.35: 361 seconds
Failed building kernel-2.6.35
f_buildrpms() returned an error, exiting
traceback:
main:580
Started: Wed Aug 29 21:20:06 2012
Ended: Wed Aug 29 21:27:19 2012
Elapsed: 433 seconds
VERSION : 11.4.1
CVS_VERSION : $Revision: 1.88 $ (Savannah)
PLATFORM : imx51
GNUTARCH : arm
TOOLCHAIN : tc-fsl-x86lnx-armeabi-nptl-4.1.2-3.i386.rpm
TOOLCHAIN_CFLAGS : -O2 -fsigned-char -mfloat-abi=softfp -mfpu=vfp
These packages failed to build:
kernel-2.6.35
Build Failed
On Wed, Aug 29, 2012 at 1:47 PM, Bair, Richard
<[email protected]> wrote:
Hello and thanks for reading!
I'm new to the imx53 QSB and that processor family in general. I have two
questions/issues:
ITEM 1
======
I've successfully installed the CVS update of LTIB on Ubuntu 12.04 based on
support from this list. I was able to successfully build uboot and a 2.6.22-mx
kernel selecting one of the supported platforms (imx31 ads).
The issue I have is that the platform for the imx53 is not available by default in the
CVS and that's my current target. I've been somewhat successful getting the imx53 and
im5x "menu items" to appear when I copy from the BSP tree to the CVS tree.
Specifically, I copy:
/home/rich/imx53/L2.6.35_11.09.01_ER/L2.6.35_11.09.01_ER_source/ltib/config/platform/imx
to the CVS build tree. Again, this allows me to pick "imx Reference Boards" and an
"im5x" platform when I run ./ltib. However, typically uboot will build and the kernel
will fail (I'll post the message later today).
a) Is there a process for integrating imx53 BSP support into the main CVS? How?
The integration may have to come from Freescale due to license
restrictions. Even if you wanted to integrate it, you may not be
allowed to distribute it [to us]. Now that Freescale requires a
login to get to their bsp's, I would not give out whatever I
downloaded unless I had specific permission to do so (that's just me).
Stuart may be able to provide some more insight to the process if
one exists.
b) I also request support on the error message (again, will post near-term)
ITEM 2
======
Once I have built /rootfs, is there a script for copying to the uSD card? So
far I've only created the uSD card using the windows application:
MCIMX535-START-R-BSP-11-09_C.exe.
You may have to dig into your bsp package but for my board there were
instructions on how to format and copy files-systems to flash, sd or
hd. i've use one called /root/diskinit-1.2.sh. Generally these type
of short scripts either tftp the disk image or mount the host nfs
share and the contents are simply copied. Nothing special about it.
Any advice you could offer would be appreciated.
Thanks,
Rich
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
