yam1

Members
  • Content Count

    58
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by yam1

  1. Thanks to everyone for the work here, so if you use armbian-add-overlay on the created file below, it should just work in the future. usbotg2host.dts
  2. Alternatively, you could use a usb to ethernet connector, this would give you network (my user build next works just fine and boots - I just did it today).
  3. That's right analog sound seems available (as shown by /proc/asound/cards) when using a pine64 5.70 next image with nanopi a64 but no sound ever comes out of the connection, wifi does work.
  4. I haven't, but you may want to try this aufs blog post: https://superuser.com/questions/833576/differences-of-aufs-unionfs-and-overlayfs-from-each-other
  5. If you add anything crappy to your system, your system would become crappy because it is contagious. I always baby mine and they provide me with joy.
  6. Still has SPI 110 errors, but seems less frequent on 4.19.y, double spi and analog audio still works.
  7. Wouldn't you opt for an oled display instead, brighter, smaller, and higher resolution for fifty cents more? And its using only 4 lines, sample usage:
  8. Here are some of my SBCs that are under $20 (see photo below). I have divided them into two categories, with hdmi and not. The ones on the left are without, and on the right are with. The ones without are mostly orangepi's and nanopi's. Just do a search on their web sites and if it is under $20, I have it. One thing to consider is the ones with two spi channels (e.g. nanopi core 1 - note core 2 is better but its over $20), this would allow connecting two spi screens. If you connect two relatively big 3.2 ili9341 screens, with the browser stretched across them, your experience would still suffer but it would be okay in some extreme situations. The ones with hdmi include, raspberrypi zero w (double spi), nanopi A64 (double spi), pcduino4 nano (double spi), nanopi m1 - same as pcduino4 nano (double spi), and the other three orangepi's. Bananapi zero is slightly over $20, I have it connected to a lap dock. Of these, the best is pcduino4 nano (get it on ebay between $5 to $16), supported well in software (armbian), and nanopi a64 ($19.99?) is my second choice, software support is getting there (may be?), at least double spi works with pine64 image (latest kernel). Raspberrypi Zero W is only $5 from my local store, and dual spi screen with camera works, you really can't beat it in price.
  9. CSC supported is just as great as any other boards. The only thing I could not get working is hdmi sound, wifi works fine, both spi channels work fine - but not as well as other boards (more 110 errors), perhaps hardware related? I use it as a laptop with my lap dock, and a bluetooth dongle for sound.
  10. You could easily do that with any SBC discussed in this forum, e.g. k1plus dual screen + bluetooth keyboard, or a zero plus 2 h5, 5 inch hdmi + bluetooh keyboard, or a pi zero with double 18650 batteries and a 2.4" screen
  11. The issue is question is missing spidev argument: param_spidev_spi_bus=0 I can confirm spi_spidev works in 4.17.11. But I could not get other user device tree overlays to work properly in 4.17.11.
  12. Tinker board dual - work in progress:
  13. Fire 3 dual - work in progress:
  14. K1 plus dual with battery power:
  15. Accidentally clicked on kodi while looking for smtube and surprised to see it on my SPI display - no more DRI authentication errors :-) This was on a OPI Prime (H5), kernel 4.17.10.
  16. Happy to report both SPI channels worked properly with 5.47 stable using 4.14.51-sunxi64:
  17. Another Neo Core dual screen version - Neo Core 256mb with USB storage integrated:
  18. Adding one more dual screen SBC, Pine64:
  19. I have no less than 50 SBCs from different vendors, including OrangePi, BananaPi, RaspberryPi, and NanoPi. All of my failures came from NanoPi, so much for providing boards with industrial quality. These were all DOA's: - one NanoPi Neo microSD slot failed to latch, new board, shipping not refunded - two of the mini shields for Neo Core/Core2 failed to do anything - I bought four of these kits, the failures were never refunded - four UNO dock V2 - I bought 4 of these, all of them not working, never refunded I do like the NanoPi boards when they work, but their quality control is terrible.
  20. Not sure if this has been reported - the usual way of enabling spi overaly "overlays=spi-spidev and param_spidev_spi_bus=x" seems to be broken and when an overlay fails at boot time, it tries to load the base dtb from /.../alllwinner/allwinner/*, note the extra allwinner in the path - so it fails. The pin definitions for the Euler SPI are wrong. When you manage to get both SPIs up. SPI 0 is being enabled as spi1.0 and SPI 1 being enabled as spi0.0. It also fails to merge board neutral ili9341 SPI definition files (at boot time) that has always worked on H3 and H5 boards. To work around for now, use the following ( spi0.dts, spi1.dts) to get the spidev's up - not sure why these worked and spi-spidev didn't (is it because of the parameter requiring fix-ups?). Also note they enable the wrong spi. After they are added, SPIs are working as you can use notro's fbtft (via modprobe) on them but not both at the same time. Cannot readily use 5.44 yet as the kernel headers are missing. I understand SPI is not in the matrix until 4.15 - how to report these issues so they can be fixed soon?
  21. It runs almost everything now with Larry's work
  22. In my experience, most of the time the SBC hangs is when all 4 cores are busy for too long the system overheats and CPU scaling causing the system to be unresponsive. CPU scaling does work as far as cutting down the load but somehow the affected processes do not like it and i have to reboot.
  23. You could also try a multi hdmi monitor switch, they are not too expansive.
  24. I can confirm the display in question works with Neo, and Neo2, and I dont see anything wrong with your wiring, but I would try to put all the wires closer together so that they can be taped into a block for ease of plugging and unplugging later on. I can also confirm when you do it this way you don't need to worry about conflicts in the fex/dts file as I have already tried them. When I did mine I just copied the wiring from a raspberry pi article, and changed the GPIO numbers in the fbtft call. The cable is the same just the GPIO numbers are different. There are really just 3 free wires, the rest are constrained. I usually leave the backlight/led wire (the yellow wire below) outside of the block so that it can be attached to a PWM pin or a 3.3v source if you are running out of pins as in Duo. The same cable would work with almost every SBC, here I have it connected up to Neo and Neo2 - note the Ethernet ports of Neo and Neo2 are upside down to each other.
  25. No, the only time it happens is when the SBC hangs and in which case it has to be rebooted.