public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] socfpga: mainline cannot boot linux
Date: Fri, 7 Nov 2014 08:24:00 +0100	[thread overview]
Message-ID: <201411070824.01048.marex@denx.de> (raw)
In-Reply-To: <545C0A26.1080800@opensource.altera.com>

On Friday, November 07, 2014 at 12:54:14 AM, Dinh Nguyen wrote:
> On 11/06/2014 05:40 PM, Anatolij Gustschin wrote:
> > Hi Dinh,
> > 
> > On Thu, 6 Nov 2014 17:03:48 -0600
> > 
> > Dinh Nguyen <dinguyen@opensource.altera.com> wrote:
> >> Hi Marek,
> >> 
> >> Have you been able to successfully boot Linux using the mainline uboot?
> >> I cannot seem to be able to boot linux on the C5 SocDK.
> >> 
> >> It starts to boot linux, but then reboots after a bit back into u-boot.
> >> So I commented out #define CONFIG_HW_WATCHDOG in
> >> include/configs/socfpga_cyclone5.h. That helped so that I can look that
> >> __log_buf.
> >> I was able to trace it down that it was not able to get a tty console,
> >> because serial8250_console_setup() is failing at:
> >> 
> >> if (!port->iobase && !port->membase)
> >> 
> >> For reasons I haven't figured out yet, both port->iobase and
> >> port->membase are NULL.
> >> 
> >> So no debug console, but Linux is able to boot all the way to the point
> >> of tyring to mount a FS.
> >> 
> >> Perhaps some kind of memory setup issue? I've seen a thread where
> >> Chin-Liang was able to boot, but I don't know if he did any other
> >> tricks.
> >> 
> >> Just wondering if I'm missing a patch or something?
> > 
> > the issue could be the wrong console= argument on the kernel command
> > line. In the current socfpga_config5.h I see
> > 
> >   #define CONFIG_BOOTARGS         "console=ttyS0"
> >   __stringify(CONFIG_BAUDRATE)
> > 
> > A comma is missing after "console=ttyS0"
> > 
> > It should be
> > 
> >   #define CONFIG_BOOTARGS         "console=ttyS0,"
> >   __stringify(CONFIG_BAUDRATE)
> > 
> > Could you please test it? Thanks.
> 
> Yep, that was it! Thanks alot for seeing that.

Thanks for spotting this, I'll pick the patch for Anatolij.

Best regards,
Marek Vasut

  reply	other threads:[~2014-11-07  7:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 19:55 [U-Boot] [PATCH 1/7] spi: altera: Use struct-based register access Marek Vasut
2014-10-22 19:55 ` [U-Boot] [PATCH 2/7] spi: altera: Clean up bit definitions Marek Vasut
2014-10-22 19:56 ` [U-Boot] [PATCH 3/7] spi: altera: Clean up most checkpatch issues Marek Vasut
2014-10-22 19:56 ` [U-Boot] [PATCH 4/7 v2] spi: altera: Zap endless loop Marek Vasut
2014-10-22 19:56 ` [U-Boot] [PATCH 5/7 v2] spi: altera: Clean up the use of variable d Marek Vasut
2014-10-22 19:56 ` [U-Boot] [PATCH 6/7 v2] spi: altera: Add short note about EPCS/EPCQx1 Marek Vasut
2014-10-22 19:56 ` [U-Boot] [PATCH 7/7] spi: altera: Move the config options to the top Marek Vasut
2014-10-27 17:11   ` Jagan Teki
2014-11-06 23:03   ` [U-Boot] socfpga: mainline cannot boot linux Dinh Nguyen
2014-11-06 23:40     ` Anatolij Gustschin
2014-11-06 23:54       ` Dinh Nguyen
2014-11-07  7:24         ` Marek Vasut [this message]
2014-10-23 14:45 ` [U-Boot] [PATCH 1/7] spi: altera: Use struct-based register access Pavel Machek

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=201411070824.01048.marex@denx.de \
    --to=marex@denx.de \
    --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