Which exact image is it? 2.0 final is currently not released. Is it 2.0 beta 4? Do you have any debug output available while this happend? Any way to reproduce the issue or it just happens once and can not be reproduced any longer?
@Saphymo: Are you using the latest I2C Lib from the lib package 2.0? I remember we earlier had issues with the I2C Lib. The power management of the device is also done over I2C, if something goes wrong there, it could freeze the device.
One other thing you could do to check this situation: If you disable DFS, you should see the freezes less often. If this is the case and you are already using the latest libs, it is likely, there is a bug in the I2C library. Let me know your findings.
In one of the previous posts your wrote, that the freeze happens if the SD gets corrupted. I this still true or did you see the freeze also independently?
If it is still true, do you see any output on the debug output in case of a freeze? Could it bee the application somehow blocks everything in case of a SD corruption, because it reads wrong data?
If this issue is an independent issue, could you once try to reproduce it a litte bit more deterministic as mentioned before. Is the freeze still there in case the DFS is disabled? (Disable DFS in the Colibri Monitor)
Dear Samuel.Tx,
According to current knowledge, it looks as follows:
The freezing of the operating system happens when a file on the SD card is corrupt and then a read access to this file takes place.
The files on the SD card corrupt through the I2C.dll of Toradex. If the I2C communication is reduced I have less problems. (actual .Dll)
Today, however, the whole operating system has been destroyed. Only a flashing could solve the problem.
Debug messages I can not see. (Communication via RS232).
The problem comes definitely from the operating system or components of Toradex.
DFS I now disabled. However, we need DFS because of the power consumption, this was one of the purchase decision for Toradex.
@Saphymo: Thanks for this update. On our side, we also still try to identify the source of the issue. If you have any sample project which can be used to easily reproduce the issue we would be happy to get it to speed up tracking down the issue.