CODESYS Soft Licensing Support on Verdin iMX8 Mini (Torizon OS)

Technical Support
, ,
22

Hi @jeremias.tx ,

Thank you for the update and your support.

Best regards,

Mehrdad

23

I consulted internally with the team.

First of all, I was slightly mistaken. This new article while Codesys related doesn’t fully go into the details of licensed usage. We’re still waiting on Codesys for some items and responses before we can proceed on this point.

As for the step you’re stuck on. It’s unclear currently why it’s occurring. That specific step doesn’t actually rely on the docker-compose running on the device just yet. This is just about establishing a connection between the host PC and the Toradex module. Does this step work if the compose is not running?

Best Regards,
Jeremias

1 Like
24

Hi Jeremias,

I rebuilt the Target-Visu stack exactly as in the new article.
Containers are Up, no errors:

  • weston-xutils:latest

  • targetvisu:latest (contains codesyscontrol 4.18.0.0 + TargetVisu 4.16.0.0)

  • -rw-r–r-- 1 torizon torizon 1236 Nov 21 16:10 Dockerfile.targetvisu
    -rw-r–r-- 1 torizon torizon 459 Nov 21 16:09 Dockerfile.weston
    -rw-r–r-- 1 torizon torizon 34733344 Nov 21 16:07 codemeter-lite_8.40.7120.501_arm64.deb
    -rw-r–r-- 1 torizon torizon 14894894 Nov 21 16:07 codesyscontrol_linuxarm64_4.18.0.0_arm64.deb
    -rw-r–r-- 1 torizon torizon 2643942 Nov 21 16:07 codesysvisualization_visualizationarm64_4.16.0.0_arm64.deb
    -rw-r–r-- 1 torizon torizon 777 Dec 4 15:30 docker-compose.yml
    -rwxr-xr-x 1 torizon torizon 180 Nov 21 16:10 targetvisu-entry.sh
    -rwxr-xr-x 1 torizon torizon 179 Nov 21 16:10 weston-xutils-entry.sh

Runtime ports are bound on the host:

udp 0 0 10.50.49.54:1740 0.0.0.0:* codesyscontrol
udp 0 0 10.50.49.54:1741 0.0.0.0:* codesysvisualisation

From the Windows IDE I can:

  • add IP address 10.50.49.54:1217 → status “Connected”

  • But as soon as I switch to “Operation → Add instance” the green “+” is greyed out and the same error dialog pops up that I reported earlier.

The article still tells users to start the Virtual Edge Gateway container (codesys_gateway) and then add an instance of that container.
With the real runtime already inside the Target-Visu container there is no separate gateway image to instantiate, so the “+” button has nothing it can start.

image
image375×119 35.3 KB

Thanks,
Mehrdad

image
image1280×960 157 KB

25

Could you try just following steps in the IDE without anything running on the board (no compose or other containers running). Just have the board on, but idle. The steps in the IDE should work independently of whatever is happening on the board.

The article still tells users to start the Virtual Edge Gateway container (codesys_gateway) and then add an instance of that container.
With the real runtime already inside the Target-Visu container there is no separate gateway image to instantiate, so the “+” button has nothing it can start.

I think there’s some confusing here.

The Virtual Edge Gateway is only installed, and it will be run after the user adds an instance of it. Also, the gateway is entirely different from the codesys runtime, so it should start in another container after adding an instance of it, separated from the docker-compose-initiated containers.

Best Regards,
Jeremias

1 Like
26

Hi @jeremias.tx ,

Thanks for your time.

there is no doucker running on my device.

image
image655×197 9.77 KB

I’m already on the newest Virtual Edge Gateway for Linux ARM64 SL 4.18.0.0 image; no newer package is offered in the store.

The crash happens after updating that click the “+” dialogue for creataing an instance

afterr connceting the device without any issue

image
image1903×1038 39.1 KB

insttalled Virtual Edge Gateway for Linux ARM64 SL 4.18.0.0

image
image1918×1039 44.7 KB

as soon as I click on + icon this error comes

image
image1919×1041 66.2 KB

I have attached txt file, error detials, might be helpful on your side

error while clicking + dialog.txt (176.6 KB)

Thanks for the help so far.

Best regards,
Mehrdad

27

It’s strange, our team is not able to replicate or even see anything close to the error you’re observing.

Since this part is not reliant on what is happening on the device yet. I can only speculate it must be something on the host PC side. Though hard to point at anything specifically with the few details given, the error log isn’t terribly helpful for narrowing things down either. Maybe something got mis-configured or installed strangely? That would be my next guess.

Best Regards,
Jeremias

1 Like
28

Hi @jeremias.tx

I now tested on an older module that still runs TorizonCore 6.2.0.

