Larry Bank

  • Content count

  • Joined

  • Last visited

About Larry Bank

Profile Information

  • Gender
  • Location
    Sarasota, FL
  • Interests
    optimization, classic gaming
  1. Armbian for NanoPi Duo

    I've been hitting similar issues trying new builds on various boards. I find it much less stressful to just use a USB wifi dongle when doing these kinds of tests. I'm running Armbian with a 4.13 kernel built for the Orange Pi Zero on my NanoPi Duo and with a USB wifi dongle, it works fine: The Linux build provided by FriendlyElec has a super slow SPI driver, so I went in search of a way to see if it was a hardware or software bug. Running the OPZ build of Armbian on the Duo shows that it's purely a software bug.
  2. I responded to your github issue
  3. You're welcome to email me ( As far as I know, the ili9481 behaves the same as the HX8357 (which I do support in that code). My code was designed for speeding up game emulation and allows you to draw image tiles up to 4K bytes (typical SPI buffer limit). The LCD in your link only talks about its 8-bit parallel interface. My code is strictly for working with SPI (serial) connected displays.
  4. Do you need to have a virtual framebuffer sent to the LCD to accomplish your task, or do you just need to draw text/graphics on the LCD under your control? The reason I ask is that I wrote a simple and fast set of functions to talk directly to SPI connected LCD displays. It doesn't create a virtual frame buffer, but it does offer simple functions to draw text and graphics ( For some projects, it will be easier to work with (and faster) than sending 'late copies' of a virtual framebuffer to the LCD.
  5. Armbian for OrangePi PC2, AllWinner H5

    I tried activating USB with DT overlays - still didn't work. When I run the OP PC2 build on the OPZ+2H5, USB and video works, so why the difference between the 2 builds? How do I activate the video driver?
  6. Armbian for OrangePi PC2, AllWinner H5

    Has anyone tried the latest nightly for the OPZ+2 H5? It works fine when connected via TTY, but HDMI turns off right after the "loading kernel" message. It also doesn't enable any of the USB ports, but Wifi works fine The OrangePi PC 2 version runs better on the OPZ+2 H5. It has video out, usb works, but the wifi is not working.
  7. Enable video out on mainline kernel?

    All composite video out on all ARM boards I've tested always has cut off edges. Maybe it's my monitor, but I hear this from others, so I assume it's a universal problem.
  8. Enable video out on mainline kernel?

    Thanks for the info, but I don't know how to apply patches nor where to get the right one(s).
  9. Enable video out on mainline kernel?

    That would be disappointing if video out is permanently disabled on mainline kernels from now on. I was hoping to use it on the OPZ and NanoPi Duo. The older kernels have a slower/broken SPI driver and overheat.
  10. I've been trying for the last 2 days to get composite video out on the mainline (4.11 and 4.13) kernels on the Orange Pi Zero. I've followed the old guide and the new and nothing works. On the 3.4 kernel, video out worked fine. Can someone please point me to a working set of instructions for accomplishing this?
  11. Larry Bank

  12. NanoPi Duo (plus Mini Shield)

    I just set up my NanoPi Duo and I was hoping to get SPI performance similar to the Orange Pi Zero. I don't have an oscilloscope, but it looks like I'm getting a max frequency of around 3Mhz (based on ili9341 LCD refresh rate). Anyone else seeing sluggish SPI performance? I mapped the GPIO numbers for the pins too. I'll update my SPI_LCD project shortly with the new pin->gpio table.
  13. OpiZero-Plus2 -H3 experimental ?

    Please see my forum post here: I mapped the majority of the pins on the OPZ+2 (H3). The GPIO numbers are quite different from the OPZ. Let me know if you have any questions
  14. I finally mapped the GPIO on the OPZ+2 (H3)

    Update: I keep crashing the machine/corrupting the SD card when trying to located the GPIO numbers for the SPI in/out pins (19/21), but I found the GPIOs for the RX/TX pins on the 3 pin header next to the 26 pin header: GPIO5 -> TTY RX GPIO4 -> TTY TX I've also noticed that the SPI kernel driver seems to run slower than it should. I can set a speed of 33Mhz (the max defined for the SPI) and on other Orange Pi devices, my LCD code can achieve around 28FPS on an ILI9341 (240x320x16bpp). On the OPZ+2, the same speed/code only gets 16.8FPS. Can anyone speculate why the SPI throughput would be slower on this device versus the regular Orange Pi Zero?
  15. The documentation on the Orange Pi Zero Plus 2 is somewhat scarce. I couldn't find information on the GPIO map for the 26-pin header anywhere, but I manually mapped it. I did this with an LED on each successive pin and testing through the /sys/class/gpio driver until I found the one to control it. This caused a bunch of resets and eventually corrupted my sd card, but I got the info Each of the numbers below is the GPIO number used for /sys/class/gpio. For example, 110 means gpio110. The list is by pin number from 1 to 26. A value of -1 means unavailable (as far as I could discover): -1, -1, 12, -1 (pin 1,2,3,4) 11,-1,6,0 (pin 5,6,7,8) -1,1,352,107 (pin 9,10,11,12) 353,-1,3,19 (pin 13,14,15,16) -1,18,-1,-1 (pin 17,18,19,20) -1,2,14,13 (pin 21,22,23,24) -1,110 (pin 25, 26) I've added this table to my SPI_LCD project to make it easier to use for generic GPIO access without having know the details of working with the sysfs kernel driver: P.S. The red LED on the board is mapped to GPIO17