Virtual kernel memory layout:įixmap : 0xffc00000 - 0xfff00000 (3072 kB)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) PID hash table entries: 4096 (order: 2, 16384 bytes) Built 1 zonelists, mobility grouping on. random: get_random_bytes called from start_kernel+0xac/0x448 with crng_init=0 Normal zone: 255488 pages, LIFO batch:31 free_area_init_node: node 0, pgdat 8148aec0, node_mem_map bd336000 OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
CPU: div instructions available: patching division code CPU: ARMv7 Processor revision 4 (ARMv7), cr=10c5383d Nothing of note in dmesg.įirst device we want to get working at /dev/ttyUSB0 is idVendor=10c4, idProduct=8a5b. I have restarted the system and the container had trouble starting the USB device the first few attempts. We have also tried to mask off the serial-getty service, as indicated in this post.Īny tips or guidance would be appreciated and I will report back here if I find anything of note. We have tried to disable UART in the device config (on the Balena platform), but this has had no effect.
This leads me to want to understand better how to eek out the maxium performance between a docker container and the base OS so that the fewer man-in-the-middle processes cause delays / corruption / bottlenecks. device reports readiness to read but returned no data. When the data is corrupt / not available, pyserial throws the following errror: Here is a snippet of the configuration: serial: The system is currently running balenaOS 2.31.5+rev1 and supervisor 9.11.3, although this problem persists into the newer base systems.
(Once device is /dev/ttyUSB0 and the other is /dev/ttyACM0) In fact we have seen situations where on opening one device, the other throws data errors, indicating there is some process in the middle that is causing the issue. While the devices are available to the containers (via privileged mode or devices config in ), we are experiencing issues with throughput / dropped bytes between PySerial and the devices.
We have a project that has a couple of containers that both need access to two specific (and present at boot) USB serial devices (by SiLabs and NXP).