RISC-V testing needs on HW?

[Mohammed Billoo]

I can access the memory regions without any issues. This is the output
of a program I slapped together:

BusyBox v1.32.0.git (2020-09-01 14:37:15 EDT) hush - the humble shell
Enter 'help' for a list of built-in commands.

/ # memory_access
Hello World
Successfully opened /dev/mem
0x80700000: 0x0
0x80700001: 0x0
0x80700002: 0x0
0x80700003: 0x0
0x80700004: 0x0
0x40700000: 0x0
0x40700001: 0x0
0x40700002: 0x0
0x40700003: 0x0
0x40700004: 0x0
0x50440000: 0xff

Looks like syscon is all 1s. Is there some documentation on the K210
that has the register definitions?

On Tue, Sep 1, 2020 at 10:16 AM Sean Anderson <seanga2 at gmail.com> wrote:
>
> On 9/1/20 10:14 AM, Mohammed Billoo wrote:
> > On Tue, Sep 1, 2020 at 6:42 AM Sean Anderson <seanga2 at gmail.com> wrote:
> >> Can you test what happens when accessing ai ram (0x40600000-0x407FFFFF
> >> and 0x80600000-0x807FFFFF)? I have two boards where this appears to lock
> >> up the bus, but I have also heard it reported that accessing this area
> >> of ram works fine. If it works for you, can you please also report what
> >> your clock and reset settings are? Those should be controlled by the
> >> syscon device at 0x50440000.
> >>
> >> The ai ram takes up 2M, which is a lot of memory on a board with 8M
> >> total. It would be great to be able to use it when the KPU is not in
> >> use, but I have been unable to access it correctly. I have been testing
> >> mostly with U-Boot, but I experience the same problems when booting
> >> Linux.
> >>
> >> --Sean
> >
> > Sure, is this on the latest master or the 5.8 release?
>
>
> Doesn't matter to me.
>
> --Sean



-- 
Mohammed A Billoo
Founder
MAB Labs, LLC
www.mab-labs.com
201-338-2022