June-15th-2021, 11:38 AM
To your question about "why the ttyAMA0 is not working in the container" on netPI. As you know on netPI the /dev/ttyAMA0 is configured to be used as UART interface for the onboard Wifi/bluetooth chip. I am pretty sure on netPI changing the config.txt file is not possible at all so that on netPI the physical interface /dev/ttyAMA0 is still running as UART for the wifi/bluetooth chip. The UART modes are descibed here: https://www.raspberrypi.org/documentatio...on/uart.md
So back to your question. You will be able to map the /dev/ttyAMA0 into the container but it is running in the wrong mode. I have doubts that "first thing I tried to do is to modify the boot partition to support the ttyAMA0. (I have done it on netpi and field connect)" works on netPI. It has multiple copies of the config.txt file and the one you edited may not be the correct one. I have never tried it myself to change anything on netPI config.txt file. On netFIELD Connect gateway this may be different.
So back to your question. You will be able to map the /dev/ttyAMA0 into the container but it is running in the wrong mode. I have doubts that "first thing I tried to do is to modify the boot partition to support the ttyAMA0. (I have done it on netpi and field connect)" works on netPI. It has multiple copies of the config.txt file and the one you edited may not be the correct one. I have never tried it myself to change anything on netPI config.txt file. On netFIELD Connect gateway this may be different.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
