Skip to content

Commit 345d8c1

Browse files
committed
boards: beagle: beaglev_fire: Fix building example
- Fix the board name in build example - Add link to datasheet - Specify the different targets supported for beaglev_fire Signed-off-by: Ayush Singh <[email protected]>
1 parent d022d31 commit 345d8c1

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

boards/beagle/beaglev_fire/doc/index.rst

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,19 @@ hobbyists, and researchers to explore and experiment with RISC-V technology.
2222
Building
2323
========
2424

25-
Applications for the ``beaglev_fire`` board configuration can be built as usual:
25+
BeagleV-Fire supports 3 board targets in Zephyr:
26+
27+
1. ``beaglev_fire/polarfire/e51``
28+
2. ``beaglev_fire/polarfire/u54``
29+
3. ``beaglev_fire/polarfire/u54/smp``
30+
31+
More information regarding the differences between the cores can be found in the `datasheet <https://ww1.microchip.com/downloads/aemDocuments/documents/FPGA/ProductDocuments/ProductBrief/PolarFire-SoC-Product-Overview-60001656.pdf>`_.
32+
33+
Here is an example of building :zephyr:code-sample:`hello_world` for E51 core.
2634

2735
.. zephyr-app-commands::
2836
:zephyr-app: samples/hello_world
29-
:board: beaglev_fire
37+
:board: beaglev_fire/polarfire/e51
3038
:goals: build
3139

3240
Debugging

0 commit comments

Comments
 (0)