From mboxrd@z Thu Jan 1 00:00:00 1970 From: Przemyslaw Marczak Date: Thu, 07 Apr 2016 12:20:06 +0200 Subject: [U-Boot] Mainline u-boot installation on Odroid-UX4 In-Reply-To: <20160407093534.GC4022@tiger> References: <20160407093534.GC4022@tiger> Message-ID: <57063456.1040800@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 Hello Shawn. On 04/07/2016 11:35 AM, Shawn Guo wrote: > Hi Przemyslaw, Anand, > > I just got a Odroid-UX4 board to play. I installed firmware (bl1, bl2, > tzsw, u-boot) from hardkernel using sd_fusing.sh, and the board boots > fine. But when I install mainline u-boot v2016.03 by following > doc/README.odroid, the board refuses to boot with nothing appearing on > serial console. > > Here is what I did: > > - make odroid-xu3_defconfig > - make (using arm-linux-gnueabi-gcc 4.7.3) > - copy u-boot.bin (which is same as u-boot-dtb.bin in v2016.03 release) > to sd_fuse/hardkernel folder, and modify sd_fusing.sh to get it point > to this new U-Boot > - ./sd_fusing.sh /dev/sdX to flash the SD card We can assume, that the aboce steps are ok. > > One thing I'm not sure is the offset that firmware should be installed > to SD card. The doc/README.odroid and hardkernel sd_fusing.sh tells > different ones. > > doc/README.odroid: > > ------------------------------------- > | Binary | Block offset| part type | > | name | SD | eMMC |(eMMC only)| > ------------------------------------- > | Bl1 | 1 | 0 | 1 (boot) | > | Bl2 | 31 | 30 | 1 (boot) | > | U-Boot | 63 | 62 | 1 (boot) | > | Tzsw | 2111 | 2110 | 1 (boot) | > | Uboot Env | 2560 | 2560 | 0 (user) | > ------------------------------------- > > sd_fusing.sh: > > signed_bl1_position=1 > bl2_position=31 > uboot_position=63 > tzsw_position=719 > env_position=1231 > > I tried both sets, and neither works for me. > > I know Odroid-UX4 is supported by mainline U-Boot today, so there must > be something missing from my setup. Could you please help me here? > Thanks. > > Shawn > > There were two variants of boot chain with U-Boot for XU3/XU4, which differs in U-Boot size - originally U-Boot was 328K, but for the mainline we assume 1MB of size. So for mainline, you need a prober version of BL2, which loads 1MB of U-Boot instead of 328K - in other way, the mainline U-Boot will be overwritten by tzsw and env. Please use the resources from this site: https://github.com/hardkernel/u-boot/tree/odroidxu3-v2012.07/sd_fuse/hardkernel_1mb_uboot In sd_fuse.1M.sh, you can see, that for U-Boot area we have: 2111-63 == 2048blk == 1MB. And of course change the U-Boot to mainline. Best regards, -- Przemyslaw Marczak Samsung R&D Institute Poland Samsung Electronics p.marczak at samsung.com