[U-Boot] [PATCH 0/6] Addition of new board Peach-Pi

Simon Glass sjg at chromium.org
Tue Oct 14 06:22:10 CEST 2014


Hi Akshay,


On 10 October 2014 05:50, Akshay Saraswat <akshay.s at samsung.com> wrote:
>
> Hi Simon,
>
> >
> >Hi Akshay,
> >
> >On 8 October 2014 02:10, Akshay Saraswat wrote:
> >> Now we are adding a new Peach-Pi board which is a variant of Peach-Pit
> >> and is based on Exynos5800. Exynos5800 itself is a variant of Exynos5420,
> >> hence, most of the hardware config and settings are reused for this board.
> >>
> >> Akshay Saraswat (5):
> >>   Exynos5800: Introduce new proid for Exynos5800
> >>   Exynos5800: Add DTS for new board Peach-Pi
> >>   Config: Exynos5800: Enable build for Peach-Pi
> >>   Config: Exynos5420: Refactor SDRAM Bank and Size
> >>   Exynos5: ddr3: Choose between single or double channel config
> >>
> >> Alim Akhtar (1):
> >>   DMC: Exynos5: Enable update mode for DREX controller
> >
> >I was not able to apply this to samsung/master. I fiddled a bit and
>
> Few patches got merged after I posted this patch-set. I will Rebase it.
>
> >got it to build (see u-boot-x86.git branch pi-working) but it would
> >not boot over USB A-A. It hung in SPL. I may have used an incorrect
>
> I don't have the SMDK for Exynos5800 and my cros_write_firmware always fails to boot through USB.
> I tested these patches with SD boot only.
>
> I could not find any difference between Pit and Pi. If Pit boots via USB then Pi should also boot.
> Plus, for both USB boot and SD boot, path is same till the point where it starts loading U-Boot.
> Please help me and let me know the steps for cros_write_firmware. I'll debug and post new patches.
>
> BL1 that I used has the following md5 sum -
> 23b60e72992d839195d48335865dbabb

Ah, mine is c33215481b579405fafb579e323b4a74 - I wonder if that is the
problem? Where is this file available?

Regards,
Simon


More information about the U-Boot mailing list