Torizon-core builder unexpected exception occured

Colibri iMX6DL 512MB IT
Colibri Evaluation Board

Running in WSL (Ubuntu 18.04.5 LTS

When I setup torizoncore-builder like so:

leighjboyd@EMERALENOVO1:/mnt/c/github3/EmeraBlockEnergyBox/deviceTreeOverlay/tcbworkdir$ cat ArmEmulation.sh
#! /bin/bash
wslfetch
sudo apt-get update && sudo apt-get install rsync ssh
docker --version
docker run hello-world
docker run --rm -it --privileged torizon/binfmt
docker run --platform linux/arm/v7 --rm -it arm32v7/debian arch
docker run --platform linux/arm64/v8 --rm -it arm64v8/debian arch
rm tcb-env-setup.sh*
wget https://raw.githubusercontent.com/toradex/tcb-env-setup/master/tcb-env-setup.sh
source ./tcb-env-setup.sh

with my .yaml file like so:

leighjboyd@EMERALENOVO1:/mnt/c/github3/EmeraBlockEnergyBox/deviceTreeOverlay/tcbworkdir$ cat tcbuild.yaml | grep -v "#"

input:
  easy-installer:
          local: torizon-core-docker-evaluation-colibri-imx6-Tezi_5.6.0-devel-202202+build.21.container.tar
customization:
   filesystem:
      - changes/
   device-tree:
     overlays:
      add:
         - my-colibri-overlay.dts
output:
  easy-installer:
    local: torizon-core-docker-evaluation-colibri-imx6-Tezi_5.6.0-devel-SPI-202203+build.21.container

I get:

leighjboyd@EMERALENOVO1:/mnt/c/github3/EmeraBlockEnergyBox/deviceTreeOverlay/tcbworkdir$ torizoncore-builder build
Building image as per configuration file 'tcbuild.yaml'...

=>> Handling input section
Unpacking Toradex Easy Installer image.
An unexpected Exception occured. Please provide the following stack trace to
the Toradex TorizonCore support team:


Traceback (most recent call last):
  File "/builder/torizoncore-builder", line 215, in <module>
    mainargs.func(mainargs)
  File "/builder/tcbuilder/cli/build.py", line 424, in do_build
    build(args.config_fname, args.storage_directory,
  File "/builder/tcbuilder/cli/build.py", line 391, in build
    handle_input_section(config["input"], storage_dir=storage_dir)
  File "/builder/tcbuilder/cli/build.py", line 80, in handle_input_section
    handle_easy_installer_input(props["easy-installer"], **kwargs)
  File "/builder/tcbuilder/cli/build.py", line 101, in handle_easy_installer_input
    images_cli.images_unpack(
  File "/builder/tcbuilder/cli/images.py", line 393, in images_unpack
    images.import_local_image(image_dir, dir_list[0], dir_list[1], dir_list[2])
  File "/builder/tcbuilder/backend/images.py", line 295, in import_local_image
    subprocess.check_output(tarcmd, shell=True, stderr=subprocess.STDOUT)
  File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'cat /workdir/torizon-core-docker-evaluation-colibri-imx6-Tezi_5.6.0-devel-202202+build.21.container.tar | cat | tar -xf - -C /storage/tezi.tmp' returned non-zero exit status 2.

This was my overlay file, incase that was the culprit (most likely… but I could have sworn this worked earlier…)


/dts-v1/;
/plugin/;

/* Colibri SSP */
&ecspi4 {
        mcp251x0: mcp251x@0 {
                compatible = "microchip,mcp2515";
                reg = <0>;
                clocks = <&clk16m>;
                interrupt-parent = <&gpio3>;
                interrupts = <27 0x2>;
                spi-max-frequency = <10000000>;
                status = "disabled";
        };
        /* To keep the CAN controller enabled by default,
         * disable conflicting spidev. This spidev device
         * enables with the devicetree overlay.
         */
        spidev0: spidev@0 {
                compatible = "toradex,evalspi";
                reg = <0>;
                spi-max-frequency = <23000000>;
                status = "okay";
        };

Greetings @leighjboyd,

Judging by the error it seems the tool is having trouble unpacking your torizon-core-docker-evaluation-colibri-imx6-Tezi_5.6.0-devel-202202+build.21.container.tar file.

Where is this file relative to where you are executing the build command? Perhaps you have it in the wrong spot?

Best Regards,
Jeremias

You are correct. It was in another directory. Thanks!

Glad I could help!