Greetings @alt.mattr,
I’m glad to hear you’re having a good experience with Torizon on the 6ULL. Allow me to clear up what the situation is regarding the support of this platform.
specifically why is it not
recommended? I assume it is better
tested than any custom yocto image I
might build for example
Torizon as you might’ve figured out relies heavily on container usage rather than traditional embedded workflows. Containers have a overhead when it comes to memory and flash usage compared to non-container equivalents. Since the 6ULL only has 512MB RAM and flash, it is more susceptible to running into issues due to these hardware constraints. As such we usually don’t recommend this configuration just to avoid any potential headaches for customers.
In the end this relies on the exact use-case though. I assume your particular use-case is light enough that it doesn’t run into these issues. Just be aware of these limitations as you work with this platform.
what are the chances that it will work
with torizon OTA in the future?
The support with OTA on the 6ULL is similar to on Torizon. It “should” work on a basic level, but it’s more liable to have issues.
can you give me any recommendations to
start measuring the health of the
flash memory with torizon?
This isn’t an easy question and depends on many factors. I’d suggest looking at this webinar we did about flash memory and monitoring the health of it: Webinar: Flash Memory in Embedded Linux Systems
Out of curiosity though, what kind of work load do you have that you are concerned about the health of the flash?
Finally I just wanted to share that we here at Toradex have planned a variant of the 6ULL with eMMC flash. This variant is planned to be fully supported and tested on Torizon and OTA. So this might be something you should keep an eye out for.
Best Regards,
Jeremias