[U-Boot] [PATCH v9 2/2] Odroid-XU3: Add documentation for Odroid-XU3

[Hyungwon Hwang]

On Thu, 27 Nov 2014 15:33:05 +0100
Sjoerd Simons <sjoerd.simons at collabora.co.uk> wrote:

> On Thu, 2014-11-27 at 22:21 +0900, Hyungwon Hwang wrote:
> > This patch adds documentation for Odroid-XU3. This documentation is
> > based on that of Odroid (doc/README-odroid) made by Przemyslaw
> > Marczak. The documentation includes basic information about boot
> > media layout, environment, partition layout, and the instruction to
> > burn the u-boot image to boot media.
> 
> >  4. Boot media layout
> >  ====================
> >  The table below shows SD/eMMC cards layout for U-boot.
> > @@ -35,18 +46,20 @@ The block offset is starting from 0 and the
> > block size is 512B. | Bl2       | 31   | 30   |  1 (boot) |
> >  | U-boot    | 63   | 62   |  1 (boot) |
> >  | Tzsw      | 2111 | 2110 |  1 (boot) |
> > -| Uboot Env | 2500 | 2500 |  0 (user) |
> > +| Uboot Env | 2560 | 2560 |  0 (user) |
> >   -------------------------------------
> 
> Where the previous values incorrect? Also this doesn't seem to match
> the hardkerel script which has:

This boot media layout is for x2/u3. I will update it in next version.

But the env offset is
#define CONFIG_ENV_OFFSET	(SZ_1K * 1280) /* 1.25 MiB offset */
as you can see in odroid.h and odroid_xu3.h.

CONFIG_ENV_OFFSET / 512 = 2560, not 2500.


> 
> signed_bl1_position=1
> bl2_position=31
> uboot_position=63
> tzsw_position=719
> env_position=1231
> 
> for the various locations.. Which also explains the limit 335872 bytes
> in your initial mail.. Awkward one though. Wonder if that's an SoC
> issue or something hardkernel could fix by having a different bl1/bl2?
> 

(719 - 63) * 512 = 335876 bytes. The limitation is needed not to
overwrite tzsw.

Are you saying that the limitation can be removed? Yes, with different
bl1/bl2. But I do not think that another bl1/bl2 will be released to
relieve the limitation.