1,723
edits
m |
m |
||
Line 21: | Line 21: | ||
For information: ubi info (only works after the above "attach" command is issued) | For information: ubi info (only works after the above "attach" command is issued) | ||
...and another 2 hours of research after this, and no luck what so ever in figuring out why everyone on the planet says that something like "ubi part firmware2" will ''attach'' a UBI volume, when on the WRT32X Marvell version of U-Boot, it executes a complete "FDISK" (guess what the F stands for here), and wipes everything on the existing partition (checked it twice and it DOES hose the partition). | ...and another 2 hours of research after this, and no luck what so ever in figuring out why everyone on the planet says that something like "ubi part firmware2" will ''attach'' a UBI volume, when on the WRT32X Marvell version of U-Boot, it executes a complete "FDISK" (guess what the F stands for here), and wipes everything on the existing partition (checked it twice and it DOES hose the partition).<syntaxhighlight lang="text"> | ||
It does this; | |||
<br /> | Venom>> ubi part firmware2 | ||
Creating 1 MTD partitions on ... | |||
Instead of this; | |||
Venom>> ubi part firmware2 | |||
mtd: Giving out device 1 to mtd=5 | |||
ubi0: attaching mtd1 | |||
</syntaxhighlight>Maybe it isn't a UBI partition at this point because it has a SquashFS image there. Who know? Certainly not a web page publically accessible and apparently an OpenWRT secret. Am I cranky? Yup. This is what happens when smart people build things. They don't document it very well.<br /> | |||
===Environment Variables=== | ===Environment Variables=== | ||
Line 697: | Line 705: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Thanks to... === | ===Thanks to...=== | ||
https://github.com/ARM-software/u-boot/blob/master/doc/README.ubi | https://github.com/ARM-software/u-boot/blob/master/doc/README.ubi |