June-15th-2021, 12:19 PM
(June-15th-2021, 12:03 PM)Armin@netPI Wrote: Oh Roy to be honest ... I do not know it how the exact boot behavior of the netPI OS really is in cases where there is a conflict between the settings made in the config.txt file compared to the settings in the EEPROM of the NPIX/HAT modules and which one finally wins.
What I can definitively say is that we are taking the sources from the original Raspbian OS and recompile it as netPI OS. So it just has a Hilscher touch ... but main behaviour of both OSs are the very same. So if Raspbian OS does not support resolving conflicts between config.txt and EEPROM settings, then our netPI OS can't be better than the behaviour of the official Raspbian OS. So to your question: "if I would have the RS232 expension(with the eeprom) then the overlay will work as expected" ... I cannot guarantee it since I have never every tested it what happens if the original config.txt says /dev/ttyAMA0 goes to UART for Wifi/Bluetooth and then an EEPROM comes and say /dev/ttyAMA0 goes to standard UART via the standard tx/rx pins put on the NPIX slot. Today all our NPIX modules are using the mini UART like it is configured via the standard config.txt
Do you know how a standard Raspberry Pi behaves on this setting when using a HAT module with EEPROM? Cause then the same behaviour will be on netPI.
Thx
Armin
I dont know much about the HAT feature and how it is working.
maybe I need to add some info about what we are trying to do.
on original raspian image we do the following:
adding to /boot/overlay the following files:
disable-bt.dtbo
uart-ctsrts.dtbo
we add to the config.txt file:
enable-uart=1
dtoverlay=disable-bt
dtoverlay=uart-ctsrts
the out come is that minicom(weaker uart) is muxed to the BT pins and PL011 is muxed to pins 14,15 cts rts is in 16,17
doing this procedure in nefied works fine in the container. with netpi not yet.
what am I missing ?
