KasperskyOS Community Edition 1.3

Limitations and known issues

Because the KasperskyOS Community Edition is intended for educational purposes only, it includes several limitations:

1. When a program is terminated through any method (for example, "return" from the main thread), the resources allocated by the program are not released, and the program goes to sleep. Programs cannot be started repeatedly.
2. You cannot start two or more programs that have the same EDL description.
3. The system stops if no running programs remain, or if one of the driver program threads has been terminated, whether normally or abnormally.
4. When connecting different USB devices, the device-id counter increases by a different value.
5. Some examples contain errors in the boot and execution logs that do not affect the functionality.
6. When running examples on the Raspberry Pi 4 Model B hardware platform, the maximum size of the solution image (kos-image file) must not exceed 248 MB, and 146 MB when running on the Radxa ROCK 3A hardware platform.
7. Full functionality of the Rust language cannot be guaranteed.
8. Full porting of third-party libraries to KasperskyOS cannot be guaranteed.
9. Network packets may be delayed after KasperskyOS startup due to operation of the STP protocol.
10. Some GPIO pins of hardware devices may contain external pull-up resistors. If these types of resistors are present, weaker internal resistors will not allow these pins to be pulled to 0.
11. After finishing examples that use the network, running processes of an example may remain in the system in QEMU by using the Ctrl+C key combination.
12. Removed support for performance counters from the KasperskyOS kernel in the SDK. Removed the perfcnt example from the SDK.
13. The libc library API supported by VFS has a limit of 30 VFS clients and 5 threads per client.
14. Only USB 2.0 devices work in USB 3.0 ports of the Radxa ROCK 3A hardware platform.