From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1UehJl-0002h6-4i for barebox@lists.infradead.org; Tue, 21 May 2013 07:49:10 +0000 From: Juergen Beisert Date: Mon, 20 May 2013 20:56:35 +0200 References: <5197608A.40707@gmail.com> In-Reply-To: <5197608A.40707@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201305202056.35305.jbe@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Unable to Boot from NAND on Mini2440 To: barebox@lists.infradead.org Vikram Narayanan wrote: > Hello, > > I followed the instructions here > > > 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