UBIFS images
I'm trying to use UBIFS on my target and I found that the images are not quite right. The soft-link points to the wrong file.
$ ls -l tmp/deploy/images/*ubi* -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.img lrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifs
I've looked through meta/classes/image_types.bbclass but it's not clear to me [yet] where that soft-link gets built and why it gets it wrong.
Any pointers?
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 7 lines · Gary Thomas
I'm trying to use UBIFS on my target and I found that the images are not quite right. The soft-link points to the wrong file.
$ ls -l tmp/deploy/images/*ubi* -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.img lrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifs
Quoted 5 lines
I've looked through meta/classes/image_types.bbclass but it's not clear to me [yet] where that soft-link gets built and why it gets it wrong.
Any pointers?
Following up on my own question, this patch seems to fix it.
meta/classes/image_types.bbclass +1 -1
@@ -67,7 +67,7 @@ IMAGE_CMD_ubi () { echo vol_flags=autoresize >> ubinize.cfg mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ubifs ${MKUBIFS_ARGS} && ubinize -o ${D } -IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}" +IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ubifs ${MKUBIFS_ARGS}" EXTRA_IMAGECMD = "" EXTRA_IMAGECMD_jffs2 ?= "--pad --little-endian --eraseblock=0x40000"
If this looks reasonable, I'll send it on to oe-core
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 7 lines · Gary Thomas
I'm trying to use UBIFS on my target and I found that the images are not quite right. The soft-link points to the wrong file.
$ ls -l tmp/deploy/images/*ubi* -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.img lrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifs
Quoted 5 lines
I've looked through meta/classes/image_types.bbclass but it's not clear to me [yet] where that soft-link gets built and why it gets it wrong.
Any pointers?
image_types.bbclass:
ln -s ${IMAGE_NAME}.rootfs.${type} ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.${type}
The problem is that $type=ubifs but the extenstion the ubifs image generates is ubifs.img:
IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}"
and we don't support generating image types where the image extension and the type name differ...
I'd guess the quick fix is s/ubifs.img/ubifs/ in the above...
Cheers,
Richard
Quoted 21 lines · Richard Purdie
Quoted 7 lines · Gary Thomas
I'm trying to use UBIFS on my target and I found that the images are not quite right. The soft-link points to the wrong file.
$ ls -l tmp/deploy/images/*ubi* -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.img lrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifsQuoted 5 lines
I've looked through meta/classes/image_types.bbclass but it's not clear to me [yet] where that soft-link gets built and why it gets it wrong.
Any pointers?
image_types.bbclass:
ln -s ${IMAGE_NAME}.rootfs.${type} ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.${type}
The problem is that $type=ubifs but the extenstion the ubifs image generates is ubifs.img:
Quoted 6 lines
IMAGE_CMD_ubifs= "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}"and we don't support generating image types where the image extension and the type name differ...
I'd guess the quick fix is s/ubifs.img/ubifs/ in the above...
Thanks
A bigger question is why is there an unused image command (IMAGE_CMD_ubi) which seems to do it right and also sets up a proper volume layout vs the current command (IMAGE_CMD_ubifs) which is incorrect?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 24 lines · Gary Thomas
Quoted 23 lines · Richard Purdie
Quoted 11 lines · Gary Thomas
I'm trying to use UBIFS on my target and I found that the images are not quite right. The soft-link points to the wrong file.
$ ls -l tmp/deploy/images/*ubi* -rw-r--r-- 1 gthomas gthomas 7483392 Jul 11 07:56 tmp/deploy/images/my_distro-console-image-my_target-20110711135454.ubifs.imglrwxrwxrwx 1 gthomas gthomas 62 Jul 11 07:56
tmp/deploy/images/my_distro-console-image-my_target.ubifs -> my_distro-console-image-my_target-20110711135454.rootfs.ubifsQuoted 5 lines
I've looked through meta/classes/image_types.bbclass but it's not clear to me [yet] where that soft-link gets built and why it gets it wrong.
Any pointers?
image_types.bbclass:
ln -s ${IMAGE_NAME}.rootfs.${type}
${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.${type}
Quoted 8 lines
Quoted 8 lines
The problem is that $type=ubifs but the extenstion the ubifs image generates is ubifs.img:
IMAGE_CMD_ubifs= "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.ubifs.img ${MKUBIFS_ARGS}"and we don't support generating image types where the image extension and the type name differ...
This might be a little problematic, or maybe it's all just in my head since we want a way to try and encourage folks to use the right part of the ubi dance and not the wrong part (which is to say the image that contains the ubifs and not just the ubifs itself).
Quoted 7 lines
Quoted 1 line
I'd guess the quick fix is s/ubifs.img/ubifs/ in the above...
Thanks
A bigger question is why is there an unused image command (
IMAGE_CMD_ubi) which seems to do it right and also sets up a proper volume layout vs the current command (IMAGE_CMD_ubifs) which is incorrect?
I think part of the problem is that oe-core and oe-classic are out of sync here as there was a symlink problem a while back.
Signature · 2 lines
Tom Rini Mentor Graphics Corporation