From mboxrd@z Thu Jan 1 00:00:00 1970 From: Przemyslaw Marczak Date: Thu, 17 Jul 2014 17:00:04 +0200 Subject: [U-Boot] uboot/odroid test report In-Reply-To: References: <53C7C8E0.8050400@samsung.com> Message-ID: <53C7E4F4.6010309@samsung.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 07/17/2014 04:30 PM, Daniel Drake wrote: > On Thu, Jul 17, 2014 at 2:38 PM, Daniel Drake wrote: >> I'm getting some new errors though, and my initramfs fails to switch >> to real root, I'll get back to you with more details if this is >> something other than a problem this side. > > Silly error this side. Now things are fine. Thanks, great work! > > I'm still curious to understand how this SPL/BL2 thing works, given > that with our setup it is basically running the first 14kb of an old > uboot version during early boot? If either of you know.. Please look into my first reply. > > Also, I didn't manage to get the initramfs to be loaded in the v5 > patch, which does: > > setenv image_addr ${kerneladdr} - ${fdtaddr} > bootz ${image_addr} ${ramdisk_addr} > > Guessing, but I think the problem here is that we end up passing 4 > args to bootz, which is not how it is documented. Instead the ramdisk > addr should be passed where the - is in image_addr. > > Daniel > I will check it tomorrow but it has works on Ubuntu. The bootz command takes only 2 arguments here -> ${image_addr} ${ramdisk_addr} which are the numbers set by: "run check_dtb" and "run check_ramdisk" Thank you, -- Przemyslaw Marczak Samsung R&D Institute Poland Samsung Electronics p.marczak at samsung.com