RISC-V interrupts

[Denis Obrezkov]

2017-06-07 14:44 GMT+03:00 Sebastian Huber <sebastian.huber at embedded-
brains.de>:

> On 06/06/17 18:58, Hesham Almatary wrote:
>
> Originally RTEMS had a one big linkcmd for each platform, which
>> defines linker symbols (used in C code) and required sections. This
>> has been improved with current BSPs (like ARM-based ones), by
>> splitting up shared linkcmd parts (linkcmd base) and BSP specific ones
>> that include the shared one. riscv_generic, given that it's old,
>> follows the old way of having a single big linkcmd. You can change
>> this for your new BSP.
>>
>
> New ports/BSPs should definitely use a shared linkcmds.base (see ARM). Use
> "riscv-rtems4.12-ld --verbose" to get the default linker script.

Ok.

Now I have a problem:
https://github.com/embeddedden/rtems-riscv/blob/hifive1/c/src/lib/libbsp/riscv32/hifive1/start/start.S#L117
When I step to that line, gdb hangs with a message:
(gdb) step
Note: automatically using hardware breakpoints for read-only addresses.

Does somebody know what can be done here?

Also, I don't like my initial linker file:
https://github.com/embeddedden/rtems-riscv/blob/hifive1/c/src/lib/libbsp/riscv32/hifive1/startup/linkcmds
Critique is very appreciated.


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