From: Sean Anderson <seanga2@gmail.com>
To: Mohammed Billoo <mab@mab-labs.com>, linux-riscv@lists.infradead.org
Subject: Re: RISC-V testing needs on HW?
Date: Tue, 1 Sep 2020 06:42:57 -0400 [thread overview]
Message-ID: <883c0f38-e002-ce16-d196-933a8b700776@gmail.com> (raw)
In-Reply-To: <CALkjhPrHDHRsFDh9n864xvK4DKU2GW68_TcA-Tz17udsOWjbFg@mail.gmail.com>
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
next prev parent reply other threads:[~2020-09-01 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 14:20 RISC-V testing needs on HW? Mohammed Billoo
2020-09-01 10:42 ` Sean Anderson [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=883c0f38-e002-ce16-d196-933a8b700776@gmail.com \
--to=seanga2@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mab@mab-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.