• Content Count

  • Joined

  • Last visited

  1. Furthermore... these i2cset commands work: i2cset -f -y 1 0x18 0x52 3 # turn off both LEDs i2cset -f -y 1 0x18 0x52 2 # turn off white, turn on red i2cset -f -y 1 0x18 0x52 1 # turn off red, turn on white i2cset -f -y 1 0x18 0x52 0 # turn on both red and white
  2. It seems Armbian is missing out in some way. The Pine64 folks know how to control them.
  3. Okay, I see, they are connected to out1 and out2 on the RK805 PMIC. So they wouldn't be just GPIOs. But - presumably - the RK805 could be told how to control them...
  4. Hm. Okay. Posts on the pine64 forum led me to believe that they were controllable.
  5. I have a C++ app that wants to indicate its activity by blinking an LED on the Rock64. How can the LEDs be controlled? The sysfs leds do not appear to be present. I'm okay with libgpiod or sysfs gpios, but I don't know what gpio numbers represent the LEDs. Anyone know? Thanks. Linux rocky64 5.0.0-rockchip64 #5.85 SMP Wed May 8 19:38:28 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic
  6. The world's most cost-effective database cluster node: Best multi-core A72 or A73 4GB fastest & widest RAM possible M.2, physical 2280 slot, PCI3 x4 for NVMe Gigabit Ethernet Power via barrel jack "Big Metal Block" heat sink For node maintenance, a serial console on micro USB port, USB3 type A for backup media/emergency boot Headless - No HDMI. RK3399 would suit. Marvell Armada 8040 is far too expensive. Amlogic S922x has one measly PCIe.
  7. So using the old sysfs (/sys/class/gpio/) interface, you "export" a gpio by spitting the gpio number into /sys/class/gpio/export. The GPIO number depends on the board and relevant documentation. Having once found that I need GPIO number 76, I'm migrating code to the new "gpio character device" interface (/dev/gpiochipn) on my Rock64. However, "gpioinfo" shows that hardly any gpios have useful labels, and Google searches always turn up Raspberry Pi results. So, can I just calculate the new gpio identify? Old gpio is 76, all /dev/gpiochips have 32 lines, 76/32 = 2 rem 12, so old gpio 76 is now /dev/gpiochip2 line 12? Edit: I tried this, and it was correct. Is this anywhere documented to be correct in all/most/many/some cases?
  8. My armbian-config went missing. I know it was there before, but apparently somehow I deleted it. "find / -mount -type f -name armbian-config" gets no hits. Is there a package I can refresh to get it back? Thanks.
  9. Humbly suggest: Beaglebone Black. [root@ny3270s bin]# uname -a Linux ny3270s 3.13.9-bone9 #1 SMP Wed Apr 9 08:39:37 EDT 2014 armv7l armv7l armv7l GNU/Linux [root@ny3270s bin]# uptime 06:20:01 up 835 days, 15:30, 1 user, load average: 0.37, 0.41, 0.49
  10. I bought a TP-Link AC1300 "High Gain" WiFi adapter, in order to try to get a connection between my house and my garage. I thought that the included rtl8812 driver was the right one, but it turns out the AC1300 is the "V3" version of the Archer T4U, and it requires the rtl8822 driver. Well, it turns out that the driver at works straight up. I followed tkaiser's directions here: ...but changed "8812au" to "8822bu". Commands executed cleanly. I blacklisted 88XXau and rebooted, and everything worked great. And, I got the signal I needed, so it was worth the effort. Anyway, I just thought it might be worth to include this driver in future builds of Armbian. Consider this a "testimonial" :-) Oh, BTW: NanoPi Neo, Armbian 5.85, Linux 4.19.38-sunxi, Stable.
  11. So obviously it's a "joke" video. April 1st. So, what board is it, really? The image in the video is mirrored from the real board (look at the chip labels - he printed the "Raspberry Pi 4" label backwards to compensate). I think it's an Orange Pi 2+, hacked up a bit...
  12. ...or, if you really have your heart set on a NanoPI or other Allwinner/Rockchip device, consider adding an NXP SC16IS750 UART beside your MAX485 chip. Awesome UART, deep FIFOs, 9 bit mode, automatic RS485 turnaround. Then write a devicetree overlay for add this SPI device (don't forget an interrupt pin), and build a kernel with the sc16is7xx driver included.
  13. In my experience RS485 (especially at 115200 baud) is VERY troublesome without a suitable UART, which the Allwinner H5 does not contain. If you are designing the protocol then maybe (I did), otherwise consider alternatives. I suggest using a Beaglebone Black instead. The OMAP UART has what's needed.