Building RISC-V BSP

[Hesham Almatary]

Hi Denis,

Yes, the Host-Target-Interface (HTIF) has been refactored/removed in
RISC-V. Also, it was meant to work with riscv front-end server
(riscv-fesvr) which is not the case for your HiFive BSP I guess.

I believe now it's the good time for you to start creating your own
HiFive BSP. You'll have to read/know how to output data over the
HiFive serial port or so, and develop your own console driver for the
board. You might find this link useful [1] when creating a new BSP,
and also use other BSPs as a reference (e.g. riscv_generic). Main
things to be aware of when creating a new BSP are: 1) startup code, 2)
console driver, and 3) timer driver. To make things easier for you,
and to give you credit for your contributions when merged upstream,
you'd want to create a new branch for your HiFive BSP based on
priv-1.10, and rebase against it when/if I make changes to it.

Keep the good work up.

[1] https://devel.rtems.org/wiki/TBR/UserManual/Submitting_a_BSP

Best,
Hesham

On Mon, Jun 5, 2017 at 7:00 AM, Denis Obrezkov <denisobrezkov at gmail.com> wrote:
> 2017-06-04 16:17 GMT+03:00 Denis Obrezkov <denisobrezkov at gmail.com>:
>>
>> 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?
>>
>
> I have built riscv-generic bsp. Though there are a lot of warnings.
> The current issue is that asm functions should be reimplemented (there is no
> more
> such a register 'mtohost' in csr).
>
> --
> Regards, Denis Obrezkov



-- 
Hesham