ls1021atwr: Missing uboot ramdisk with sdk 1.9

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ls1021atwr: Missing uboot ramdisk with sdk 1.9

Jump to solution
2,574 Views
vsiles
Senior Contributor I

Hi,

I'm using a LS1021atwr board, with NXP SDK 1.9

Following the documentation, I'm trying to boot Linux from the Flash.

Both build instructions and Ramdisk Deployment from TFTP refer to a

  • fsl-image-<machine>.ext2.gz.u-boot - ramdisk image that can be loaded with U-Boot

But in my build folder, I only get a fsl-image-full-ls1021atwr-20160321145603.rootfs.tar.gz with is refused by bootm with

Wrong Ramdisk Image Format

Ramdisk image is corrupt or invalid

How can I procude such a gz.u-boot file ?

Best,

Vincent

Labels (1)
Tags (2)
1 Solution
1,968 Views
vsiles
Senior Contributor I

It seems that patching the IMAGE_FSTYPES_qoriq in fsl-image-full.bb to add ext2.gz.u-boot  did the trick, I got the file generated. i'll try to flash it. Thanks for the information !

View solution in original post

14 Replies
1,968 Views
manjunathjoshi
Contributor V

Hi all,

I got this error when i tried to build ext3.gz

ERROR: Error executing a python function in /home/ravi/pga/svn/trunk/software/imx/filesystem/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-multimedia_backup.bb:

The stack trace of python calls that resulted in this exception/failure was:

File: 'do_rootfs', lineno: 17, function: <module>

     0013:    # generate final images

     0014:    create_image(d)

     0015:

     0016:

*** 0017:do_rootfs(d)

     0018:

File: 'do_rootfs', lineno: 14, function: do_rootfs

     0010:    # generate rootfs

     0011:    create_rootfs(d)

     0012:

     0013:    # generate final images

*** 0014:    create_image(d)

     0015:

     0016:

     0017:do_rootfs(d)

     0018:

File: '/home/ravi/pga/svn/trunk/software/imx/filesystem/sources/poky/meta/lib/oe/image.py', lineno: 337, function: create_image

     0333:        execute_pre_post_process(self.d, post_process_cmds)

     0334:

     0335:

     0336:def create_image(d):

*** 0337:    Image(d).create()

     0338:

     0339:if __name__ == "__main__":

     0340:    """

     0341:    Image creation can be called independent from bitbake environment.

File: '/home/ravi/pga/svn/trunk/software/imx/filesystem/sources/poky/meta/lib/oe/image.py', lineno: 315, function: create

     0311:        execute_pre_post_process(self.d, pre_process_cmds)

     0312:

     0313:        self._remove_old_symlinks()

     0314:

*** 0315:        image_cmd_groups = self._get_imagecmds()

     0316:

     0317:        for image_cmds in image_cmd_groups:

     0318:            # create the images in parallel

     0319:            nproc = multiprocessing.cpu_count()

File: '/home/ravi/pga/svn/trunk/software/imx/filesystem/sources/poky/meta/lib/oe/image.py', lineno: 285, function: _get_imagecmds

     0281:                localdata.setVar('OVERRIDES', '%s:%s' % (type, old_overrides))

     0282:                bb.data.update_data(localdata)

     0283:                localdata.setVar('type', type)

     0284:

*** 0285:                cmds.append("\t" + localdata.getVar("IMAGE_CMD", True))

     0286:                cmds.append(localdata.expand("\tcd ${DEPLOY_DIR_IMAGE}"))

     0287:

     0288:                if type in cimages:

     0289:                    for ctype in cimages[type]:

Exception: TypeError: cannot concatenate 'str' and 'NoneType' objects

ERROR: Function failed: do_rootfs

ERROR: Logfile of failure stored in: /home/ravi/pga/svn/trunk/software/imx/filesystem/build_ramdisk/tmp/work/imx6qsabresd-poky-linux-gnueabi/fsl-image-multimedia/backup-r0/temp/log.do_rootfs.14668

ERROR: Task 7 (/home/ravi/pga/svn/trunk/software/imx/filesystem/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-multimedia_backup.bb, do_rootfs) failed with exit code '1'

NOTE: Tasks Summary: Attempted 4686 tasks of which 490 didn't need to be rerun and 1 failed.

No currently running tasks (4686 of 4687)

Summary: 1 task failed:

  /home/ravi/pga/svn/trunk/software/imx/filesystem/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-multimedia_backup.bb, do_rootfs

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Has anyone seen this before.

Please reply.

Regards

Manju

0 Kudos
1,968 Views
vsiles
Senior Contributor I

Ok, now it boots ! I've got quite some errors but at least linux is started.

Many thanks to you !

Vincent

0 Kudos
1,968 Views
manjunathjoshi
Contributor V

Hello vincent,

Can you share me the bb file for how you got the ext2.gz.u-boot file.

Thanks for help.

Regards,

Manju

0 Kudos
1,968 Views
vsiles
Senior Contributor I

Sure, here are my local.conf and bb file

Best,

Vincent

1,968 Views
addiyi
NXP Employee
NXP Employee

Vincent,

Are you using sd card boot? If yes, why don't you use tar.gz image, create a linux partition on the sd card and untar the image?

For "Ramdisk image is corrupt or invalid", make sure the image is not override uImage, when is loaded in RAM.

Adrian

0 Kudos
1,968 Views
vsiles
Senior Contributor I

I already successfully started using sd card boot, but since I have issues performing secure boot from sd card, I wanted to boot from ramdisk, and try an "out of the box" secure boot from ramdisk as described in the SDK. So I'm trying to boot from ram disk atm.

Since I'm trying to flash the -full-, the ramdisk is way bigger. I'll try to put the dtb further away. Thank you for the suggestion !

0 Kudos
1,968 Views
vsiles
Senior Contributor I

I almost got it. When I flash the file and perform the 'bootm' command, I get (after some computation time)

## Loading init Ramdisk from Legacy Image at 88000000 ...

   Image Name:   fsl-image-full-ls1021atwr-201605

   Image Type:   ARM Linux RAMDisk Image (gzip compressed)

   Data Size:    190697971 Bytes = 181.9 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... Bad Data CRC

Ramdisk image is corrupt or invalid

However verification of the kernel is fine. I'll investigate. If you have any suggestions, do not hesitate :smileywink:

0 Kudos
1,969 Views
vsiles
Senior Contributor I

It seems that patching the IMAGE_FSTYPES_qoriq in fsl-image-full.bb to add ext2.gz.u-boot  did the trick, I got the file generated. i'll try to flash it. Thanks for the information !

1,968 Views
addiyi
NXP Employee
NXP Employee

Try also bitbake -c compile -f fsl-image-full

Adrian

0 Kudos
1,968 Views
vsiles
Senior Contributor I

Thank you for the suggestion.

With fsl-image-core, I have manage to get fsl-image-core-ls1021atwr.ext2.gz.u-boot.

Should I comment the "IMAGE_FSTYPES_qoriq" in fsl-image-full.bb to test if I get a *-full-* version of ext2.gz.u-boot ?

0 Kudos
1,968 Views
addiyi
NXP Employee
NXP Employee

Could you try to bitbake fsl-image-core, of course with IMAGE_FSTYPES = "tar.gz ext2.gz ext2.gz.u-boot jffs2 ubi" in QorIQ-SDK-V1.9-20151210-yocto\sources\meta-freescale\recipes-fsl\images\?

Adrian

0 Kudos
1,968 Views
addiyi
NXP Employee
NXP Employee

Go to QorIQ-SDK-V1.9-20151210-yocto\sources\meta-freescale\recipes-fsl\images\ and add ext2.gz.u-boot into fsl-image-minimal.bb as below:

IMAGE_FSTYPES = "tar.gz ext2.gz ext2.gz.u-boot jffs2 ubi"

Adrian

0 Kudos
1,968 Views
vsiles
Senior Contributor I

I tried to add a variable in my local.conf file, and it seems to be ignored:

bitbake -e virtual/kernel | grep ^IMAGE_FSTYPES

IMAGE_FSTYPES="ext2.gz.u-boot tar.bz2 ext3 sdcard"

but I only get a tar.gz file, neigher ext2.gz.u-boot nor .sdcard file

0 Kudos
1,968 Views
vsiles
Senior Contributor I

Dear addiyi​, this value already contains this exact value. I tried to modify the IMAGE_FSTYPES_qoriq of the fsl-image-full.bb file, but it did not help. Maybe this value is overridden somewhere else ?

Best,

Vincent

0 Kudos