From: yanhong wang <yanhong.wang@starfivetech.com>
To: <u-boot@lists.denx.de>
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Simon Glass <sjg@chromium.org>, Torsten Duwe <duwe@lst.de>
Subject: Re: The latest U-boot reports an error when running on StarFive visionfive2 1.3B board
Date: Fri, 2 Jun 2023 09:16:25 +0800 [thread overview]
Message-ID: <87df93fb-38b0-d293-c2cf-cf887e275130@starfivetech.com> (raw)
In-Reply-To: <CAPnjgZ1YU+Luu94_d5g-0zRbrifWSfOYf6-fEx7djvCN3iQBcA@mail.gmail.com>
On 2023/5/31 2:11, Simon Glass wrote:
> Hi Yanhong,
>
> Please can you send this to the mailing list and cc me?
>
> Regards,
> Simon
>
> On Tue, 16 May 2023 at 20:48, yanhong wang
> <yanhong.wang@starfivetech.com> wrote:
>>
>> Hi Simon Glass,
>>
>> Running the latest U-boot on the StarFive VisionFive 2 1.3B board prompts the following error message:
>>
>> U-Boot 2023.07-rc2-00133-g6e1852ca2c (May 17 2023 - 09:08:48 +0800)
>>
>> CPU: rv64imafdc_zba_zbb
>> Model: StarFive VisionFive 2 v1.3B
>> DRAM: 8 GiB
>> initcall sequence 00000000fffe08b0 failed at call 000000004021611e (err=-19)
>> ### ERROR ### Please RESET the board ###
>>
>> Roll back the most recent submission, and finally confirm that one of the submission affected [commit ID: 55171aedda88d12666e2a1bbc661dea1bec65337].
>> The author of this submission is you, so I sent this email to learn more about the specific situation.
>>
>> Do you have any suggestions to solution this issue?
>>
>>
>> Best Regards.
>>
>> yanhong.wang@starfivetech.com
next parent reply other threads:[~2023-06-02 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c94484c6-0c84-5e04-3b8a-e2c08f31398d@starfivetech.com>
[not found] ` <CAPnjgZ1YU+Luu94_d5g-0zRbrifWSfOYf6-fEx7djvCN3iQBcA@mail.gmail.com>
2023-06-02 1:16 ` yanhong wang [this message]
2023-06-02 17:10 ` [RFC] riscv: JH7110: move pll clocks to their own device node (Was: The latest U-boot...) visionfive2 1.3B board Torsten Duwe
2023-06-03 1:05 ` The latest U-boot reports an error when running on StarFive " Simon Glass
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=87df93fb-38b0-d293-c2cf-cf887e275130@starfivetech.com \
--to=yanhong.wang@starfivetech.com \
--cc=duwe@lst.de \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox