January-16th-2020, 12:27 PM
(This post was last modified: January-16th-2020, 12:52 PM by Armin@netPI.)
One remark: If you would use netPI during your first tests with the original Raspbian OS image (with antoher SD card you insert into netPI's SD card slot) instead of the secured netPI image then you have much more options to enable SPI, TTY and so on using netx to "raspi-config" tool also the config.txt file as described here https://www.raspberrypi.org/documentatio...onfig-txt/
For example to enable the /ttyS0 interface you have to add the
entry in the confix.txt file.
The config.txt file serve to statically configure the Linux device tree ... while the ID EEPROM is made for flexible and dynamic use without the need to make edits in config.txt by any user. It is adjusting the Linux hardware device tree automatically.
For example to enable the /ttyS0 interface you have to add the
Code:
enable_uart=1
entry in the confix.txt file.
The config.txt file serve to statically configure the Linux device tree ... while the ID EEPROM is made for flexible and dynamic use without the need to make edits in config.txt by any user. It is adjusting the Linux hardware device tree automatically.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)