AW: AW: latest u-boot branch for Marvell Armada 88F3720

Fri Apr 3 16:33:04 CEST 2020

Hi Moritz,

On 03.04.20 16:25, Moritz Berghof wrote:
> Hi Stefan, Hi Marek
> 
> I got your U-Boot mainline booting on the ESPRESSObin. First Step is done.
> 
> Your are right Stefan, the SATA makes kind of Issues. With disabling it 
> is booting!

Okay, thanks for testing and reporting. But we should strive to fix
this SATA issue in mainline as well. If you find the time, it would be
great if you (or someone else) could dig into this and send a patch
to fix the real issue.

Thanks,
Stefan

> You guys done a great job, the mainline works with that little changes.
> 
> It tested for my need:
> 
> USB 2.0 and USB 3.0 --- works
> 
> If I will do further tests, I will commit.
> 
> Changes are:
> 
> diff --git a/arch/arm/dts/armada-3720-espressobin.dts 
> b/arch/arm/dts/armada-3720-espressobin.dts
> 
> index 84e2c2adba..f8701c0e87 100644
> 
> --- a/arch/arm/dts/armada-3720-espressobin.dts
> 
> +++ b/arch/arm/dts/armada-3720-espressobin.dts
> 
> @@ -106,9 +106,9 @@
> 
> };
> 
>   /* CON3 */
> 
> -&sata {
> 
> -       status = "okay";
> 
> -};
> 
> +//&sata {
> 
> +//     status = "okay";
> 
> +//};
> 
>   &spi0 {
> 
>          status = "okay";
> 
> I would make it clean and suggest a pull request, therefore we have a 
> base, everybody can work on.
> 
> The working boot-log is:
> 
>     DLL 0xc0001074NOTICE:  Booting Trusted Firmware
> 
> NOTICE:  BL1: v1.3(release):armada-17.10.8:34247e02
> 
> NOTICE:  BL1: Built : 10:52:47, Mar 31 2NOTICE:  BL2: 
> v1.3(release):armada-17.10
> 
> .8:34247e02
> 
> NOTICE:  BL2: Built : 10:52:48, Mar 31 2020
> 
> NNOTICE:  BL31: v1.3(release):armada-17.10.8:34247e02
> 
> NOTICE:  BL31:
> 
> U-Boot 2020.04-rc3-00188-g350c44dfb9-dirty (Apr 03 2020 - 12:28:10 +0200)
> 
> DRAM:  512 MiB
> 
> Comphy-0: USB3_HOST0    5 Gbps
> 
> Comphy-1: PEX0          2.5 Gbps
> 
> Comphy-2: SATA0         5 Gbps
> 
> PCIE-0: Link down
> 
> MMC:
> 
> Loading Environment from SPI Flash... SF: Detected w25q32dw with page 
> size 256 Bytes, erase size 4 KiB, total 4 MiB
> 
> OK
> 
> Model: Marvell Armada 3720 Community Board ESPRESSOBin
> 
> Net:   No ethernet found.
> 
> Hit any key to stop autoboot:  0
> 
> Unknown command 'tftp' - try 'help'
> 
> Unknown command 'tftp' - try 'help'
> 
> Bad Linux ARM64 Image magic!
> 
> Thank you very much, have a great weekend,
> 
> --
> 
> Moritz Berghof
> 
> Software Engineer
> 
> Tel. +49 30 921028-209 <tel:+49%C2%A030%C2%A0921028-204>
> 
> Fax +49 30 921028-020 <tel:+49%C2%A030%C2%A0921028-020>
> 
> mberghof at phoenixcontact.com <mailto:mberghof at phoenixcontact.com>
> 
> www.phoenixcontact.com <http://www.phoenixcontact.com/>
> 
> PHOENIX CONTACT Cyber Security GmbH
> 
> Richard-Willstätter-Straße 6 <x-apple-data-detectors://1/1>
> D-12489 Berlin <x-apple-data-detectors://1/1>
> 
> Register Court: AG Charlottenburg, HR B 202908
> Geschäftsführer/General Manager: Kilian Golm
> 
> --
> 
> On Thu, 2 Apr 2020 14:18:24 +0200
> 
> Stefan Roese <sr at denx.de <https://lists.denx.de/listinfo/u-boot>> wrote:
> 
>>/Hi Moritz,/
> 
>>//
> 
>>/On 02.04.20 13:30, Moritz Berghof wrote:/
> 
>>/> it's really great that you answered so fast and helpfully, thank you!/
> 
>>/> /
> 
>>/> It's great you want get the board ported to mainline. Me too./
> 
>>/> /
> 
>>/> /
> 
>>/> I build the U-boot mainline and uploaded on my espressobin. Used the ATF/
> 
>>/> and WTMI from Marvell./
> 
>>/> /
> 
>>/> When I start the flashed .bin file, the U-boot crashed at this following/
> 
>>/> point. "Synchronous Abort" handler, esr 0x96000210 /
> 
>>//
> 
>>/Looks like an issue with SATA - not sure why. You might want to try to/
> 
>>/disable SATA / AHCI for testing./
> 
>>//
> 
>>/> Prompt is attached at this mail./
> 
>>/> /
> 
>>/> I think there is a problem with the RAM. For example, I build the U-Boot/
> 
>>/> for 1 GB RAM with the Marvell U-boot and the mainline/master. Important/
> 
>>/> constant is DDR_TOPOLOGY=2/
> 
>>/> /
> 
>>/> make DEBUG=0 USE_COHERENT_MEM=0 LOG_LEVEL=20 SECURE=0 
> CLOCKSPRESET=CPU_1000_DDR_800 DDR_TOPOLOGY=2 WTP=... BOOTDEV=SPINOR 
> PARTNUM=0 PLAT=a3700 all fip/
> 
>>/> /
> 
>>/> But when the u-boot mainline starts it promts:/
> 
>>/> U-Boot 2020.04-rc3-00188-g350c44dfb9 (Mar 31 2020 - 10:52:01 +0200)/
> 
>>/> /
> 
>>/> DRAM:  512 MiB/
> 
>>/> /
> 
>>/> /
> 
>>/> The Marvell U-boot promts DRAM: 1 GiB/
> 
>>/> /
> 
>>/> /
> 
>>/> /
> 
>>/> So my question is, where do you define the RAM Size? /
> 
>>//
> 
>>/Take a look at arch/arm/mach-mvebu/arm64-common.c. Perhaps this code/
> 
>>/needs some changes for CONFIG_ARMADA_A3700 similar to what is done/
> 
>>/for CONFIG_ARMADA_8K ?/
> 
>>//
> 
>>/I suggest you debug in this area a bit to see, where it goes wrong./
> 
> There is a register on A3720 which should contain information about how
> 
> much RAM the system has (0xD0000200 if the device contains only one
> 
> DDR chip). It is written by the TIM image. I am going to send a patch
> 
> which uses this register to determine RAM size for Turris Mox.
> 
> The thing is that without upgrade of TIM header some Moxes may report
> 
> 1 GB RAM in this register, although they only have 512 MB. So a call to
> 
> get_ram_size will still be needed.
> 
> Marek
> 
> .......................................................................................
> 
> PHOENIX CONTACT Cyber Security GmbH　
> 
> Richard-Willstätter-Straße 6 　
> 
> D-12489 Berlin 　
> 
> 　
> 
> Register Court: AG Charlottenburg, HR B 202908　
> 
> Geschäftsführer/General Manager: Kilian Golm
> 
> //

Viele Grüße,
Stefan

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr at denx.de