Closed hannes09 closed 3 years ago
It looks like you're building for a custom machine. If you are upgrading from a prior BSP version, did you refresh your tegra-flashvars
configuration for R32.5.0? For the Xavier-based machines, there's a new MINRATCHET_CONFIG file that has to be specified there, and the UPHY_CONFIG setting (if it's an AGX Xavier) now has to include the --uphy_config
option in front of the cfg file name (that config used to be needed for Xavier NX as well, but was dropped in R32.5.0).
If you've got meta-tegra cloned locally, try:
$ git diff origin/dunfell-l4t-r32.4.3 origin/master -- recipes-bsp/tegra-binaries/tegra-flashvars
to see the differences in the config files for the development kit platforms, and make sure you've made corresponding changes for your custom machine. (Substitute whatever branch/BSP version corresponds to your pre-upgrade builds in the first parameter). You might also repeat that for the conf/machine
subdirectory, to see if there are other machine settings that have changed between BSP versions which you need to account for.
The other thing that you could try is to go to the working directory for kernel-bup-payload
, modify the tegraflash_internal.py
script that's there under recipe-sysroot-native
to dump the contents of cmd
at line 189 (with a simple print()
function, for instance) and manually run temp/run.do_deploy
to try and zero in on what's missing from that command. Hopefully that will provide enough information to trace back to what might be missing from your machine configuration.
Yes, you are right.
Updating my flashvar with UPHY_CONFIG
and MINRATCHET_CONFIG
solved the issue.
Thanks for the help.
The deploy task of kernel-bup-payload fails since 32.5:
/meta-tegra/recipes-kernel/kernel-bup-payload/kernel-bup-payload.bb:do_deploy) failed with exit code '1'