meta-mender-commercial failed with kirkstone branch about tegra-demo-distro HOT 6 CLOSED

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.

from tegra-demo-distro.

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

from tegra-demo-distro.

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.

from tegra-demo-distro.

Thanks @dwalkes for the clarification.

I didn't try kirkstone / kirkstone-next branch in mender with L4T R32.7.2 / JetPack 4.6.2

from tegra-demo-distro.

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

from tegra-demo-distro.

Ok thanks @madisongh
It's what I observed.
I make the change in a fork of mine and it's working perfectly

from tegra-demo-distro.