is there a way to enable the mini-UART on the GPIO header on the Pi3 in OSMC?
Under Raspbian Jessie - if I add enable_uart=1 to config.txt - I can use ttyS0 (or serial0), but under OSMC adding enable_uart=1 to config.txt doesn’t seem to have any effect.
I don’t need a serial console, ssh is fine. And isn’t ttyAMA0 bound to Bluetooth?
I just want to use the mini UART ttyS0, like the default Raspbian configuration for the Pi 3 with some self written software.
This is possible, but I don’t have to do this under raspbian, (except for the enable_uart=1 line in config.txt), so why would this be needed for OSMC?
Is the boot process / loader / firmware different?
What overlay would this be? I haven’t found anything useful in the overlays directory.
Or could it be, that the kernel doesn’t detect the actually (hardware wise) working uart1 configuration?
Hi @sam_nazarko, do you think you can you have a look at this issue ?
It is a getting quite frustrating to loose access to the GPIO UART ports when using OSMC on a Rpi3 …
It broke some of my integrations, like ambilight clone, or a IR receiver, that both used UART.
I know that disabling Bluetooth allows to re-assign the hardware UART to GPIO to get the same features as the Rpi2, but it is not an option … I bought a Rpi3 to also use bluetooth as part of my projects, not to disable it
As a reminder, Raspbian exposes 2 UART on the Rpi3 - we should get the same feature-set on OSMC:
/dev/ttyAMA0 which is the hardware UART of the BCM chip, and used by the Bluetooth chip (and you also use it in OSMC)
/dev/ttyS0 that needs to be enabled in config.txt (enable_uart=1) that connects to the UART GPIO ports (the same as Rpi2). It is a software based UART. This should be use in all projets needing GPIO UART. It is missing from OSMC.