torizon@verdin-imx8mm-07201697:~$ cat /etc/os-release
ID=torizon
NAME=“TorizonCore”
VERSION=“6.2.0+build.2 (kirkstone)”
VERSION_ID=6.2.0-build.2
PRETTY_NAME=“TorizonCore 6.2.0+build.2 (kirkstone)”
DISTRO_CODENAME=“kirkstone”
BUILD_ID=“2”
ANSI_COLOR=“1;34”
VARIANT=“Docker”
torizon@verdin-imx8mm-07201697:~$ uname -a
Linux verdin-imx8mm-07201697 5.15.77-6.2.0+git.aa0ff7e3554e #1-TorizonCore SMP

With the same Windows PC / IDE / Virtual-Edge-Gateway 4.18.0.0 the “+” dialogue works and the gateway container starts.

image
image1915×1074 195 KB

image
image1912×1072 205 KB

image
image1919×1079 209 KB

On the new module with Torizon OS 7.4.0 the IDE add-on crashes (stack-trace already sent).

So the behaviour you see is not reproducible on 7.4 simply because the OS on my new module is already newer than the one your team tested against, and the IDE deploy tool is not yet compatible with that combination.

If you need me to run any specific test on 6.2 in the meantime just let me know.

Best regards,
Mehrdad

29

Let me check with our team and run some tests. That’s odd that 6.2.0 works, but not 7.4.0.

Just to check is it specifically 6.2.0, or does a later version of 6.X work as well, like 6.8.X for example?

Best Regards,
Jeremias

1 Like
30

Hi @jeremias.tx

I flashed a fresh module to TorizonCore 6.8.4-build.40 and repeated the exact same steps.
The result is identical to 7.4.0: the IDE can connect to the gateway, but as soon as I press the “+” button the same .NET NullReferenceException pops up and no instance can be added.

torizon@verdin-imx8mm-07220314:~$ torizon@verdin-imx8mm -sh: torizon@verdin-imx8mm: command not found torizon@verdin-imx8mm-07220314:~$ cat /etc/os-release ID=torizon NAME=“TorizonCore” VERSION=“6.8.4+build.40 (kirkstone)” VERSION_ID=6.8.4-build.40 PRETTY_NAME=“TorizonCore 6.8.4+build.40 (kirkstone)” DISTRO_CODENAME=“kirkstone” BUILD_ID=“40” ANSI_COLOR=“1;34” VARIANT=“Docker” torizon@verdin-imx8mm-07220314:~$ uname -a Linux verdin-imx8mm-07220314 5.15.191-6.8.4+git.88e9f1ec02f8 #1-TorizonCore SMP PREEMPT Sun Sep 14 21:18:28 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux torizon@verdin-imx8mm-07220314:~$ uname -r 5.15.191-6.8.4+git.88e9f1ec02f8 torizon@verdin-imx8mm-07220314:~$ sudo ostree admin status We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. For security reasons, the password you type will not be visible. Password: * torizon d54af1269f0a6e87a08b06da70a31332bc0b0ccd5bcc833b827c2dd548837dba.0 Version: 6.8.4+build.40-tcbuilder.20251021151838 origin refspec: torizon

For completeness: the only things running on the 6.8.4 module right now are the Torizon easy-pairing containers (view + server on port 3030); no CODESYS-related container is up.

torizon@verdin-imx8mm-07220314:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d3388f713300 torizonextras/easy-pairing-view “./erosView” 15 minutes ago Up 15 minutes torizon-easy-pairing-view-1 ad737ffa0bcc torizonextras/easy-pairing-server “node out/lib/index.…” 15 minutes ago Up 15 minutes 0.0.0.0:3030->3030/tcp, :::3030->3030/tcp torizon-easy-pairing-server-1

Best regards,
Mehrdad

31

Yeah something is not making sense here. We don’t see this issue where the version of Torizon OS on the module matters on our end. When you tested with 6.2.0 was this using the same exact setup on your host PC with the same exact Codesys IDE installation?

Otherwise something here is strange. This new article was written way after 6.2.0 was even released, and it was written for the latest 7.X versions specifically. So it wouldn’t make sense that it only works retroactively on the older 6.2.0.

Unfortunately, I’m at a bit of a loss of what else to suggest here. The observations you’re seeing don’t make sense to us, and are not reproducible.

Are there any other versions you have tried? Is it just 6.2.0 that works?

Best Regards,
Jeremias

1 Like
32

Hi @jeremias.tx ,

Quick summary on my side:

  • Same PC, same IDE, same Verdin iMX8-Mini

  • 6.2.0 → “+” button opens, gateway starts

  • 6.8.4 & 7.4.0 → identical crash, 100 % repeatable

All I need now is the shortest possible path to drop my CODESYS soft-license into the running runtime so I can download a one-ladder, one-visu test project and see it on the local display.

Best regards,

Mehrdad

33

Our team will try to look into this though, again it’s strange the version of the OS affects the outcome for you in the way that it does.

Also just to be clear, this article does not go into soft-licensing. We are still trying to work out a solution with Codesys on that topic.

Best Regards,
Jeremias

1 Like