What I mean is that you can try to rename your custom board config name to the default one(jetson-orin-nano-devkit.conf) but keep your customized content.
I don’t think you have to update this script if you’ve rename it to jetson-orin-nano-devkit.conf
My base device, which I want to update was flashed with: p3509-a02+p3767-0000 config, so when I am making OTA with renamed config to jetson-orin-nano-devkit its not working, I am able to bypass check for rootfs but not for uefi
Do you mean that you board were flashed with p3509-a02+p3767-0000 before?
Okay, do you have any chance to flash it again with jetson-orin-nano-devkit as board config?
If not, what happen if you keep using p3509-a02+p3767-0000 to generate OTA payload? Please share the full log when you use p3509-a02+p3767-0000 to generate OTA package.
Yes
No, devices already distributed all over the country, reflash them to latest image physically also not possible
Its crashing right at the beginning
$ ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh -s --external-device nvme0n1 -S 118GiB p3509-a02+p3767-0000 R35-5
tools/ota_tools/version_upgrade/ota_validate_params.sh: line 76: P3509_A02+P3767_0000_R35_5_ALIAS: invalid variable name
$ ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh -s --external-device nvme0n1 -S 118GiB recomputer-orin-j401 R35-5
Target board(RECOMPUTER_ORIN_J401) and base version(R35_5) is not supported
Failed to run "ota_validate_params recomputer-orin-j401 R35-5 internal /media/saschao/Storage/seeed/Linux_for_Tegra/tools/ota_tools/version_upgrade/ota_board_specs.conf BOARD_SPECS_ARRAY CHIPID"
Its all comes to spec files, we already tried to modify them at the beginning of this topic, its dead end
Have you tried to add P3509_A02+P3767_0000_R35_5_ALIAS in ota board spec?
Since your board is flashed with p3509-a02+p3767-0000, please do not use recomputer-orin-j401, let us focus on the case of p3509-a02+p3767-0000
I would like to check the full log when your run this command to generate OTA payload.
We tried it for different config here, new error appear
I have 2 exactly the same carrier board from seeed
J5.1.3 - flashed with p3509-a02+p3767-0000
J6.1 - flashed with recomputer-orin-j401
Need OTA from p3509-a02+p3767-0000 to recomputer-orin-j401, I believe its just new fancy name for config from Seeed + some changed in dtb files for support modern stuff
Thats the only line of output, I am under root
I didn’t see you’ve added P3509_A02+P3767_0000_R35_5_ALIAS in ota board spec?
It seems you added RECOMPUTER_ORIN_J401_R35_5_ALIAS instead?!
It is not the valid use case since you should use exact same board config name to generate the OTA payload.
(i.e. the board config name used to flash the board should be the same as the one used in OTA)
Yes, I know, but nothing I can do about it, that what Seeed decide to do, I have to deal with it, device it self support it, so the only problem remain are OTA scripts compatibility checks
J6.1 doesnt have such config anymore, I believe they just rename it to recomputer-orin-j401 to have fancy config name, even if it was renamed, its not possible to create OTA with any of these names
Kevin we are walking in circles, could you please help me how to disable check compatibility for capsule update?
That’s why I suggested you implement using p3509-a02+p3767-0000 to generate OTA payload in JP6.1.
I would like to check the log when you’ve added them to board spec in JP6.1.
It is impossible that you were using p3509-a02+p3767-0000.conf as board config in old release and you are trying to generate OTA payload with recomputer-orin-j401.conf.
And please note that they are totally the customization since we support only using jetson-orin-nano-devkit.conf as board config officially.
Theoretically, you or SeeedStudio should customize them according to how jetson-orin-nano-devkit.conf implements in BSP package for your customized project.
Please share your ota_board_specs.conf and l4t_generate_ota_package.sh from JP6.1 for further check.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.