Torizon IDE Extension cannot push a custom package to Torizon Cloud

[vix]

I would like using Torizon IDE Extension to push m7-firmware to Torizon Cloud, as described here.

So I created anew task, based on the existing tcb-platform-push-ostree.

        {
            "label": "tcb-platform-push-m7-firmware",
            "detail": "Run the torizoncore-builder platform push command to torizon.io cloud - m7-firmware",
            "command": "DOCKER_HOST=",
            "type": "shell",
            "options": {
                "cwd": "${workspaceFolder}",
                "env": {
                    "VSCODE_CMD": "--verbose platform push --credentials credentials.zip --hardwareid cortex-firmware --package-name demo-firmware --package-version 0.0.1 ./my-firmware.bin"
                }
            },
            "args": [
                "source",
                "./.conf/tcb-env-setup.sh",
                "-s",
                "${workspaceFolder}/storage",
                "-t",
                "${config:tcb.version}"
            ],
            "problemMatcher": [
                "$tsc"
            ],
            "dependsOrder": "sequence",
            "dependsOn": [
                "tcb-unpack"
            ],
            "icon": {
                "id": "cloud-upload",
                "color": "terminal.ansiYellow"
            },
            "presentation": {
                "echo": true,
                "reveal": "always",
                "focus": true,
                "panel": "dedicated",
                "group": "cloud-related"
            }
        },

Running it I get the following error:

An unexpected Exception occurred. Please provide the following stack trace to
the Toradex TorizonCore support team:


Traceback (most recent call last):

  File "/builder/torizoncore-builder", line 230, in <module>
    mainargs.func(mainargs)
  File "/builder/tcbuilder/cli/platform.py", line 584, in do_platform_push
    platform.push_ref(
  File "/builder/tcbuilder/backend/platform.py", line 1035, in push_ref
    commit = repo.read_commit(ref).out_commit
gi.repository.GLib.GError: g-io-error-quark: Invalid refspec ./my-firmware.bin (0)

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

Thank you for reaching out with your question. It seems you’re encountering an issue with the “Invalid refspec ./my-firmware.bin” error while trying to push your firmware to Torizon Cloud using the Torizon IDE Extension.

Here are some steps to help you resolve this issue:

1. File Type Verification: Ensure that ./my-firmware.bin is indeed the correct file you wish to push. The TorizonCore Builder tool expects specific file types, and your binary file might not be recognized as a valid reference.

2. Command Configuration: The platform push command is typically used for Docker Compose files or OSTree references. Since you’re pushing a binary file, ensure that your command is correctly formatted to handle this type of package. You may need to specify that this is a generic package.

3. Correct Argument Usage: Double-check that you are using the correct arguments for pushing a generic package:

   • Use --package-name to define the name under which the package will appear in Torizon Cloud.
   • Use --package-version to specify the version string.
   • Use --hardwareid to indicate compatible hardware IDs.

4. Environment Setup: Verify that your environment is set up correctly, with all necessary paths and environment variables configured. Ensure that the VSCODE_CMD environment variable is properly formatted and includes all required options.

By following these steps, you should be able to address the “Invalid refspec” error and successfully push your firmware to Torizon Cloud. If you have any further questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

OTA update of M7 firmware

The topic has been discussed several times on this community, but with Torizon OS 6 on Verdin iMX8M-Plus it’s only the bootloader that can load a M7 firmware that runs from DDR (not from internal ITCM). Not problem in creating a TEZI image which contains the M7 firmware. But how can I handle this with Torizon OTA feature? It’s not an Operating System update (that is OSTree), but I think it’s a bootloader update. Is this true? How can I push/load this bootloader in Torizon Cloud (it’s not a …

Torizon IDE Installation Wizard for Windows - Early Access Feedback Thread

Dear Everyone, The Torizon Team is happy to announce the release of an attended Installation Wizard to help easily setup VS Code for Torizon development on Windows. Learn more about it in the blog post Next, Next, Install: The Easiest Way to Setup Your Windows PC for Embedded Linux and in the short video below: [Torizon IDE Installation Wizard: The New Era of “Easy-To-Use”] This tool came to life after observing new customers do the setup manually in training sessions and custome…

TorizonCore Builder Tool - Customizing Torizon OS Images | Toradex Developer Center.

[vix]

There is some issue in the firmware path.

I can have it working oly if I se the source to

@vix

  "-s",
  "${workspaceFolder}"

and the file must be inside this root folder.

Subfolders don’t work with the above error.

[jeremias.tx]

Greetings @vix,

Sounds like an issue with what TorizonCore Builder sees. Keep in mind the Builder tool runs in a container and can only see the current directory and below with respect to where it’s being executed.

To explain the error, the builder tool tried to treat ./my-firmware.bin as an OSTree, which means it couldn’t find this file via the provided path, so the tool assumed you were describing an OSTree reference instead.

So yeah it’s just a matter of what the Builder container sees in respect to the actual path of the file.

Best Regards,
Jeremias