Yes, right. Like below. U-Boot> fdt addr 0x100 libfdt fdt_check_header(): FDT_ERR_BADMAGIC
_Swami On Fri, May 6, 2016 at 7:28 AM, Swami <s.swa...@gmail.com> wrote: > oh okay. Thanks for the info. I remember getting the same BAD MAGIC error, > if I am not wrong. But, will confirm it in a moment. > > _Swami > > On Fri, May 6, 2016 at 7:20 AM, Oliver Grawert <o...@ubuntu.com> wrote: > >> Am Freitag, den 06.05.2016, 07:11 -0700 schrieb Swami: >> > Got it Oliver. But, I didn't modify anything in uboot.env.in and is >> > same as given from [1] and have copied it to [2]. The printenv after >> > loading others during uboot is showing this loadfdt though. Have put >> > the printenv during this time @ [3]. Do I need to have >> > snappy-system.txt as per your blog[4], as I don't see any file like >> > that from the boot-assets code retrieved from [1]. >> > >> > >> > >> > >> > [1] https://code.launchpad.net/~snappy-dev/snappy-hub/snappy-systems >> > >> > [2] http://paste.ubuntu.com/16259368/ >> > [3] http://paste.ubuntu.com/16259410/ >> > [4] >> > >> https://ograblog.wordpress.com/2015/01/25/porting-ubuntu-snappy-to-a-yet-unsupported-armhf-board/ >> > >> >> snappy-system-txt is long obsolete (even in 15.04 which we also do not >> actively touch any more) ... what happens if you run: >> >> fdt addr 0x100 >> >> at the u-boot prompt in [3] ? >> >> ciao >> oli >> > >
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
