auderer mailto:l...@c-mauderer.de>>,
"rtems-de...@rtems.org<mailto:rtems-de...@rtems.org>"
mailto:devel@rtems.org>>
Subject: Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3
I looked at the source code for UART. RTEMS uses the PL011 which is by default
connect
I'm not that sure that the right UART is used. The driver in the
raspberry BSP doesn't care for the configuration file. So it most likely
always uses the same UART regardless what the bootloader tells.
The
dtoverlay=disable-bt
in the config file just adds a devicetree overlay. We currently don
;
> devel@rtems.org>
> *Subject: *Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3
>
>
>
> I looked at the source code for UART. RTEMS uses the PL011 which is by
> default connected to the bluetooth module, but this can be changed by
> adding disable-bt command t
e: Problem running RTEMS on raspberrypi3
I looked at the source code for UART. RTEMS uses the PL011 which is by default
connected to the bluetooth module, but this can be changed by adding disable-bt
command to the config.txt
this will configure PL011 as the primary uart. So I don't think anyt
I looked at the source code for UART. RTEMS uses the PL011 which is by
default connected to the bluetooth module, but this can be changed by
adding disable-bt command to the config.txt
this will configure PL011 as the primary uart. So I don't think anything
has to be changed.
On Mon, Dec 16, 2019
Has the RPI3 UART/Console been addressed in RTEMS?
My understanding is that the RPI 1, Zero (without wireless) and 2 all share the
same UART/Console driver. But the Raspberry Pi 3 and Zero W use that UART to
talk to the Bluetooth module. The “mini” UART is then used for the console.
So, at a mini
