apritzel / arm-trusted-firmware Goto Github PK

Boot log:

U-Boot SPL 2017.11-rc2-00047-gbe5b96f0e4 (Oct 27 2017 - 18:06:42)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000)
NOTICE:  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):1a5edb31
NOTICE:  BL3-1: Built : 18:06:26, Oct 27 2017

at all. Also, the ATF is complaining about setting up the PMIC which may be
related?

U-Boot SPL 2018.03 (Mar 13 2018 - 16:40:00 +0100)                                                                                          
DRAM: 1024 MiB                                                                                                                             
Trying to boot from MMC1                                                                                                                   
NOTICE:  BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000)                                                                            
NOTICE:  Configuring SPC Controller                                                                                                        
NOTICE:  BL3-1: v1.0(debug):ae787242                                                                                                       
NOTICE:  BL3-1: Built : 17:30:05, Mar 12 2018                                                                                              
NOTICE:  DT: sun50i-a64-olinuxino                                                                                                          
NOTICE:  Configuring AXP PMIC                                                                                                              
NOTICE:  PMIC: Output power control 2 is an unexpected 0x40                                                                                
ERROR:   PMIC: setup failed: -3                                                                                                            

Yeah, I think I need to remove the molly guards in ATF when setting up
the PMIC. The code checks whether the PMIC registers it touches contain
certain values, to make sure it is in a sensible state.
Now with Linux driving the PMIC itself and new boards using more rails,
a reboot (which does not reset the PMIC!) lets ATF find the PMIC in some
"unknown" state. Power-cycling fixes this, as you observed.

Can you please file an issue in my ATF github, so that I don't forget to
fix it [1]?

From what I gathered there is a power distribution chips on the OrangePi Win (Plus) that needs to be configured correctly to enable the external ethernet chip (MAC?).

I guess this is a known issue and I am not even sure this is the right place to put this, but the whole process and all interlocking components are a bit opaque to me and it seems to be that here is the place that has should be fixed?

From looking around the internet there is little to no information available on the topic. Or at least none that is readily applicable (by me). But as there is an old u-boot version that apparently initializes the board correctly it seems to me that it is only a matter of adapting what's in there into the new u-boot version? I'd gladly help out, but I have no idea where to start.

Kind regards,
Florian