BeagleBoardNAND - Revision history

JKSH: /* Hardware */ BeagleBoard RevC5 memory increase

2012-10-14T08:38:23Z

‎Hardware: BeagleBoard RevC5 memory increase

Semenko: /* X-Loader */ and in the instructions

2010-06-03T16:45:43Z

‎X-Loader: and in the instructions

Semenko: /* X-Loader */ changed to update version

2010-06-03T16:45:08Z

‎X-Loader: changed to update version

Jsarao: /* X-Loader */ capitalize ROM

2010-01-05T17:26:01Z

‎X-Loader: capitalize ROM

Jsarao: minor grammer / english corrections

2010-01-05T17:24:56Z

minor grammer / english corrections

Dirk: Undo revision 13470: On recent U-Boot's, it's "nandecc": http://elinux.org/BeagleBoardFAQ#U-Boot_v1_.232 . If it isn't at yours, please update U-Boot.

2009-08-28T16:48:19Z

Undo revision 13470: On recent U-Boot's, it's "nandecc": http://elinux.org/BeagleBoardFAQ#U-Boot_v1_.232 . If it isn't at yours, please update U-Boot.

Zecke: It appears to be nand ecc and not nandecc.

2009-08-27T09:08:59Z

It appears to be nand ecc and not nandecc.

Challinan: /* U-Boot */

2009-08-05T19:57:18Z

‎U-Boot

Challinan: /* X-Loader */

2009-08-05T19:56:48Z

‎X-Loader

Mpoullet: /* Writing kernel with kernel */ Use the padding option

2009-05-16T21:26:10Z

‎Writing kernel with kernel: Use the padding option

@@ Line 9: / Line 9: @@
 OMAP3530 has 256MB NAND flash in PoP (PoP: Package-On-Package implementation for Memory Stacking) configuration.
-* [[BeagleBoard]] has 256MB of Micron NAND
+* [[BeagleBoard]] has 256MB of Micron NAND (512MB as of Rev C5)
 * [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html EVM] 128MB of Samsung OneNAND or 128MB of Micron NAND
 * [http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit Zoom MDK] also uses the Micron NAND

@@ Line 60: / Line 60: @@
   OMAP3 beagleboard.org # '''mmc init'''
-  OMAP3 beagleboard.org # '''fatload mmc 0:1 80000000 x-load.bin.ift_for_NAND'''
+  OMAP3 beagleboard.org # '''fatload mmc 0:1 80000000 x-load_revc_v3.bin.ift'''
   reading x-load.bin.ift_for_NAND

← Older revision		Revision as of 16:45, 3 June 2010
Line 36:		Line 36:
	==X-Loader==		==X-Loader==

−	[http://code.google.com/p/beagleboard/wiki/BeagleSoftCompile Build] or download [http://code.google.com/p/beagleboard/downloads/list binary] (x-~~load~~.bin.~~ift_for_NAND~~) X-Loader. Put it at the first (boot) FAT partition of MMC/SD card and boot from the card. Then start boot from card and use the following to write X-Loader to NAND:	+	[http://code.google.com/p/beagleboard/wiki/BeagleSoftCompile Build] or download [http://code.google.com/p/beagleboard/downloads/list binary] (x-load_revc_v3.bin.ift) X-Loader. Put it at the first (boot) FAT partition of MMC/SD card and boot from the card. Then start boot from card and use the following to write X-Loader to NAND:

← Older revision		Revision as of 17:26, 5 January 2010
Line 83:		Line 83:


−	Note: The command ''nandecc hw'' is essential here! X-Loader is started by OMAP3 boot ~~rom~~. This uses HW ECC while reading the NAND, so while writing, we have to use OMAP3 HW ECC, too. If you don't use HW ECC boot ~~rom~~ [[BeagleBoardRecovery\|can't boot from NAND]] any more.	+	Note: The command ''nandecc hw'' is essential here! X-Loader is started by OMAP3 boot ROM. This uses HW ECC while reading the NAND, so while writing, we have to use OMAP3 HW ECC, too. If you don't use HW ECC boot ROM [[BeagleBoardRecovery\|can't boot from NAND]] any more.

	==U-Boot==		==U-Boot==

@@ Line 30: / Line 30: @@
 x00680000-0x10000000 : "File System"
-To be able to write something to (empty) NAND, you first need to boot from an other source, e.g. [[BeagleBoard#MMC.2FSD_boot|MMC/SD card boot]]. Besides the files you need for MMC/SD card boot (MLO & U-Boot), put the files you want to flash into first FAT partition of MMC/SD card, too. Then you can read them from there and write them to NAND.
+To be able to write something to (empty) NAND, you first need to boot from another source, e.g. [[BeagleBoard#MMC.2FSD_boot|MMC/SD card boot]]. In addition to the files you need for MMC/SD card boot (MLO & U-Boot), put the files you want to flash into the first FAT partition of MMC/SD card. Then you can read them from there and write them to NAND.
-Note: If something goes wrong writing the initial X-Loader, your board might not boot any more without pressing the [[BeagleBoard#User_button|user button]]. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this, then.
+Note: If something goes wrong writing the initial X-Loader, your board might not boot any more without pressing the [[BeagleBoard#User_button|user button]]. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.
 ==X-Loader==
-[http://code.google.com/p/beagleboard/wiki/BeagleSoftCompile Build] or download [http://code.google.com/p/beagleboard/downloads/list binary] (x-load.bin.ift_for_NAND) X-Loader. Put it at first (boot) FAT partition of MMC/SD card and boot from card. Then start boot from card and use the following to write X-Loader to NAND:
+[http://code.google.com/p/beagleboard/wiki/BeagleSoftCompile Build] or download [http://code.google.com/p/beagleboard/downloads/list binary] (x-load.bin.ift_for_NAND) X-Loader. Put it at the first (boot) FAT partition of MMC/SD card and boot from the card. Then start boot from card and use the following to write X-Loader to NAND:
   ...40T.......
@@ Line 80: / Line 81: @@
 bytes written: OK
   OMAP3 beagleboard.org #
 Note: The command ''nandecc hw'' is essential here! X-Loader is started by OMAP3 boot rom. This uses HW ECC while reading the NAND, so while writing, we have to use OMAP3 HW ECC, too. If you don't use HW ECC boot rom [[BeagleBoardRecovery|can't boot from NAND]] any more.
@@ Line 146: / Line 148: @@
 ===Writing kernel with kernel===
-Once you have a kernel booted, e.g. from MMC card, you can use it to write himself (uImage) to NAND and then switch from MMC boot to kernel NAND boot. For this, observe kernel's boot messages. These should have something like
+Once you have a kernel booted, e.g. from MMC card, you can use it to write the kernel itself (uImage) to NAND and then switch from MMC boot to kernel NAND boot. For this, observe the kernel's boot messages. These should have something like:
   ...
@@ Line 170: / Line 172: @@
   mtd4: 0f980000 00020000 "File System"
-While the first three partitions (X-Loader, U-Boot and U-Boot Env) are read only from kernel point of view, Kernel and File System partition can be written by kernel itself. To do this, you need [http://www.linux-mtd.infradead.org/doc/general.html MTD User modules] in your kernel's root file system.
+While the first three partitions (X-Loader, U-Boot and U-Boot Env) are read only from kernel point of view, Kernel and File System partition can be written by the kernel itself. To do this, you need [http://www.linux-mtd.infradead.org/doc/general.html MTD User modules] in your kernel's root file system.
 In this example we mount boot (FAT) partition of MMC card (using a dual boot card) to read kernel image (uImage) from. If you have network connection in your kernel, you can use this, too. Or you put uImage in your root file system. Goal is to have access to uImage from running kernel to be able to write it to NAND.

@@ Line 69: / Line 69: @@
   nand_unlock: start: 00000000, length: 268435456!
   NAND flash successfully unlocked
-  OMAP3 beagleboard.org # '''nand ecc hw'''
+  OMAP3 beagleboard.org # '''nandecc hw'''
   OMAP3 beagleboard.org # '''nand erase 0 80000'''
@@ Line 81: / Line 81: @@
   OMAP3 beagleboard.org #
-Note: The command ''nand ecc hw'' is essential here! X-Loader is started by OMAP3 boot rom. This uses HW ECC while reading the NAND, so while writing, we have to use OMAP3 HW ECC, too. If you don't use HW ECC boot rom [[BeagleBoardRecovery|can't boot from NAND]] any more.
+Note: The command ''nandecc hw'' is essential here! X-Loader is started by OMAP3 boot rom. This uses HW ECC while reading the NAND, so while writing, we have to use OMAP3 HW ECC, too. If you don't use HW ECC boot rom [[BeagleBoardRecovery|can't boot from NAND]] any more.
 ==U-Boot==
@@ Line 98: / Line 98: @@
   nand_unlock: start: 00000000, length: 268435456!
   NAND flash successfully unlocked
-  OMAP3 beagleboard.org # '''nand ecc sw'''
+  OMAP3 beagleboard.org # '''nandecc sw'''
   OMAP3 beagleboard.org # '''nand erase 80000 160000'''
@@ Line 112: / Line 112: @@
 Note: You can use the same u-boot.bin you use to boot from MMC/SD card for NAND. There are no differences between U-Boot used for MMC/SD card boot and NAND boot.
-Note: Here, you don't need the ''nand ecc hw'' option. X-Loader which loads & starts U-Boot is able to understand SW ECC written by U-Boot.
+Note: Here, you don't need the ''nandecc hw'' option. X-Loader which loads & starts U-Boot is able to understand SW ECC written by U-Boot.
 ==Kernel==
@@ Line 126: / Line 126: @@
   reading uImage
-  OMAP3 beagleboard.org # '''nand ecc sw'''
+  OMAP3 beagleboard.org # '''nandecc sw'''
   OMAP3 beagleboard.org # '''nand erase 280000 400000'''
@@ Line 210: / Line 210: @@
   nand_unlock: start: 00000000, length: 268435456!
   NAND flash successfully unlocked
-  OMAP3 beagleboard.org # '''nand ecc sw'''
+  OMAP3 beagleboard.org # '''nandecc sw'''
   OMAP3 beagleboard.org # '''nand erase 680000 F980000'''

@@ Line 93: / Line 93: @@
 bytes read
   OMAP3 beagleboard.org # '''nand unlock'''
   device 0 whole chip
   nand_unlock: start: 00000000, length: 268435456!

@@ Line 181: / Line 181: @@
   root@beagleboard:~# '''flash_eraseall /dev/mtd3'''
   Erasing 128 Kibyte @ 3e0000 -- 96 % complete.
-  root@beagleboard:~# '''nandwrite /dev/mtd3 uImage'''
+  root@beagleboard:~# '''nandwrite -p /dev/mtd3 uImage'''
-  Input file is not page aligned
+  Writing data to block 0 at offset 0x0
-  Data did not fit into device, due to bad blocks
+  <...>
-  : Success
+  Writing data to block 20 at offset 0x280000
   root@beagleboard:~#