![]() Scripts/kconfig/conf -silentoldconfig Kconfig Scripts/kconfig/menu.c:548:19: note: 'jump' was declared here Scripts/kconfig/menu.c:587:18: warning: 'jump' may be used uninitialized in this function Scripts/kconfig/menu.c: In function 'get_symbol_str': In file included from scripts/kconfig/:2537:0: Make: Entering directory '/usr/lib/modules/3.14.4-1-ARCH/build' If the driver on the base OS could be updated, then this would not be an issue (as the container can access /dev/ttyUSB0 fine), it just does not recognise our dongle!Īny ideas on how we can progress on this, as otherwise it looks like we need to find a different solution.Make -C /lib/modules/3.14.4-1-ARCH/build M= modules ![]() Is there a way to have a custom module added to the base OS (which is read-only)? We have even tried to build the module with a different name to see if there is a conflict that way, but the balenaOS is still winning most of the time at grabbing the device. No matter of how much rmmod / ins mod / modprob’ing that is done, it’s just not reliable or very repeatable. I have compiled the driver in a Raspbian stretch container (build version) and that sometimes loads, but it would appear that the base balenaOS is also trying to load and there is a race condition / conflict with the containered OS trying to access the cp210x / usbserial module. The source files need to be updated to add the VID and PID of the serial device, which can usually be done on a standard OS (Raspbian, etc.) by simply replacing the cp210x.ko module file. We have a USB serial device that is not supported by the default cp210x driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |