[U-Boot] howto write uboot to nand
I thought I should ask before I screw this up. I have a new uboot that I load with kwboot. It works fine and I want to write it to nand. I see many references to write it after loading with tftp but not kwboot. Can I do this? How? This is to a Guruplug. Using tftp
tftp 0x6400000 u-boot.kwb nand erase 0x00000000 0x0100000 nand write 0x6400000 0x0000000 0x80000
Richard
On 06/28/2013 03:15:03 PM, kqt4at5v@gmail.com wrote:
I thought I should ask before I screw this up. I have a new uboot that I load with kwboot. It works fine and I want to write it to nand. I see many references to write it after loading with tftp but not kwboot. Can I do this? How? This is to a Guruplug. Using tftp
tftp 0x6400000 u-boot.kwb nand erase 0x00000000 0x0100000 nand write 0x6400000 0x0000000 0x80000
I'm not familiar with guruplug or kwboot (if you want an answer from someone who is, you should put it in the subject line) -- but assuming the image is supposed to be written to the beginning of NAND, the commands look good.
I'm curious why you erase 1 MiB but only write 512 KiB, though. Even if your erase block size really is that large, the "nand erase" command will round up (so you can use $filesize if you want).
-Scott
On Fri, Jun 28, 2013 at 03:15:03PM -0500, kqt4at5v@gmail.com wrote:
I thought I should ask before I screw this up. I have a new uboot that I load with kwboot. It works fine and I want to write it to nand. I see many references to write it after loading with tftp but not kwboot. Can I do this? How? This is to a Guruplug. Using tftp
tftp 0x6400000 u-boot.kwb nand erase 0x00000000 0x0100000 nand write 0x6400000 0x0000000 0x80000
Well, I typically use openocd and the jtag board to do the same thing. I'll use openocd to load and execute the new version of u-boot that I built, and then from that new u-boot, I'll transfer the .kwb image I want to burn to flash.
So, basically, you can just use tftp like you outlined above, but from the new image you loaded and executed via kwboot.
Ultimately, you're responsible if it breaks. No response here is going to mitigate that ;-)
hth,
Jason.
participants (3)
-
Jason Cooper -
kqt4at5v＠gmail.com -
Scott Wood