Bad block inside kernel nand mapping
xiangfu at sharism.cc
Wed May 12 22:01:13 EDT 2010
On 05/12/2010 01:56 AM, Kristoffer Ericson wrote:
> Thought that I would give the debian release a try and tried
> to reflash my device.
> I ended up having great difficulty getting this to work. First off
> the bootloader flashing didnt work so I redid it about 7-8 times
> before it seemed to work.
> When I try to flash the kernel It gives me at the end
> "Skip a old bad block!" and while the bootloader loads the
> kernel it reacts at the bad CRC.
> Ive made sure to erase the nand before writing, both by myself
> and using scripts. Ive tried several kernels without success and
> I always get exact same error.
> So, as far as I can understand I would need to :
> 1) change u-boot to ignore bad CRC
maybe it's not good. u-boot use CRC to check the kernel image.
> 2) map kernel area somewhere else
yes. we can map the kernel to offset 1M ~ 6M, but we need change the u-boot source code.
for example change the kernel to 1M offset:
#define CONFIG_BOOTCOMMAND "nand read 0x80600000 0x400000 0x200000;bootm"
#define CONFIG_BOOTCOMMAND "nand read 0x80600000 0x100000 0x200000;bootm"
change the flash command to:
sudo usbboot -c "boot;nprog 256 openwrt-xburst-uImage.bin 0 0 -n"
> Any ideas on what I might have missed? Ive done all the
if there is bad block. bootloader and usbboot will take care of it.
we need find out if there is a bug in u-boot or usbboot.
make sure the "NAND_FORCEERASE" is "1" in /etc/xburst-tools/usbboot.cfg
is there any bad block message when you flash the bootloader?
can you send the all flash output to me.
> change cable, change usb port, restart and so on.
> Best wishes
More information about the discussion