Re: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader
On 31/10/2022 10:44 pm, Hesham Almatary wrote: > Hello, > > I tried to push that but got an error message: > "remote: git_buildbot: ERROR: Could not connect to > buildbot.int.rtems.org:9899: Connection was refused by other side: 61: > Connection refused." Please try again. We have had some server issues. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader
Hello, I tried to push that but got an error message: "remote: git_buildbot: ERROR: Could not connect to buildbot.int.rtems.org:9899: Connection was refused by other side: 61: Connection refused." Please push if you're happy with the patch. Cheers, Hesham On Tue, 25 Oct 2022 at 19:04, Hesham Almatary wrote: > > On Tue, 25 Oct 2022 at 18:59, Alan Cudmore wrote: > > > > I agree – I am working on a riscv BSP variant (Sipeed MAIX Bit with K210 > > CPU) where the RTEMS image can be flashed directly to the board and boots > > without a bootloader. > > > > I was also wondering if the statement “Each variant corresponds to a GCC > > multilib” is still accurate as BSP variants such as the FE310Arty and > > Microchip Polarfire are added? > > > I agree. It only applies to rv* BSPs. We should fix that. > > > Thanks, > > > > Alan > > > > From: heshamelmat...@gmail.com > > Sent: Tuesday, October 25, 2022 1:48 PM > > To: devel@rtems.org > > Subject: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance > > on a boot loader > > > > > > > > From: Hesham Almatary > > > > > > > > The BSP is capable of initialising the hardware being the first software > > > > that takes control on hardware reset (after the bootrom). For instance, > > > > using on QEMU's virt platforms, RTEMS runs as a bios without BBL. > > > > Similarily, RTEMS can also be run on harware/FPGA and loaded using > > > > GDB; the bootrom (or a GDB script) should just set the a0/a1 registers > > > > with the boot HART ID and DTB address respectively. > > > > --- > > > > user/bsps/bsps-riscv.rst | 4 +--- > > > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > > > > > diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rst > > > > index 48e7ee7..224506d 100644 > > > > --- a/user/bsps/bsps-riscv.rst > > > > +++ b/user/bsps/bsps-riscv.rst > > > > @@ -43,9 +43,7 @@ This BSP offers 15 variants: > > > > Each variant corresponds to a GCC multilib. A particular variant reflects > > an > > > > ISA with ABI and code model choice. > > > > -The basic hardware initialization is not performed by the BSP. A boot > > loader > > > > -with device tree support must be used to start the BSP, e.g. BBL. The BSP > > must > > > > -be started im machine mode. > > > > +The BSP must be started im machine mode. > > > > The reference platform for this BSP is the Qemu `virt` machine. > > > > -- > > > > 2.25.1 > > > > > > > > ___ > > > > devel mailing list > > > > devel@rtems.org > > > > http://lists.rtems.org/mailman/listinfo/devel > > > > > > > > -- > Hesham -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader
On Tue, 25 Oct 2022 at 18:59, Alan Cudmore wrote: > > I agree – I am working on a riscv BSP variant (Sipeed MAIX Bit with K210 CPU) > where the RTEMS image can be flashed directly to the board and boots without > a bootloader. > > I was also wondering if the statement “Each variant corresponds to a GCC > multilib” is still accurate as BSP variants such as the FE310Arty and > Microchip Polarfire are added? > I agree. It only applies to rv* BSPs. We should fix that. > Thanks, > > Alan > > From: heshamelmat...@gmail.com > Sent: Tuesday, October 25, 2022 1:48 PM > To: devel@rtems.org > Subject: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance > on a boot loader > > > > From: Hesham Almatary > > > > The BSP is capable of initialising the hardware being the first software > > that takes control on hardware reset (after the bootrom). For instance, > > using on QEMU's virt platforms, RTEMS runs as a bios without BBL. > > Similarily, RTEMS can also be run on harware/FPGA and loaded using > > GDB; the bootrom (or a GDB script) should just set the a0/a1 registers > > with the boot HART ID and DTB address respectively. > > --- > > user/bsps/bsps-riscv.rst | 4 +--- > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rst > > index 48e7ee7..224506d 100644 > > --- a/user/bsps/bsps-riscv.rst > > +++ b/user/bsps/bsps-riscv.rst > > @@ -43,9 +43,7 @@ This BSP offers 15 variants: > > Each variant corresponds to a GCC multilib. A particular variant reflects an > > ISA with ABI and code model choice. > > -The basic hardware initialization is not performed by the BSP. A boot loader > > -with device tree support must be used to start the BSP, e.g. BBL. The BSP > must > > -be started im machine mode. > > +The BSP must be started im machine mode. > > The reference platform for this BSP is the Qemu `virt` machine. > > -- > > 2.25.1 > > > > ___ > > devel mailing list > > devel@rtems.org > > http://lists.rtems.org/mailman/listinfo/devel > > -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RE: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader
I agree – I am working on a riscv BSP variant (Sipeed MAIX Bit with K210 CPU) where the RTEMS image can be flashed directly to the board and boots without a bootloader.I was also wondering if the statement “Each variant corresponds to a GCC multilib” is still accurate as BSP variants such as the FE310Arty and Microchip Polarfire are added?Thanks,AlanFrom: heshamelmat...@gmail.comSent: Tuesday, October 25, 2022 1:48 PMTo: devel@rtems.orgSubject: [PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader From: Hesham Almatary The BSP is capable of initialising the hardware being the first softwarethat takes control on hardware reset (after the bootrom). For instance,using on QEMU's virt platforms, RTEMS runs as a bios without BBL.Similarily, RTEMS can also be run on harware/FPGA and loaded usingGDB; the bootrom (or a GDB script) should just set the a0/a1 registerswith the boot HART ID and DTB address respectively.--- user/bsps/bsps-riscv.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rstindex 48e7ee7..224506d 100644--- a/user/bsps/bsps-riscv.rst+++ b/user/bsps/bsps-riscv.rst@@ -43,9 +43,7 @@ This BSP offers 15 variants: Each variant corresponds to a GCC multilib. A particular variant reflects an ISA with ABI and code model choice. -The basic hardware initialization is not performed by the BSP. A boot loader-with device tree support must be used to start the BSP, e.g. BBL. The BSP must-be started im machine mode.+The BSP must be started im machine mode. The reference platform for this BSP is the Qemu `virt` machine. -- 2.25.1 ___devel mailing listdevel@rtems.orghttp://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH 1/2] bsps/riscv: Remove inaccurate statement about reliance on a boot loader
From: Hesham Almatary The BSP is capable of initialising the hardware being the first software that takes control on hardware reset (after the bootrom). For instance, using on QEMU's virt platforms, RTEMS runs as a bios without BBL. Similarily, RTEMS can also be run on harware/FPGA and loaded using GDB; the bootrom (or a GDB script) should just set the a0/a1 registers with the boot HART ID and DTB address respectively. --- user/bsps/bsps-riscv.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rst index 48e7ee7..224506d 100644 --- a/user/bsps/bsps-riscv.rst +++ b/user/bsps/bsps-riscv.rst @@ -43,9 +43,7 @@ This BSP offers 15 variants: Each variant corresponds to a GCC multilib. A particular variant reflects an ISA with ABI and code model choice. -The basic hardware initialization is not performed by the BSP. A boot loader -with device tree support must be used to start the BSP, e.g. BBL. The BSP must -be started im machine mode. +The BSP must be started im machine mode. The reference platform for this BSP is the Qemu `virt` machine. -- 2.25.1 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
