• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by yam1

  1. 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.
  2. 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
  3. 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.
  4. Tinker board dual - work in progress:
  5. Fire 3 dual - work in progress:
  6. K1 plus dual with battery power:
  7. 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.
  8. Happy to report both SPI channels worked properly with 5.47 stable using 4.14.51-sunxi64:
  9. Another Neo Core dual screen version - Neo Core 256mb with USB storage integrated:
  10. Adding one more dual screen SBC, Pine64:
  11. 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.
  12. 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?
  13. It runs almost everything now with Larry's work
  14. 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.
  15. You could also try a multi hdmi monitor switch, they are not too expansive.
  16. 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.
  17. No, the only time it happens is when the SBC hangs and in which case it has to be rebooted.
  18. yam1

    SBC choice

    I would suggest looking into neo core 256mb/4gb emmc as its wide open as far as connectivity goes - you add what you really need. I would recommend against wifi and instead use nrf for control. Here is my simple nrf hand held control, one or two joy sticks.
  19. Great idea, I have attached a camera to a raspberry before but not in stereo mode. I guess I could do that to one of these with a similar setup - using a game pad with cell phone holder and reuse the portable battery. I have seen it done before with edge detection on one side.
  20. I just need the ethernet connector. Does anyone know the pin connections to this? It's not marked. The double USB from orange pi zero IO expansion works fine but the audio out is a bit noisy. I had to use a separate audio port. This is one of the few boards with double SPIs and they both work fine. Thanks for the easy user overlay customization support. This is my $7.99 256mb neo core, note there is a chip missing (3rd picture). Starting up in X is slower - it waits for a second or two each time - don't know why, any ideas? It cannot be the swap as I monitored the swap and its only using 125mb. I have the system on the USB thumb drive.
  21. You may want to try this if your orangepi zero plus with NAS IO expansion combination is running too hot, with Nanopi neo 2 it runs a bit cooler (~ 65 vs 70 in full load). Not sure if it is because of the slower CPU speed or the more exposed heat sink.
  22. I must admit I don't really know what to do with my sbc's. After getting them set up there is nothing more I could think of to use them for. I guess part of the fun is in getting them set up, and to run them cool during native kernel builds. Just so it's not a complete waste of money, I spent more (though not a lot) to add dual screens to some of them. Any ideas what else I could use them for? I already have music players (a lot of them, DACs), NAS, home control, security camera, what else do you use them for? I haven't left any of them outside in the sun yet to try out solar power. So, I added dual screens to these ones (left to right, counter clockwise) nanopi neo core, bananapi m1 (original banana pi), pcduino 4 nano (same as nanopi m1), bananapi m2 (a31s), and raspberry pi 3. All of them have two separate SPI channels, it was fun in making them, getting videos to play in dual screens (though not accelerated, but still ran fine in software), but now what? Almost forgot, all of them are running Armbian next (except the raspberry) and thanks for the good work here!!!.
  23. I have a similar problem, the screen is tearing and I get SPI 110 errors filling up the dmesg log. Somebody mentioned the maximum transfer size should be the FIFO size (or FIFO size - 1) rather than the maximum transfer size (or maximum transfer size - 1). I tried all that and it did not seem to help. If I change the txbuflen to something smaller (like 16384 instead of 65536 or 32768), the tearings seem to happen less often. This happens to both SPIs, I have attached an image showing the tearings - note the extra rectangles (above the login box) on both screens.
  24. You could use user overlays as "patches" without touching anything else. That's what I have been using and it works pretty well.
  25. You could use alsamixer to increase the volume, the default volume is too low. This is different from the default on the legacy which is close to 100%.