Changes in 1:
# ifdef CONFIG_SYS_BOOT_NAND
# define CONFIG_MFG_NAND_PARTITION "mtdparts=gpmi - nand: 2 m (boot), and 128 k (env), 8 m (kernel), and 128 k (DTB), - (rootfs)"
/* # define CONFIG_MFG_NAND_PARTITION "mtdparts=gpmi - nand: 5 m (boot), 1 m (env), 10 m (kernel), 1 m (DTB), - (rootfs)" */
Changes in 2:
# if defined (CONFIG_SYS_BOOT_NAND)
# define CONFIG_NAND_MTDPARTS "gpmi - nand: 2 m (boot), and 128 k (env), 8 m (kernel), and 128 k (DTB), - (rootfs)"
/* # define CONFIG_NAND_MTDPARTS "gpmi - nand: 5 m (boot), 1 m (env), 10 m (kernel), 1 m (DTB), - (rootfs)" */
Changes in 3:
/*
# the else
# define CONFIG_BOOTCOMMAND \
Nand read "${loadaddr} 0 x600000 0 xa00000;" \
Nand read "${fdt_addr} 0 x1000000 0 x100000;" \
"Bootz ${loadaddr} - ${fdt_addr}"
# endif
*/
# the else
# define CONFIG_BOOTCOMMAND \
Nand read "${loadaddr} 0 x220000 0 x800000;" \
Nand read "${fdt_addr} 0 xa20000 0 x20000;" \
"Bootz ${loadaddr} - ${fdt_addr}"
Changes in 4:
# elif defined (CONFIG_ENV_IS_IN_NAND)
# undef CONFIG_ENV_SIZE
/*
# define CONFIG_ENV_OFFSET (5 & lt; <20)
# define CONFIG_ENV_SECT_SIZE (1 & lt; <20)
*/
# define CONFIG_ENV_OFFSET (2 & lt; <20)
# define CONFIG_ENV_SECT_SIZE (1 & lt; <17)
Then use mfgtool download tool, replace the firmware and the file under uboot. Took imx
Update download every error:
MTD: the opened '/dev/mtd0' - '(null)'
MTD: bootstream too large
Mtd_init failed!
CodePudding user response:
This kind of circumstance needs to locate, suggest don't change so many parameters, every change a part of the test, so you can find out the problem, I use the Beijing newsletter for 6 ull terminator development board, mfgtool burning question, also has appeared at that time because copies of the file is not complete,You this hint 'MTD: bootstream too large,' is clearly beyond the scope of the, make dot try, or widen the space,
CodePudding user response:
I'm kangkang..CodePudding user response:
Per the uboot mfgtools used for burning inside ram should be changed, you give you to modify partitions, mfgtools, there is a partition script mfgtools principle is:1, through usb burning ram the uboot version and image
2, boot in ram system,
3, according to the script partitioning
4, through fastboot (or the like) should remember this way, the uboot burning into 0 x1000 seems to be the position (a) - this is you want to change
5, the kernel burning boot partition (emmc boot partition, this is a physical good, emmc factory generally have)
6, burning burning file system
7, finished work
Specific steps should have an XML file, to learn myself
CodePudding user response:
https://blog.csdn.net/mack_liu/article/details/106658151