Search the Community

Showing results for tags 'hardware hack'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

  1. I am trying to use a Waveshare e-Paper (2.9") with an Orange Pi Zero LTS. To enable the SPI interface, I have added this to /boot/armbianEnv.txt: overlays=spi-add-cs1 spi-spidev param_spidev_spi_bus=1 param_spidev_max_freq=10000000 and installed WiringPI from Github. The e-Paper module is connected to the following GPIO pins: VCC: 3.3V GND: GND DIN: 19(phys)/11(wPi) CLK: 23(phys)/14(wPi) CS: 24(phys)/15(wPi) DC: 22(phys)/13(wPi) RST: 3(phys)/0(wPi) BUSY: 5(phys)/1(wPi) I have checked the connections by using the gpio command line tool to set all 6 ports above to low and to high, and verifying the output with a multimeter. Then I downloaded the e-Paper software from Github, and made it compatible with the Orange Pi via the following changes to lib/Config/DEV_Config.c: 1. In DEV_Equipment_Testing(void), comment out the code that checks if the file /etc/issue contains the string "Raspian" 2. Set EPD_RST_PIN=0, EPD_DC_PIN=13, EPD_CS_PIN=15, EPD_BUSY_PIN=1. 3. Uncomment "if(wiringPiSetup() < 0)", add a curly open brace, and comment out the line after. 4. Change "wiringPiSPISetup(0,10000000);" into "wiringPiSPISetup(1,10000000);" to use spidev1.0 When I run this e-Paper example, nothing happens on the e-Paper display, although I can detect voltage changes on the GPIO ports with a multimeter. The same software works on a Raspberry Pi without problems. Any hints are appreciated!
  2. First of all, credits goes to https://4pda.ru/forum/lofiversion/index.php?t750921-2560.html Device that I used for this guide: https://www.aliexpress.com/item/3-5-Inch-TFT-LCD-Moudle-For-Raspberry-Pi-2-Model-B-RPI-B-raspberry-pi/32707058182.html Pinout: http://www.waveshare.com/3.5inch-rpi-lcd-a.htm (Yes, the device is a waveshare knockoff) How to place the device? For Orange pi lite/one it is reversed. For the rest, it should be normal. Refer to https://forum.armbian.com/index.php?/topic/724-quick-review-of-orange-pi-one/ for more info. There are two sections to this guide. Legacy / Mainline Legacy Kernel [You can only EITHER use touch or LCD due to issues with spi chip select] LCD 1) Load fbtft and fbtft_device on boot sudo nano /etc/modules-load.d/fbtft.conf fbtft fbtft_device 2) Load fbtft_device options nano /etc/modprobe.d/fbtft.conf options fbtft_device rotate=90 name=piscreen speed=16000000 gpios=reset:2,dc:71 txbuflen=32768 fps=25 3) Make sure X11 loads to the correct framebuffer (fb8 for legacy) nano /etc/X11/xorg.conf.d/50-fbturbo.conf find fb0 and change to fb8 4) Reboot your device (sudo reboot) and you screen should be lit up ============================================ TOUCH 1) Download ads7846 touch driver (compatible with xpt2046) mkdir ds7846 cd ds7846 wget https://raw.githubusercontent.com/raspberrypi/linux/rpi-3.6.y/drivers/input/touchscreen/ads7846.c 2) Create a makefile (Take note that it is TABS instead of spaces before the $(MAKE)) nano Makefile Insert the below in without the ----- -------------------------------- obj-m := ads7846.o KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd) all: $(MAKE) -C $(KDIR) M=$(PWD) modules clean: $(MAKE) -C $(KDIR) M=$(PWD) clean install: $(MAKE) -C $(KDIR) M=$(PWD) modules_install -------------------------------- 3) Exit nano and run the following sudo make sudo make install sudo depmod 4) Download and compile and install ads7846_device cd .. git clone https://github.com/notro/fbtft_tools/ cd fbtft_tools/ads7846_device make sudo make install sudo depmod 5) Load ads7846 and ads7846_device on boot sudo nano /etc/modules-load.d/ads7846.conf ads7846 ads7846_device 6) Load ads7846_device options nano /etc/modprobe.d/ads7846_device.conf options ads7846_device model=7846 cs=0 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 7) Reboot your device and run evtest sudo reboot sudo evtest Find your touch device and happy touching. Every touch should generate an event.
  3. I am releasing this patch in the hope of you may find it useful. I have also included a sample dts file. It seems to work in 48mhz quite well with very few SPI errors. (Note that the pieces of the driver has been around for some time but I have never seen it put together without further work. Hopefully this patch would make it readily usable. I have tested it on 5.5.18 and quite happy with it.) 0001-fbtft-fb_ili9488.patch 1_ili9488.dts Sample file is for nanopi neo. Driver also works with 4 inch LCD, MSP4020, MSP4021
  4. Hello, I'm new here and do not quite understand the sub-forums here but hopefully this is the right one. I got an Orange pi ONE running 4.19 RT kernel with Armbian buster. I was testing out the GPIO capabilities of the H3 SoC without any libraries and got only 1.67 Mhz at best(which is ironically the same as WiringPIOP) with some task interrupt issues. #define INP_GPIO(g) *(unsigned int *)(gpio+0x04) &= ~(7 << (((g) % 10) * 3)) //I did not thoroughly check if the mapping is okay #define OUT_GPIO(g){\ *(unsigned int *)(gpio+0x04) &= ~(6 << (((g) % 8) * 4));\ *(unsigned int *)(gpio+0x04) |= (1 << (((g) % 8) * 4));\ } #define GET_GPIO(g) (*(unsigned int *)(gpio+0x10) & (1<<g))// 0 if LOW, (1<<g) if HIGH #define GPIO_SET(g) if(!GET_GPIO(g)){*(unsigned int *)(gpio+0x10) |= (1 << g);} #define GPIO_CLR(g) if(GET_GPIO(g)){*(unsigned int *)(gpio+0x10) &= ~(1<< g);} //after accessing /dev/mem OUT_GPIO(12); for(;;) { GPIO_SET(12); GPIO_CLR(12); } The result is pretty inconsistent but at least works (any suggestions?). One could say remove the if statement(got 2Mhz) but that makes the output even more bizarre. At this point i am quite stuck and not sure how to get a faster result with correct timing when rising and falling. Any suggestions for this would be helpful. Thank you! test.cpp
  5. A very hackish port exists of this Raspberry PI RGB LED Matrix Library which works for Allwinner H3 devices. This works by bit-banging 14 GPIO pins simultaneously to achieve about a 10Mhz throughput / 100fps refresh rate. Refer to here: https://github.com/mrfaptastic/opi-allwinner-h3-rgb-led-matrix I managed to easily get up and running using an Orange PI. Refer to the README of the github repository.
  6. Hello, I don't know where to start, but I am looking to use Velleman VM140 USB IO-board with Armbian Linux. I tried first on NanoPi R1 that I have succesfully installed Armbian Linux. Linux I have installed is Armbian Buster for NanoPi R1. root@nanopi-r1:/etc# uname -r 5.7.15-sunxi I read somewhere there is kernel support for K8061 (the usb chip on the board if I understood correctly, looks to be a pic with USB). dmesg after attaching USB cable to R1: [960949.202099] usb 6-1: new full-speed USB device number 2 using ohci-platform [960949.435136] usb 6-1: New USB device found, idVendor=10cf, idProduct=8061, bcdDevice= 0.00 [960949.435160] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [960949.435175] usb 6-1: Product: K8061 USB Interface Board [960949.435188] usb 6-1: Manufacturer: Velleman-kit It looks like kernel recognises what is attached to it. No device appears in the /dev filesystem on Armbian. Another Linux machine running ubuntu 20.04LTS on Atom CPU dmesg after attaching the same VM140: [1625465.062860] usb 1-1: new full-speed USB device number 10 using xhci_hcd [1625465.217190] usb 1-1: New USB device found, idVendor=10cf, idProduct=8061, bcdDevice= 0.00 [1625465.217196] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1625465.217199] usb 1-1: Product: K8061 USB Interface Board [1625465.217202] usb 1-1: Manufacturer: Velleman-kit [1625465.262491] comedi: module is from the staging directory, the quality is unknown, you have been warned. [1625465.262617] comedi: module verification failed: signature and/or required key missing - tainting kernel [1625465.265181] comedi: version 0.7.76 - http://www.comedi.org [1625465.266168] comedi_usb: module is from the staging directory, the quality is unknown, you have been warned. [1625465.275029] vmk80xx: module is from the staging directory, the quality is unknown, you have been warned. [1625465.276014] comedi comedi0: driver 'vmk80xx' has successfully auto-configured 'K8061 (VM140)'. [1625465.276167] usbcore: registered new interface driver vmk80xx And from /dev filesystem I can find from that system /dev/comedi0 device after attaching the board. From this ubuntu 20.04LTS I can find the kernel module at /lib/modules/$(uname -r)/kernel/drivers/staging/comedi In armbian such module does not exist. /lib/modules/$(uname -r)/kernel/drivers/staging/ folder is present,but no comedi sub folder exists. Can anyone help me to know what I need to do and also is this the correct forum to ask such questions? Is it possible that I could find the comedi module to be isntalled or do I have to compile it from source (if I knwo how to, sooner or later I guess I could). I am also planning to use VM140 on Armbian and NanoPi M4. It seems to have different CPU, looks to be Rockchip RK3399. Will that be very much different? Petri
  7. I know the RPi is pretty limited on the GPIO pins. Now my question is how it looks on Le Potato, i.E. is it possible to power a fan directly from the GPIO pins? Powering it from the 3.3 V line seems to work just fine but I fear damaging hardware by trying to connect it to a GPIO instead.
  8. Hi, all! Is it possible to make micro usb otg connection through gpio pins on the orange pi zero? I'm asking because when OPi is located in the box, I need to use external USB type B socket to micro usb cable. So it will be really cool, if I will have opportunity to connect usb otg socket through gpios. Regards.
  9. It's simple guide, presenting how to setup LCD (ili9431) with integrated touchscreen (tsc2046) on mainline kernel (4.11). It may be not fully "armbian way", since I'm pretty new in armbian In case that somebody is interested, I recently bought couple those displays from here Few basic informations: 1. OrangePiZero has two SPI buses. First one is usually occupied by build in memory. So we can only use bus1 2. tsc2046 chip is fully compatible with ads7846, and we have drivers for it since years now 3. Maximum clock frequency for ads7846 is 3.25Mhz, but don't expect that it will work with that. Reasonable value is something beetween 0.5-2Mhz. Lower frequency, if you observing misbehavior. 4. Probably most important information ili9431 and tsc2046 poorly cooperate on shared bus. I don't know exactly why, because I don't have access to logic analyzer, but it's proven fact (at least on my equipment). You have to lower bus frequency to 2MHz (highest common value), and even then it work very unstable. My educated guess is that, missed interrupt from touchscreen (when SPI is busy with sending data to LCD) makes it stop making further attempts to communicate. Or maybe there is some incompatibility on electrical level, I really don't know. 5. My electrical setup (keep in mind it's 3.3V) OPIZ - LCD (ili9431) PA13 - CS PA14 - SCK PA16 - SDO PA15 - SDI PA03 - DC PA00 - RESET PA06 - controls transistor which is driving current to LCD pin. You may also connect LCD pin to VCC, and leave PA06 floating. And here is part for touchscreen. We are going to use emulated spi bus with bitbang. At this point bitbang isn't compiled in armbian kernel - we will take care of this later. OPIZ - LCD (tsc2046) PA10 - T_CS PA18 - T_IRQ PA19 - T_CLK PA11 - T_DIN PA12 - T_DO Configuration for the first spi bus: Configuration for touchscreen driver: Compile and add those DTS with "armbian-add-overlay" command. Next, download armbian sources and cross compile kernel - without any modifications, just to make sure that everything is compiling without issues: # mkdir armbian # cd armbian # git clone https://github.com/armbian/build.git # git clone https://github.com/igorpecovnik/lib # cp lib/compile.sh . # ./compile.sh BRANCH=dev BOARD=orangepizero KERNEL_ONLY=yes PROGRESS_DISPLAY=plain RELEASE=jessie Enable required modules : echo "CONFIG_SPI_BITBANG=m" >> lib/config/kernel/linux-sun8i-dev.config echo "CONFIG_SPI_GPIO=m" >> lib/config/kernel/linux-sun8i-dev.config ... and recompile kernel, then install deb packages from output directory. You may also copy drivers, it may be faster for testing but it's not advised for "serious" deployment. Loading modules at startup: # cat > /etc/modprobe.d/fb_ili9341.conf << _EOF_ options fbtft_device custom name=fb_ili9341 gpios=dc:3,reset:0,led:6 speed=16000000 busnum=1 _EOF_ # echo fbtft_device >> /etc/modules # echo ads7846 >> /etc/modules If you connected LED pin to VCC, then you should omit that ",led:6" in configuration above. I hope that this will help anyone who want to connect LCD display and build simple touchscreen based Orange Pi Zero terminal
  10. Hello, I'm trying to use Armbian with a Nanopi NEO Core (Allwinner H3) mounted on its Mini Shield. I was able to use the CAN controller MCP2518FD through SPI1 and CS1. Now I need to use, always on the same SPI1, the demo board TPM SLB 9670 TPM2.0 that I have already verified on a Raspberry Pi. I found the tpm_tis_spi Kernel module by compiling Armbian Bionic 5.4.37, but I was unable to locate the DTB overlay needed to set-up the following pins: SPI1 MOSI SPI1 MISO SPI1 CLK SPI1 CS IRQ (from SLB9670's demo board to Nanopi NEO Core) RESET (from Nanopi NEO Core to SLB9670's demo board) Can anyone help me? Thanks in advance Regards P.S. I apologize, I have already created this topic in "General chit chat", but I think I didn't make the right choice...
  11. Hi there. Trying to get SPIDEV working on my good old cubietruck aka cubieboard3 with an allwinner A20. Found some posts here and there dealing with A20 boards. But nothing of that did anything for me so far. Enabled it in armbian-config hardware settings and rebooted. No /dev/spi* at all. No mentioning of "spi" in dmesg. Step 1 gave a line "overlays=spi-spidev" in /boot/armbianEnv.txt. Read somewhere else that there should be another line "param_spidev_spi_bus=0", but that was not created by armbian-config. Added that ...bus=0 line myself and rebooted. Still no spi device and nothing in dmesg /proc/device-tree-model says "cubietech cubietruck" which is correct. Running 5.4.20-sunxi, fresh install a few days ago. Nothing special done to it yet. Anyone still playing with these old toys and done this? Thanks!
  12. Hello Opi Community, I have an Orange Pi PC with the below HW Specs: Snippet of lshw output: description: ARMv7 Processor rev 5 (v7l) product: Xunlong Orange Pi PC width: 32 bits capabilities: smp 4 CPU Issue: Chromium locks up frequently while browsing the internet. Yes I'm running the ARMBIAN OS (Armbian Buster) Chromium Version 76.0.3809.100 (Developer Build) built on Debian 10.0, running on Debian 10.1 (32-bit) Not sure if it is an H2 or H3 board. How do I find it? It is an AllWinner Sun8i family H3 Board armbian-firmware 20.02.4 ArmbianMonitor dump is here: http://ix.io/2kMo I would like to know if I can upgrade the RAM from 1 GB to 2GB ? If yes which RAM chip do I purchase? I have a soldering kit with me to replace the RAM chip. Bonus Question: Not sure if the issue is with chromium itself, if anyone has experienced this, is there an alternate browser? Regards, OPi user
  13. Trying to figure out which NOR chip to buy for my ZeroPi is giving me a headache. FriendlyArm has very little info available on what works. The board has an empty spot to solder a NOR chip that I would like to populate. There are so many chips all with different voltages and clock frequencies. The wiki and schematic omit the connection all together so I really have no idea what would work. Can someone point me in the right direction?
  14. I do some tests on a new display from WaveShare : 5.5inch HDMI AMOLED, 1080x1920 https://www.waveshare.com/product/modules/oleds-lcds/oled/5.5inch-hdmi-amoled.htm On the wiki, it's wrote : To use it on RaspberryPi, you must change the config.txt file for to ajuste hdmi parameters : https://www.waveshare.com/wiki/5.5inch_HDMI_AMOLED max_framebuffer_height=1920 max_usb_current=1 config_hdmi_boost=10 hdmi_group=2 hdmi_force_hotplug=1 hdmi_mode=87 hdmi_timings=1080 1 26 4 50 1920 1 8 2 6 0 0 0 60 0 135580000 3 I do it and that working fine I add this to ajust resolution max_framebuffer_width=1080 max_framebuffer_height=1920 framebuffer_width=600 framebuffer_height=1080 But all that is on RasberryPI and i would like use it on BananaPI M1 on M2 zero I tried to write it in armbianEnv.txt but the resolution of display haven't changed How i can do that on BananaPi ?
  15. This falls somewhere between "how-to", "research", and "development", so I stuck it here. @adafruit is working to target CircuitPython to Armbian devices, something that will be a bit of a task. I've been playing with the code to get it working on my Tritium H3, finally did (some extra sudo-ing was needed), so I'll probably toss in a couple board definitions/help here and there if I can. it had hijacked a C2 thread (not completely, it was at least about using it on the C2), and I thought it best to continue discussion here. @chwe, @sgjava, and @Larry Bank all have various experience with various GPIO tools, their interest may vary. My current observations, doing some hacking to make it run on my board: superuser is necessary to get to the gpio I had to install wheel before blinka or setup failed spectacularly board detection is crazy (I noticed in the PR that it is planned to get worked on) I had to inject my board name into seemingly 30000000000000 files. Next up is to actually use it to read something/write something, and make a PR or two.
  16. Hi All, I am trying to use a 4x4 matrix keypad on Orange pi GPIO ,I am connecting the keypad with 8 GPIO's 4 GPIOs for rows, 4 for coloumns ,the problem I am facing is when I try to test the keypad few keys are read only on repeated attempts or pressing. The following is my code. Is this because of Hardware debouncing?. I don't have much knowledge on debouncing. I suspect there is a delay happening in reading and writing GPIOs , because of user process scheduling can be delayed. I don't think accesing GPIO at faster rate is not possible from user application. Please suggest me the best approach. Please suggest me where I am doing wrong. I appreciate any help, thanks in advance.
  17. Some of the boards supported by Armbian have an mpcie slot. The only one that I know of that also has a sim slot is the celarfog pro. (Correct me if I missed something) I found this little add on board that supposedly adds a sim card to an mpcie modem. Think it might work on some or which of the boards? I looked at this but I get lost in figuring out how to form the udev rules. Anyone get 4g going on Armbian on any board in the US?
  18. Hi, anybody knows what size of a heatsink can I put on an Orange Pi Zero? It is in the small cube enclosure (without additional addon board). Maybe a link to eBay or Aliexpress? Thanks!
  19. Hello, the Rock64 SBC can receive an add-on board with audio ports and an additional ethernet port. I have used it a lot before, with Debian Stretch. With the armbian image it does not work. The reason is simple, this board must be activated by a script which is missing. Ayufan has added a set of scripts in /usr/local/sbin, but they are not present in this build. They can be found here : https://github.com/ayufan-rock64/linux-package/blob/master/root/usr/local/sbin/enable_dtoverlay Then run the necessary command : enable_dtoverlay eth1 ethernet@ff550000 okay and the card is present in ifconfig. Once given an iP address, it works perfectly. Nevertheless, the log indicates a conflct with the ic2 interface. Jul 16 14:39:33 localhost systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon. Jul 16 14:39:33 localhost rc.local[1312]: Applying... Jul 16 14:39:33 localhost rc.local[1312]: /dts-v1/; Jul 16 14:39:33 localhost rc.local[1312]: / { Jul 16 14:39:33 localhost rc.local[1312]: #011fragment@0 { Jul 16 14:39:33 localhost rc.local[1312]: #011#011target-path = "/ethernet@ff550000"; Jul 16 14:39:33 localhost kernel: [ 37.895961] rockchip-pinctrl pinctrl: pin gpio2-25 already requested by ff150000.i2c; cannot claim for ff550000.ethernet Jul 16 14:39:33 localhost kernel: [ 37.895967] rockchip-pinctrl pinctrl: pin-89 (ff550000.ethernet) status -22 Jul 16 14:39:33 localhost kernel: [ 37.895972] rockchip-pinctrl pinctrl: could not request pin 89 (gpio2-25) from group fephyled-rxm1 on device rockchip-pinctrl Jul 16 14:39:33 localhost kernel: [ 37.895976] rk_gmac-dwmac ff550000.ethernet: Error applying setting, reverse things back Jul 16 14:39:33 localhost kernel: [ 37.896167] rk_gmac-dwmac ff550000.ethernet: Looking up phy-supply from device tree Jul 16 14:39:33 localhost kernel: [ 37.896433] rk_gmac-dwmac ff550000.ethernet: clock input or output? (output). Jul 16 14:39:33 localhost kernel: [ 37.896440] rk_gmac-dwmac ff550000.ethernet: Can not read property: tx_delay. Jul 16 14:39:33 localhost kernel: [ 37.896446] rk_gmac-dwmac ff550000.ethernet: set tx_delay to 0x30 Jul 16 14:39:33 localhost kernel: [ 37.896451] rk_gmac-dwmac ff550000.ethernet: Can not read property: rx_delay. Jul 16 14:39:33 localhost kernel: [ 37.896454] rk_gmac-dwmac ff550000.ethernet: set rx_delay to 0x10 Jul 16 14:39:33 localhost kernel: [ 37.896509] rk_gmac-dwmac ff550000.ethernet: integrated PHY? (yes). Jul 16 14:39:33 localhost kernel: [ 37.896644] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_refout Jul 16 14:39:33 localhost kernel: [ 37.896650] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_speed Jul 16 14:39:33 localhost kernel: [ 37.901732] rk_gmac-dwmac ff550000.ethernet: init for RMII Jul 16 14:39:33 localhost rc.local[1312]: #011#011__overlay__ { Jul 16 14:39:33 localhost rc.local[1312]: #011#011#011status="okay"; Jul 16 14:39:33 localhost rc.local[1312]: #011#011}; Jul 16 14:39:33 localhost rc.local[1312]: #011}; Jul 16 14:39:33 localhost rc.local[1312]: }; Jul 16 14:39:34 localhost kernel: [ 37.936441] stmmac - user ID: 0x10, Synopsys ID: 0x35 Jul 16 14:39:34 localhost kernel: [ 37.936452] Ring mode enabled Jul 16 14:39:34 localhost kernel: [ 37.936457] DMA HW capability register supported Jul 16 14:39:34 localhost kernel: [ 37.936461] Normal descriptors Jul 16 14:39:34 localhost kernel: [ 37.936466] RX Checksum Offload Engine supported (type 2) Jul 16 14:39:34 localhost kernel: [ 37.936470] TX Checksum insertion supported Jul 16 14:39:34 localhost kernel: [ 37.936475] Enable RX Mitigation via HW Watchdog Timer Jul 16 14:39:34 localhost kernel: [ 37.936660] of_get_named_gpiod_flags: can't parse 'snps,reset-gpio' property of node '/ethernet@ff550000[0]' Nevertheless, the ethernet port is working. Is this a false alarm ? The Rock64 has two GPIO connectors, and the ethernet port is on the second. But the ic2 should be on the first. Whatever the reason, the port works fine.
  20. Hello! Recently, Armbian Debian 10 was installed on my ODROID-C2 I can't configure lircd, but it worked on Odrobian Debian 9! Please, explain how they configure LIRC to 4.19 now without /dev/lirc*? WBR, WRA-RIPE
  21. I was able to read a DHT22 on PA10 with my Orange Pi Prime using https://github.com/Jeremie-C/OrangePi.GPIO Minimal documentation provided in readme https://github.com/lanefu/DHT22-Python-library-Orange-PI
  22. Hello, I am trying to connect an enc28j60 ethernet port to spi0.0 on an orange pi pc, running armbian (debian stretch 4.19.5). I have the jumpers all connected in what I believe is the correct pattern. I compiled a device tree (overlay?) for the enc28j60 on h3, the dtbo file now exists in /boot/overlay-user/spi-enc28j60.dtbo. /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; /* This fragment is required only if the IRQ pin requires internal pull-up */ fragment@0 { target = <&pio>; __overlay__ { enc28j60_pins: enc28j60_pins { pins = "PA7"; function = "irq"; bias-pull-up; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; enc28j60 { compatible = "microchip,enc28j60"; reg = <0>; interrupt-parent = <&pio>; interrupts = <0 7 2>; /* PA7 IRQ_TYPE_EDGE_FALLING */ spi-max-frequency = <12000000>; status = "okay"; /* These are required only if internal pull-up is used for the IRQ pin */ pinctrl-names = "default"; pinctrl-0 = <&enc28j60_pins>; }; }; }; }; and I configured the /boot/armbianEnv.txt. (I just recently added spi-jedec-nor/spi-add-cs1 just for the hell of it to test). verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=1b49372a-ea5b-42f6-9e60-036606066891 rootfstype=ext4 overlays=spi-add-cs1 spi-jedec-nor spi-spidev param_spidev_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But the device still does not come up. I get a dmesg of "spidev spi0.0: probing from DT" and no errors anymore. And I configured the /etc/hosts/interfaces file, but ip a just shows an "unknown" state instead of up or down. All the tutorials (for raspberry pi's on raspbian... seriously only 2 people have ever tried this on orange pi/armbian?) I can find only show these few steps. And I can't even think of how to go about troubleshooting this. I am kind of new though so maybe I am missing something. What else should I try?
  23. I have orange pi pc with debian. Orange Pi is connected via mobile connection (Wifi AP). Every day I lose more than 500mb data to nothing. What I must disable to normal operations without any update?
  24. I'm not sure what will and won't be a worthy overlay to put directly into Armbian itself with the current script structure, I intend to document the ones I add here, @martinayotte may as well if he's bored. :-P I will be focusing on RPi GPIO compatibles, since those are nice pre-packaged devices in general. I have Tinker, RockPi 4, Le Potato/K2/C2, Tritium H2+/3/5, Rock64, Renegade, and some others. Everything here is a placeholder at the moment. Status Tinker Le Potato Meson64 Renegade Tritium Automation Hat Generic DAC (Pi) MCC 118 DAQ MicroDot PHAT Inky WHAT (e-ink) ENC28J60 for Pi