te:
>> >
>> > Hello Simon,
>> >
>> > My board boots well . When I added the second partition into my kernel I
>> > got this message
>> > *Verifying Checksum ... Bad Data CRC*
>> > what could be the root cause ?
>>
>> Try to run "saveenv",
Oct 10, 2022 at 6:31 PM momo aubin wrote:
> >
> > Hello Simon,
> >
> > My board boots well . When I added the second partition into my kernel I
> > got this message
> > *Verifying Checksum ... Bad Data CRC*
> > what could be the root cause ?
>
> Try to run "saveenv",
>
On Mon, Oct 10, 2022 at 6:31 PM momo aubin wrote:
>
> Hello Simon,
>
> My board boots well . When I added the second partition into my kernel I
> got this message
> *Verifying Checksum ... Bad Data CRC*
> what could be the root cause ?
Try to run "saveenv",
gt;
> >> My board boots well . When I added the second partition into my kernel I
> >> got this message
> >> Verifying Checksum ... Bad Data CRC
> >> what could be the root cause ?
> >>
> >> Which data is talking about ? u boot data or kernel d
Hi Simon
> On 11 Oct 2022, at 12:33 AM, Simon Glass wrote:
>
> Hi Momo,
>
>> On Mon, 10 Oct 2022 at 15:31, momo aubin wrote:
>>
>> Hello Simon,
>>
>> My board boots well . When I added the second partition into my kernel I got
>> thi
Hi Momo,
On Mon, 10 Oct 2022 at 15:31, momo aubin wrote:
>
> Hello Simon,
>
> My board boots well . When I added the second partition into my kernel I got
> this message
> Verifying Checksum ... Bad Data CRC
> what could be the root cause ?
>
> Which data is tal
Hello Simon,
My board boots well . When I added the second partition into my kernel I
got this message
*Verifying Checksum ... Bad Data CRC*
what could be the root cause ?
Which data is talking about ? u boot data or kernel data ?
Thanks in advance.
Ok, I've found my error
I don't used FTP in binary mode when I download file in filesystem.
Sorry, for the disruption.
Sophie
--
View this message in context:
http://u-boot.10912.n7.nabble.com/Load-kernel-from-JFFS2-Bad-Data-CRC-tp176605p176610.html
Sent from the U-Boot ma
n context:
http://u-boot.10912.n7.nabble.com/Load-kernel-from-JFFS2-Bad-Data-CRC-tp176605p176607.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
hello,
I try to load from JFFS2 filesystem , the kernel,rootfs and DTB. and I
have bad data CRC error on my file.
Have you any idea of the reason ?
I try to copy several kernel image in the filesystem i've got the same
error, also with rootfs.
I've no problem with "raw"
"bad data CRC" error.. Why? Kernel load entry point is 10008000, uboot
loadaddr is 0x1200
Please help me to boot my UDOO!!! Thanks
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
MB
>Load Address: 8000
> Entry Point: 8000
>Verifying Checksum ... Bad Data CRC
>
>
> The script I'm using to make my kernel image is:
>
> SRC=$2/arch/arm/boot/uImage
> if [ -f $SRC ]; then
> printf "Kernel source in: %s\n"
owing
errors
Booting image at 0006 ...
## Copy image from flash 0006 to ram 0020 ...
Image Name:
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1759300 Bytes = 1.7 MB
Load Address: 8000
Entry Point: 8000
Verifying Checksum ... Bad Data CRC
Hi ZHAO JiHua,
> I've found the answer and confirmed it. FTP transfer corrupted uImage.
[...]
> I don't know which, FileZilla or WS_FTP, corrupted uImage.
Very likely you need to sort out the well known ascii/binary problem
(e.g. [1]) for your ftp setups.
Cheers
Detlev
--
So maybe I lost t
Hi all
I've found the answer and confirmed it. FTP transfer corrupted uImage.
As my development laptop has no COM port, I transferred uImage from this
development laptop to my company's FTP server using FileZilla 3.0.11.1,
then from this FTP server to my desktop using WS_FTP 9.01. Then, I used
th
Hi all
I can successfully boot my kernel when I download it using
the ethernet. But if I download the same kernel through serial COM port
or from my on-board micro-SD card to the same DRAM address, this "Bad
Data CRC" always pops up:
$ bootm 0x8000
## Booting kernel from Legac
Yes i am running little endian kernel, but this error comes in both little as
well as big endian kernel.
--- On Thu, 15/4/10, Detlev Zundel wrote:
From: Detlev Zundel
Subject: Re: [U-Boot] Bad Data CRC ERROR: can't get kernel image!
To: "Ronny D"
Cc: "U-boot"
Date:
Hi Ronny,
> I used "iminfo 0xffdc" and got following log
>Image Name: Linux-2.6.31-LE
Just out of curiosity - does the "-LE" mean that you do have a
little-endian linux running on this platform?
Cheers
Detlev
--
Those who do not understand Unix are condemned to reinvent it,
poorl
>
>
> Hi Detlev,
>
> I used "iminfo 0xffdc" and got following log
> Image Name: Linux-2.6.31-LE
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 936145 Bytes = 914.2 kB
> Load Address: 0000
> Entry Point
Hi Detlev,
I used "iminfo 0xffdc" and got following log
Image Name: Linux-2.6.31-LE
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 936145 Bytes = 914.2 kB
Load Address:
Entry Point: 00000000
Bad Data CRC
Here i am confused
Hi Ronny,
> Bad Data CRC
>
>
> ERROR: can't get kernel image!
[...]
> Please let me know your input on this.
Well your data seems to be corrupt - what more can we say? What does
"imi 0xffdc" say?
Maybe you did not flash the whole image correctly? E.g. d
Bad Data CRC
ERROR: can't get kernel image!
When I print the data that we
calculated in image_check_dcrc() I found foloowing difference:
Calculated DCRC Data :
0xffdc0040 Len: 0xe48d1 dcrc: 0x5fe26d1e
From image_get_dcrc function DCRC: 0x72e08293
And hence return
t;
> 2097152 bytes read: ERROR
You got a read error here. Seems your NAND reading failed for some
reason (bad sector?).
> Verifying Checksum ... Bad Data CRC
Well, that's only logical, then.
> 4.then i use the bootloader vivi in NorFlash to flash the uImage to NAND
> Flash
Bytes = 1.6 MB
Load Address:
Entry Point:
Verifying Checksum ... Bad Data CRC
# open24x0 Bootloader for FA24x0 #
[u] Download u-boot
[k] Download Linux kernel
[j] Download JFFS2 image
[y] Download YAFFS image
[d] Download to SDRAM & Run
[b] Boot
ot/uImage' to 0x8080
>> Scanning JFFS2 FS: . ..- done.
>> ### JFFS2 load complete: 3249008 bytes loaded to 0x8080
>> ## Booting image at 8080 ...
>> Image Name: Linux Kernel Image with ramdisk.
>> Created: 200
.- done.
> ### JFFS2 load complete: 3249008 bytes loaded to 0x8080
> ## Booting image at 8080 ...
> Image Name: Linux Kernel Image with ramdisk.
> Created: 2009-06-22 4:37:12 UTC
> Image Type: MIPS Linux Kernel Image (gzip compressed)
>
26 matches
Mail list logo
