RISC-V testing needs on HW?

Sean Anderson seanga2 at gmail.com
Tue Sep 29 19:41:30 EDT 2020


On 9/1/20 5:08 PM, Mohammed Billoo wrote:
> 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

Thanks for testing this. I eventually determined the cause of the bug
was due to not setting K210_PLL_EN.

> Looks like syscon is all 1s.

Hm, that's strange. I'll have to try that out myself.

> Is there some documentation on the K210 that has the register
> definitions?

There is no documentation of register definitions besides the SDK.

--Sean



More information about the linux-riscv mailing list