Skip to contentSkip to conversation

Addition of new board Peach-Pi

PATCH New Simon Glass 1 participant 2 messages Oct 10, 2014 – Oct 14, 2014 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 1298874295.477681412941824708.JavaMail.weblogic@epmlwas03d

#1 lore raw

cover Addition of new board Peach-Pi

Hi Akshay,

Quoted 22 lines · Akshay Saraswat

Hi Simon,

Quoted 15 lines

Hi Akshay,

Quoted 11 lines · Akshay Saraswat

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

Quoted 4 lines
Quoted 2 lines

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

Quoted 8 lines

Few patches got merged after I posted this patch-set. I will Rebase it.

Quoted 2 lines

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.

OK, it doesn't work on SD for me either. I think the best thing is to wait until you rebase and retest the patches then I'll try again.

Quoted 3 lines

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.

I am using crosfw which automates most of that (crosfw -b peach_pi) but I have had to change it to support pi (to use exynos5800 instead of exynos5420). I'll be away for a week but will take a look when I get back.

Quoted 5 lines

BL1 that I used has the following md5 sum -
23b60e72992d839195d48335865dbabb

Quoted 1 line

option though.

I'm pretty sure it is getting to BL2 since it says that PSHOLD is enabled.

Regards,
Simon

#2 lore raw

cover Addition of new board Peach-Pi

In reply to a message not in the archive

Hi Akshay,

Quoted 31 lines · Akshay Saraswat

Hi Simon,

Quoted 15 lines

Hi Akshay,

Quoted 11 lines · Akshay Saraswat

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

Quoted 4 lines
Quoted 2 lines

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.

Quoted 2 lines

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.

Quoted 6 lines

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