Jump to content

madeofstown

Members
  • Posts

    5
  • Joined

  • Last visited

  1. I've seen this question asked quite frequently here and all the posts end before there is a solution. I think it's time we had a crystal clear discussion on how it can be done. Not just for my curiosity, but for the people who've asked before and for the people who will ask in the future. The reason: Many hats/shields designed for RaspberryPi would otherwise be compatible with OrangePi if Armbian/u-boot didn't direct the debug output to UART0. UART0 is the most commonly used serial connection for hats/shields designed for RaspberryPi. OrangePi has multiple UART gpio so it would make sense for the O.S. (Armbian) to use the one that least impacts the users ability to actually use their hardware. Debug output is important but not so much so that the user cannot easily disable it.
  2. Using a different UART is not really practical with a hat/shield designed to use UART0... It would be better for the system to use one that isn't commonly required by hats/shields to be the debug interface. I'll keep looking around.
  3. @ag123 Thank you. I was able to apply that patch and now Armbian is running on my OPIZ2W 1.5GB! One more question. I have a LoRa/GNSS hat that requires the use of Serial 0 for communication with the GNSS model. How would I go about disabling Armbian debug outputing to that? I would rather not have to use bodge wires. `gpioinfo` shows me that the 2 pins are used by the kernel. Do I need to recompile the kernel to change this? Seems like a lot of the hats/shields that use Serial need to use Serial0... So I'm thinking there must be a simple way to get it working in Armbian.
  4. I'll take your word for it @SteeMan, thank you. When I search for "orangepi 1.5GB" my post is the only one that comes up. Ill try different combinations but you already gave me my answer.
  5. Forgive me if I am missing something. I have a 1.5GB oPiZ2W and I cannot get it to boot with the community builds or the unofficial builds. No green activity light, just the red power light. No output from HDMI. I've let it sit like this for 15 minutes and still nothing. Is there something else I need to do to get this to boot? I've had no issues with the Debian/Ubuntu images provided by OrangePi.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines