We’re evaluating the Torizon Platform with the TorizonCore image. Our board uses the VUB300 USB controller, but It seems like the support for VUB300 MMC/SDIO is not enabled in the current kernel of TorizonCore 5.7.0 (
What options do we have to get support for the mentioned config in the kernel? And in which time frame?
Thanks in advance,
- Colibri IMX8QXP
- TorizonCore 5.7.0
- Torizon Builder 3.7.0
We certainly can enable that config option for you. However, you are currently on TorizonCore 5.7.0 which is an LTS release. Our LTS releases once initially released only contain bug fixes going forward. We do not typically add features or change the kernel config once released.
At the moment we are only taking requests for new kernel configs on TorizonCore 6.X which is in active development by our team. Now I see you are on the Colibri i.MX8X which does not have a stable TorizonCore 6.X release yet, but our team recently have things working on this module in recently nightly builds.
All that to say, it’s unlikely we add this to TorizonCore 5.7. But we are more than happy to add it to TorizonCore 6.X. That said, are you willing to eventually migrate your development to TorizonCore 6.X?
Thanks for your reply @jeremias.tx .
A migration to 6.x is an option as soon as it can be considered as “stable”. Do you have a timeline to share regarding the release of 6.x?
Can you recommend other options for us to get support for VUB300 with TorizonCore 5.7.0, like …
- building the module out-of-tree?
- building our own TorizonCore image with Yocto (although it seems to be an overkill)?
- use an alternative (change hardware) to VUB300 which is supported by the TorizonCore 5.7.0 kernel?
Do you have a timeline to share regarding the release of 6.x?
The plan is to have the Colibri i.MX8X supported with the 6.3.0 Quarterly release, assuming nothing goes wrong. We are currently in the process of creating the release for the 6.2.0 Quarterly, which is planned for the start of April 2023. However, the Colibri i.MX8X didn’t make it in time for this release, which is why I said we plan for 6.3.0 instead. The 6.3.0 release will be in about another quarter or so (around July or so). That said this is the current outlook and things could change.
Just to clarify we do have recent nightly builds of Colibri i.MX8X booting on TorizonCore 6.X, though this just happened recently so there might still be some kinks to work out.
building the module out-of-tree?
You could, though I can’t gurantee how this driver will work as an out-of-tree module. You’ll also need to maintain this out-of-tree module variant.
building our own TorizonCore image with Yocto (although it seems to be an overkill)?
This is also another okay option.
use an alternative (change hardware) to VUB300 which is supported by the TorizonCore 5.7.0 kernel?
If your project is flexible enough this is also another option.
Other than these options you’ve listed I can’t think of anymore practical options.
@lzaugg_parametric I see you marked my last response as a solution. Does that mean you will work around this on TorizonCore 5, or do you want us to add this config in TorizonCore 6?
@jeremias.tx Thanks for asking - almost forgot. The answer is yes and yes (please). We will do a workaround (probably not the hardware replacement) for 5.7.0 until a migration to 6.x gets feasible. It would be appreciated to have VUB300 support in TorizonCore 6.x - because we’re planning to use Torizon on different products, long term.
Thanks a lot,
Alright I put the request to our team. If there are no issues found then I expect it to be added to our default kernel configuration within a week or so. I will try and let you know when this has been done though.
Just to give an update, this config is a part of our default kernel configuration now. Also our recent nightly builds for TorizonCore 6.X are now booting on the Colibri i.MX8X. Therefore you can give this a try if you’d like.