Error Reading Boot Sector Beagle
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Beagleboard: Erased NAND flash and now not booting up vote 3 down vote favorite 1 I have a Beagle board OMAP3530-GP and I had copied my kernel and rootfs into two partitions of the SDcard and wanted to boot it. partition 1 of the SDcard: FAT32 boot partition with the following files in the same order: MLO u-boot.bin uImage uInitrd And in partition 2: rootfs Now I had initially booted it whereby I got: Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24) Reading boot sector Error: reading boot sector Loading u-boot.bin from nand U-Boot 2011.03 (Apr 20 2011 - 07:19:53) OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 In: serial Out: serial Err: serial Beagle Rev C1/C2/C3 timed out in wait_for_pin: I2C_STAT=0 No EEPROM on expansion board Die ID #5738000300000000040323091100e002 Hit any key to stop autoboot: 0 MMC: block number 0x1 exceeds max(0x0) ** Can't read from device 0 ** ** Unable to use mmc 0:1 for fatload ** MMC: block number 0x1 exceeds max(0x0) ** Can't read from device 0 ** ** Unable to use mmc 0:1 for fatload ** Wrong Image Format for bootm command ERROR: can't get kernel image! I thought it had an earlier u-boot.bin in NAND that it was reading and wanted to erase it so in a freaky moment did: OMAP3 beagleboard.org # nandecc sw SW ECC selected OMAP3 beagleboard.org # nand erase 0 80000 NAND erase: device 0 offset 0x0, size 0x80000 Erasing at 0x60000 -- 100% complete. OK OMAP3 beagleboard.org # nand erase 80000 160000 NAND erase: device 0 offset 0x80000, size 0x160000 Erasing at 0x1c0000 -- 100% complete. OK And booted again to only notice just a few non-readable serial characters and the bootloader not coming up anymore. Then it hit me that I had perhaps deleted the X-loader 1.4.2 in the NAND! I copied it into my
("bricked"). Contents 1 Symptoms 2 What has happened? 3 What to do now? 3.1 MMC recovery 3.2 MMC recovery Troubleshooting 3.3 USB recovery 3.4 UART recovery Symptoms Normally, if you boot from MMC, you will get something like ...40T... in terminal program connected to UART (115200 8N1). This is output from OMAP3's bootrom while scanning the UART for boot source before trying to boot from MMC card. If you don't get this, but want to boot from MMC, most probably bootrom doesn't reach the MMC boot stage any more. If you played with NAND before getting this, most probably NAND contains some broken content. What has happened? Depending on user button OMAP3 on BeagleBoard uses different boot order. Normal order if user http://stackoverflow.com/questions/9823699/beagleboard-erased-nand-flash-and-now-not-booting button isn't pressed at power up is boot from NAND -> USB -> UART -> MMC in this order. Depending on the boot medium (e.g. MMC) this might fail if something bad is in NAND flash which confuses OMAP3 bootrom thus stopping it to reach MMC boot stage. This might happen if you e.g. mess your NAND, e.g. something went wrong with NAND boot. What to do now? First, we have to press user button at power up http://elinux.org/BeagleBoardRecovery to switch boot order to USB -> UART -> MMC -> NAND to have option to boot from other sources than broken NAND (which is first if user button is not pressed). Then, there are three options to boot from: MMC USB UART Below, MMC and USB recovery will be done in detail. The goal is to get a U-Boot prompt and then to erase the non-booting NAND. MMC recovery For the most up to date instruction to restore any BeagleBoard version SD card to the factory image see the CircuitCo Wiki. The procedure to put your board into the "factory fresh state" used on all boards being made now is at http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation. The original recovery method is described below. MMC recovery should be straight forward. Press user button at power up and according to above boot order MMC boot is before NAND. With this, we should be able to boot as we did without pressing the user button before bricking the board. But: There are some broken MLO (x-loader) out there which fail to boot if something wrong is in NAND. E.g.: ...40T......... Texas Instruments X-Loader 1.41 Starting on with MMC Reading boot sector 150832 Bytes Read from MMC Starting OS Bootloader from MMC... U-Boot 1.3.3 (Jun 20 2008 - 17:06:22) OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz OMAP3 Beagle Board + LPDDR/NAND RAM Configuration: Bank #0: 80000000 128 MB Bank #1: 88000000 0 k
date ] [ thread ] [ subject ] [ author ] On Tue, Dec 7, 2010 at 1:10 PM, Guilherme Salgado
från GoogleLogga inDolda fältSök efter grupper eller meddelanden