Error Reading Boot Sector X-loader Hangs
Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support Blogs Analog Wire Analog: The real world Behind the Wheel ConnecTIng Wirelessly Enlightened: The TI DLP® Blog Fully Charged Industrial Strength Launch Your Design Learn E2E Motor Drive & Control MSP Low-Power Plays On the Grid Power House Precision Hub The Process Think. Innovate TI Live @... Tools Insider University Program Groups Corporate Citizenship TI University Program Russian E2E (сообщество E2E) Japanese E2E (日本語コミュニティ) Learn E2E Launch Your Design Motor Drive & Control Videos More Cancel OMAP™ Processors OMAP35x Processors Forum (Archived) Mentions Tags More Cancel Sign In to Post Sign In to Post Cancel Go to Digital Signal Processors (DSP) Forums Amplifiers Switches & Multiplexers Applications Processors Clock and Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support Announcements Amplifiers Switches & Multiplexers Applications Processors Clock and Timing Data Converters Development Tools Digital Signal Processors (DSP) DLP® Products & MEMS Embedded Software Interface Isolation Logic Microcontrollers OMAP™ Applications Processors (Read Only) Power Management RF & Digital Radio Sensor Products Haptics & Touch Wireless Connectivity /etc Support More Cancel Not Answered Booting OMAP3530 evm with MMC/SD Prodigy 170 points Jean FAYE Hello everybody, Sorry for my english which is not excellent. I have a problem and I hope you will be able to help me. Thank you in advance. So I am working with an OMAP3530 and tried to make it boot on the MMC. But it fail. It display this message on the terminal (minicom): Texas Instruments X-Loader 1.42Starting X-loader on MMC Reading boot sectorError: reading boot sectorX-Loader hangs Can you help me to resolve this error? thank you Prodigy 170 points Jean FAYE Feb 17, 2010 4:40 PM Reply Cancel Cancel Reply Suggest as Answer Use rich formatting 6 Replies Mastermind 36620 points Juan Gonzales Feb 17, 2010 4:57 PM Did you make sure to follow the instructions at http://wiki.davincidsp.com/index.php/SD/MMC_format_for
SDcard is not inserted into the Panda Board, the status LED 2 (D2) isturned ON. Once the SD card is inserted, the status LED 2 turned OFF.Whenever i press the Power ON_RESET button, the status LED 1(D1) and LED 2 will blink once. Is this normal?I have flashed the SD card with pre-built binaries, downloaded fromhttp://omappedia.org/wiki/Android_Pre-built_Binaries_Guide. BasicallyI followed all the 6 steps stated in the link but when I use minicomto connect to the board, I'm seeing the following error messages:Error: Reading boot sectorCould not https://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/35268 read bootloader!X-Loader hangsI have tried to re-format the SD card for a few times but failed.Please advice what is going wrong.Thanks,MM Ram 2011-08-10 02:30:36 UTC PermalinkRaw Message Hi,I am not sure of what the LEDs denote to the user. But, I was hittingthe same condition as follow.Post by Mooi Mooi TanError: Reading boot sectorCould not read bootloader!X-Loader hangsWhat I did was to http://pandaboard.narkive.com/g9GzFroq/status-led-1-and-led-2-error-reading-boot-sector copy the MLO first, followed by u-boot then finallycopy kernel image after formatting the FAT partition. If you are usingGUI, I would recommend copying them one by one.If that still didnt solve, try to get a new MLO image.BR,RamPost by Mooi Mooi TanHi,Will status LED 1 and LED 2 turn ON when the minicom started? When SDcard is not inserted into the Panda Board, the status LED 2 (D2) isturned ON. Once the SD card is inserted, the status LED 2 turned OFF.Whenever i press the Power ON_RESET button, the status LED 1(D1) and LED 2 will blink once. Is this normal?I have flashed the SD card with pre-built binaries, downloaded fromhttp://omappedia.org/wiki/Android_Pre-built_Binaries_Guide. BasicallyI followed all the 6 steps stated in the link but when I use minicomError: Reading boot sectorCould not read bootloader!X-Loader hangsI have tried to re-format the SD card for a few times but failed.Please advice what is going wrong.Thanks,MM 1 Reply 2 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation Mooi Mooi Tan 2011-08-09 08:24:10 UTC Ram 2011-08-10 02:30:36 UTC about - legalese Loading...
here for a quick overview of the site Help Center Detailed answers to any questions you might have http://unix.stackexchange.com/questions/122582/bootloader-fails-to-load-linux-kernel 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 http://www.techradar.com/how-to/computing/how-to-boot-repair-ubuntu-1315203 us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and error reading other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Bootloader fails to load linux kernel up vote 1 down vote favorite I upgraded linux kernel from 2.6.32 to 3.0.7 but now error reading boot bootloader isn't able to load the kernel image. Specifically, boot procedure freezes after: Starting kernel ... Uncompressing Linux... done, booting the kernel. The reason was that bootloader (U-Boot) wasn't properly configured, which was confirmed by the fact that between kernel 2.6.x and kernel 3.0.x the serial ports have been renamed from ttySx to ttyOx. The next step was to edit an uEnv.txt, stored on boot partition, in order to get read during the boot procedure. uEnv.txt: mpurate=1000 dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" vram=16M optargs="consoleblank=0" console="tty0 console=ttyO2,115200n8" Boot procedure fails with: Texas Instruments X-Loader 1.5.0 (Jun 14 2011 - 22:04:07) Beagle xM Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42) OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #7ba200029ff800000168300f0802900e Hit any key to stop autoboot: 0
won't boot How to repair Ubuntu if it won't boot By Nick Peers How To Fix startup issues Shares Page 1 of 3: Fixing boot problems Fixing boot problems Non-Grub boot issues Post-Grub troubleshooting Start-up problems. That moment when – having expected yourself to be getting on with your day's work or entertainment – you find yourself staring at a cryptic error message, or even worse, a blank screen.No matter how many times you press reset or restart, the same impenetrable barrier blocks your path. So, what can you do? Start-up problems come in all shapes and sizes, and they can be difficult to track down.There are, however, some sound principles to use that will resolve many errors, and in this tutorial, we're going to look at the tools and techniques required to troubleshoot most start-up problems. You should start by examining how the boot process works.This reveals that the boot process can be split into three broad stages centred around the Grub 2 boot loader: pre-Grub, Grub and post-Grub. Knowing this allows you to focus your troubleshooting efforts based on where in the process the error or freeze occurs.If you're struggling to get the Boot-Repair tool disc to boot, experiment with the various fail-safe boot options.Let's start at the beginning. You switch on your PC. If power comes on, but nothing else happens, chances are you've a hardware issue to sort – if you recently poked around the innards of your PC, then check everything is connected correctly.If not, unplug all external devices except your keyboard and try again. If this doesn't work, open the case carefully and disconnect your internal drives too. If the computer now boots to the splash screen, you can try reconnecting the internal drives and trying again; if you're now able to boot to the login screen, shut down your PC and start reconnecting your external peripherals to see if the problem has cleared itself or can be targeted to a single device, in which case try a different cable, or go online and Google for known boot problems involving that device.If you're lucky, your motherboard will emit a series of beeps or flashing lights you can use – again by enlisting the help of the internet – to identify the likely problem. This may involve replacing a component or something more drastic.If you're able to get as far as your PC's splash screen, but then your computer hangs or a 'missing operating syst