* RISC-V testing needs on HW?
@ 2020-08-24 14:20 Mohammed Billoo
2020-09-01 10:42 ` Sean Anderson
0 siblings, 1 reply; 6+ messages in thread
From: Mohammed Billoo @ 2020-08-24 14:20 UTC (permalink / raw)
To: linux-riscv
My Kendryte board should arrive this Thursday. Is there any targeted
testing that anyone would like done, or should I just build the latest
5.9 rc for riscv, load it on the board, and see what happens?
Thanks
--
Mohammed A Billoo
Founder
MAB Labs, LLC
www.mab-labs.com
201-338-2022
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RISC-V testing needs on HW?
2020-08-24 14:20 RISC-V testing needs on HW? Mohammed Billoo
@ 2020-09-01 10:42 ` Sean Anderson
2020-09-01 14:14 ` Mohammed Billoo
0 siblings, 1 reply; 6+ messages in thread
From: Sean Anderson @ 2020-09-01 10:42 UTC (permalink / raw)
To: Mohammed Billoo, linux-riscv
Hi,
On 8/24/20 10:20 AM, Mohammed Billoo wrote:
> My Kendryte board should arrive this Thursday. Is there any targeted
> testing that anyone would like done, or should I just build the latest
> 5.9 rc for riscv, load it on the board, and see what happens?
>
> Thanks
>
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RISC-V testing needs on HW?
2020-09-01 10:42 ` Sean Anderson
@ 2020-09-01 14:14 ` Mohammed Billoo
2020-09-01 14:16 ` Sean Anderson
0 siblings, 1 reply; 6+ messages in thread
From: Mohammed Billoo @ 2020-09-01 14:14 UTC (permalink / raw)
To: Sean Anderson; +Cc: linux-riscv
On Tue, Sep 1, 2020 at 6:42 AM Sean Anderson <seanga2@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?
--
Mohammed A Billoo
Founder
MAB Labs, LLC
www.mab-labs.com
201-338-2022
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RISC-V testing needs on HW?
2020-09-01 14:14 ` Mohammed Billoo
@ 2020-09-01 14:16 ` Sean Anderson
2020-09-01 21:08 ` Mohammed Billoo
0 siblings, 1 reply; 6+ messages in thread
From: Sean Anderson @ 2020-09-01 14:16 UTC (permalink / raw)
To: Mohammed Billoo; +Cc: linux-riscv
On 9/1/20 10:14 AM, Mohammed Billoo wrote:
> On Tue, Sep 1, 2020 at 6:42 AM Sean Anderson <seanga2@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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RISC-V testing needs on HW?
2020-09-01 14:16 ` Sean Anderson
@ 2020-09-01 21:08 ` Mohammed Billoo
2020-09-29 23:41 ` Sean Anderson
0 siblings, 1 reply; 6+ messages in thread
From: Mohammed Billoo @ 2020-09-01 21:08 UTC (permalink / raw)
To: Sean Anderson; +Cc: linux-riscv
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@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@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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: RISC-V testing needs on HW?
2020-09-01 21:08 ` Mohammed Billoo
@ 2020-09-29 23:41 ` Sean Anderson
0 siblings, 0 replies; 6+ messages in thread
From: Sean Anderson @ 2020-09-29 23:41 UTC (permalink / raw)
To: Mohammed Billoo; +Cc: linux-riscv
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-09-29 23:41 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-24 14:20 RISC-V testing needs on HW? Mohammed Billoo
2020-09-01 10:42 ` Sean Anderson
2020-09-01 14:14 ` Mohammed Billoo
2020-09-01 14:16 ` Sean Anderson
2020-09-01 21:08 ` Mohammed Billoo
2020-09-29 23:41 ` Sean Anderson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.