[yocto] Date/Time Update Without NTP

[Donal Morrissey]

Hi There,

I'm using yocto sumo with systemd, and have an issue where I can't identify
which service is grabbing time from the ethernet based network.

If I start the unit without a network connection, the time is reported as
EPOC. As soon as I connect the network, the date/time is updated. However,
there isn't anything in the logs that I can see which tells details of the
service which has updated time. Also, the ntpd binary is not installed.

Is there a time service, other than NTP, which would typically be enabled
on Yocto builds?

Cheers,
Donal
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Modify login prompt with script output

[Donal Morrissey]

Hi There,
Is it possible to modify the login prompt so that it includes the output of
a script?
I know I can modify the /etc/issue file as part of the build to include
custom text, but I would like to have a script which is executed to
generate some text to be displayed as part of the prompt.
Cheers,
Donal
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wic creates invalid image

[Donal Morrissey]

Hi Alex & Dimitris,
Thank you for the info.
I tried to use gpt partition table as you suggested, but the raspberry pi
compute module 3 I am using wouldn't boot, so i switched back to mbr/msdos.
Now that I understand the origin of the extra extended partition, I can
work around it.
best regards,
Donal

On Tue, 13 Nov 2018 at 19:29, Dimitris Tassopoulos 
wrote:

> Hi Alex,
>
> If you don't want the extended partitions you need to create a gpt
> partition, you can do this by adding this to your wks file.
>
> bootloader --ptable gpt
>
> Regards,
> Dimitris
>
>
> On Tue, 13 Nov 2018, 20:23 Alex Kiernan 
>> On Tue, Nov 13, 2018 at 7:13 PM Donal Morrissey
>>  wrote:
>> >
>> > Hi There,
>> > I have a problem with an image being created by wic. If I add more than
>> 4 partition definitions to the wks file, the generated image will include
>> an additional partition with no Fstype, and spanning the full length of the
>> additional partitions.
>> >
>> > Take the following wks file:
>> >
>> > part --source rawcopy --sourceparams="file=> path>/image-r0/uboot.env" --ondisk "mmcblk0" --align 4096 --no-table
>> > part --source bootimg-partition --ondisk "mmcblk0" --fstype=vfat
>> --label boot --align 4096 --active --fixed-size 40
>> > part --source rootfs --ondisk "mmcblk0" --fstype=ext4 --label primary
>> --align 4096 --fixed-size 147456k --exclude-path data/
>> > part --source rootfs --ondisk "mmcblk0" --fstype=ext4 --label secondary
>> --align 4096 --fixed-size 147456k --exclude-path data/
>> > part --ondisk "mmcblk0" --fstype=ext4 --label appdata1 --align 4096
>> --fixed-size 147456k
>> > part --ondisk "mmcblk0" --fstype=ext4 --label appdata2 --align 4096
>> --fixed-size 147456k
>> > bootloader --ptable msdos
>> >
>> > wic will create a .direct file with the following structure:
>> > Num StartEnd  Size  Fstype
>> >  1  12582912 54525951 41943040  fat16
>> >  2  54525952205520895150994944  ext4
>> >  3 205520896356515839150994944  ext4
>> >  4 360709632666894335306184704
>> >  5 360710144511705087150994944  ext4
>> >  6 515899392666894335150994944  ext4
>> >
>> > Note the start and end addresses of partition 4, it spans from the
>> start of partitions 5 (appdata1)  to the end of partition 6 (appdata2).
>> >
>> > If I modify the wks file and remove the entry for appdata2, the created
>> direct file is valid:
>> >
>> > Num StartEnd  Size  Fstype
>> >  1  12582912 54525951 41943040  fat16
>> >  2  54525952205520895150994944  ext4
>> >  3 205520896356515839150994944  ext4
>> >  4 356515840507510783150994944  ext4
>> >
>> > Any suggestions on what is going on here?
>> >
>>
>> I've not checked, but I'd assume it's switched to extended partitions,
>> since MBR only has 4 primary partitions.
>>
>> --
>> Alex Kiernan
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] wic creates invalid image

[Donal Morrissey]

Hi There,
I have a problem with an image being created by wic. If I add more than 4
partition definitions to the wks file, the generated image will include an
additional partition with no Fstype, and spanning the full length of the
additional partitions.

Take the following wks file:

