Werner

You should do like me : I have more than a dozen of USB-TTL around, almost every boards have one, so I don't have to waste time unplugging/plugging them while testing. I've even placed a new order on eBay to get more ...
Tested on OPiOnePlus, now doing the OPiLite2 and OPi3 ... Patch is already committed to Armbian !
Thanks a lot for the help !
 
EDIT : OPiLite2 and OPi3 tested too ...

What would be this second patch for the U-Boot "reset" ?
 
EDIT : for the "reboot" patch, I'm confirming : it works ! Thanks a lot to both @froezus and @megi !!!
EDIT2 : tested on all my H6, OPiOne+/OPiLite2/OPi3 ... And patch committed in Armbian !

https://github.com/leeboby/OrangePiH6_Linux4.9

- firmware to support Orangepi 3 https://github.com/armbian/firmware/commit/fe584970a1f8e718540a3cec4838e7a4cad5f263
- spelling and grammar in armbian-config  https://github.com/armbian/config/commit/92ad8e77eec2e71429d677852654cfeb1a0ea3f0

Please refer to this topic rgd issue 1)
Also to create some more awareness I contacted "Allwinner Customer Service Team" recently and they made this a Xunlong issue,
their response: " After a short discussion internally, we suggest you contact Xunlong for clarification.
Let's hope for a satisfactory solution, little/ some hope this can be increased as Xunlog is partnering with armbian ... ...
 
let's keep fingers crossed...

Here you go ;)

This smells like someone savvy with higher ed dollars and grant money
 
So in all seriousness, what would armbian certified look like to you.  What are the skills that one would be trying to master.  As a brainstorming here's some possibilities:
 
Using build system to build custom images and kernels alternate kernel options the user-patches framework kernel patches alternate system configurations software preinstallaion Understanding the SBC ecosystem vendor culture kernel fragmentation u-boot fragmentation Mainlining Initiatives u-boot kernel Adding your own community support board to the ecosystem -- assuming you plan to continue to support it

That's super awesome.   Out of curiousity, what do you and you students do with armbian?  and what kind of hardware generally?
 

Thanks Martin! I just validated on my OpiOne+

Not on fresh boot, as well as original OPi U-Boot, but both work well if the BSP U-Boot handler is still in memory.
 
This is why I've said "Back to SquareOne" when I've investigated the reset_cpu() code from arch/arm/mach-sunxi/board.c
... and I still don't catch why PineH64 U-Boot works fine on PineH64 boards ...

https://github.com/armbian/documentation/pulls
 

you're still a machine.

Here is the explanation why it was working earlier, but only for awhile :
I've booted a BSP U-Boot and stopped it without unplugging the power, then using any Mainline U-Boot, the "reboot/reset" is working fine since the BSP code still in memory, until I'm unpowering the board.
I've just did the same sequence with OPiOne, and the "reboot/reset" is working again there too ...
 
So, back to SquareOne !
 
Can you bring me some light ? I'm currently digging a whole while been in the fog without any shovel ...

omg, let's bump dev to 5.05 ( current kernel ) and build a fresh debian image.
Mr martinayotte, I should like to express my respect to you for your work!
Will check back later as duty calls ( cooking for the wife ;-) )

Almost all H6 boards have problem with "reboot" command, we din't find solution yet, we need to re-cycle power to reboot.

https://github.com/leeboby/OrangePiH6_Linux4.9

I've committed the initial stuff !
Now, I will pursue the patch cleaning ...
Let me know if you are unable to build 5.0.y on some Allwinner boards ...

Uhh so i installed mate desktop...and other than stuck with a 1024x768 modeline... the display driver is crazy fast!

totally!

 

 

I've done several local builds with success, although some patches are still failing, they don't prevent doing a build.
I will push preliminary stuff soon ...

Thanks ! Good to know !
Since I'm preparing Armbian-DEV to switch to 5.0.y, I've simply added it to OPiLite2 and OPiOne+, and it works (at least in plain text console) !
 

Should we tag the last commit before changing to the 5.0 work?

Ok ! Since switching U-Boot is a less painful task than kernel itself, maybe we can switch sooner !
I will try this afternoon ...

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

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 ?