03-26-2017 10:30 AM
Hello,
In Petalinux 2016.1, the rootfs image had the files /etc/version and /etc/product pulled in from the top level config generated with petalinux-config
In 2016.4 this is no longer the case. The /etc/version file does not match the version string I put in using petalinux-config. Instead it just seems to be a timestamp
The product name is not included as an /etc/product file. There is no /etc/product file
Also, the hostname doesn't match the product name like it used to. Instead it is the generic plnx-arm
How can I modify the recipe or configuration to
1) Put the correct information into /etc/version
2) Create a product text file in /etc/product
3) Change the hostname
Thanks!
03-29-2017 05:24 AM
Ok. In the short term I just used a .bbappend file to copy over my own files into /etc
this works fine for product. The version file always seems to get overwritten by the yocto build. For now I just create a file with a different name (firmware_version) and use that. The transition to Yocto has not been smooth. I think Xilinx really rushed this.
In case it helps anyone:
FILESEXTRAPATHS_prepend := "${THISDIR}/initscripts:" SRC_URI += " \ file://product \ file://firmware_version \ " do_install_append() { install -m 0755 ${WORKDIR}/product ${D}${sysconfdir} install -m 0755 ${WORKDIR}/firmware_version ${D}${sysconfdir} }
03-29-2017 04:31 AM
03-29-2017 05:24 AM
Ok. In the short term I just used a .bbappend file to copy over my own files into /etc
this works fine for product. The version file always seems to get overwritten by the yocto build. For now I just create a file with a different name (firmware_version) and use that. The transition to Yocto has not been smooth. I think Xilinx really rushed this.
In case it helps anyone:
FILESEXTRAPATHS_prepend := "${THISDIR}/initscripts:" SRC_URI += " \ file://product \ file://firmware_version \ " do_install_append() { install -m 0755 ${WORKDIR}/product ${D}${sysconfdir} install -m 0755 ${WORKDIR}/firmware_version ${D}${sysconfdir} }
08-03-2017 05:30 AM
Hello,
I get the same behavior in 2017.2. Will it be fixed in 2017.3 ?
Thanks
04-07-2021 02:25 PM - edited 04-07-2021 03:21 PM
I believe this is also affecting Petalinux 2020.1 and 2020.2