part --source rawcopy --sourceparams="file=/image-r0/uboot.env"
--ondisk "mmcblk0" --align 4096 --no-table
part --source bootimg-partition --ondisk "mmcblk0" --fstype=vfat --label
boot --align 4096 --active --fixed-size 40
part --source rootfs --ondisk "mmcblk0" --fstype=ext4 --label primary
--align 4096 --fixed-size 147456k --exclude-path data/
part --source rootfs --ondisk "mmcblk0" --fstype=ext4 --label secondary
--align 4096 --fixed-size 147456k --exclude-path data/
part --ondisk "mmcblk0" --fstype=ext4 --label appdata1 --align 4096
--fixed-size 147456k
part --ondisk "mmcblk0" --fstype=ext4 --label appdata2 --align 4096
--fixed-size 147456k
bootloader --ptable msdos

wic will create a .direct file with the following structure:
Num StartEnd  Size  Fstype
 1  12582912 54525951 41943040  fat16
 2  54525952205520895150994944  ext4
 3 205520896356515839150994944  ext4
 4 360709632666894335306184704
 5 360710144511705087150994944  ext4
 6 515899392666894335150994944  ext4

Note the start and end addresses of partition 4, it spans from the start of
partitions 5 (appdata1)  to the end of partition 6 (appdata2).

If I modify the wks file and remove the entry for appdata2, the created
direct file is valid:

Num StartEnd  Size  Fstype
 1  12582912 54525951 41943040  fat16
 2  54525952205520895150994944  ext4
 3 205520896356515839150994944  ext4
 4 356515840507510783150994944  ext4

Any suggestions on what is going on here?

Cheers,
Donal
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] non-existent task do_package_write_ipk

[Donal Morrissey]

Hi Ross,
I had to use IMAGE_PREPROCESS_COMMAND in my own image recipe, the execution
order of the ROOTFS_POSTPROCESS_COMMAND commands didn't work for me.
Thanks for your help.
Donal

On Fri, 9 Nov 2018 at 14:53, Burton, Ross  wrote:

> On Fri, 9 Nov 2018 at 14:48, Donal Morrissey 
> wrote:
> > Thank you for your help. My build is using a layer which is generating a
> file in a ROOTFS_POSTPROCESS_COMMAND command. I would like to modify this
> file as part of the yocto build, but I'd prefer not to modify/fork this
> layer as it is from a vender.
> >
> > I'm creating my own layer, which will modify the file created in the
> vender layer's ROOTFS_POSTPROCESS_COMMAND command. If I use pkg_postinst,
> then the file will not have been created when pkg_postinst is called,
> because (as far as i understand) the ROOTFS_POSTPROCESS_COMMAND commands
> will only be executed after all packages have been installed on the root
> filesystem image.
>
> You'll have to set your own ROOTFS_POSTPROCESS_COMMAND in your image
> recipe.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] non-existent task do_package_write_ipk

[Donal Morrissey]

Hi Ross,
Thank you for your help. My build is using a layer which is generating a
file in a ROOTFS_POSTPROCESS_COMMAND command. I would like to modify this
file as part of the yocto build, but I'd prefer not to modify/fork this
layer as it is from a vender.

I'm creating my own layer, which will modify the file created in the vender
layer's ROOTFS_POSTPROCESS_COMMAND command. If I use pkg_postinst, then the
file will not have been created when pkg_postinst is called, because (as
far as i understand) the ROOTFS_POSTPROCESS_COMMAND commands will only be
executed after all packages have been installed on the root filesystem
image.

Any suggestions on how to proceed?

Regards,
Donal

On Fri, 9 Nov 2018 at 12:13, Burton, Ross  wrote:
>
> A recipe that ship files and generates packages can't also inherit
> core-image because it can't both be a package and an image.  If you
> want this package to run something when it is installed, write a
> post-install function (pkg_postinst).
>
> Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] non-existent task do_package_write_ipk

[Donal Morrissey]

Hi There,
I'm not able to inherit core-image into my recipe, when I do, I get the
following error:
ERROR: Task do_populate_sdk in .../poky/meta/recipes-core/images/
core-image-base.bb rdepends upon non-existent task do_package_write_ipk in
/home/donal/Projects/farkas/source/meta-my-platform/recipes-tools/system-scripts/
system-scripts.bb
ERROR: Command execution failed: 1

The reason I'm inheriting core-image, is so that I can append a command to
the ROOTFS_POSTPROCESS_COMMAND variable.

The following are the contents of my bb file:

SUMMARY = "Set of common platform tools."
DESCRIPTION = "..."
AUTHOR = "..."
LICENSE = "CLOSED"

inherit core-image

my_post_process_cmd() {
touch ${IMAGE_ROOTFS}/test
}
ROOTFS_POSTPROCESS_COMMAND += " my_post_process_cmd;"

Any suggestions on how to fix this?

Thank you,
Donal
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto