summaryrefslogtreecommitdiffstats
path: root/user/bsps/bsps-microblaze.rst
diff options
context:
space:
mode:
authorChris Johns <chrisj@rtems.org>2022-08-03 14:22:20 +1000
committerChris Johns <chrisj@rtems.org>2022-08-03 14:28:19 +1000
commit3859073d5be52c7161e734067748d5dba9a67bc4 (patch)
tree76f1274d38223c4bb171556a0bef8ab0054da9b4 /user/bsps/bsps-microblaze.rst
parentversions: Update arm (diff)
downloadrtems-docs-3859073d5be52c7161e734067748d5dba9a67bc4.tar.bz2
versions: Update microblaze, powerpc, riscv and x86_64
Updates #4695
Diffstat (limited to 'user/bsps/bsps-microblaze.rst')
-rw-r--r--user/bsps/bsps-microblaze.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/user/bsps/bsps-microblaze.rst b/user/bsps/bsps-microblaze.rst
index e20df53..32aad90 100644
--- a/user/bsps/bsps-microblaze.rst
+++ b/user/bsps/bsps-microblaze.rst
@@ -53,8 +53,8 @@ The name ``system_dtb`` is significant as it is the name expected by the BSP.
$ rtems-bin2c -C -A 8 -N system_dtb my_device_tree.dtb my_dtb
The ``BSP_MICROBLAZE_FPGA_DTB_HEADER_PATH`` BSP configuration option can then be
-set to the path of the resulting source file, ``my_dtb.c``, to include it in the
-BSP build.
+set to the path of the resulting source file, ``my_dtb.c``, in the waf INI file
+to include it in the BSP build.
.. code-block:: none
@@ -64,7 +64,7 @@ BSP build.
Running Executables
-------------------
-A .dtb (device tree blob) file should be provided to QEMU via the ``-hw-dtb``
+A ``.dtb`` (device tree blob) file should be provided to QEMU via the ``-hw-dtb``
option. In the example command below, the device tree blob comes from the Xilinx
Petalinux KCU105 MicroBlaze BSP (https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html).
@@ -94,7 +94,7 @@ Then start GDB and connect to QEMU.
.. code-block:: none
- $ microblaze-rtems6-gdb build/microblaze/kcu105_qemu/testsuites/samples/hello.exe
+ $ microblaze-rtems@rtems-ver-major@-gdb build/microblaze/kcu105_qemu/testsuites/samples/hello.exe
(gdb) target remote localhost:1234
(gdb) break Init
(gdb) continue
@@ -146,7 +146,7 @@ application, and debug as usual. By default the GDB server listens on port 3002.
.. code-block:: none
- $ microblaze-rtems6-gdb example.exe
+ $ microblaze-rtems@rtems-ver-major@-gdb example.exe
(gdb) target extended-remote localhost:3002
(gdb) load
(gdb) break Init