public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH v5 11/11] riscv: Add FPIOA and GPIO support for Kendryte K210
Date: Fri, 21 Aug 2020 06:06:18 -0400	[thread overview]
Message-ID: <6fc7bdac-476d-9e4e-926f-354acdc49d7d@gmail.com> (raw)
In-Reply-To: <20200821090848.GA2451@APC301.andestech.com>

On 8/21/20 5:08 AM, Ruinland ChuanTzu Tsai wrote:
> Hi Sean and all,
> 
> Sorry for dropping this mail out of the blue.
> 
> I'm trying to follow the instrcutions from `doc/board/sipeed/maix.rst`
> to build and flash u-boot so as to verify Sean's work on `maix_gpio_good` tree.
> 
> Yet the console has no output.
> 
> Furthermore, I found the documentation on Sipeed board to be a little bit confusing.
> In your first commit of that document, it's stated that "only the Sipeed MAIX BiT
> V2.0 (bitm) and Sipeed MAIXDUINO are supported."

Those are the only boards I have, so those are all that I can support.

> Yet the later commit (137dc15) added a table which implies that the older version
> of MAIX BiT is supported. So I'm a bit confused about whether older MAIX BiTs get
> supported or not ? (I'm testing the builts on the older version.)

It *should* work, but I haven't tested anything on a bit v1. Have you
tried booting with v2020.07? That release should have the bare minimum
needed to get things working.

> Does the replacement of CH34x with CH552 may cause the issue I'm encountering ?

Probably not.

> 
> By the way, I was trying to use the pre-built toolchain from kendryte's GitHub [1].
> Yet the linker (riscv64-unknown-elf-ld.bfd) complains that `-pie` is not supported.
> Hence I switched to the the binutils v2.34 built from upstream and the u-boot could
> be built without that hiccup.

I have been using the toolchain which comes with my distro
(riscv64-linux-gnu-* on Arch). I don't know whether that makes much
difference, but I have never used Canaan's pre-build toolchain.

--Sean

> 
> Could someone tell me which toolchain is recommended for building the u-boot for
> boards Kendryte K210 ?
> 
> [1] https://github.com/kendryte/kendryte-gnu-toolchainhttps://github.com/kendryte/kendryte-gnu-toolchain
> 
> Many thanks,
> Ruinland
> 
> On Thu, Aug 20, 2020 at 02:25:36PM +0800, Rick Jian-Zhi Chen(???) wrote:
>>
>>
>> -----Original Message-----
>> From: Sean Anderson [mailto:seanga2 at gmail.com] 
>> Sent: Wednesday, August 19, 2020 7:13 PM
>> To: Rick Chen
>> Cc: U-Boot Mailing List; Simon Glass; Tom Rini; Bin Meng; Rick Jian-Zhi Chen(???); Alan Quey-Liang Kao(???)
>> Subject: Re: [PATCH v5 11/11] riscv: Add FPIOA and GPIO support for Kendryte K210
>>
>> On 8/18/20 11:48 PM, Rick Chen wrote:
>>> Hi Tom
>>>
>>>> This patch adds the necessary configs and docs for FPIOA and GPIO support
>>>> on the K210.
>>>>
>>>> The board does not boot unless CONSOLE_LOGLEVEL is set to a non-default
>>>> value . It also boots when the tree is dirty (and CONSOLE_LOGLEVEL is not
>>>> changed). It also boots when changes are made to the device tree and then
>>>> committed. I don't know why this happens. These breakages only occur after
>>>> bf2fb81ad3.
>>>>
>>>> Signed-off-by: Sean Anderson <seanga2@gmail.com>
>>>> ---
>>>>
>>>> Changes in v5:
>>>> - Increase CONSOLE_LOGLEVEL to 5 as a hack to get the board booting again
>>>> - Patch 05/12 "gpio: sifive: Use generic reg read function" has been superseded
>>>>   by commit 2548493ab4.
>>>
>>> Would you like to pick up this series, [PATCH v5 00/11] riscv: Add
>>> FPIOA and GPIO support for Kendryte K210 ?
>>> Or maybe it is better to figure out what is wrong here and find the
>>> root cause why it need to Increase CONSOLE_LOGLEVEL to 5 as a hack ?
>>
>> As an additional note, *CONFIG_LOGLEVEL (whoops) can also be decreased
>> for the same effect. In addition, there are several other ways I found
>> to "fix" this bug (as noted in the commit message). If you would like to
>> test this out, I have two trees [1, 2] where this series (actually a slightly
>> earlier version of this series) is applied just before and just after
>> bf2fb81ad3. The original patch is located at [3].
>>
>> --Sean
>>
>> [1] https://github.com/Forty-Bot/u-boot/tree/maix_gpio_good
>> [2] https://github.com/Forty-Bot/u-boot/tree/maix_gpio_bad
>> [3] https://patchwork.ozlabs.org/project/uboot/patch/20200724111225.12513-15-ovidiu.panait at windriver.com/

      reply	other threads:[~2020-08-21 10:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-15 15:52 [PATCH v5 00/11] riscv: Add FPIOA and GPIO support for Kendryte K210 Sean Anderson
2020-08-15 15:52 ` [PATCH v5 01/11] pinctrl: Add pinmux property support to pinctrl-generic Sean Anderson
2020-08-15 15:52 ` [PATCH v5 02/11] pinctrl: Reformat documentation in dm/pinctrl.h Sean Anderson
2020-09-02 12:26   ` Heinrich Schuchardt
2020-09-02 14:56     ` Sean Anderson
2020-09-02 15:17       ` Heinrich Schuchardt
2020-09-02 15:38         ` Sean Anderson
2020-08-15 15:52 ` [PATCH v5 03/11] test: pinmux: Add test for pin muxing Sean Anderson
2020-08-15 15:52 ` [PATCH v5 04/11] pinctrl: Add support for Kendryte K210 FPIOA Sean Anderson
2020-08-15 15:52 ` [PATCH v5 05/11] gpio: dw: Fix warnings about casting int to pointer Sean Anderson
2020-08-15 15:52 ` [PATCH v5 06/11] gpio: dw: Add a trailing underscore to generated name Sean Anderson
2020-08-15 15:52 ` [PATCH v5 07/11] gpio: dw: Return output value when direction is out Sean Anderson
2020-08-15 15:52 ` [PATCH v5 08/11] led: gpio: Default to using node name if label is absent Sean Anderson
2020-08-15 15:52 ` [PATCH v5 09/11] test: dm: Test for default led naming Sean Anderson
2020-08-15 15:52 ` [PATCH v5 10/11] riscv: Add pinmux and gpio bindings for Kendryte K210 Sean Anderson
2020-09-02 18:04   ` Heinrich Schuchardt
2020-09-02 20:43     ` Sean Anderson
2020-08-15 15:52 ` [PATCH v5 11/11] riscv: Add FPIOA and GPIO support " Sean Anderson
2020-08-19  3:48   ` Rick Chen
2020-08-19 11:12     ` Sean Anderson
2020-08-20  8:07       ` Rick Chen
2020-08-20  8:47         ` Rick Chen
2020-08-31 21:48           ` Sean Anderson
2020-09-01  1:19             ` Rick Chen
2020-09-02 12:26               ` Heinrich Schuchardt
2020-09-02 15:59                 ` Sean Anderson
2020-09-05 14:40                   ` Sean Anderson
     [not found]       ` <752D002CFF5D0F4FA35C0100F1D73F3FA473754A@ATCPCS16.andestech.com>
2020-08-21  9:08         ` Ruinland ChuanTzu Tsai
2020-08-21 10:06           ` Sean Anderson [this message]

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=6fc7bdac-476d-9e4e-926f-354acdc49d7d@gmail.com \
    --to=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox