Editing Linuxstamp II 9260
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 133: | Line 133: | ||
> '''nand help''' | > '''nand help''' | ||
So if to update the kernel, you must first be able to load the uImage into ram. This is normally done from tftpboot, with something like: | So if to update the kernel, you must first be able to load the uImage into ram. This is normally done from tftpboot, with something like: | ||
− | > '''tftpboot 0x20800000 uImage.9g20r5''' | + | > '''tftpboot 0x20800000 uImage.9g20r5''' where 0x20800000 is the ram address, and uImage.9g20r5 is the file name on the tftp server. |
− | + | Now you need to erase the kernel block. This is necessary because a NAND write by itself can only switch bits to 0's: | |
− | > '''nand erase 0xa0000 0x200000''' | + | > '''nand erase 0xa0000 0x200000''' where 0xa0000 is the offset and 0x200000 is the length |
− | + | Now the new kernel can be written: | |
− | > '''nand write 0x20800000 0xa0000 0x200000''' | + | > '''nand write 0x20800000 0xa0000 0x200000''' where 0xa0000 is the offset and 0x200000 is the length |
− | |||
== License == | == License == |