mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Javier Fileiv <javier.fileiv@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Loading kernel issues
Date: Tue, 18 Oct 2016 07:37:05 +0200	[thread overview]
Message-ID: <20161018053705.lajqirng3w6wkb2x@pengutronix.de> (raw)
In-Reply-To: <CABvwO2ARpHSzYE6Y3JrfFAQ2jEzw3EXfP36goL6kPogcBbNLKQ@mail.gmail.com>

Hi Javier,

On Sun, Oct 16, 2016 at 11:06:15PM +0200, Javier Fileiv wrote:
> Hi everyone, I've just flashed barebox on my Mini2440. I have 2
> questions/issues now
> 
> 1) When trying to load the kernel from TFTP, everything is ok but when
> it's trying to mount the rootfs something is not working, even though
> I set the rootdelay param to 5 secs.
> 
> 2) I tried also the boot from nand and is working just fine, but there
> no is auto boot when reseting the board... it just give me the barebox
> prompt each time, and if i run from there boot nand it works OK, but
> no automaGically. :)
> 
> Any suggestions? Thank you very much
> 
> 
> LOG FOR TFTP BOOT:
> 
> mini2440:/ boot tftp
> warning: No MAC address set. Using random address A2:50:1F:24:DF:AB
> phy0: Link is up - 100/Full
> T DHCP client bound to address 192.168.0.15
> TFTP from server 192.168.0.10 ('uImage-mini2440' -> '/dev/ram0.kernel')
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ################################################
> booting kernel of type uimage from /dev/ram0.kernel
>    Verifying Checksum ... OK
>    Image Name:   Linux-3.16.7-ptx-master
>    Created:      2016-10-13  20:23:14 UTC
>    Image Type:   <NULL> <NULL> <NULL> (<NULL>)
>    Data Size:    1910288 Bytes =  1.8 MB
>    Load Address: 30008000
>    Entry Point:  30008000
> OK
> commandline: console=ttySAC0,115200 mini2440=0tbc rootdelay=5 ip=dhcp
> root=/dev/nfs nfsroot=/path/to/nfs/root,v3,tcp noinitrd

You have to replace nfsroot=/path/to/nfs/root with some valid path.
Since your dhcp server does not pass a root server ip you'll have to add
that aswell, so your nfsroot should look like
nfsroot=192.168.x.y:/path/to/nfsroot. Try 'edit /env/config' to edit
the parameter to your needs. Do not forget saveenv afterwards.

To boot from Nand also edit /env/config and adjust the kernel_loc and
rootfs_loc variables.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

       reply	other threads:[~2016-10-18  5:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABvwO2ARpHSzYE6Y3JrfFAQ2jEzw3EXfP36goL6kPogcBbNLKQ@mail.gmail.com>
2016-10-18  5:37 ` Sascha Hauer [this message]
2016-10-18  8:17 ` Juergen Borleis
2016-10-18  8:24   ` Javier Fileiv
2016-10-18 16:56     ` Javier Fileiv
2016-10-19  7:53       ` Juergen Borleis
2016-10-19 18:17         ` Javier Fileiv
2016-10-19 18:18           ` Javier Fileiv
2016-10-20  9:13             ` Juergen Borleis
2016-10-20  9:17               ` Javier Fileiv
2016-10-20 17:59                 ` Javier Fileiv
2016-10-21  7:39                   ` Juergen Borleis
2016-10-21  7:41                     ` Javier Fileiv
2016-10-21  7:53                       ` Juergen Borleis
2016-10-21  7:54                         ` Javier Fileiv
2016-10-21  8:02                           ` gianluca
2016-10-21  8:05                           ` Juergen Borleis
2016-10-21  8:07                         ` Sascha Hauer
2016-10-21  8:11                           ` Javier Fileiv

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=20161018053705.lajqirng3w6wkb2x@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=javier.fileiv@gmail.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