Building RISC-V BSP

Sun Jun 4 13:17:50 UTC 2017

Now I have a problem with console-io.c file.
The problem is with csr macros - there is no more such a register "tohost".
Here it is described a little:
https://github.com/riscv/riscv-pk/issues/25

Could you explain what should be done here and what for was mtohost
register?

2017-06-02 2:22 GMT+03:00 Hesham Almatary <heshamelmatary at gmail.com>:

> On Fri, Jun 2, 2017 at 9:12 AM, Denis Obrezkov <denisobrezkov at gmail.com>
> wrote:
> > So, am I understand right, that I should make my repo, submit commits to
> it,
> > produce patches and send them to your repo as pool requests?
> > And should I make my repo by cloning yours?
> >
> Correct. Make sure your work with priv-1.10 (as a base) branch since
> this is the one that should end up upstream. Ideally, you would
> fork/clone my repo, checkout priv-1.10 branch, create your own branch
> based on it, and submit pull requests to my priv-1.10 branch.
> Regularly, you'd want to rebase against priv-1.10 when I make changes
> to it.
>
>
> > 2017-06-02 2:02 GMT+03:00 Hesham Almatary <heshamelmatary at gmail.com>:
> >>
> >> Hi Denis,
> >>
> >> On Fri, Jun 2, 2017 at 1:27 AM, Denis Obrezkov <denisobrezkov at gmail.com
> >
> >> wrote:
> >> > Hello Hesham,
> >> >
> >> > should I apply your patches? or should I paste all of them to
> >> > some directory (rsb has several 'patches' folders).
> >> >
> >> You only need to apply this patch [1] to RSB and build the tools again.
> >>
> >> [1] https://lists.rtems.org/pipermail/devel/2017-May/017951.html
> >> > Also, could you describe our workflow? In the context of with what
> >> > repository
> >> >  I should work and where I should direct my pull requests.
> >> >
> >> Since the port is not upstream yet, you can submit PRs to my GitHub
> >> repo in the time being until we get it upstreamed. After this you can
> >> submit patches for review to this mailing list.
> >>
> >> > 2017-06-01 5:09 GMT+03:00 Hesham Almatary <heshamelmatary at gmail.com>:
> >> >>
> >> >> Hi Denis,
> >> >>
> >> >> I submitted two patches for the tools, please use the latest only and
> >> >> rebuild the tools. This should avoid the newlib issues you had above
> >> >> as it uses main riscv patches.
> >> >>
> >> >> I'll look into the port this weekend and submit fixes unless you beat
> >> >> me to it. Meanwhile, you can submit error messages and I'll see if I
> >> >> can help.
> >> >>
> >> >> Keep the good work.
> >> >>
> >> >> Cheers,
> >> >> Hesham
> >> >>
> >> >> On Thu, Jun 1, 2017 at 12:04 AM, Denis Obrezkov
> >> >> <denisobrezkov at gmail.com>
> >> >> wrote:
> >> >> > 2017-05-31 16:39 GMT+03:00 Denis Obrezkov <denisobrezkov at gmail.com
> >:
> >> >> >>
> >> >> >> Thanks, I downloaded it.
> >> >> >> There was a mistake also that _JBLEN wasn't defined in
> >> >> >> machine/setjmp.h
> >> >> >> I don't know the exact value, so I did the following:
> >> >> >> #ifdef __riscv
> >> >> >>
> >> >> >> /* TBD: not the exact number */
> >> >> >>
> >> >> >> #define _JBLEN 16
> >> >> >>
> >> >> >> #endif
> >> >> >>
> >> >> >> Now, it compiles further. But then I get the error:
> >> >> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> >> >> >> -B../../../riscv_generic/lib/
> >> >> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> >> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> >> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> >> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\"
> >> >> >> -DPACKAGE_URL=\"\"
> >> >> >> -I.
> >> >> >>
> >> >> >>
> >> >> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> >> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> >> >> -Wmissing-prototypes -Wimplicit-function-declaration
> >> >> >> -Wstrict-prototypes
> >> >> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP
> >> >> >> -MF
> >> >> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> >> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> >> >> >> 'display/disp_hcms29xx.c'
> >> >> >> ||
> >> >> >> echo
> >> >> >>
> >> >> >>
> >> >> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >> >> >> riscv32-rtems4.12-gcc: error: bsp_specs: No such file or directory
> >> >> >>
> >> >> >> So, I inserted it manually. But I can't figure out, why it wasn't
> >> >> >> copied
> >> >> >> automatically.
> >> >> >>
> >> >> >> Now I have an error:
> >> >> >> riscv32-rtems4.12-gcc --pipe -B../../../lib/
> >> >> >> -B../../../riscv_generic/lib/
> >> >> >> -specs bsp_specs -qrtems -DPACKAGE_NAME=\"rtems-c-src\"
> >> >> >> -DPACKAGE_TARNAME=\"rtems-c-src\" -DPACKAGE_VERSION=\"4.11.99.0\"
> >> >> >> -DPACKAGE_STRING=\"rtems-c-src\ 4.11.99.0\"
> >> >> >> -DPACKAGE_BUGREPORT=\"https://devel.rtems.org/newticket\"
> >> >> >> -DPACKAGE_URL=\"\"
> >> >> >> -I.
> >> >> >>
> >> >> >>
> >> >> >> -I/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip
> >> >> >> -isystem ../../../riscv_generic/lib/include   -O0 -g -Wall
> >> >> >> -Wmissing-prototypes -Wimplicit-function-declaration
> >> >> >> -Wstrict-prototypes
> >> >> >> -Wnested-externs -MT display/libdisplay_a-disp_hcms29xx.o -MD -MP
> >> >> >> -MF
> >> >> >> display/.deps/libdisplay_a-disp_hcms29xx.Tpo -c -o
> >> >> >> display/libdisplay_a-disp_hcms29xx.o `test -f
> >> >> >> 'display/disp_hcms29xx.c'
> >> >> >> ||
> >> >> >> echo
> >> >> >>
> >> >> >>
> >> >> >> '/home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/'`display/disp_hcms29xx.c
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> /home/reprofy/Projects/riscv/rtems/development/rtems/
> kernel/rtems-riscv/c/src/libchip/display/disp_hcms29xx.c:26:10:
> >> >> >> fatal error: bsp.h: No such file or directory
> >> >> >>  #include <bsp.h>
> >> >> >>
> >> >> >> It seems that configure scripts should be modified.
> >> >> >>
> >> >> >> 2017-05-31 8:46 GMT+03:00 Hesham Almatary
> >> >> >> <heshamelmatary at gmail.com>:
> >> >> >>>
> >> >> >>> Hi Denis,
> >> >> >>>
> >> >> >>> Please use priv-1.10 branch. I rebased it (against master) and
> >> >> >>> added
> >> >> >>> some fixes to make the build progress. Still, there's more work
> >> >> >>> needed. Your contributions are welcomed.
> >> >> >>>
> >> >> >>> Cheers,
> >> >> >>> Hesham
> >> >> >>> .
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Regards, Denis Obrezkov
> >> >> >
> >> >> > I think I worked it out. In a few days I will produce patches.
> >> >> > Now I am trying to compile .S files. Seems that some instructions
> are
> >> >> > missing.
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Regards, Denis Obrezkov
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Hesham
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Regards, Denis Obrezkov
> >>
> >>
> >>
> >> --
> >> Hesham
> >
> >
> >
> >
> > --
> > Regards, Denis Obrezkov
>
>
>
> --
> Hesham
>

-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170604/19dc429a/attachment-0002.html>