PDA

View Full Version : Kernel checksum error in update



cincinatofurtado
05-28-10, 05:13 PM
Hi everyone,

I've a PIKA Warp with S/N PIK-229-00421 and model number PIK-99-00910 .
So, I tried to fully update (including u-boot, kernel, persistents, FPGA...) the appliance via tftp to get new versions and the recent GUI and everything was appears to be ok. So I tried to reset the appliance and got an error when verifying checksum in u-boot: "Verifying checksum ... ERROR: Image data failed checksum verification" . The new files were obtained in file "images_2.2.2.3.tgz" and the old one was the stock one. Then I tried all again with files from "images_2.2.1.1.tgz" and same error. Now I've bricked my Warp because I can't boot the kernel.

I'm writing here because didn't find any other topic about this problem.

I appreciate any help. Thank you.

agauthier
05-31-10, 09:51 AM
Did you follow the instructions as per
ftp://ftp.pikatech.com/outgoing/appliance/2.2/docs/PIKA_WARP_the_Appliance_2.2_Release_Notes.pdf
section 4.1.1 Upgrade Information

There should be a log file on the USB stick telling you what may have gone wrong.

mrecoskie
05-31-10, 10:16 AM
Hi,

It sounds like you performed this upgrade manually through uboot and serial cable - is that correct? If so, I believe the error you are seeing is due to a mismatch between the actual size of the kernel image and the size allocated for the kernel on Warp. For reference - http://forum.pikatechnologies.com/showthread.php?t=390 (http://forum.pikatechnologies.com/showthread.php?t=390)

As suggested in that post you could resolve the error you are seeing by increasing the size of the kernel specified in uboot unfortunately I believe you will then just run into additional problems afterwards.

Instead I would strongly recommend the following - update by uboot and serial cable to the latest uboot image, reset the Warp and then update all the remaining image files. This should hopefully get you around the problems you are seeing. Let me know if any of this is unclear.

In the future I would recommend looking at the 'autorun' mechanism for upgrades. It may save a lot of headaches.

\Mark

awayte
05-31-10, 11:16 AM
Hi,

I thought that for the benefit of others who might encounter this same issue that I would outline a detailed procedure. So here are the steps you are required to perform for recovery:

1. Copy all of the new images to your tftp server.

2. Go to the PIKA FTP server and copy the following uboot image to your tftp server:

ftp://ftp.pikatech.com/outgoing/u-boot-1.3.0-95/u-boot-1.3.0-95.bin

3. Reboot the warp, halt the boot process when prompted with the following (Step up the tftp server environment variables if required):

Hit any key to stop autoboot: 0

=>

4. Update the uboot with the following command:

update uboot u-boot-1.3.0-95.bin

5. Reboot the warp and again halt the boot process when prompted.

6. Burn the fpga:

update fpga fpga3011.wrp -d tftp

7. Enter the following commands as follows:

setenv load_nand_kernel nand read.jffs2 0x02000000 0x00000000 0x00200000

saveenv

8. Reboot the warp and again halt the boot process when prompted.

9. Enter the following commands as follows. Select yes when prompted for confirmation. No need to reset after each image is burned. You can reboot at the end (Note: the image file names in this case may differ from the images your are upgrading) :

update kernel kernel-2.6.31.7-7.wrp -d tftp
update persistent persistent-2.2.2-3.wrp -d tftp
update persistent1 persistent1-2.2.2-3.wrp -d tftp
update persistent2 persistent2-2.2.2-3.wrp -d tftp
update ramdisk ramdisk-2.2.2-3.wrp -d tftp

10. Reboot the Warp and you should be ready to go!

/Adam

cincinatofurtado
06-01-10, 07:58 AM
Hi guys,

First, thank you all. Just for clarify I used a tftp server in my PC to update Warp and got the error. I didn't used USB nor SD card.

As I have some experience on u-boot , I thought the error was about image corruption, but I didn't knew why.

My first try was the command below, as suggested by user awayte:
# setenv load_nand_kernel nand read.jffs2 0x02000000 0x00000000 0x00200000

Then I saved with "saveenv" and re-updated. And it worked! Now I'm able to boot in Linux and will try further updates with the "autorun" mechanisms.

Again, thank you everyone.