13826 2020-03-10 21:46:12 +0000 Default EXTRA_IMAGECMD_jffs2 drops JFFS2_ENDIANNESS 2020-03-10 21:56:05 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified All Multiple RESOLVED INVALID Undecided normal --- 1 yocto unassigned meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 86692 0 yocto 2020-03-10 21:46:12 +0000 I think ${JFFS2_ENDIANNESS} has no effect (jffs2 will always be generated as big endian, the default of mkfs.jffs2). meta/classes/image_types.bbclass defines default arguments for mkfs.jffs2: EXTRA_IMAGECMD_jffs2 ?= "--pad ${JFFS2_ENDIANNESS} --eraseblock=${JFFS2_ERASEBLOCK} --no-cleanmarkers" Those are inserted into IMAGE_CMD_jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} --faketime --output=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.jffs2 ${EXTRA_IMAGECMD}" According to "man mkfs.jffs2": -p, --pad[=SIZE] Pad output to SIZE bytes with 0xFF. If SIZE is not specified, the output is padded to the end of the final erase block. pad expects a size argument. mkfs.jffs2 now silently accepts -b or -l and converts it to 0. Hence the argument is already consumed and will not have the intended effect. Workaround: Overwrite EXTRA_IMAGECMD_jffs2 in image-recipe 86693 1 yocto 2020-03-10 21:56:05 +0000 Sorry for opening the ticket. I just noticed size should be optional. Therefore my issue must have different source.