1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
|
.. SPDX-License-Identifier: CC-BY-SA-4.0
.. Copyright (C) 2018 embedded brains GmbH & Co. KG
.. Copyright (C) 2022 On-Line Applications Research Corporation (OAR)
microblaze (MicroBlaze)
***********************
KCU105 QEMU
===========
The basic hardware initialization is performed by the BSP. This BSP supports the
QEMU emulated Xilinx AXI Interrupt Controller v4.1.
Boot via ELF
------------
The executable image is booted by QEMU in ELF format.
Clock Driver
------------
The clock driver supports the QEMU emulated Xilinx AXI Timer v2.0. It is
implemented as a simple downcounter. If device tree support is enabled in the
build configuration, the clock driver will use the node that is compatible with
`xlnx,xps-timer-1.00.a` from the device tree to configure the clock. The
following device tree node properties are used to configure the clock driver:
``reg``, ``clock-frequency``, and ``interrupts``.
Console Driver
--------------
The console driver supports the QEMU emulated Xilinx AXI UART Lite v2.0. It is
initialized to a baud rate of 115200. If device tree support is enabled in the
build configuration, the console driver will use the node that is compatible
with `xlnx,xps-uartlite-1.00.a` from the device tree to configure the console.
The following device tree node properties are used to configure the console
driver: ``reg``, ``status``, ``port-number``, and ``interrupts``.
Network Driver
--------------
Support for networking is provided by the libbsd library. Network interface
configuration is extracted from the device tree binary which, by default, is
in `<bsp/microblaze-dtb.h> <https://git.rtems.org/rtems/tree/bsps/microblaze/microblaze_fpga/include/bsp/microblaze-dtb.h>`_.
The device tree source for the default device tree is at `dts/system.dts <https://git.rtems.org/rtems/tree/bsps/microblaze/microblaze_fpga/dts/system.dts>`_.
To replace the default device tree with your own, assuming ``my_device_tree.dts``
is the name of your device tree source file, first you must convert your device
tree to .dtb format.
.. code-block:: none
$ dtc -I dts -O dtb my_device_tree.dts > my_device_tree.dtb
The device tree blob, ``my_device_tree.dtb``, can now be converted to a C file.
The name ``system_dtb`` is significant as it is the name expected by the BSP.
.. code-block:: none
$ 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``, in the waf INI file
to include it in the BSP build.
.. code-block:: none
BSP_MICROBLAZE_FPGA_DTB_HEADER_PATH = /path/to/my_dtb.c
QSPI NOR JFFS2 Driver
---------------------
The QSPI NOR JFFS2 driver supports the QEMU emulated n25q512a11 QSPI NOR flash
device. It is initialized to a page size of 256 bytes and a sector size of 64
KiB. If device tree support is enabled in the build configuration, the QSPI NOR
JFFS2 driver will use the node that is compatible with `xlnx,xps-spi-2.00.a`
from the device tree to configure the QSPI NOR JFFS2 driver. The following
device tree node properties are used to configure the QSPI NOR JFFS2 driver:
``reg`` and ``interrupts``.
Running Executables
-------------------
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).
Executables generated by this BSP can be run using the following command:
.. code-block:: none
$ qemu-system-microblazeel -no-reboot -nographic -M microblaze-fdt-plnx -m 256 \
-serial mon:stdio -display none -hw-dtb system.dtb -kernel example.exe
Debugging with QEMU
-------------------
To debug an application, add the option ``-s`` to make QEMU listen for GDB
connections on port 1234. Add the ``-S`` option to also stop execution until
a connection is made.
For example, to debug the hello sample and break at ``Init``, first start QEMU.
.. code-block:: none
$ qemu-system-microblazeel -no-reboot -nographic -M microblaze-fdt-plnx -m 256 \
-serial mon:stdio -display none -hw-dtb system.dtb -kernel \
build/microblaze/kcu105_qemu/testsuites/samples/hello.exe -s -S
Then start GDB and connect to QEMU.
.. code-block:: none
$ microblaze-rtems@rtems-ver-major@-gdb build/microblaze/kcu105_qemu/testsuites/samples/hello.exe
(gdb) target remote localhost:1234
(gdb) break Init
(gdb) continue
KCU105
======
The basic hardware initialization is performed by the BSP. This BSP supports the
Xilinx AXI Interrupt Controller v4.1.
This BSP was tested using the Xilinx Kintex UltraScale FPGA KCU105 board
configured with the default Petalinux KCU105 MicroBlaze BSP. The defaults may
need to be adjusted using BSP configuration options to match the memory layout
and configuration of your board.
Clock Driver
------------
The clock driver supports the Xilinx AXI Timer v2.0. It is implemented as a
simple downcounter. If device tree support is enabled in the
build configuration, the clock driver will use the node that is compatible with
`xlnx,xps-timer-1.00.a` from the device tree to configure the clock. The
following device tree node properties are used to configure the clock driver:
``reg``, ``clock-frequency``, and ``interrupts``.
Console Driver
--------------
The console driver supports the Xilinx AXI UART Lite v2.0. It is initialized to
a baud rate of 115200. If device tree support is enabled in the build
configuration, the console driver will use the node that is compatible with
`xlnx,xps-uartlite-1.00.a` from the device tree to configure the console. The
following device tree node properties are used to configure the console driver:
``reg``, ``status``, ``port-number``, and ``interrupts``.
Debugging
---------
The following debugging procedure was used for debugging RTEMS applications
running on the Xilinx KCU105 board using GDB.
First send an FPGA bitstream to the board using OpenOCD.
.. code-block:: none
$ openocd -f board/kcu105.cfg -c "init; pld load 0 system.bit; exit"
After the board has been programmed, start the Vivado ``hw_server`` application
to serve as the debug server. Leave it running in the background for the rest of
the process.
.. code-block:: none
$ tools/Xilinx/Vivado/2020.2/bin/hw_server
With the debug server running, connect to the debug server with GDB, load the
application, and debug as usual. By default the GDB server listens on port 3002.
.. code-block:: none
$ microblaze-rtems@rtems-ver-major@-gdb example.exe
(gdb) target extended-remote localhost:3002
(gdb) load
(gdb) break Init
(gdb) continue
|
