mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: Unable to Boot from NAND on Mini2440
Date: Mon, 20 May 2013 20:56:35 +0200	[thread overview]
Message-ID: <201305202056.35305.jbe@pengutronix.de> (raw)
In-Reply-To: <5197608A.40707@gmail.com>

Vikram Narayanan wrote:
> Hello,
>
> I followed the instructions here
> <http://barebox.org/documentation/barebox-2011.04.0/mini2440.html>
>
> After writing to NAND, I switched the boot mode to NAND and did a reset.
> Nothing comes up on the prompt. I tried to verify the 'write', by a
> 'nand_boot_test'. That works. Please find the log below. I'm on the
> latest master.
>
> --- start log ---
> Supervivi> go 0x31000000
> go to 0x31000000
>    argument 0 = 0x00000000
>    argument 1 = 0x00000000
>    argument 2 = 0x00000000
>    argument 3 = 0x00000000
>
>
> barebox 2013.05.0-00126-g19bc427 #4 Sat May 18 15:53:01 IST 2013
>
>
> Board: Mini 2440
> nand: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V
> 8-bit), page size: 2048, OOB size: 64
> dm9000 dm90000: Found DM9000E at i/o: 0x20000300
> mdio_bus: miibus0: probed
> s3c_mci s3c_mci0: registered as s3c_mci0
> malloc space: 0x31bf8000 -> 0x31ff7fff (size 4 MiB)
> refclk:    12000 kHz
> mpll:     405000 kHz
> upll:      48000 kHz
> fclk:     405000 kHz
> hclk:     101250 kHz
> pclk:      50625 kHz
> SDRAM1:   CL4@101MHz
> SDRAM2:   CL4@101MHz
> envfs: wrong magic on /dev/env0
> no valid environment found on /dev/env0. Using default environment
> running /env/bin/init...
> set parameter: Invalid argument
>
> Hit any key to stop autoboot:  3
> mini2440:/ eth0.ipaddr=192.168.1.240
>
> mini2440:/ eth0.netmask=255.255.255.0
> mini2440:/ eth0.serverip=192.168.1.14
> mini2440:/ erase /dev/nand0.barebox.bb
> mini2440:/ tftp barebox.bin /dev/nand0.barebox.bb
> warning: No MAC address set. Using random address F2:08:F4:9F:14:99
> 100Mbps full duplex link detected
>          ###############
> mini2440:/ nand_boot_test 0x32000000 0x40000
> mini2440:/ go 0x32000000
> ## Starting application at 0x32000000 ...
>
>
> barebox 2013.05.0-00126-g19bc427 #4 Sat May 18 15:53:01 IST 2013
>
>
> Board: Mini 2440
> nand: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V
> 8-bit), page size: 2048, OOB size: 64
> dm9000 dm90000: Found DM9000E at i/o: 0x20000300
> mdio_bus: miibus0: probed
> s3c_mci s3c_mci0: registered as s3c_mci0
> malloc space: 0x31bf8000 -> 0x31ff7fff (size 4 MiB)
> refclk:    12000 kHz
> mpll:     405000 kHz
> upll:      48000 kHz
> fclk:     405000 kHz
> hclk:     101250 kHz
> pclk:      50625 kHz
> SDRAM1:   CL4@101MHz
> SDRAM2:   CL4@101MHz
> envfs: wrong magic on /dev/env0
> no valid environment found on /dev/env0. Using default environment
> running /env/bin/init...
> set parameter: Invalid argument
>
> Hit any key to stop autoboot:  3
> mini2440:/
>
> --- end log ----
>
> Any idea on what goes wrong?

Hmm, never had a Mini2440 with a 1 GiB NAND. Can you see, what kind of SDRAM 
devices are on your Mini2440 board? Maybe they also changed the SDRAMs...

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

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

  reply	other threads:[~2013-05-21  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18 11:05 Vikram Narayanan
2013-05-20 18:56 ` Juergen Beisert [this message]
2013-05-27  0:37   ` Vikram Narayanan
2013-05-27  7:26     ` Juergen Beisert
2013-05-21  7:13 ` Sascha Hauer

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=201305202056.35305.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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