Hi Alan, Thank you for review. I will update same in Patch v2.
Regards Padmarao ________________________________ From: Alan Cudmore <alan.cudm...@gmail.com> Sent: Wednesday, October 5, 2022 7:52 PM To: Padmarao Begari - I30397 <padmarao.beg...@microchip.com> Cc: devel@rtems.org <devel@rtems.org>; Cyril Jean - M31571 <cyril.j...@microchip.com> Subject: Re: [PATCH rtems-docs] user/bsps: Update riscv for PolarFire SoC Hi Padmarao, The docs look good to me. I have a couple of minor comments inline. I'm really glad to see this BSP in RTEMS. Thanks, Alan On Wed, Sep 28, 2022 at 4:07 PM Padmarao Begari <padmarao.beg...@microchip.com<mailto:padmarao.beg...@microchip.com>> wrote: Update the riscv documentation for the Microchip PolarFire SoC BSP variant including information about SMP test procedure for the Microchip PolarFire Icicle Kit. --- user/bsps/bsps-riscv.rst | 114 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 113 insertions(+), 1 deletion(-) diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rst index 5faa87b..be65a68 100644 --- a/user/bsps/bsps-riscv.rst +++ b/user/bsps/bsps-riscv.rst @@ -8,7 +8,7 @@ riscv (RISC-V) riscv ===== -This BSP offers 13 variants: +This BSP offers 15 variants: * rv32i @@ -38,6 +38,8 @@ This BSP offers 13 variants: * frdme310arty +* mpfs64imafdc + Each variant corresponds to a GCC multilib. A particular variant reflects an ISA with ABI and code model choice. @@ -47,6 +49,9 @@ be started im machine mode. The reference platform for this BSP is the Qemu `virt` machine. +The reference platform for the mpfs64imafdc BSP variant is the Microchip +PolarFire SoC Icicle Kit. + Build Configuration Options --------------------------- @@ -94,6 +99,13 @@ configuration INI file. The ``waf`` defaults can be used to inspect the values. Enables support sifive Freedom E310 Arty board if defined to a non-zero value,otherwise it is disabled (disabled by default) +``RISCV_ENABLE_MPFS_SUPPORT`` + Enables support Microchip PolarFire SoC if defined to a non-zero + value, otherwise it is disabled (disabled by default). + +``RISCV_BOOT_HARTID`` + The boot hartid (processor number) of risc-v cpu by default 0. + Interrupt Controller -------------------- @@ -124,6 +136,106 @@ They are initialized according to the device tree. The console driver does not configure the pins or peripheral clocks. The console device is selected according to the device tree "/chosen/stdout-path" property value. +Microchip PolarFire SoC +----------------------- + +The PolarFire SoC is the 4x 64-bit RISC-V U54 cores and a 64-bit RISC-V +E51 monitor core SoC from the Microchip. + +The ``mpfs64imafdc`` BSP variant supports the U54 cores not the E51 because +the E51 monitor core is reserved for first stage bootloader +(Hart Software Services) and default ``RISCV_BOOT_HARTID`` is 1. I would suggest "... BSP variant supports the U54 cores but not the E51 because the E51 monitor core is reserved for the first stage bootloader (Hart Software Services). In order to boot from the first U54 core, ``RISCV_BOOT_HARTID`` is set to 1 by default. + +**SMP test procedure for the Microchip PolarFire Icicle Kit:** + +The "config.ini" file. + +.. code-block:: none + + [riscv/mpfs64imafdc] + BUILD_TESTS = True + RTEMS_POSIX_API=True + RTEMS_SMP = True + BSP_START_COPY_FDT_FROM_U_BOOT=False + BSP_VERBOSE_FATAL_EXTENSION = False + +Build RTEMS. + +.. code-block:: shell + + $ ./waf configure --prefix=$HOME/rtems-start/rtems/6 + $ ./waf + +Convert .exe to .elf file. + +.. code-block:: shell + + $ riscv-rtems6-objcopy build/riscv/mpfs64imafdc/testsuites/smptests/smp01.exe build/riscv/mpfs64imafdc/testsuites/smptests/smp01.elf I believe the .exe file is already .elf, so the file can be renamed or used as is. Probably OK to leave this since it makes it clear that the elf file format is needed for the next step. Also, is it worth mentioning that the DTB is embedded in the BSP rather than loaded from the eMMC/SD card? + +Generate a payload for the `smp01.elf` using the `hss-payload-generator <https://github.com/polarfire-soc/hart-software-services/blob/master/tools/hss-payload-generator>`_. + +* Copy `smp01.elf` file to the HSS/tools/hss-payload-generator/test directory. + +* Go to hss-payload-generator source directory. + +.. code-block:: shell + + $ cd hart-software-services/tools/hss-payload-generator + +* Edit test/uboot.yaml file for the hart entry points and correct name of the + binary file. + +.. code-block:: none + + set-name: 'PolarFire-SoC-HSS::RTEMS' + hart-entry-points: {u54_1: '0x1000000000', u54_2: '0x1000000000', u54_3: '0x1000000000', u54_4: '0x1000000000'} + payloads: + test/smp01.elf: {exec-addr: '0x1000000000', owner-hart: u54_1, secondary-hart: u54_2, secondary-hart: u54_3, secondary-hart: u54_4, priv-mode: prv_m, skip-opensbi: true} + +* Generate payload + +.. code-block:: shell + + $ ./hss-payload-generator -c test/uboot.yaml payload.bin + +Once the payload binary is generated, it should be copied to the eMMC/SD. + +`FPGA design with HSS programming file <https://github.com/polarfire-soc/polarfire-soc-documentation/blob/master/boards/mpfs-icicle-kit-es/updating-icicle-kit/updating-icicle-kit-design-and-linux.md>`_. + +Program the eMMC/SD with the payload binary. + +* Power Cycle the Microchip PolarFire Icicle Kit and stop at the HSS. + +* type "mmc" and then "usbdmsc" on the HSS terminal(UART0). + +* Load the payload.bin from the Host PC. + +.. code-block:: shell + + $ sudo dd if=payload.bin of=/dev/sdb bs=512 + +Reset the Microchip PolarFire SoC Icicle Kit. + +Serial terminal UART1 displays the SMP example messages + +.. code-block:: none + + *** BEGIN OF TEST SMP 1 *** + *** TEST VERSION: 6.0.0.ef33f861e16de9bf4190a36e4d18062c7300986c + *** TEST STATE: EXPECTED_PASS + *** TEST BUILD: RTEMS_POSIX_API RTEMS_SMP + *** TEST TOOLS: 12.1.1 20220622 (RTEMS 6, RSB 3cb78b0b815ba05d17f5c6 + 5865d246a8333aa087, Newlib ea99f21) + + CPU 3 start task TA0 + CPU 2 running Task TA0 + CPU 3 start task TA1 + CPU 1 running Task TA1 + CPU 3 start task TA2 + CPU 0 running Task TA2 + + *** END OF TEST SMP 1 *** + griscv ====== -- 2.25.1 _______________________________________________ devel mailing list devel@rtems.org<mailto:devel@rtems.org> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
