openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: www <ouyangxuan10@163.com>
Cc: openbmc@lists.ozlabs.org, "Cédric Le Goater" <clg@kaod.org>
Subject: Re: [openbmc-qemu]: Add read mac from eeprom in uboot by i2c and lead to the image unable to start  in QEMU?
Date: Wed, 26 May 2021 08:36:24 +0930	[thread overview]
Message-ID: <9d6af632-ce29-4b4e-b039-077913cc9e0d@www.fastmail.com> (raw)
In-Reply-To: <3c87dea1.379a.179a29ccce3.Coremail.ouyangxuan10@163.com>

Hi Byron,

I've Cc'ed the openbmc mailing list on this reply.

On Tue, 25 May 2021, at 17:50, www wrote:
> 
> 
> At 2021-05-24 08:22:58, "Andrew Jeffery" <andrew@aj.id.au> wrote:
> >Hi Byron
> >
> >On Sat, 22 May 2021, at 19:32, www wrote:
> >> Hi Andrew Jeffery, Joel Stanley & Cédric Le Goater,
> >> 
> >> chip:aspeed 2500
> >> uboot : u-boot-2016.07  commit-id: cc6c5bef00ebbac0b37
> >> platform: romulus
> >> 
> >> I enable read mac from eeprom by i2c in uboot, and lead to  the image 
> >> unable to start  in QEMU. The startup process stops at "Starting kernel 
> >> ...“
> >> I'd like to ask:
> >> 1. How can I solve this problem? Do you have any suggestions?
> >
> >Can you please configure your kernel with the following and re-run?
> >
> > CONFIG_DEBUG_LL=y
> > CONFIG_DEBUG_LL_UART_8250=y
> > CONFIG_DEBUG_UART_PHYS=0x1e784000
> > CONFIG_DEBUG_UART_VIRT=0xf8184000
> >
> I set up these four items and didn't print any information.
> then I add "*#define DEBUG*" in the file of *arch/arm/boot/compressed/head.S*, 
> It's just one more line printed.

Sorry, I failed to mention that you also need to add 'debug' and 
'earlyprintk' to your kernel commandline (i.e. append them to the 
'bootargs' u-boot environment variable) for the CONFIG_DEBUG_* bits 
above to be useful.

Let me know if that helps.

Andrew

> 
> thanks,
> Byron
> 
> >This allows us to see the kernel log before the UART driver is probed.
> >
> >Also, please ask these questions on the mailing list. Other people 
> >might have similar problems and so a public discussion will help them 
> >too. Posting publicly can help you also, because you're relying on at 
> >least one of the three of us to reply to you in a reasonable timeframe. 
> >If your question is public anyone who has the skills and time can chime 
> >in to help you out.
> >
> >Andrew
> 
> 
>  
> 
> Attachments:
> * image.png

           reply	other threads:[~2021-05-25 23:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3c87dea1.379a.179a29ccce3.Coremail.ouyangxuan10@163.com>]

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=9d6af632-ce29-4b4e-b039-077913cc9e0d@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ouyangxuan10@163.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;
as well as URLs for NNTP newsgroup(s).