Closed Gandouge78 closed 2 years ago
Hello @Gandouge78
We didn't work yet on the update mechanism (using mender
).
You should open an issue in the mender and ask them about kirkstone
because it doesn't exists in both meta-mender
and meta-mender-community
We didn't work yet on the update mechanism (using mender).
One clarification here - kirkstone branch should be working for Jetpack 4.6 on https://github.com/oe4t/tegra-demo-distro/tree/kirkstone for tegrademo-mender
using https://github.com/mendersoftware/meta-mender-community/tree/kirkstone-next. I haven't tried any recipe in meta-mender-commercial, however, and this is something you should bring up with Mender.
Thanks @dwalkes for the clarification.
I didn't try kirkstone / kirkstone-next
branch in mender
with L4T R32.7.2 / JetPack 4.6.2
Thanks for the answer. Yes tegrademo-mender is working perfectly. The problem is when you add mender-binary-delta or mender-monitor to tegrademo-mender. I will look into mender repo and ask them
I think I just converted meta-mender-core to use the new overrides syntax for our kirkstone-compatible fork of the meta-mender repository, since that's all we use here.
Ok thanks @madisongh It's what I observed. I make the change in a fork of mine and it's working perfectly
Hi,
I try to update my current distro from dunfell to kirkstone. We use mender-delta-binary and I have some issue with the meta-mender repository. It seems that the receipts in meta-mender-commercial are not compatible with kirkstone.
For now i will create a fork on my account an try to fix it but do you have an idea of when you will make the change ?
ERROR: Variable EXTRA_IMAGECMD_ext4_append file: /home/DockerUser/working_directory/workspace/BXT4_folder/BXT4/layers/meta-mender-commercial/conf/layer.conf line: 20 contains an operation using the old override syntax. Please convert this layer/metadata before attempting to use with a newer bitbake.