custom image_types bbclass approach and errors

* custom image_types bbclass approach and errors
@ 2018-11-13 20:50 Bryan Fishell
  2018-11-18 21:12 ` Otavio Salvador
  0 siblings, 1 reply; 5+ messages in thread
From: Bryan Fishell @ 2018-11-13 20:50 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

I am relatively new to Yocto, but have a need to create a custom
image_types_x.bbclass extending the image_types_fsl.bbclass that simply
adds two ext4 partitions of size PARTITION_SIZE to the end of an .sdcard
image.

The approach I took - created an entirely new image_types_mycustom.bbclass
based on the image_types_fsl.bbclass, and overrode the creation of the
.sdcard file into a file called .mysdcard.

Note that I still have sdcard in IMAGE_FSTYPES. I thought this wouldn't
pose a problem, but I keep getting errors when a dependent step (creation
of an .ext4 image prior to the .mysdcard task) was getting skipped, but the
do_image_mysdcard task did not reuse the (valid and already existing) .ext4
image, indicating that my parallel bbclass could not find the file with a
slightly different timestamp than the first (note that I added a # to my
bbclass to invalidate the basehash).

1. For my approach, is there something I could do to force my bbclass to
not re-evaluate the DATETIME if bitbake was smart enough to know that the
do_image_ext4 task can be reused? (i.e. how do I pass the older, but valid
DATETIME from the pre-existing  .ext4 image so my custom image can be
generated successfully?)

2. I assume I could work around this by simply extending the existing
image_types_fsl.bbclass function generate_imx_sdcard to resize the .sdcard
file and generate the partitions, is that right?

TIA

[-- Attachment #2: Type: text/html, Size: 1561 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread