latest u-boot branch for Marvell Armada 88F3720

latest u-boot branch for Marvell Armada 88F3720

[Moritz Berghof]

Dear U-Boot developers,

My Name is Moritz and we evaluate the Marvell Armada 88F3720 on the Marvell ESPRESSObin and the TURRIS MOX.

Does someone know, where is the actual or latest u-boot branch for Marvell Armada 88F3720 placed? At the u-boot master or a marvell custodian tree or somewhere else? Does Marvell develop u-boot still for their Armada 88F3720 and when yes, where?

Because that https://github.com/MarvellEmbeddedProcessors/u-boot-marvell, which is well used on the ESPRESSObin is NOT up-to-date. 4 Years ago, last commit.

I'm searching an actual u-boot platform for my Chip.


I look forward to your reply, thank you very much,

--
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@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


.......................................................................................
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

latest u-boot branch for Marvell Armada 88F3720

[Stefan Roese]

Hi Moritz,

On 25.03.20 16:05, Moritz Berghof wrote:
> My Name is Moritz and we evaluate the Marvell Armada 88F3720
> on the Marvell ESPRESSObin and the TURRIS MOX.
> 
> Does someone know, where is the actual or latest u-boot branch
> for Marvell Armada 88F3720 placed? At the u-boot master or a
> marvell custodian tree or somewhere else? Does Marvell develop
> u-boot still for their Armada 88F3720 and when yes, where?

Those boards are supported in general in mainline U-Boot. Though I
have to admit, that I didn't test any of those ports recently. I
added Marek Behun to Cc, as he did submit most of the Turris Mox
stuff and has more recent experience than I do.

> Because that https://github.com/MarvellEmbeddedProcessors/u-boot-marvell,
> which is well used on the ESPRESSObin is NOT up-to-date. 4 Years ago,
> last commit.

I just took a quick glance at this repo and there are newer, more
recent branches, e.g. "u-boot-2018.03-armada-18.12". But still, this
is far away from mainline, I agree.

Perhaps someone else (Marek) can comment on the current status of
mainline U-Boot on those boards? Is something missing? If yes, it
would be great to get it ported to mainline.

Thanks,
Stefan

> I'm searching an actual u-boot platform for my Chip.
> 
> 
> I look forward to your reply, thank you very much,
> 
> --
> 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@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
> 
> 
> .......................................................................................
> 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
> 

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

Hi,

mainline U-Boot should work for Armada 3720, although I haven't tested
recent master (so I don't know if there are some regressions). But
Turris Mox uses cca 1 year old upstream with just few Mox specific
patches atop (which I plan to get merged soon). You can find it here:
https://gitlab.labs.nic.cz/turris/mox-u-boot

One thing that may need reworking (to become compatible with Linux) is
the comphy driver. Linux' comphy driver for this SOC uses smccc calls
to ARM Trusted Firmware, but U-Boot does not, and instead initializes
SERDESes on its own.

Bear in mind that U-Boot is not enough for booting Armada 3720 SOC. You
do also need ARM Trusted Firmware (you don't need to use Marvell's
ATF, since their patches are merged into upstream ATF), and you also
need firmware for the secure Cortex-M3 processor (Marvell's name for
this firmware is WTMI), which does DDR training. Marvell has this in
A3700-utils-marvell repository. For Turris MOX, we build all of this via
https://gitlab.labs.nic.cz/turris/mox-boot-builder
but this code can be MOX specific, so if you want to use it for other
boards, I can provide more explanation of which does what and so on.

Marek

On Wed, 25 Mar 2020 17:44:57 +0100
Stefan Roese <sr@denx.de> wrote:

> Hi Moritz,
> 
> On 25.03.20 16:05, Moritz Berghof wrote:
> > My Name is Moritz and we evaluate the Marvell Armada 88F3720
> > on the Marvell ESPRESSObin and the TURRIS MOX.
> > 
> > Does someone know, where is the actual or latest u-boot branch
> > for Marvell Armada 88F3720 placed? At the u-boot master or a
> > marvell custodian tree or somewhere else? Does Marvell develop
> > u-boot still for their Armada 88F3720 and when yes, where?  
> 
> Those boards are supported in general in mainline U-Boot. Though I
> have to admit, that I didn't test any of those ports recently. I
> added Marek Behun to Cc, as he did submit most of the Turris Mox
> stuff and has more recent experience than I do.
> 
> > Because that https://github.com/MarvellEmbeddedProcessors/u-boot-marvell,
> > which is well used on the ESPRESSObin is NOT up-to-date. 4 Years ago,
> > last commit.  
> 
> I just took a quick glance at this repo and there are newer, more
> recent branches, e.g. "u-boot-2018.03-armada-18.12". But still, this
> is far away from mainline, I agree.
> 
> Perhaps someone else (Marek) can comment on the current status of
> mainline U-Boot on those boards? Is something missing? If yes, it
> would be great to get it ported to mainline.
> 
> Thanks,
> Stefan
> 
> > I'm searching an actual u-boot platform for my Chip.
> > 
> > 
> > I look forward to your reply, thank you very much,
> > 
> > --
> > 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@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
> > 
> > 
> > .......................................................................................
> > 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
> >   

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

On Wed, 25 Mar 2020 18:48:50 +0100
Marek Behun <marek.behun@nic.cz> wrote:

> One thing that may need reworking (to become compatible with Linux) is
> the comphy driver. Linux' comphy driver for this SOC uses smccc calls
> to ARM Trusted Firmware, but U-Boot does not, and instead initializes
> SERDESes on its own.

By this I mean that it works in U-Boot, but the driver should be
rewritten to at least have the same DTS bindings as Linux.

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

[Moritz Berghof]

Hey Marek, Hi Stefan,


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 

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?

At armada-3720-espressobin.dts i expanded the memory size. No success. 
At mvebu_armada-37xx.h I expand the RAM for two banks. No success.

Or do you see there other problems by starting the mainline? 


Thanks,


--
Moritz Berghof
Software Engineering
Tel.?+49?30?921028-209 
Fax?+49?30?921028-020
mberghof at phoenixcontact.com
www.phoenixcontact.com
?
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

-----Urspr?ngliche Nachricht-----
Von: Marek Behun <marek.behun@nic.cz> 
Gesendet: Mittwoch, 25. M?rz 2020 18:49
An: stefan roese <sr@denx.de>
Cc: Moritz Berghof <mberghof@phoenixcontact.com>; u-boot mailing list <u-boot@lists.denx.de>
Betreff: Re: latest u-boot branch for Marvell Armada 88F3720

***External email! Do not click links or open attachments unless you recognize the sender and know the content is safe.***

Hi,

mainline U-Boot should work for Armada 3720, although I haven't tested recent master (so I don't know if there are some regressions). But Turris Mox uses cca 1 year old upstream with just few Mox specific patches atop (which I plan to get merged soon). You can find it here:
https://gitlab.labs.nic.cz/turris/mox-u-boot

One thing that may need reworking (to become compatible with Linux) is the comphy driver. Linux' comphy driver for this SOC uses smccc calls to ARM Trusted Firmware, but U-Boot does not, and instead initializes SERDESes on its own.

Bear in mind that U-Boot is not enough for booting Armada 3720 SOC. You do also need ARM Trusted Firmware (you don't need to use Marvell's ATF, since their patches are merged into upstream ATF), and you also need firmware for the secure Cortex-M3 processor (Marvell's name for this firmware is WTMI), which does DDR training. Marvell has this in A3700-utils-marvell repository. For Turris MOX, we build all of this via https://gitlab.labs.nic.cz/turris/mox-boot-builder
but this code can be MOX specific, so if you want to use it for other boards, I can provide more explanation of which does what and so on.

Marek

On Wed, 25 Mar 2020 17:44:57 +0100
Stefan Roese <sr@denx.de> wrote:

> Hi Moritz,
>
> On 25.03.20 16:05, Moritz Berghof wrote:
> > My Name is Moritz and we evaluate the Marvell Armada 88F3720 on the 
> > Marvell ESPRESSObin and the TURRIS MOX.
> >
> > Does someone know, where is the actual or latest u-boot branch for 
> > Marvell Armada 88F3720 placed? At the u-boot master or a marvell 
> > custodian tree or somewhere else? Does Marvell develop u-boot still 
> > for their Armada 88F3720 and when yes, where?
>
> Those boards are supported in general in mainline U-Boot. Though I 
> have to admit, that I didn't test any of those ports recently. I added 
> Marek Behun to Cc, as he did submit most of the Turris Mox stuff and 
> has more recent experience than I do.
>
> > Because that 
> > https://github.com/MarvellEmbeddedProcessors/u-boot-marvell,
> > which is well used on the ESPRESSObin is NOT up-to-date. 4 Years 
> > ago, last commit.
>
> I just took a quick glance at this repo and there are newer, more 
> recent branches, e.g. "u-boot-2018.03-armada-18.12". But still, this 
> is far away from mainline, I agree.
>
> Perhaps someone else (Marek) can comment on the current status of 
> mainline U-Boot on those boards? Is something missing? If yes, it 
> would be great to get it ported to mainline.
>
> Thanks,
> Stefan
>
> > I'm searching an actual u-boot platform for my Chip.
> >
> >
> > I look forward to your reply, thank you very much,
> >
> > --
> > 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@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
> >
> >
> > .......................................................................................
> > 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
> >


.......................................................................................
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Crashed_u-boot_mainline
Type: application/octet-stream
Size: 1510 bytes
Desc: Crashed_u-boot_mainline
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200402/4c1f3ee7/attachment.obj>

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

[Stefan Roese]

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.

> At armada-3720-espressobin.dts i expanded the memory size. No success.
> At mvebu_armada-37xx.h I expand the RAM for two banks. No success.
> 
> Or do you see there other problems by starting the mainline?

Thanks,
Stefan

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

On Thu, 2 Apr 2020 14:18:24 +0200
Stefan Roese <sr@denx.de> 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

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

Hi Moritz,

which version of EspressoBin do you have? How much RAM, is it DDR3 or
DDR4? How many RAM chips are there?

Marek

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

[Moritz Berghof]

Hi Marek,

we use the ESPRESSObin Version V5_0_1. We have 2GB-DDR3 memory size and two chips. On of the one side and the other chip directly on the other side of the board.

Have a good day,

--
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@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

Hi Moritz,

which version of EspressoBin do you have? How much RAM, is it DDR3 or
DDR4? How many RAM chips are there?

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

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

Hi Moritz,

could you please compile and test current u-boot master on your
EspressoBin? My patches regarding DDR size determination on A3700 were
applied and I would like to know if it works correctly for you.

Marek

On Mon, 6 Apr 2020 09:43:27 +0000
Moritz Berghof <mberghof@phoenixcontact.com> wrote:

> Hi Marek,
> 
> we use the ESPRESSObin Version V5_0_1. We have 2GB-DDR3 memory size and two chips. On of the one side and the other chip directly on the other side of the board.
> 
> Have a good day,
> 
> --
> 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@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
> 
> Hi Moritz,
> 
> which version of EspressoBin do you have? How much RAM, is it DDR3 or
> DDR4? How many RAM chips are there?
> 
> 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

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

[Moritz Berghof]

Hi Marek,

sorry i'm not that fast. Different things around.

I tested the u-boot master with your patches. But it crashed on my espressobin, unfortunately. 

Log:

DLL 0xc0001050[29:24]: [5,32,1b]
   DLL 0xc0001054[21:16]: [4,2b,17]
   DLL 0xc0001054[29:24]: [a,35,1f]
   DLL 0xc0001074[21:16]: [0,3f,1f]
   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-00490-ge4837da782 (Apr 21 2020 - 12:06:24 +0200)

DRAM:  1 GiB
Comphy-0: UNCONNECTED   2.5 Gbps  
Comphy-1: UNCONNECTED   5 Gbps    
Comphy-2: SATA0         5 Gbps    
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs 
"Synchronous Abort" handler, esr 0x96000210
elr: 0000000000028afc lr : 0000000000028acc (reloc)
elr: 000000003ff6aafc lr : 000000003ff6aacc
x0 : 00000000d0074000 x1 : 0000000000000000
x2 : 0000000000000008 x3 : 0000000000000000
x4 : 0000000000000018 x5 : 0000000000000000
x6 : 000000003fb2f440 x7 : 00000000ffffffe0
x8 : 000000003fb2f640 x9 : 0000000000000008
x10: 0000000000000abc x11: 000000003fb2f23c
x12: 0000000000000a2b x13: 0000000000000a20
x14: 0000000000000000 x15: 000000003fb2f640
x16: 000000003ffc7f41 x17: 000000003ffc7f41
x18: 000000003fb31de0 x19: 000000003fb33aa0
x20: 000000003fb33880 x21: 000000003ffd2800
x22: 0000000000000000 x23: 0000000000000000
x24: 0000000000000000 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 000000003fb2f540

Code: 91406000 b9000001 f9400260 91401000 (b9480001) 
Resetting CPU ...

resetting ...





Even when I disable the sata device at the espressobin .dts, the actuall master crashs.

Log:

DLL 0xc0001050[29:24]: [5,32,1b]
   DLL 0xc0001054[21:16]: [4,2b,17]
   DLL 0xc0001054[29:24]: [a,35,1f]
   DLL 0xc0001074[21:16]: [0,3f,1f]
   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-00490-ge4837da782 (Apr 21 2020 - 12:06:24 +0200)

DRAM:  1 GiB
Comphy-0: UNCONNECTED   2.5 Gbps  
Comphy-1: UNCONNECTED   5 Gbps    
Comphy-2: SATA0         5 Gbps    
"Synchronous Abort" handler, esr 0x96000210
elr: 0000000000028afc lr : 0000000000028acc (reloc)
elr: 000000003ff6aafc lr : 000000003ff6aacc
x0 : 00000000d0074000 x1 : 0000000000000000
x2 : 0000000000000008 x3 : 0000000000000000
x4 : 0000000000000018 x5 : 0000000000000000
x6 : 000000003fb2f440 x7 : 00000000ffffffe0
x8 : 000000003fb2f640 x9 : 0000000000000008
x10: 0000000000000abc x11: 000000003fb2f23c
x12: 0000000000000a2b x13: 0000000000000a20
x14: 0000000000000000 x15: 000000003fb2f640
x16: 000000003ffc7f41 x17: 000000003ffc7f41
x18: 000000003fb31de0 x19: 000000003fb33aa0
x20: 000000003fb33880 x21: 000000003ffd2800
x22: 0000000000000000 x23: 0000000000000000
x24: 0000000000000000 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 000000003fb2f540

Code: 91406000 b9000001 f9400260 91401000 (b9480001) 
Resetting CPU ...

resetting ...



To disable Sata device at .dts  worked well with the commit a5730fed6bca80376c95d209166f87ba42e887a0 to boot the u-boot master. I mentioned that some weeks ago.  

Sorry for the bad news. 


Btw, do you or someone else have an idea why eth, switch and mmc is not working on espressobin? I found out that some mii, net configs at the _defconfig file helped to activate the eth, phy, mio and switch, but it works not properly. For example on error: U-Boot: Non unique device name eth. Ideas?

I'm digging further,

--
Moritz Berghof
Software Engineer
Tel.?+49?30?921028-209 
Fax?+49?30?921028-020
mberghof at phoenixcontact.com
www.phoenixcontact.com
?
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

-----Urspr?ngliche Nachricht-----
Von: Marek Behun <marek.behun@nic.cz> 
Gesendet: Mittwoch, 15. April 2020 01:53
An: Moritz Berghof <mberghof@phoenixcontact.com>
Cc: u-boot mailing list <u-boot@lists.denx.de>
Betreff: Re: latest u-boot branch for Marvell Armada 88F3720

***External email! Do not click links or open attachments unless you recognize the sender and know the content is safe.***

Hi Moritz,

could you please compile and test current u-boot master on your EspressoBin? My patches regarding DDR size determination on A3700 were applied and I would like to know if it works correctly for you.

Marek

On Mon, 6 Apr 2020 09:43:27 +0000
Moritz Berghof <mberghof@phoenixcontact.com> wrote:

> Hi Marek,
>
> we use the ESPRESSObin Version V5_0_1. We have 2GB-DDR3 memory size and two chips. On of the one side and the other chip directly on the other side of the board.
>
> Have a good day,
>
> --
> 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@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
>
> Hi Moritz,
>
> which version of EspressoBin do you have? How much RAM, is it DDR3 or 
> DDR4? How many RAM chips are there?
>
> 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


.......................................................................................
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

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

Moritz,
is it possible for you to give me ssh access to a computer connected to
the espressobin? Are you open to that? I could give you information
about how to do it.
Marek

On Tue, 21 Apr 2020 10:25:22 +0000
Moritz Berghof <mberghof@phoenixcontact.com> wrote:

> Hi Marek,
> 
> sorry i'm not that fast. Different things around.
> 
> I tested the u-boot master with your patches. But it crashed on my espressobin, unfortunately. 
> 
> Log:
> 
> DLL 0xc0001050[29:24]: [5,32,1b]
>    DLL 0xc0001054[21:16]: [4,2b,17]
>    DLL 0xc0001054[29:24]: [a,35,1f]
>    DLL 0xc0001074[21:16]: [0,3f,1f]
>    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-00490-ge4837da782 (Apr 21 2020 - 12:06:24 +0200)
> 
> DRAM:  1 GiB
> Comphy-0: UNCONNECTED   2.5 Gbps  
> Comphy-1: UNCONNECTED   5 Gbps    
> Comphy-2: SATA0         5 Gbps    
> SATA link 0 timeout.
> AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
> flags: ncq led only pmp fbss pio slum part sxs 
> "Synchronous Abort" handler, esr 0x96000210
> elr: 0000000000028afc lr : 0000000000028acc (reloc)
> elr: 000000003ff6aafc lr : 000000003ff6aacc
> x0 : 00000000d0074000 x1 : 0000000000000000
> x2 : 0000000000000008 x3 : 0000000000000000
> x4 : 0000000000000018 x5 : 0000000000000000
> x6 : 000000003fb2f440 x7 : 00000000ffffffe0
> x8 : 000000003fb2f640 x9 : 0000000000000008
> x10: 0000000000000abc x11: 000000003fb2f23c
> x12: 0000000000000a2b x13: 0000000000000a20
> x14: 0000000000000000 x15: 000000003fb2f640
> x16: 000000003ffc7f41 x17: 000000003ffc7f41
> x18: 000000003fb31de0 x19: 000000003fb33aa0
> x20: 000000003fb33880 x21: 000000003ffd2800
> x22: 0000000000000000 x23: 0000000000000000
> x24: 0000000000000000 x25: 0000000000000000
> x26: 0000000000000000 x27: 0000000000000000
> x28: 0000000000000000 x29: 000000003fb2f540
> 
> Code: 91406000 b9000001 f9400260 91401000 (b9480001) 
> Resetting CPU ...
> 
> resetting ...
> 
> 
> 
> 
> 
> Even when I disable the sata device at the espressobin .dts, the actuall master crashs.
> 
> Log:
> 
> DLL 0xc0001050[29:24]: [5,32,1b]
>    DLL 0xc0001054[21:16]: [4,2b,17]
>    DLL 0xc0001054[29:24]: [a,35,1f]
>    DLL 0xc0001074[21:16]: [0,3f,1f]
>    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-00490-ge4837da782 (Apr 21 2020 - 12:06:24 +0200)
> 
> DRAM:  1 GiB
> Comphy-0: UNCONNECTED   2.5 Gbps  
> Comphy-1: UNCONNECTED   5 Gbps    
> Comphy-2: SATA0         5 Gbps    
> "Synchronous Abort" handler, esr 0x96000210
> elr: 0000000000028afc lr : 0000000000028acc (reloc)
> elr: 000000003ff6aafc lr : 000000003ff6aacc
> x0 : 00000000d0074000 x1 : 0000000000000000
> x2 : 0000000000000008 x3 : 0000000000000000
> x4 : 0000000000000018 x5 : 0000000000000000
> x6 : 000000003fb2f440 x7 : 00000000ffffffe0
> x8 : 000000003fb2f640 x9 : 0000000000000008
> x10: 0000000000000abc x11: 000000003fb2f23c
> x12: 0000000000000a2b x13: 0000000000000a20
> x14: 0000000000000000 x15: 000000003fb2f640
> x16: 000000003ffc7f41 x17: 000000003ffc7f41
> x18: 000000003fb31de0 x19: 000000003fb33aa0
> x20: 000000003fb33880 x21: 000000003ffd2800
> x22: 0000000000000000 x23: 0000000000000000
> x24: 0000000000000000 x25: 0000000000000000
> x26: 0000000000000000 x27: 0000000000000000
> x28: 0000000000000000 x29: 000000003fb2f540
> 
> Code: 91406000 b9000001 f9400260 91401000 (b9480001) 
> Resetting CPU ...
> 
> resetting ...
> 
> 
> 
> To disable Sata device at .dts  worked well with the commit a5730fed6bca80376c95d209166f87ba42e887a0 to boot the u-boot master. I mentioned that some weeks ago.  
> 
> Sorry for the bad news. 
> 
> 
> Btw, do you or someone else have an idea why eth, switch and mmc is not working on espressobin? I found out that some mii, net configs at the _defconfig file helped to activate the eth, phy, mio and switch, but it works not properly. For example on error: U-Boot: Non unique device name eth. Ideas?
> 
> I'm digging further,
> 
> --
> Moritz Berghof
> Software Engineer
> Tel.?+49?30?921028-209 
> Fax?+49?30?921028-020
> mberghof at phoenixcontact.com
> www.phoenixcontact.com
> ?
> 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
> 
> -----Urspr?ngliche Nachricht-----
> Von: Marek Behun <marek.behun@nic.cz> 
> Gesendet: Mittwoch, 15. April 2020 01:53
> An: Moritz Berghof <mberghof@phoenixcontact.com>
> Cc: u-boot mailing list <u-boot@lists.denx.de>
> Betreff: Re: latest u-boot branch for Marvell Armada 88F3720
> 
> ***External email! Do not click links or open attachments unless you recognize the sender and know the content is safe.***
> 
> Hi Moritz,
> 
> could you please compile and test current u-boot master on your EspressoBin? My patches regarding DDR size determination on A3700 were applied and I would like to know if it works correctly for you.
> 
> Marek
> 
> On Mon, 6 Apr 2020 09:43:27 +0000
> Moritz Berghof <mberghof@phoenixcontact.com> wrote:
> 
> > Hi Marek,
> >
> > we use the ESPRESSObin Version V5_0_1. We have 2GB-DDR3 memory size and two chips. On of the one side and the other chip directly on the other side of the board.
> >
> > Have a good day,
> >
> > --
> > 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@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
> >
> > Hi Moritz,
> >
> > which version of EspressoBin do you have? How much RAM, is it DDR3 or 
> > DDR4? How many RAM chips are there?
> >
> > 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  
> 
> 
> .......................................................................................
> 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

latest u-boot branch for Marvell Armada 88F3720

[Marek Behun]

On Wed, 22 Apr 2020 09:03:58 +0000
Moritz Berghof <mberghof@phoenixcontact.com> wrote:

> Hi Marek,
> 
> do you have an espressobin? If not, please give me an answer, I can send you one board for development / testing if you like. Unfortunately ssh access is not possible. 
> 
> Greetings,

No, I do not. That's why I wanted to test u-boot via ssh :)
Marek