Re: [rtems commit] psxrwlock01: Use an initilized lock for tests

[Joel Sherrill]

I think the ticket was targeting 5 as the milestone. You should push this
to 5 also if it applies.

On Fri, Oct 7, 2022, 12:15 AM Sebastian Huber  wrote:

> Module:rtems
> Branch:master
> Commit:46f08961a22ff7ffc6196971c0ff04006689ded1
> Changeset:
> http://git.rtems.org/rtems/commit/?id=46f08961a22ff7ffc6196971c0ff04006689ded1
>
> Author:Sebastian Huber 
> Date:  Fri Oct  7 07:14:02 2022 +0200
>
> psxrwlock01: Use an initilized lock for tests
>
> Close #4738.
>
> ---
>
>  testsuites/psxtests/psxrwlock01/test.c | 28 
>  1 file changed, 20 insertions(+), 8 deletions(-)
>
> diff --git a/testsuites/psxtests/psxrwlock01/test.c
> b/testsuites/psxtests/psxrwlock01/test.c
> index 5767aa7c07..f6954007c0 100644
> --- a/testsuites/psxtests/psxrwlock01/test.c
> +++ b/testsuites/psxtests/psxrwlock01/test.c
> @@ -454,10 +454,6 @@ int main(
>status = pthread_rwlock_timedrdlock( NULL, &abstime);
>rtems_test_assert( status == EINVAL );
>
> -  puts( "pthread_rwlock_timedrdlock( &rwlock, NULL) -- EINVAL" );
> -  status = pthread_rwlock_timedrdlock( &rwlock, NULL);
> -  rtems_test_assert( status == EINVAL );
> -
>puts( "pthread_rwlock_tryrdlock(NULL) -- EINVAL" );
>status = pthread_rwlock_tryrdlock(NULL);
>rtems_test_assert( status == EINVAL );
> @@ -470,10 +466,6 @@ int main(
>status = pthread_rwlock_timedwrlock( NULL, &abstime );
>rtems_test_assert( status == EINVAL );
>
> -  puts( "pthread_rwlock_timedwrlock( &rwlock, NULL) -- EINVAL" );
> -  status = pthread_rwlock_timedwrlock( &rwlock, NULL);
> -  rtems_test_assert( status == EINVAL );
> -
>puts( "pthread_rwlock_trywrlock(NULL) -- EINVAL" );
>status = pthread_rwlock_trywrlock(NULL);
>rtems_test_assert( status == EINVAL );
> @@ -482,6 +474,26 @@ int main(
>status = pthread_rwlock_unlock(NULL);
>rtems_test_assert( status == EINVAL );
>
> +  status = pthread_rwlock_init( &rwlock, NULL );
> +  rtems_test_assert( status == 0 );
> +
> +  status = pthread_rwlock_wrlock( &rwlock );
> +  rtems_test_assert( status == 0 );
> +
> +  puts( "pthread_rwlock_timedrdlock( &rwlock, NULL) -- EINVAL" );
> +  status = pthread_rwlock_timedrdlock( &rwlock, NULL);
> +  rtems_test_assert( status == EINVAL );
> +
> +  puts( "pthread_rwlock_timedwrlock( &rwlock, NULL) -- EINVAL" );
> +  status = pthread_rwlock_timedwrlock( &rwlock, NULL);
> +  rtems_test_assert( status == EINVAL );
> +
> +  status = pthread_rwlock_unlock( &rwlock );
> +  rtems_test_assert( status == 0 );
> +
> +  status = pthread_rwlock_destroy( &rwlock );
> +  rtems_test_assert( status == 0 );
> +
>/*** BAD ID CHECK */
>/* make a valid abstime */
>puts( "clock_gettime(CLOCK_REALTIME, &abstime) -- OK" );
>
> ___
> vc mailing list
> v...@rtems.org
> http://lists.rtems.org/mailman/listinfo/vc
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-docs v4] raspberrypi4.rst: Documentation for the new AArch64 Raspberry pi 4B BSP

[Kinsey Moore]

Looks good to me. Thanks for sticking with this!


Kinsey

On 10/7/2022 00:00, Mohd Noor Aman wrote:

This patch adds the relevant documentations required for booting the new BSP.
JTAG support is added for debugging. I have built the HTML docs and verified
them.
---
  user/bsps/aarch64/raspberrypi4.rst | 111 +
  user/bsps/bsps-aarch64.rst |   1 +
  2 files changed, 112 insertions(+)
  create mode 100644 user/bsps/aarch64/raspberrypi4.rst

diff --git a/user/bsps/aarch64/raspberrypi4.rst 
b/user/bsps/aarch64/raspberrypi4.rst
new file mode 100644
index 000..b36d47b
--- /dev/null
+++ b/user/bsps/aarch64/raspberrypi4.rst
@@ -0,0 +1,111 @@
+.. SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. Copyright (C) 2022 Mohd Noor Aman
+
+.. _BSP_aarch64_Raspberrypi_4:
+
+Raspberry Pi 4B
+===
+
+The 'raspberrypi4b' BSP currently supports only the LP64 ABI. ILP32 is not
+supported. Raspberry pi 4B all variants and Raspberry Pi 400  are supported. 
The
+default bootloader which is used by the Raspbian OS or other OS can be used to
+boot RTEMS. SMP is currently not supported.
+
+Raspberry Pi 4B has 2 types of interrupt controller, GIC-400 (GICv2) and ARM
+legacy generic controller. Both are supported. By default, raspberrypi 4B uses
+ARM legacy generic controller. Set ``enable_gic=1`` in the ``config.txt`` file
+to enable GIC.
+
+Clock Driver
+
+
+The clock driver uses the `ARM Generic Timer`.
+
+Console Driver
+--
+
+Raspberry pi 4B has 2 types of UARTs, ARM PL011 and Mini-uart. The PL011 is a
+capable, broadly 16550-compatible UART, while the mini UART has a reduced
+feature set. The console driver supports the default Qemu emulated ARM PL011
+PrimeCell UART as well as the physical ARM PL011 PrimeCell UART in the
+raspberrypi hardware. Mini-uart is not supported.
+
+Preparing to boot
+--
+
+Raspberry Pi uses a different mechanism to boot when compared with any ARM SoC.
+First the GPU initializes, loads the bootloader (Raspberry pi firmware) and 
then
+looks for the kernel img. This whole process is done by the GPU (VideoCore IV)
+till the kernel is loaded. More information can be found on the `Raspberry pi
+documentation page
+`_.
+By default the arm64 mode looks for the ``kernel8.img``. Any other kernel can 
be
+loaded by adding ``kernel=`` to the ``config.txt`` file.
+
+The Firmware files are required in order to boot RTEMS. The latest firmware can
+be downloaded from the `Raspberry Pi Firmware Repository
+`_. USB boot is supported. All the
+files (Firmwares and kernel) must be place in the FAT32 partition only. Add
+``arm_64bit=1`` in the ``config.txt`` file in order to boot the BSP in 64bit
+kernel mode.
+
+
+UART Setup
+^^
+
+Connect your serial device to the GPIO15 and GPIO14. Add the following to the
+``config.txt`` file in order to use the PL011 UART0 and thus disabling the
+default Mini-uart.
+
+.. code-block:: none
+
+  # if user wants to enable GIC, uncomment the next line
+  # enable_gic=1
+  arm_64bit=1
+  dtoverlay = disable-bt
+  enable_uart=1
+
+.. note::
+  The Raspberry Pi 4B and 400 have an additional four PL011 UARTs. They are not
+  supported.
+
+Generating kernel image
+^^^
+
+The following steps show how to run ``hello.exe`` on the BSP. Other executables
+can be processed in a similar way.
+
+To create the kernel image:
+
+.. code-block:: shell
+
+  $ aarch64-rtems@rtems-ver-major@-objcopy -Obinary hello.exe kernel8.img
+
+Copy the kernel image to the SD card.
+
+JTAG Setup
+--
+
+The Raspberry Pi 4 doesn't have dedicated JTAG pins. Instead, you must 
configure
+the GPIO pins (GPIO22-GPIO27) to activate the JTAG functionality. The RPi 4
+documentation refers to this as Alt4 functions of those pins. Alt5 does exist
+too, which goes from GPIO4, 5, 6, 12 and 13. you can check this out from
+`pinout.xyz `_ or `eLinux
+`_
+
+One more thing to note on JTAG with Raspberry pi 4B is that, by default, All 
the
+GPIO pins are pulled down, according to the `BCM2711 documentation
+`_. This
+wasn't the case in the earlier models. So in order to let the data flow freely,
+we will have to disable them.
+
+.. code-block:: none
+
+  # Disable pull downs
+  gpio=22-27=np
+
+  # Enable jtag pins (i.e. GPIO22-GPIO27)
+  enable_jtag_gpio=1
+
+
diff --git a/user/bsps/bsps-aarch64.rst b/user/bsps/bsps-aarch64.rst
index 933370f..f3aa15c 100644
--- a/user/bsps/bsps-aarch64.rst
+++ b/user/bsps/bsps-aarch64.rst
@@ -9,3 +9,4 @@ aarch64 (AArch64)
  .. include:: aarch64/a72.rst
  .. include:: aarch64/xilinx-versal.rst
  .. include:: aarch64/xilinx-zynqmp.rst
+.. include:: aarch64/raspberrypi4.rst
\ No newline at end of file

docs not building to PDF

[Joel Sherrill]

Hi

I have been building the docs fairly regularly as part of pushing
patches but it is not building PDF on the master for me.

===
[62/62] Compiling build/filesystem/latex/filesystem.tex
first pass on pdflatex
11:48:31 runner ['/usr/local/texlive/2019/bin/x86_64-linux/pdflatex',
'-shell-escape', '-interaction=batchmode',
'/home/joel/rtems-work/rtems-docs/build/filesystem/latex/filesystem.tex']
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded
format=pdflatex)
 \write18 enabled.
entering extended mode

Waf: Leaving directory `/home/joel/rtems-work/rtems-docs/build'
Build failed
Traceback (most recent call last):
  File
"/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",
line 180, in process
ret=self.run()
  File
"/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
line 204, in run
self.call_latex()
  File
"/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
line 234, in call_latex
self.check_status('error when calling latex',self.texfun())
  File
"/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
line 119, in check_status
raise Errors.WafError('%r command exit status %r'%(msg,retcode))
waflib.Errors.WafError: 'error when calling latex' command exit status 1
===

Any suggestions? Does this happen to anyone else?

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

git master vs main/devel/etc

[Joel Sherrill]

Hi

I have renamed the rtems-lwip main to master to be consistent with the
other repositories.

Once we reach consensus about the new name for master across all repos, are
willing to update documentation, and have it scheduled, we can rename
master across all RTEMS repos at the same time.

Hopefully, since the rtems-lwip repo is only used by a small subset of the
community, this won't be a big deal. Changing all the repos will be a
bigger deal.

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Noor Aman]

I can confirm that the same is happening on my PC too.
===
$ uname -a

Linux lynx 5.15.72-1-lts #1 SMP Wed, 05 Oct 2022 12:15:15 + x86_64
GNU/Linux
$ pip list
Package   Version
- -
absl-py   1.2.0
alabaster 0.7.12
appdirs   1.4.4
astunparse1.6.3
autocommand   2.2.1
Babel 2.10.3
btrfsutil 5.19.1
build 0.8.0
cachetools5.2.0
chardet   5.0.0
Cython0.29.32
distro1.7.0
docutils  0.19
esbonio   0.14.1
flatbuffers   1.12
gast  0.4.0
google-auth   2.11.0
google-auth-oauthlib  0.4.6
google-pasta  0.2.0
h5py  3.7.0
idna  3.4
imagesize 1.4.1
importlib-metadata4.9.0
inflect   6.0.0
jaraco.context4.1.2
jaraco.functools  3.5.2
jaraco.text   3.9.1
Jinja23.1.2
keras 2.9.0
Keras-Preprocessing   1.1.2
latexcodec2.0.1
libclang  14.0.6
libfdt1.6.1
Mako  1.2.3
Markdown  3.4.1
MarkupSafe2.1.1
more-itertools8.13.0
numpy 1.23.2
opt-einsum3.3.0
ordered-set   4.1.0
packaging 21.3
pep5170.13.0
pip   22.2.2
pip-autoremove0.10.0
py-cpuinfo8.0.0
pyasn10.4.8
pyasn1-modules0.2.8
pybtex0.24.0
pybtex-docutils   1.0.2
pycairo   1.21.0
pydantic  1.9.2
pygls 0.12.1
Pygments  2.13.0
PyGObject 3.42.2
pyinotify 0.9.6
pyparsing 3.0.9
PyQt5 5.15.7
PyQt5-sip 12.11.0
PyQtWebEngine 5.15.6
pyspellchecker0.7.0
python-xlib   0.31
pytz  2022.1
PyYAML6.0
requests  2.28.1
requests-oauthlib 1.3.1
rsa   4.9
ruamel.yaml   0.17.21
ruamel.yaml.clib  0.2.6
setuptools63.1.0
six   1.16.0
smbus 1.1
snowballstemmer   2.2.0
Sphinx5.2.3
sphinxcontrib-applehelp   1.0.2
sphinxcontrib-bibtex  2.5.0
sphinxcontrib-devhelp 1.0.2
sphinxcontrib-htmlhelp2.0.0
sphinxcontrib-jsmath  1.0.1
sphinxcontrib-qthelp  1.0.3
sphinxcontrib-serializinghtml 1.1.5
system-monitoring-center  1.27.0
team  1.0
tensorboard   2.9.1
tensorboard-data-server   0.6.1
tensorboard-plugin-wit1.8.1
tensorflow-io-gcs-filesystem  0.26.0
termcolor 1.1.0
tomli 2.0.1
trove-classifiers 2022.9.26
typeguard 2.13.3
typing_extensions 4.3.0
urllib3   1.26.12

On Fri, 7 Oct 2022 at 22:50, Joel Sherrill  wrote:

> Hi
>
> I have been building the docs fairly regularly as part of pushing
> patches but it is not building PDF on the master for me.
>
> ===
> [62/62] Compiling build/filesystem/latex/filesystem.tex
> first pass on pdflatex
> 11:48:31 runner ['/usr/local/texlive/2019/bin/x86_64-linux/pdflatex',
> '-shell-escape', '-interaction=batchmode',
> '/home/joel/rtems-work/rtems-docs/build/filesystem/latex/filesystem.tex']
> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded
> format=pdflatex)
>  \write18 enabled.
> entering extended mode
>
> Waf: Leaving directory `/home/joel/rtems-work/rtems-docs/build'
> Build failed
> Traceback (most recent call last):
>   File
> "/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",
> line 180, in process
> ret=self.run()
>   File
> "/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
> line 204, in run
> self.call_latex()
>   File
> "/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
> line 234, in call_latex
> self.check_status('error when calling latex',self.texfun())
>   File
> "/home/joel/rtems-work/rtems-docs/.waf3-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Tools/tex.py",
> line 119, in check_status
>

Re: [PATCH rtems-docs v4] raspberrypi4.rst: Documentation for the new AArch64 Raspberry pi 4B BSP

[Joel Sherrill]

I pushed it but could only build html. See the other thread for issues
building PDF.

On Fri, Oct 7, 2022 at 8:38 AM Kinsey Moore 
wrote:

> Looks good to me. Thanks for sticking with this!
>
>
> Kinsey
>
> On 10/7/2022 00:00, Mohd Noor Aman wrote:
> > This patch adds the relevant documentations required for booting the new
> BSP.
> > JTAG support is added for debugging. I have built the HTML docs and
> verified
> > them.
> > ---
> >   user/bsps/aarch64/raspberrypi4.rst | 111 +
> >   user/bsps/bsps-aarch64.rst |   1 +
> >   2 files changed, 112 insertions(+)
> >   create mode 100644 user/bsps/aarch64/raspberrypi4.rst
> >
> > diff --git a/user/bsps/aarch64/raspberrypi4.rst
> b/user/bsps/aarch64/raspberrypi4.rst
> > new file mode 100644
> > index 000..b36d47b
> > --- /dev/null
> > +++ b/user/bsps/aarch64/raspberrypi4.rst
> > @@ -0,0 +1,111 @@
> > +.. SPDX-License-Identifier: CC-BY-SA-4.0
> > +
> > +.. Copyright (C) 2022 Mohd Noor Aman
> > +
> > +.. _BSP_aarch64_Raspberrypi_4:
> > +
> > +Raspberry Pi 4B
> > +===
> > +
> > +The 'raspberrypi4b' BSP currently supports only the LP64 ABI. ILP32 is
> not
> > +supported. Raspberry pi 4B all variants and Raspberry Pi 400  are
> supported. The
> > +default bootloader which is used by the Raspbian OS or other OS can be
> used to
> > +boot RTEMS. SMP is currently not supported.
> > +
> > +Raspberry Pi 4B has 2 types of interrupt controller, GIC-400 (GICv2)
> and ARM
> > +legacy generic controller. Both are supported. By default, raspberrypi
> 4B uses
> > +ARM legacy generic controller. Set ``enable_gic=1`` in the
> ``config.txt`` file
> > +to enable GIC.
> > +
> > +Clock Driver
> > +
> > +
> > +The clock driver uses the `ARM Generic Timer`.
> > +
> > +Console Driver
> > +--
> > +
> > +Raspberry pi 4B has 2 types of UARTs, ARM PL011 and Mini-uart. The
> PL011 is a
> > +capable, broadly 16550-compatible UART, while the mini UART has a
> reduced
> > +feature set. The console driver supports the default Qemu emulated ARM
> PL011
> > +PrimeCell UART as well as the physical ARM PL011 PrimeCell UART in the
> > +raspberrypi hardware. Mini-uart is not supported.
> > +
> > +Preparing to boot
> > +--
> > +
> > +Raspberry Pi uses a different mechanism to boot when compared with any
> ARM SoC.
> > +First the GPU initializes, loads the bootloader (Raspberry pi firmware)
> and then
> > +looks for the kernel img. This whole process is done by the GPU
> (VideoCore IV)
> > +till the kernel is loaded. More information can be found on the
> `Raspberry pi
> > +documentation page
> > +<
> https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#boot-sequence
> >`_.
> > +By default the arm64 mode looks for the ``kernel8.img``. Any other
> kernel can be
> > +loaded by adding ``kernel=`` to the ``config.txt`` file.
> > +
> > +The Firmware files are required in order to boot RTEMS. The latest
> firmware can
> > +be downloaded from the `Raspberry Pi Firmware Repository
> > +`_. USB boot is supported.
> All the
> > +files (Firmwares and kernel) must be place in the FAT32 partition only.
> Add
> > +``arm_64bit=1`` in the ``config.txt`` file in order to boot the BSP in
> 64bit
> > +kernel mode.
> > +
> > +
> > +UART Setup
> > +^^
> > +
> > +Connect your serial device to the GPIO15 and GPIO14. Add the following
> to the
> > +``config.txt`` file in order to use the PL011 UART0 and thus disabling
> the
> > +default Mini-uart.
> > +
> > +.. code-block:: none
> > +
> > +  # if user wants to enable GIC, uncomment the next line
> > +  # enable_gic=1
> > +  arm_64bit=1
> > +  dtoverlay = disable-bt
> > +  enable_uart=1
> > +
> > +.. note::
> > +  The Raspberry Pi 4B and 400 have an additional four PL011 UARTs. They
> are not
> > +  supported.
> > +
> > +Generating kernel image
> > +^^^
> > +
> > +The following steps show how to run ``hello.exe`` on the BSP. Other
> executables
> > +can be processed in a similar way.
> > +
> > +To create the kernel image:
> > +
> > +.. code-block:: shell
> > +
> > +  $ aarch64-rtems@rtems-ver-major@-objcopy -Obinary hello.exe
> kernel8.img
> > +
> > +Copy the kernel image to the SD card.
> > +
> > +JTAG Setup
> > +--
> > +
> > +The Raspberry Pi 4 doesn't have dedicated JTAG pins. Instead, you must
> configure
> > +the GPIO pins (GPIO22-GPIO27) to activate the JTAG functionality. The
> RPi 4
> > +documentation refers to this as Alt4 functions of those pins. Alt5 does
> exist
> > +too, which goes from GPIO4, 5, 6, 12 and 13. you can check this out from
> > +`pinout.xyz `_ or `eLinux
> > +`_
> > +
> > +One more thing to note on JTAG with Raspberry pi 4B is that, by
> default, All the
> > +GPIO pins are pulled down, according to the `BCM2711 documentation
> > +`_

Re: [PATCH rtems-docs v4] raspberrypi4.rst: Documentation for the new AArch64 Raspberry pi 4B BSP

[Noor Aman]

I'm on an older commit of master branch (20 commits behind) and on that,
the pdf builds fine, If that helps you in any way.

thanks,

On Fri, 7 Oct 2022 at 23:19, Joel Sherrill  wrote:

> I pushed it but could only build html. See the other thread for issues
> building PDF.
>
> On Fri, Oct 7, 2022 at 8:38 AM Kinsey Moore 
> wrote:
>
>> Looks good to me. Thanks for sticking with this!
>>
>>
>> Kinsey
>>
>> On 10/7/2022 00:00, Mohd Noor Aman wrote:
>> > This patch adds the relevant documentations required for booting the
>> new BSP.
>> > JTAG support is added for debugging. I have built the HTML docs and
>> verified
>> > them.
>> > ---
>> >   user/bsps/aarch64/raspberrypi4.rst | 111 +
>> >   user/bsps/bsps-aarch64.rst |   1 +
>> >   2 files changed, 112 insertions(+)
>> >   create mode 100644 user/bsps/aarch64/raspberrypi4.rst
>> >
>> > diff --git a/user/bsps/aarch64/raspberrypi4.rst
>> b/user/bsps/aarch64/raspberrypi4.rst
>> > new file mode 100644
>> > index 000..b36d47b
>> > --- /dev/null
>> > +++ b/user/bsps/aarch64/raspberrypi4.rst
>> > @@ -0,0 +1,111 @@
>> > +.. SPDX-License-Identifier: CC-BY-SA-4.0
>> > +
>> > +.. Copyright (C) 2022 Mohd Noor Aman
>> > +
>> > +.. _BSP_aarch64_Raspberrypi_4:
>> > +
>> > +Raspberry Pi 4B
>> > +===
>> > +
>> > +The 'raspberrypi4b' BSP currently supports only the LP64 ABI. ILP32 is
>> not
>> > +supported. Raspberry pi 4B all variants and Raspberry Pi 400  are
>> supported. The
>> > +default bootloader which is used by the Raspbian OS or other OS can be
>> used to
>> > +boot RTEMS. SMP is currently not supported.
>> > +
>> > +Raspberry Pi 4B has 2 types of interrupt controller, GIC-400 (GICv2)
>> and ARM
>> > +legacy generic controller. Both are supported. By default, raspberrypi
>> 4B uses
>> > +ARM legacy generic controller. Set ``enable_gic=1`` in the
>> ``config.txt`` file
>> > +to enable GIC.
>> > +
>> > +Clock Driver
>> > +
>> > +
>> > +The clock driver uses the `ARM Generic Timer`.
>> > +
>> > +Console Driver
>> > +--
>> > +
>> > +Raspberry pi 4B has 2 types of UARTs, ARM PL011 and Mini-uart. The
>> PL011 is a
>> > +capable, broadly 16550-compatible UART, while the mini UART has a
>> reduced
>> > +feature set. The console driver supports the default Qemu emulated ARM
>> PL011
>> > +PrimeCell UART as well as the physical ARM PL011 PrimeCell UART in the
>> > +raspberrypi hardware. Mini-uart is not supported.
>> > +
>> > +Preparing to boot
>> > +--
>> > +
>> > +Raspberry Pi uses a different mechanism to boot when compared with any
>> ARM SoC.
>> > +First the GPU initializes, loads the bootloader (Raspberry pi
>> firmware) and then
>> > +looks for the kernel img. This whole process is done by the GPU
>> (VideoCore IV)
>> > +till the kernel is loaded. More information can be found on the
>> `Raspberry pi
>> > +documentation page
>> > +<
>> https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#boot-sequence
>> >`_.
>> > +By default the arm64 mode looks for the ``kernel8.img``. Any other
>> kernel can be
>> > +loaded by adding ``kernel=`` to the ``config.txt`` file.
>> > +
>> > +The Firmware files are required in order to boot RTEMS. The latest
>> firmware can
>> > +be downloaded from the `Raspberry Pi Firmware Repository
>> > +`_. USB boot is supported.
>> All the
>> > +files (Firmwares and kernel) must be place in the FAT32 partition
>> only. Add
>> > +``arm_64bit=1`` in the ``config.txt`` file in order to boot the BSP in
>> 64bit
>> > +kernel mode.
>> > +
>> > +
>> > +UART Setup
>> > +^^
>> > +
>> > +Connect your serial device to the GPIO15 and GPIO14. Add the following
>> to the
>> > +``config.txt`` file in order to use the PL011 UART0 and thus disabling
>> the
>> > +default Mini-uart.
>> > +
>> > +.. code-block:: none
>> > +
>> > +  # if user wants to enable GIC, uncomment the next line
>> > +  # enable_gic=1
>> > +  arm_64bit=1
>> > +  dtoverlay = disable-bt
>> > +  enable_uart=1
>> > +
>> > +.. note::
>> > +  The Raspberry Pi 4B and 400 have an additional four PL011 UARTs.
>> They are not
>> > +  supported.
>> > +
>> > +Generating kernel image
>> > +^^^
>> > +
>> > +The following steps show how to run ``hello.exe`` on the BSP. Other
>> executables
>> > +can be processed in a similar way.
>> > +
>> > +To create the kernel image:
>> > +
>> > +.. code-block:: shell
>> > +
>> > +  $ aarch64-rtems@rtems-ver-major@-objcopy -Obinary hello.exe
>> kernel8.img
>> > +
>> > +Copy the kernel image to the SD card.
>> > +
>> > +JTAG Setup
>> > +--
>> > +
>> > +The Raspberry Pi 4 doesn't have dedicated JTAG pins. Instead, you must
>> configure
>> > +the GPIO pins (GPIO22-GPIO27) to activate the JTAG functionality. The
>> RPi 4
>> > +documentation refers to this as Alt4 functions of those pins. Alt5
>> does exist
>> > +too, which goes from GPIO4, 5, 6, 12 and 13. you can check this out
>> from
>> > +`

Re: [PATCH rtems-docs v4] raspberrypi4.rst: Documentation for the new AArch64 Raspberry pi 4B BSP

[Chris Johns]

On 8/10/2022 10:29 am, Noor Aman wrote:
> I'm on an older commit of master branch (20 commits behind) and on that, the 
> pdf
> builds fine, If that helps you in any way.

Please make sure the patches you post are based on the latest when you post
them. We assume this is the case.

Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Chris Johns]

On 8/10/2022 10:12 am, Noor Aman wrote:
> I can confirm that the same is happening on my PC too.

Could you please bisect the repo to find the patch that broke things?

Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: docs not building to PDF

[Chris Johns]

On 8/10/2022 9:47 am, Chris Johns wrote:
> On 8/10/2022 10:12 am, Noor Aman wrote:
>> I can confirm that the same is happening on my PC too.
> 
> Could you please bisect the repo to find the patch that broke things?

A simpler way to find the commit is to see the last build on docs.rtems.org
which is 6.278550b and the next commit after 278550b is:

commit 23fc93bf648507ac417237c20069c4ab7c793251
Author: Frank Kühndel 
Date:   Thu Jun 9 15:21:05 2022 +0200

TFTPFS: New documentation

Frank ?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel