* Unable to Boot from NAND on Mini2440
@ 2013-05-18 11:05 Vikram Narayanan
2013-05-20 18:56 ` Juergen Beisert
2013-05-21 7:13 ` Sascha Hauer
0 siblings, 2 replies; 5+ messages in thread
From: Vikram Narayanan @ 2013-05-18 11:05 UTC (permalink / raw)
To: barebox; +Cc: Juergen Beisert
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?
Thanks,
Vikram
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Unable to Boot from NAND on Mini2440
2013-05-18 11:05 Unable to Boot from NAND on Mini2440 Vikram Narayanan
@ 2013-05-20 18:56 ` Juergen Beisert
2013-05-27 0:37 ` Vikram Narayanan
2013-05-21 7:13 ` Sascha Hauer
1 sibling, 1 reply; 5+ messages in thread
From: Juergen Beisert @ 2013-05-20 18:56 UTC (permalink / raw)
To: barebox
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to Boot from NAND on Mini2440
2013-05-20 18:56 ` Juergen Beisert
@ 2013-05-27 0:37 ` Vikram Narayanan
2013-05-27 7:26 ` Juergen Beisert
0 siblings, 1 reply; 5+ messages in thread
From: Vikram Narayanan @ 2013-05-27 0:37 UTC (permalink / raw)
To: Juergen Beisert; +Cc: barebox
On 21/05/2013 00:26, Juergen Beisert wrote:
>
> 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...
Sorry, I was totally away from mail access.
Here is the name on the chip.
K4S561632N -> 256 Mbit x 2
Regards,
Vikram
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to Boot from NAND on Mini2440
2013-05-27 0:37 ` Vikram Narayanan
@ 2013-05-27 7:26 ` Juergen Beisert
0 siblings, 0 replies; 5+ messages in thread
From: Juergen Beisert @ 2013-05-27 7:26 UTC (permalink / raw)
To: barebox
Vikram Narayanan wrote:
> On 21/05/2013 00:26, Juergen Beisert wrote:
> > 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...
>
> Sorry, I was totally away from mail access.
> Here is the name on the chip.
> K4S561632N -> 256 Mbit x 2
This memory is different from the HY57V561620 and MT48LC16M16 types I know and
Barebox is adapted to.
Maybe your system doesn't come up due to a wrong SDRAM configuration.
You should compare the SDRAM datasheets and check if the SDRAM controller
settings in Mini2440 'config.h' match the requirements of your SDRAM type.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to Boot from NAND on Mini2440
2013-05-18 11:05 Unable to Boot from NAND on Mini2440 Vikram Narayanan
2013-05-20 18:56 ` Juergen Beisert
@ 2013-05-21 7:13 ` Sascha Hauer
1 sibling, 0 replies; 5+ messages in thread
From: Sascha Hauer @ 2013-05-21 7:13 UTC (permalink / raw)
To: Vikram Narayanan; +Cc: barebox, Juergen Beisert
Hi Vikram,
On Sat, May 18, 2013 at 04:35:46PM +0530, 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.
Sorry, I can't help you here. I think Juergen can tell you more once
he is back in the office.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-05-27 7:30 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-05-18 11:05 Unable to Boot from NAND on Mini2440 Vikram Narayanan
2013-05-20 18:56 ` Juergen Beisert
2013-05-27 0:37 ` Vikram Narayanan
2013-05-27 7:26 ` Juergen Beisert
2013-05-21 7:13 ` Sascha Hauer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox