From mboxrd@z Thu Jan 1 00:00:00 1970 From: rosysong at rosinson.com Date: Wed, 20 Feb 2019 10:16:51 +0800 Subject: [U-Boot] Kernel hang when replace older uboot with uboot master V2 References: <2019021917305692094016@rosinson.com>, <20190219103729.2cba8561@jawa>, <2019021917451193905118@rosinson.com>, <20190219114903.66ed8250@jawa> Message-ID: <201902201016506560860@rosinson.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de My old u-boot is 1.1.4 On Tue, 19 Feb 2019 17:45:12 +0800 "rosysong at rosinson.com" wrote:   > Thanks for your reply, but this firmware can find the rootfs itself,  > > >[    0.337492] 5 fixed-partitions partitions found on MTD device > >spi0.0 [    0.344060] Creating 5 MTD partitions on "spi0.0": > >[    0.349014] 0x000000000000-0x000000040000 : "u-boot" > >[    0.354834] 0x000000040000-0x000000050000 : "u-boot-env" > >[    0.360944] 0x000000050000-0x000000060000 : "factory" > >[    0.366831] 0x000000060000-0x000000fe0000 : "firmware" > >[    0.374973] 2 uimage-fw partitions found on MTD device firmware > >[    0.381090] Creating 2 MTD partitions on "firmware": > >[    0.386258] 0x000000000000-0x000000190000 : "kernel" > >[    0.392027] 0x000000190000-0x000000f80000 : "rootfs" > >[    0.397783] mtd: device 5 (rootfs) set to be root filesystem  >   This is too late - as this is the MTD partition info provided from kernel's DTB.   You need the root= information which is probably available on your environment (not accessible by some reason from new u-boot).   BTW: What is the version of old u-boot ?     Best regards,   Lukasz Majewski   --   DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de