Changes between Version 5 and Version 6 of linux/ubi

Timestamp:

10/01/2018 04:33:48 PM (6 years ago)

Author:

Cale Collins

Comment:

added clarity to On a target board with NAND FLASH

linux/ubi

@@ -212 +212 @@
 === On a target board with NAND FLASH ===
 [=#ubiontarget]
-To extract or manipulate the contents of a UBI within the NAND Flash of a Linux system, Linux must be booted from a secondary medium on a device with NAND FLASH and without the NAND FLASH partition being mounted.
+To extract or manipulate the contents of a UBI within the NAND Flash of a Linux system, Linux must be booted from a secondary medium without the NAND FLASH partition being mounted.
 
 The following examples assume that UBI has been configured to use the 3rd (zero based) MTD FLASH partition ({{{ubi.mtd=2}}} kernel command line) as we typically use the {{{mtdparts=nand:16m(uboot),1m(env),-(rootfs)}}} env variable in U-Boot to dynamically modify the Linux Device-Tree to partition the NAND flash device into 3 partitions: bootloader, bootloader-env, and rootfs. Thus the bootloader is {{{/dev/mtd0}}}, the bootloader env is {{{/dev/mtd1}}}, and the rootfs is {{{/dev/mtd2}}}.
@@ -249 +249 @@
 umount /mnt/ubi # unmount filesystem
 }}}
-
+Troubleshooting:
+
+The output beneath indicates that /dev/mtd2 is not attached and you may proceed with manipulating the NAND flash.
+{{{#!bash
+root@OpenWrt:/# ubidetach /dev/ubi_ctrl -m 2
+ubidetach: error!: cannot detach mtd2
+           error 16 (Resource busy)
+}}}
 
 == Working with UBI in U-boot Bootloader ==