October-22nd-2019, 12:42 PM
(October-22nd-2019, 12:10 PM)Armin@netPI Wrote: Well, a device "/dev/..." in a container is as good as if you would access it on a native host. This is all managed by Docker automatically and is not related to netPI or its hardware.I mapped /dev/ttyACM0 as /dev/ttyS0. It was same as your suggestion. Luckily your yocto build and raspbian uses same driver.
The very same applies for any software that runs in a container. Python runs the same as on a native host.
These three restrictions we have on netPI
* privileged mode is not automatically adding all host devices /dev/ to a container
* volume bind mounts to rootfs is not supported
* the devices /dev,/dev/mem,/dev/sd*,/dev/dm*,/dev/mapper,/dev/mmcblk* cannot be added to a container
Others are not know by me or my team.
So to which device was your CDC device finally mapped to? How did you find it?
You say you have a problem with python. Which problem do you have?
Thx
Armin
I checked image file and found out pi isn't added to dialout group and mounted /dev/ttyS0 didn't have other users access.
After adding pi to dialout group i also changed permissions of /dev/ttyS0 to 666 then everything started working.
But not able to see enumareted device is still big question mark for me to continue.
