Imx28 custom board, how to configure mfgtool (xml file) to run Yocto 2.6.36 images?

[edwardtyrrell]

Hi,

I have a custom imx28 board that was running LTIB perfectly using mfgtool. Due to 3rd party developers we are forced to change to the Yocto build system for compiler and other issues. Yocto builds, the issue is getting the build into our NAND (there is no SD). We would like to stick with mfgtool if possible and so far I have modified the ucl.xml file to at least get u-boot running on our hardware. It runs but doesn't load the kernel. Ultimately I'd like not to use u-boot and to follow LTIB's way of booting using a *.sb file with all the necessary loading bits and kernel image inside. Is this possible using bitbake on a 2.6 kernel?

Option 2 would be any information how I could use existing Yocto images and modify mfgtool's xml to load them. My understanding of the inners of u-boot is limited, as mentioned I did get u-boot to load and run via mfgtool but how do I configure mfgtool's xml to get u-boot to find/run/link to the kernel image and also the rootfs.tar.b2z? How should the mtd's/ubi's be handled in the xml file and what goes where?

Any help would be appreciated!

Thanks.

Ed.

[edwardtyrrell · Accepted solution]

All sorted! Board is now running and booting from NAND using u-boot and standard Yocto kernel 2.6.35 - all downloaded using the mfgtool.

Ed

[igorpadykov]

Hi Edward

I am afraid i.MX28 mfg tools is not supported in yocto, however

one can try existing mfg tools and just rename files produces by yocto, then

put them to /files folder, attached ucl.xml shows linux commands.

In general mfg tools firmware is small linux image which can execute

all commands as usual linux. Regarding question:

"get u-boot to find/run/link to the kernel image and also the rootfs.tar.b2z":

for NAND official FSL BSP uses only linux_ivt.sb and rootfs.tar.bz2, for NAND supported only ubifs.

Available kernel boot options one can find in attached Linux Guide

sect.5.1.1 Setting Up Kernel Command Line

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[edwardtyrrell]

Hi,

Found attachments. The xml attachment appears to be the same as what

comes with mfgtool. To narrow things down and I think there's a little

more than changing file names in this respect. In the case of the u-boot

file this was a name change in the xml and it worked, but u-boot looks

for a loadable kernel image at a specific address e.g.

loadaddr=0x42000000 so the kernel image must be resident at that

location. How can the xml file be set up so the kernel image is at the

correct nand address for u-boot to find it? Just changing a file name

for the second file (this would be the kernel) in the xml could put the

image anywhere, or is this incorrect? The next question after getting

this to work would be is there a specific location for the rootfs or is

this taken care of by the kernel providing the rootfs is located at mtdx

or whatever the standard is?

Thanks,

Ed.

[igorpadykov]

Hi Edward

for booting from sd, xml file gives example with

<LIST name="SD(with uboot)"> and in uboot one can use

parameter : root=/dev/mmcblk0p[N] rw rootwait

as described in Linux User Guide.

As for NAND, such configuration is not supported in FSL BSP.

On the other hand there are different approaches to i.MX28 with

NAND which are used on other third parties BSPs, like

http://www.denx.de/wiki/view/DULG/Manual?stickboard=m28evk

Best regards

igor

[edwardtyrrell]

Hi,

Could you send me the attachment, must of been left off?

Thanks,

Ed.