martinayotte

Hi everyone !
 
I'm starting this new dedicated thread because I've got some new headache about this issue that we tried to figured out since months...
 
I've received my PineH64 last week, and with this board I don't faced the reboot hang behaviour !
 
Today, since I've committed the OPi3 WIP scripts, and facing same reboot hang, I've decided to to try booting PineH64 image on this OPi3 board, but unfortunately reboot hang still occurs ...
 
This brings me to a conclusion that it is not a software issue, but maybe hardware one ... I will dig on that during next few days by comparing PMIC and other between all those boards ...
 
But I remember that @jernej said that Reboot worked on one of his H6 board ...
@jernej can you confirm which board ? Do you have some boards where you still face reboot hang issue ? Can you try to mix image like I did to give clues ?
 
 
 

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...
 

Done !
https://github.com/armbian/build/commit/fa232d17ed1488bd19be4dbc9f7f3b174f85ef73
 

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...
 

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...
 

True ! ... I've just committed one more : the OrangePi3 WIP ...

Ahahah !
Are all those soldiers representing the number of boards that Armbian is supporting ?

Don't give up ! All those looks nice !
For this latest Space one, could you try to put propeller flames at the bottom of his fleet ?
 

Done !
https://github.com/armbian/build/commit/fa232d17ed1488bd19be4dbc9f7f3b174f85ef73
 

No need to worry about this failure, if I remember, those clm blobs are used to determine countries and allowed channels...

No need to worry about this failure, if I remember, those clm blobs are used to determine countries and allowed channels...

Maybe you can look into snow flakes too ...
I know ! I´ve done some decades ago with 3D-Studio during early 199x, on a x386/x486 ! It was painful !
 

I think clouds are looking like asteroids ...
 

I like both, but maybe a bit more the smoothened one ...

I've received mine today ... Thanks to Humberg !
I've built an Armbian 4.20.y image this afternoon, it boot fine, but no eth0 or WiFi, but I got networking using USB-WiFi dongle.
For RTL8723, I've tried adding it in DT, but it still not appearing ... It is difficult to figure out without schematic, and schematic doesn't seems to be public yet ...
I've posted on forum.pine64.org asking for that schematic, but no answer yet ...
 
EDIT : Forgot to mention, "reboot" is working fine on this H6 board, I don't experience freezing found with other H6s ...

Oh ! I've found that Armbian build for H6 exceptionally using https://github.com/Icenowy/u-boot , which is pretty old, that could be that, I will try u-boot mainstream ...
 
EDIT : Mainstream U-Boot doesn't seems to be enough ...

@Igor can probably arrange things so that Steven from Xunlung can ship you one for free ...

If you mean that you don't see any kernel logs after "starting kernel", make sure that /boot/armbianEnv.txt have "console=serial" and "verbosity=7" ...

Edit the following file : /etc/default/armbian-zram-config

So, it reach login prompt, you've logged in an still don't see the /dev/spidev0.0 ?
What shows up doing "grep SPIDEV /boot/config-*" ?
It should show :
CONFIG_SPI_SPIDEV=m Which kernel are you using ?

It is not for NanoPi-M4, as I mentioned I've use NanoPC-T4 ...
 
EDIT : I've just double checked on my T4 : SPI1 is really on spi@ff1d0000 ...
So, why your M4 doesn't boot after such changes ? Maybe you did some typo errors ?

I got the things working !
Although I didn't tested it with real SPI device, I've at least tested it with loopback wire between MISO/MOSI and executed spidev_test ...
https://github.com/armbian/build/commit/34205e60b3efa0ef3acc293ed9e02b801f8a52c1
 

I got the things working !
Although I didn't tested it with real SPI device, I've at least tested it with loopback wire between MISO/MOSI and executed spidev_test ...
https://github.com/armbian/build/commit/34205e60b3efa0ef3acc293ed9e02b801f8a52c1
 

Do you mean you have some spares to give away ?
Maybe I could be interested ...

If you do a "i2cdetect -l", you will probably see that i2c-0 is dedicated to "sun4i_hdmi_i2c adapter", which maybe wasn't present before ...