Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Verifying Checksum ... Bad Data CRC
@ 2016-01-27 14:20 Gabriel Andrés Castillo
  2016-01-27 15:33 ` Thomas Petazzoni
  0 siblings, 1 reply; 4+ messages in thread
From: Gabriel Andrés Castillo @ 2016-01-27 14:20 UTC (permalink / raw)
  To: buildroot

Hi, when i configure linux kernel, on kernel features -> preemption model,
i had "No forced preemption" and the boot was working fine. But when i want
to change the option to "Preemptible Kernel", i want to boot again and i
get this:


NAND read: device 0 offset 0x180000, size 0x10000
 65536 bytes read: OK

NAND read: device 0 offset 0x200000, size 0x380000
 3670016 bytes read: OK
## Booting kernel from Legacy Image at 22000000 ...
   Image Name:   Linux-4.1.0-linux4sam_5.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3730848 Bytes = 3.6 MiB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

How can i make my kernel preemptible?

--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160127/789e157b/attachment.html>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Verifying Checksum ... Bad Data CRC
  2016-01-27 14:20 [Buildroot] Verifying Checksum ... Bad Data CRC Gabriel Andrés Castillo
@ 2016-01-27 15:33 ` Thomas Petazzoni
  2016-01-27 16:01   ` Gabriel Andrés Castillo
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Petazzoni @ 2016-01-27 15:33 UTC (permalink / raw)
  To: buildroot

Gabriel,

On Wed, 27 Jan 2016 11:20:10 -0300, Gabriel Andr?s Castillo wrote:
> Hi, when i configure linux kernel, on kernel features -> preemption model,
> i had "No forced preemption" and the boot was working fine. But when i want
> to change the option to "Preemptible Kernel", i want to boot again and i
> get this:
> 
> 
> NAND read: device 0 offset 0x180000, size 0x10000
>  65536 bytes read: OK
> 
> NAND read: device 0 offset 0x200000, size 0x380000
>  3670016 bytes read: OK
> ## Booting kernel from Legacy Image at 22000000 ...
>    Image Name:   Linux-4.1.0-linux4sam_5.0
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3730848 Bytes = 3.6 MiB
>    Load Address: 20008000
>    Entry Point:  20008000
>    Verifying Checksum ... Bad Data CRC
> ERROR: can't get kernel image!
> 
> How can i make my kernel preemptible?

This error has nothing to do with the kernel being preemptible or not.
It generally means that you improperly flashed your kernel image, or
are improperly loading it. Maybe you forgot to erase your NAND before
reflashing your kernel? Maybe you didn't reflash the entire kernel
image which is bigger than it used to be?

You're actually not *reading* enough: you're reading 0x380000 bytes
(i.e 3670016 bytes) from your NAND to load the kernel image, but the
mkimage header says the image is 3730848 bytes in size.

Please double check your NAND programming and reading commands, to make
sure that they accommodate the slightly larger kernel.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Verifying Checksum ... Bad Data CRC
  2016-01-27 15:33 ` Thomas Petazzoni
@ 2016-01-27 16:01   ` Gabriel Andrés Castillo
  2016-01-27 16:14     ` Thomas Petazzoni
  0 siblings, 1 reply; 4+ messages in thread
From: Gabriel Andrés Castillo @ 2016-01-27 16:01 UTC (permalink / raw)
  To: buildroot

Thanks for the answer. I'm erasing the NAND before reflashing the kernel.
I'm sure of that becouse, when i go back with non preemptible kernel, all
is working fine.

I think that the problem is that the uImage is being stored in other part
of the memory of the SOM. Could be that on "menuconfig-> Kernel ->
(0x20008000) load address" is setting wrong? In case of that, what is the
value that i have to set it?

2016-01-27 12:33 GMT-03:00 Thomas Petazzoni <
thomas.petazzoni@free-electrons.com>:

> Gabriel,
>
> On Wed, 27 Jan 2016 11:20:10 -0300, Gabriel Andr?s Castillo wrote:
> > Hi, when i configure linux kernel, on kernel features -> preemption
> model,
> > i had "No forced preemption" and the boot was working fine. But when i
> want
> > to change the option to "Preemptible Kernel", i want to boot again and i
> > get this:
> >
> >
> > NAND read: device 0 offset 0x180000, size 0x10000
> >  65536 bytes read: OK
> >
> > NAND read: device 0 offset 0x200000, size 0x380000
> >  3670016 bytes read: OK
> > ## Booting kernel from Legacy Image at 22000000 ...
> >    Image Name:   Linux-4.1.0-linux4sam_5.0
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    3730848 Bytes = 3.6 MiB
> >    Load Address: 20008000
> >    Entry Point:  20008000
> >    Verifying Checksum ... Bad Data CRC
> > ERROR: can't get kernel image!
> >
> > How can i make my kernel preemptible?
>
> This error has nothing to do with the kernel being preemptible or not.
> It generally means that you improperly flashed your kernel image, or
> are improperly loading it. Maybe you forgot to erase your NAND before
> reflashing your kernel? Maybe you didn't reflash the entire kernel
> image which is bigger than it used to be?
>
> You're actually not *reading* enough: you're reading 0x380000 bytes
> (i.e 3670016 bytes) from your NAND to load the kernel image, but the
> mkimage header says the image is 3730848 bytes in size.
>
> Please double check your NAND programming and reading commands, to make
> sure that they accommodate the slightly larger kernel.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>



--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160127/d3467970/attachment.html>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Verifying Checksum ... Bad Data CRC
  2016-01-27 16:01   ` Gabriel Andrés Castillo
@ 2016-01-27 16:14     ` Thomas Petazzoni
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Petazzoni @ 2016-01-27 16:14 UTC (permalink / raw)
  To: buildroot

Gabriel,

Please don't top post, this is bad practice on mailing lists.

On Wed, 27 Jan 2016 13:01:35 -0300, Gabriel Andr?s Castillo wrote:
> Thanks for the answer. I'm erasing the NAND before reflashing the kernel.
> I'm sure of that becouse, when i go back with non preemptible kernel, all
> is working fine.
> 
> I think that the problem is that the uImage is being stored in other part
> of the memory of the SOM. Could be that on "menuconfig-> Kernel ->
> (0x20008000) load address" is setting wrong? In case of that, what is the
> value that i have to set it?

Please read my original reply entirely. It tells you why your kernel
doesn't boot.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-01-27 16:14 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-27 14:20 [Buildroot] Verifying Checksum ... Bad Data CRC Gabriel Andrés Castillo
2016-01-27 15:33 ` Thomas Petazzoni
2016-01-27 16:01   ` Gabriel Andrés Castillo
2016-01-27 16:14     ` Thomas Petazzoni

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox