The download may take some time. Please waitâŚ
Download Complete!
Unpacking Toradex Easy Installer image.
Copying Toradex Easy Installer image.
Unpacking TorizonCore Toradex Easy Installer image.
Importing OSTree revision e18fde565a513f5014c22060e6c60d620d0df10393358fc64e4e94fb3569daec from local repositoryâŚ
1083 metadata, 12634 content objects imported; 405.9 MB content written
Unpacked OSTree from Toradex Easy Installer image:
Commit checksum: e18fde565a513f5014c22060e6c60d620d0df10393358fc64e4e94fb3569daec
TorizonCore Version: 5.6.0+build.13
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 213, in
mainargs.func(mainargs)
File â/builder/tcbuilder/cli/dto.pyâ, line 357, in do_dto_deploy
dt_cli.do_dt_checkout(args)
File â/builder/tcbuilder/cli/dt.pyâ, line 47, in do_dt_checkout
if args.update:
AttributeError: âNamespaceâ object has no attribute âupdateâ
The board currently contains the following image, installed with the Easy Installer:
Hope youâre doing good! From your error, it seems that there may be a problem with the Device Trees and/or the overlays youâre trying to add to your device. I think your command seems fine according to this page: TorizonCore Builder Tool - Commands Manual | Toradex Developer Center.
Could you please share with us the Device Tree overlay file you were trying to use? There may be a problem on that file.
I also attached the tcbuild.yaml file. I donât know whether this could have any influence on the error⌠colibri-imx7_interferometer.dts (303 Bytes) tcbuild.yaml (4.6 KB)
I just did that.
Running the simple âtorizoncore-builder buildâ command with the following configuration (tcbuild.yaml) did indeed create a new image:
The download may take some time. Please waitâŚ
Download Complete!
Unpacking Toradex Easy Installer image.
Copying Toradex Easy Installer image.
Unpacking TorizonCore Toradex Easy Installer image.
Importing OSTree revision e18fde565a513f5014c22060e6c60d620d0df10393358fc64e4e94fb3569daec from local repositoryâŚ
1083 metadata, 12634 content objects imported; 405.9 MB content written
Unpacked OSTree from Toradex Easy Installer image:
Commit checksum: e18fde565a513f5014c22060e6c60d620d0df10393358fc64e4e94fb3569daec
TorizonCore Version: 5.6.0+build.13
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 213, in
mainargs.func(mainargs)
File â/builder/tcbuilder/cli/dto.pyâ, line 357, in do_dto_deploy
dt_cli.do_dt_checkout(args)
File â/builder/tcbuilder/cli/dt.pyâ, line 47, in do_dt_checkout
if args.update:
AttributeError: âNamespaceâ object has no attribute âupdateâ
So the error seems to come from the part that installs the image on the moduleâŚ
A related question is why the deploy command is downlowding the image from the toradex server while it is locally available as specified in the tcbuild.yaml file shown above.
On the link I sent you there is an example of how to add device trees and overlays directly on the configuration file so youâd not need to use the dto deploy command. Could you please test it to see if you can generate an image with your overlays?
Yes I did follow the steps in the link you mentioned. Without using the dto deploy command (i.e. using torizoncore-builder build), I can successfully create an image with the device tree overlay that disables UART2.
After installing it via SD card and EasyInstaller, the system came up and Iâm missing /dev/ttymxc1, i.e. UART 2 is gone as was planned, great !
The fact that I do not have the errors and that it works, means that there doesnât seem to be any error in my tcbuild.yaml and device tree overlay file.
The âEasyInstaller wayâ will work for me although it is a bit clumsy to startup in recovery mode, download EasyInstaller, select the image and copy it to Flash !
So if you have another method (a variant of the deploy command?) that installs my new image on the module, that would be nice.
Iâm glad we could make it work that way. There are a few issues with the torizoncore-builder dto deploy command that we are working on to make sure everything works. The command torizoncore-builder deploy alone usually works and then you can create your image with the build command and follow the procedure here to deploy it to the module: Building External Kernel Modules With Torizon | Toradex Developer Center. There is a dropdown fild called: Deploy The Custom Toradex Easy Installer Image.
A second option would be for you to use the TorizonPlatform to send updates over the air if the device is connected to the internet. This can be really useful if you plan to keep updating the modules once they are in the field.
Iâm sorry but there is finally an issue. When I said the deploy command works fine, that is only partially true. It does indeed install an image on the module but it is not the correct one !
When copying the new image to SD card and installing it with EasyInstaller, I see in the log that my overlay (colibri-imx7_interferometer) is added:
Executing script at 87000000
Saving Environment to MMC⌠Writing to MMC(0)⌠OK
4527 bytes read in 22 ms (200.2 KiB/s)
56570 bytes read in 30 ms (1.8 MiB/s)
143 bytes read in 27 ms (4.9 KiB/s)
Applying Overlay: colibri-imx7_parallel-rgb_overlay.dtbo
686 bytes read in 33 ms (19.5 KiB/s)
Applying Overlay: colibri-imx7_ad7879_overlay.dtbo
451 bytes read in 31 ms (13.7 KiB/s)
Applying Overlay: display-vga_overlay.dtbo
807 bytes read in 33 ms (23.4 KiB/s) Applying Overlay: colibri-imx7_interferometer.dtbo
446 bytes read in 31 ms (13.7 KiB/s)
8380928 bytes read in 209 ms (38.2 MiB/s)
8052184 bytes read in 204 ms (37.6 MiB/s)
Kernel image @ 0x81000000 [ 0x000000 - 0x7fe200 ]
But when I use the deploy command, the module does NOT show my overlay in the log. It looks like it is using the original tar-ed image that I used to build mine (the devices I disabled in my overlay, uart2 and espi3, are again present under /dev).
This is the command Iâm using:
torizoncore-builder deploy --remote-host 192.168.0.18 --remote-username torizon --remote-password colibri --reboot
Pulling OSTree with ref base (checksum e18fde565a513f5014c22060e6c60d620d0df10393358fc64e4e94fb3569daec) from local archive repositoryâŚ
Starting http server to serve OSTree.
OSTree server listening on âlocalhost:41091.â
Starting OSTree pull on the deviceâŚ
Deploying new OSTree on the deviceâŚ
Deploying successfully finished.
Device reboot initiatedâŚ
Can you please share with us your tcbuild.yaml file? Also, as a sanity check, before deploying, did you use $ torizoncore-builder images unpack your_image_output_local before doing the deploy?
When I run torizoncore-builder build, it creates a non-compressed file structure under the directory âtorizon-core-docker-colibri-imx7-emmc-Tezi_5.6.0+build.13.CUSTOMâ (not a tar file).
I did NOT run the unpack command on it. I just tried it:
$ torizoncore-builder images unpack torizon-core-docker-colibri-imx7-emmc-Tezi_5.6.0+build.13.CUSTOM
Storage not empty. Delete current image before continuing? [y/N] y
Copying Toradex Easy Installer image.
Unpacking TorizonCore Toradex Easy Installer image.
Importing OSTree revision 267cead20797c86730990b268d83e5f4e8a06e1c15549a0841282b88b1b10ab1 from local repositoryâŚ
1083 metadata, 12635 content objects imported; 405.9 MB content written
Unpacked OSTree from Toradex Easy Installer image:
Commit checksum: 267cead20797c86730990b268d83e5f4e8a06e1c15549a0841282b88b1b10ab1
TorizonCore Version: 5.6.0+build.13-tcbuilder.20220701112339
And now it works. when running deploy I see that my overlay appears in the log of the module when it reboots.
So, as I understand it correctly, instead of having to unpack the âinputâ tar file, I have to unpack the result of the build command.
Just a bit confusing since I have to unpack a non-compressed output result while I donât need to unpack the compressed / tar-ed input fileâŚ
