Hello
I work with the Verdin imx8m mini dual SOM and the apolloX extension for vsc.
When I try to do a Torizon AMD64 build for a c++ project, the task ‘build-container-torizon-debug-amd64’ fails because there is no image torizon/debian for AMD64 available (there is for arm and arm64). Dockerfile involved: Dockerfile.debug: line 33f
FROM --platform=linux/${IMAGE_ARCH}
torizon/debian:${BASE_VERSION} AS Debug
Do you provide another torizon/debian image for that? I like to debug my cpp Code first in a running container on my Host. I’ve done all the settings in the extension so that “torizon_arch”: “amd64” is set.
At the moment we only provide container images for our hardware which is arm-based. Just so I understand, what’s the purpose or reason for trying to run and debug on your development host? Do you not have the Toradex hardware available yet?
Thanks for your answers. @jeremias.tx : we have Toradex HW available. But we are several people working on the project, some of them do the HW stuff, others only our business logic. Debugging for business logic in container running on the host has the advantage that they do not have to install all libs on their host and it is nearer to the final target system. We even wanna have connection from containers running on the target (for HW relevant data) with containers running on the host (for business logic).
I just wonder why you do not support AMD64 torizon/debian package, because in the apolloX extension generated tasks (task.json) have the task ‘build-container-torizon-debug-amd64’. Also the cross toolchain am64 image is available from the torizon hub.
We even wanna have connection from containers running on the target (for HW relevant data) with containers running on the host (for business logic).
Oh so if I understand then, you plan to have part of your application stack, some containers running not on Toradex hardware but on x86/amd64 hardware instead? Then these would interface with the containers running on the Toradex hardware, did I understand that correctly?
I just wonder why you do not support AMD64 torizon/debian package, because in the apolloX extension generated tasks (task.json) have the task ‘build-container-torizon-debug-amd64’.
We have some interest in creating x86/amd64 containers but this is far from ready at the moment. This task would work theoretically if users provide their own x86/amd64 containers. I mean in the end we sell arm based hardware so our focus will always be on this primarily.
Also the cross toolchain am64 image is available from the torizon hub.
As the name suggests this is a container for cross-compiling. Therefore it runs on an x86/amd64 host to cross-compile arm software. This is just a build container it’s not the actual container that would be ran on the target hardware.
Sorry, there is a typing error. Not ‘cross toolchain am64’, but ‘cross toolchain amd64’.
There are no cross compilier in the ‘cross toolchain amd64’ container. They are in the ‘cross toolchain arm64’ container.
But it’s ok. I just have to use my own linux amd64 container instead of the torizon/debian container, and then all works perfect.
Thanks a lot for your support!
Best regards,
pitschen
We just released amd64 containers under the 4-bookworm-rc (for torizon/debian) and 4-rc (for all other containers) tags.
It’s a release candidate, and although we can’t guarantee everything works, it should be somewhat stable as it is built under the current stable release of Debian, so pretty much the same as our non-rc images. Hope this makes things easier for you, seems like a cool use-case!
Please keep in mind our provided containers were designed and tested for use on devices running TorizonCore. In your case it sounds like you’d be using some host/server machine that isn’t running TorizonCore. Now these containers should still run at a basic level on your machine since it’s amd64, but keep this in mind if you run into any quirks or issues.
