Documentation | Add BeagleV-Fire Board Documentation (!45)

[Joel Sherrill (@joel)]

Merge request https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45 was reviewed by Joel Sherrill

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111547

 > +BeagleV-Fire supports the riscv/beaglevfire BSP variant.
 > +
 > +Building upon base BSP work to further enhance the functionality and compatibility of the `BSP <https://github.com/purviyeshi/rtems/tree/bvf>`__ for uni-processing and multi-processing.

This still sounds like a final report. The Base BSP has since been enhanced to include X, Y, and Z. We shouldn't need the github reference since it should all be in gitlab.rtems.org. And make sure that it all is. :)

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111548

 > +-------------
 > +
 > +The BeagleV-Fire board is equipped with the Microchip’s PolarFire MPFS025T System on Chip (SoC), featuring a 5-core configuration. It includes 4 RV64GC cores for U54 and 1 RV64IMAC core for E51.

Some lines look well over 80 columns. Make a pass.

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111549

 > +``RTEMS_SMP``: Set to ``False`` to run the system in uniprocessor mode,
 > +where only one core (e.g., U54_1) handles processing. This mode is
 > +suitable for scenarios where multiprocessing is not required or not

Why wouldn't SMP be supported. I suspect it is just not required.

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111550

 > +   $ ./waf configure --prefix=$HOME/rtems-start/rtems/6
 > +   $ ./waf
 > +

This isn't needed. It is generic across all BSPs. No need to repeat.

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111551

 > +
 > +**Convert .exe to .elf file:**
 > +

I thought the exe file was an elf file. Please confirm whether this step is needed or not.

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111552

 > +   of the binary file.
 > +
 > +   The HSS repository has been forked, and the modified test/hss.yaml file is directly accessible `here <https://github.com/purviyeshi/hart-software-services.git>`__

This ultimately needs to be an RSB generated executable package. Resolve this by filing an issue in the rtems-source-builder project and citing it in the reply. Make sure that issue says to update this text when the RSB supports HSS.

--
  
Joel Sherrill started a new discussion on user/bsps/bsps-riscv.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45#note_111553

 > +
 > +**Reset the BeagleV-Fire board and check the output**
 > +

Add introductory paragraph with something like the output should be similar to the following:"




-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/45
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20240827/6ce57f19/attachment-0001.htm>