From: Alistair Francis <alistair23@gmail.com>
To: Vijai Kumar K <vijai@behindbytes.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] docs: Add documentation for shakti_c machine
Date: Thu, 15 Apr 2021 14:48:27 +1000 [thread overview]
Message-ID: <CAKmqyKP=rX01hbZRqdiKACgoasHotkN93pwCb3o_o0mpHN5tSw@mail.gmail.com> (raw)
In-Reply-To: <20210412174248.8668-1-vijai@behindbytes.com>
On Tue, Apr 13, 2021 at 3:44 AM Vijai Kumar K <vijai@behindbytes.com> wrote:
>
> Add documentation for Shakti C reference platform.
>
> Signed-off-by: Vijai Kumar K <vijai@behindbytes.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> docs/system/riscv/shakti-c.rst | 82 ++++++++++++++++++++++++++++++++++
> 1 file changed, 82 insertions(+)
> create mode 100644 docs/system/riscv/shakti-c.rst
>
> diff --git a/docs/system/riscv/shakti-c.rst b/docs/system/riscv/shakti-c.rst
> new file mode 100644
> index 0000000000..a6035d42b0
> --- /dev/null
> +++ b/docs/system/riscv/shakti-c.rst
> @@ -0,0 +1,82 @@
> +Shakti C Reference Platform (``shakti_c``)
> +==========================================
> +
> +Shakti C Reference Platform is a reference platform based on arty a7 100t
> +for the Shakti SoC.
> +
> +Shakti SoC is a SoC based on the Shakti C-class processor core. Shakti C
> +is a 64bit RV64GCSUN processor core.
> +
> +For more details on Shakti SoC, please see:
> +https://gitlab.com/shaktiproject/cores/shakti-soc/-/blob/master/fpga/boards/artya7-100t/c-class/README.rst
> +
> +For more info on the Shakti C-class core, please see:
> +https://c-class.readthedocs.io/en/latest/
> +
> +Supported devices
> +-----------------
> +
> +The ``shakti_c`` machine supports the following devices:
> +
> + * 1 C-class core
> + * Core Level Interruptor (CLINT)
> + * Platform-Level Interrupt Controller (PLIC)
> + * 1 UART
> +
> +Boot options
> +------------
> +
> +The ``shakti_c`` machine can start using the standard -bios
> +functionality for loading the baremetal application or opensbi.
> +
> +Boot the machine
> +----------------
> +
> +Shakti SDK
> +~~~~~~~~~~
> +Shakti SDK can be used to generate the baremetal example UART applications.
> +
> +.. code-block:: bash
> +
> + $ git clone https://gitlab.com/behindbytes/shakti-sdk.git
> + $ cd shakti-sdk
> + $ make software PROGRAM=loopback TARGET=artix7_100t
> +
> +Binary would be generated in:
> + software/examples/uart_applns/loopback/output/loopback.shakti
> +
> +You could also download the precompiled example applicatons using below
> +commands.
> +
> +.. code-block:: bash
> +
> + $ wget -c https://gitlab.com/behindbytes/shakti-binaries/-/raw/master/sdk/shakti_sdk_qemu.zip
> + $ unzip shakti_sdk_qemu.zip
> +
> +Then we can run the UART example using:
> +
> +.. code-block:: bash
> +
> + $ qemu-system-riscv64 -M shakti_c -nographic \
> + -bios path/to/shakti_sdk_qemu/loopback.shakti
> +
> +OpenSBI
> +~~~~~~~
> +We can also run OpenSBI with Test Payload.
> +
> +.. code-block:: bash
> +
> + $ git clone https://github.com/riscv/opensbi.git -b v0.9
> + $ cd opensbi
> + $ wget -c https://gitlab.com/behindbytes/shakti-binaries/-/raw/master/dts/shakti.dtb
> + $ export CROSS_COMPILE=riscv64-unknown-elf-
> + $ export FW_FDT_PATH=./shakti.dtb
> + $ make PLATFORM=generic
> +
> +fw_payload.elf would be generated in build/platform/generic/firmware/fw_payload.elf.
> +Boot it using the below qemu command.
> +
> +.. code-block:: bash
> +
> + $ qemu-system-riscv64 -M shakti_c -nographic \
> + -bios path/to/fw_payload.elf
> --
> 2.25.1
>
>
>
next prev parent reply other threads:[~2021-04-15 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 17:42 [PATCH] docs: Add documentation for shakti_c machine Vijai Kumar K
2021-04-15 4:48 ` Alistair Francis [this message]
2021-04-15 22:33 ` Alistair Francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKmqyKP=rX01hbZRqdiKACgoasHotkN93pwCb3o_o0mpHN5tSw@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=vijai@behindbytes.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).