Orange Pi Win Plus - no screen image after uboot


Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

22 minutes ago, svsd_val said:

Are there any assumptions how to fix this?


Orange Pi Win support is under development - there are only experimental images and things might be missing. IIRC there is no HDMI support yet or it's (partially) broken ATM. Attach a serial console to see what's going on. Both boards will use the same image ...

Link to post
Share on other sites

To bring up this board or in general? State of general A64 development within mainline kernel: http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix 

 

If you want just help, there are many things to do:

 

Docs:

https://docs.armbian.com/Process_Contribute/


Build system sources:

https://github.com/armbian/build

 

Configuration sources:

https://github.com/armbian/config

 

Documentation sources:

https://github.com/armbian/documentation

 

Even the smallest help save us time. For example altering typo, whether in apps or documentation. Code cleaning, testing, fixing ... core drivers, which is the problem here, come into action last.

Link to post
Share on other sites

I have no experience in driver development, but there is experience in bash, fpc, and little c/c++ and python. I can help with programming utility programs, testing and a small donate.

For testing, I have these boards:

Orange PI Lite , Orange PI PC, Orange PI PC + , Orange PI Prime and Orange PI Win +

Link to post
Share on other sites
51 minutes ago, Ucino said:

Is this can help you ? (replacing the dtb files)


That's a hack for the old stock kernel which we don't use on this board. We use that kernel on a similar board - Pine64 and Pinebook but haven't managed to adjust it for Oranges or Bananas ... we lack resources and working mostly with a modern kernel. That one is not very far away.

Link to post
Share on other sites
7 hours ago, t-bob said:

I like many others would like to help. We seem to have many general unix coders and not enough driver people


There are also many easy and trivial tasks out there. We have to find and fix as many bugs as possible and we got less than two months for this. Approximately. My motto for any newcomer is: Start with easy tasks. Do what you are comfortable with.

 

7 hours ago, t-bob said:

Where do we go to find problems to correct ? From that I can see/read it's the Issues section on github which has 3 in config and 27 in build.


Yes, this is one way - start on recognized troubles. Another is optimising code and find & fix what's unknown. https://github.com/armbian/config This utility needs testing and code observation from another perspective. The best would be to work on this with some Debian Stretch image and find & fix stretch problems if any left. Make sure to check this too: https://forum.armbian.com/index.php?/topic/5149-upcoming-release-date-feature-freeze/

 

Link to post
Share on other sites
On 23/09/2017 at 11:49 PM, Igor said:


That's a hack for the old stock kernel which we don't use on this board. We use that kernel on a similar board - Pine64 and Pinebook but haven't managed to adjust it for Oranges or Bananas ... we lack resources and working mostly with a modern kernel. That one is not very far away.

Ok, thanks for your feedback.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.