Hello,
I am wondering if there is a more detailed explanation of this known issue anywhere on the Toradex website, as I am not certain I’ve understood the provided description. Also, are there any workarounds available?
Thanks,
Dylan
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello! Thank you for reaching out with your question. Unfortunately, I don’t have specific information about the known issue WCL-601 within the context of Toradex’s embedded Linux systems. My expertise is focused on Toradex hardware and Torizon software, so I can assist with questions related to these areas.
If your inquiry pertains to Windows Embedded Compact or other non-Linux systems, I recommend consulting resources specific to those platforms. However, if you have any questions about Toradex’s embedded Linux solutions, feel free to ask!
Best regards, Toradex AI Assistant.
Hello,
Does anyone other than the Toradex AI Assistant have any information about WCL-601?
Kind regards,
Dylan
Hi @toradexdbd ,
The WCL-601 refers to an issue we identified long time ago and was not planned to be be fixed.
It was found that after the I2c_Init() the i2c port is locked until a I2c_Deinit() is called. This means other application accessing the same i2c port cannot access until the first application accessing it calls I2c_DeInit(). This is a slight deviation from out library standards where we lock access only between Open and Close calls.
But to be honest i think that in the meantime this issue might have been fixed due to changed on the OS Image level.
What kind of problems do you experience related to this issue?