RTEMS | Add BSP to BeagleV-Fire board (!194)

[Francescodario Cuzzocrea (@fcuzzocrea)]

Francescodario Cuzzocrea commented on a discussion on bsps/riscv/shared/start/bspgetworkarea.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/194#note_111864

 >    int ac;
 >    int sc;
 >    int len;
 > +  uint64_t start64;
 > +  uint64_t size64;
 > +  uint64_t start32;
 > +  uint64_t size32;

Actually instead of beaglevfire would be polarfire soc :slight_smile: .

I do not know if it is feasible to switch with a config options with the current build system, because the 2 different configurations requires 2 different device trees.

What would be great instead would be to avoid relying on a prebuilt device tree have the device tree being compiled before the compilation of rtems. This could let us easily add support for different boards using polarfire soc by including a common mpfs.dtsi. I always wanted to do this but never find the time sadly.

I can give another try at mstrict-align after I am back from vacations :slight_smile: .

To boot rtems on E51 on icile kit I use a custom bootloader developed with polarfire soc baremetal library. I store the image on an external spi flash (or I load it directly in ram with a debugger). On beagle v fire one can think of storing the rtems image on the qspi flash instead.

On U54 I run Linux (one can start if from the rtems image which is loaded on E51 using opensbi).
Otherwise it is also possible to run another rtems instance on the U54s (with SMP).

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/194#note_111864
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/20240909/7d7da5b3/attachment.htm>