Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the provided context, it seems like there might be an issue with the naming convention used by the torizoncore-builder tool when it tries to locate the image in the Toradex Artifactory. The discrepancy between the expected and actual tarball names could indeed be causing the problem.
Here are a few steps you can take to troubleshoot and potentially resolve this issue:
-
Verify the Image Name: Double-check the exact name of the tarball in the Toradex Artifactory. Ensure there are no typos or discrepancies in the name.
-
Check for Updates: Ensure that you are using the latest version of the
torizoncore-buildertool. There might have been updates or bug fixes related to this issue. -
Manual Download and Deployment:
- Download the correct tarball manually from the Toradex Artifactory.
- Use the
torizoncore-buildertool to deploy the device tree overlay locally instead of relying on the remote download feature.
-
Report the Issue: If the problem persists, it might be a bug in the
torizoncore-buildertool. You can report this issue to Toradex support or on their GitHub repository, providing all the details and the discrepancy in the naming convention. -
Workaround: As a temporary workaround, you can manually adjust the naming convention in your local environment to match what the
torizoncore-buildertool expects, if feasible.
If none of these steps resolve the issue, it would be best to contact Toradex support directly with all the details, including the exact command you are using and the error message you are receiving. They would be able to provide more specific guidance or a fix for the issue.
Please, also check if these links can help you solve your problem:
Am I misunderstanding intent/use of torizoncore-builder dto deploy?.