Crc Error Linux Kernel
Today's Posts Advanced Search Find the answer to your Linux question: Entire Site Articles Downloads Forums Linux Hosting Forum GNU Linux Zone Kernel Kernel fails to boot with "crc error -- System halted" If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now supports the Tapatalk app for your mobile device. Results 1 to 8 of 8 Thread: Kernel fails to boot with "crc error -- System halted" Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Enjoy an ad free experience by logging in. Not a member yet? Register. 09-14-2012 #1 AJEllisuk View Profile View Forum Posts Private Message View Articles Just Joined! Join Date Aug 2012 Posts 39 Kernel fails to boot with "crc error -- System halted" Hi I have run into a major problem in that when I program my kernel into flash on my system or try and run it from RAM I get the following output: ## Booting image at 00060000 ... ## Copy image from flash 00060000 to ram 00200000 ... Image Name: Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1871640 Bytes = 1.8 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux............................................. .................................................. .................... crc error -- System halted The checksum passes, but the image type is uncompressed, so why is the kernel trying to decompress? From a successful build I had the same message about uncompressing the kernel, so I don't understand what the problem is. I have
it enabled. Please turn JavaScript back on and reload this page.More questions in i.MX Community Where is this place located?NXP CommunityAll Placesi.MX CommunityLog in to create and rate content, and to follow, bookmark, and share content with other members.AnsweredAssumed AnsweredError message "Verifying Checksum ... Bad Data CRC" appears when uboot load linux kernelQuestion asked by Eddy Liu on Apr 1, 2014Latest reply on Aug 4, 2014 by Yuri Muhin Like • Show 0 Likes0 Comment • 5Hi Guys,I add initramfs(based on http://www.linuxforums.org/forum/kernel/191833-kernel-fails-boot-crc-error-system-halted.html busy box) in linux kernel compiling. uImage becomes bigger than default(no initramfs support):Error message generates in the process of downloading uboot and kernel image using Mfgtools:Header 1U-Boot 2009.08 (Aug 16 2013 - 15:02:51)CPU: Freescale i.MX6 family TO1.1 at 792 MHzThermal sensor with ratio = 188Temperature: 39 C, calibration data 0x5a34e87dmx6q pll1: 792MHzmx6q pll2: 528MHzmx6q https://community.nxp.com/thread/321740 pll3: 480MHzmx6q pll8: 50MHzipg clock : 66000000Hzipg per clock : 66000000Hzuart clock : 80000000Hzcspi clock : 60000000Hzahb clock : 132000000Hzaxi clock : 198000000Hzemi_slow clock: 99000000Hzddr clock : 396000000Hzusdhc1 clock : 198000000Hzusdhc2 clock : 198000000Hzusdhc3 clock : 198000000Hzusdhc4 clock : 198000000Hznfc clock : 24000000HzBoard: i.MX6DL/Solo-SABRESD: unknown-board Board: 0x61011 [POR ]Boot Device: MMCI2C: readyDRAM: 512 MBMMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3Using default environmentIn: serialOut: serialErr: serialNet: got MAC address from IIM: 00:00:00:00:00:00FEC0 [PRIME]Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 10800000 ... Image Name: Linux-3.0.35-2508-g54750ff Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 9181376 Bytes = 8.8 MB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... Bad Data CRCERROR: can't get kernel image!MX6Solo SABRESD-MFG U-Boot > uboot environment:Header 1MX6Solo SABRESD-MFG U-Boot > printenvbootargs=console=ttymxc0,115200 rdinit=/linuxrc enable_wait_mode=off nosmpbootcmd=bootm 0x10800000 0x10c00000bootdelay=0baudrate=115200ipaddr=192.168.1.103serverip=192.168.1.101netmask=255.255.255.0loadaddr=0x10800000rd_loadaddr=(0x10800000 + 0x300000)netdev=eth0ethprime=FEC0uboot=u-boot.binkernel=uImagestdin=serialstdout=serialstderr=serialethact=FEC0Environment size: 371/131068 bytesI enlarged parameter rd_loadaddr, which is 10 times than before:Header 1MX6Solo SABRESD-MFG U-Boot > set rd_loadaddr (0x10800000+0x1E00000)MX6Solo SABRESD-MFG U-Boot > printenvbootargs=console=ttymxc0
© Arch Linux ARM
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 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 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 Kernel booting stops right after “Uncompressing Linux…” up vote 5 down vote favorite 1 I'm trying to bring up an ARM-based board. I've got U-Boot working but can't seem to get the kernel to load. Most of the time it only goes as far as: Starting kernel ... Uncompressing Linux... A couple of times while playing with U-Boot env settings it followed up with: uncompression error -- System halted I found some threads that suggested using LZO compression instead of GZIP so I've reconfigured the kernel, but now it's getting the LZO compression error message: Compressed data violation -- System halted Any suggestions how I could try to debug this? I've already enabled DEBUG_LL and printk in the kernel, but those haven't served me at all. linux kernel arm u-boot share|improve this question edited Feb 20 '14 at 9:12 Timo 3,9271024 asked Feb 19 '14 at 18:04 Gatica 13314 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote Seems that there was an read error so the decompressed data has no valid checksum. Possible reasons: RAM/SRAM errrors. Too little RAM/SRAM. share|improve this answer edited Feb 20 '14 at 16:59 answered Feb 19 '14 at 19:57 user55518 Yes, I'm worried it may be