Search the Community

Showing results for tags 'mainline'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Allwinner H6
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 898 results

  1. K-worker takes 10-20 % of one cpu core with later kernels. Does the 4.17 kernel still have this problem? Or is bionic a solution?
  2. Hi! Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One. So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay. But for now, it fails to compile with: $ sudo armbian-add-overlay sun8i-h3-csi.dts Compiling the overlay Error: sun8i-h3-csi.dts:27.23-24 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay My current overlay looks like this: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { csi_mclk_pin: csi-mclk-pin { pins = "PE1"; function = "csi"; }; }; }; fragment@1 { target = <&i2c2>; __overlay__ { status = "okay"; ov5640: camera@3c { compatible = "ovti,ov5640"; reg = <0x3c>; pinctrl-names = "default"; pinctrl-0 = <&csi_mclk_pin>; clocks = <&ccu CLK_CSI_MCLK>; clock-names = "xclk"; AVDD-supply = <&reg_aldo1>; DOVDD-supply = <&reg_dldo3>; DVDD-supply = <&reg_eldo3>; reset-gpios = <&pio 4 14 GPIO_ACTIVE_LOW>; /* CSI-RST-R: PE14 */ powerdown-gpios = <&pio 4 15 GPIO_ACTIVE_HIGH>; /* CSI-STBY-R: PE15 */ port { ov5640_ep: endpoint { remote-endpoint = <&csi_ep>; bus-width = <8>; data-shift = <2>; /* lines 9:2 are used */ hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; fragment@2 { target = <&csi>; __overlay__ { status = "okay"; port { csi_ep: endpoint { remote-endpoint = <&ov5640_ep>; bus-width = <8>; hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; So the line 27, which seem to trigger the error is: `clocks = <&ccu CLK_CSI_MCLK>;` Also, according to the documentation, the regulator fields are required but this board does not have much regulators (like AXP209), so I have no idea what to write here. But this is my first time writing a device-tree overlay so I am not sure what is wrong with this line. Could someone guide me to get my overlay right? And, does anyone already got the CSI interface working with OV5460 sensor on a H3 based board? Thank you.
  3. Using Armbian_20.02.1 with 5.4 kernel on NEO2 board, I'm running into an issue trying to get the USB OTG working with the g_ether module. When I run modprobe g_ether I see the following in dmesg: [ 490.490582] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I've also tried compiling my own img using the Armbian builder but it looks like all the correct OTG options are already selected by default. Any ideas what I'm doing wrong?
  4. Hello people, I use a Tinker Board as a low power desktop computer for browsing, office documents and general tinkering, and after all this time it got personalized enough to worry about loosing all this setup and it is a hassle to just overwrite everything every time a new image comes around. Was wondering if it is possible to use apt dist-upgrade as means to get from Bionic Desktop 5.4 to Focal Desktop 5.4 as can be done on x86 platforms without breaking everything?
  5. I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed. I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port. I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware. Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 600 at 60Hz using xrandr Exactly the same settings on TinkerOS works perfectly., but has many other issues! In the /var/log/Xorg.0.log file there is an message Allocate new frame buffer 1024 x 600 stride failed to set mode : Invalid argument. I used cvt to generate the modeline using settings 1024 600 60 then I used xrandr --newmode and added the modeline xrandr --addmode HDMI-1 1024x600_60.00 When I set the output to use this setting xrandr --output HDMI-1 --mode "1024x600_60.00" I get the error crtc 0 failed. As mentioned this works on TinkerOS and is the device that is included in the tested 3rd party hardware. What I am doing wrong? Thanks in advance.
  6. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.
  7. Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if a working mainline kernel with DSI for the Pine 64 is starting to look like a possibility and if it might be possible to include in an armbian build. I might be able to do some testing of anyone can guide me in making a build with the necessary patches.
  8. Just wanted to note this - target NanoPi NEO2 - task at hand is Byte-UnixBench.... more to follow...
  9. Enable in armbian-config USB and this no detect USB OTG and additional USB host on the board no working any usb device (microphone, usb storage, keyboard, etc.) that connects detects it Any help you can give me
  10. I am using a orangepi win plus. I have attached a ssd1306 OLED display to the board, using i2c1 interface, using the luma.oled library as driver. import sys from PIL import Image from PIL import ImageDraw from PIL import ImageFont import subprocess from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306, ssd1325, ssd1331, sh1106 from time import sleep serial = i2c(port=1, address=0x3C) device = ssd1306(serial, rotate=0) width=device.width height=device.height image ='1', (device.width, device.height)) # Get drawing object to draw on image. draw = ImageDraw.Draw(image) # Draw a black filled box to clear the image. draw.rectangle((0,0,device.width,device.height), outline=0, fill=0) padding = 2 top = padding bottom = device.height-padding # Move left to right keeping track of the current x position for drawing shapes. x = 0 while True: # Draw a black filled box to clear the image. draw.rectangle((0,0,width,height), outline=0, fill=0) # Shell scripts for system monitoring from here :$ cmd = "hostname -I | cut -d\' \' -f1" IP = subprocess.check_output(cmd, shell = True ) cmd = "top -bn1 | grep load | awk '{printf \"CPU Load: %.2f\", $(NF-2)}'" CPU = subprocess.check_output(cmd, shell = True ) cmd = "free -m | awk 'NR==2{printf \"Mem: %s/%sMB %.2f%%\", $3,$2,$3*100/$2 }'" MemUsage = subprocess.check_output(cmd, shell = True ) cmd = "df -h | awk '$NF==\"/\"{printf \"Disk: %d/%dGB %s\", $3,$2,$5}'" Disk = subprocess.check_output(cmd, shell = True ) # Write two lines of text. draw.text((x, top),"IP:"+str(IP,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+8),str(CPU,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+16),str(MemUsage,encoding = "utf-8"), font=font, fill=255) draw.text((x, top+25),str(Disk,encoding = "utf-8"), font=font, fill=255) device.display(image) sleep(0.5) At the kernel version 5.3.9, the display worked perfectly, without any problem. But after updating the kernel version to above 5.4.20, the same code don't work at all. Traceback (most recent call last): File "./", line 12, in <module> device = ssd1306(serial, rotate=0) File "/usr/local/lib/python3.6/dist-packages/luma/oled/device/", line 188, in __init__ self.clear() File "/usr/local/lib/python3.6/dist-packages/luma/core/", line 46, in clear self.display(, self.size)) File "/usr/local/lib/python3.6/dist-packages/luma/oled/device/", line 220, in display File "/usr/local/lib/python3.6/dist-packages/luma/core/", line 46, in data File "/usr/local/lib/python3.6/dist-packages/luma/core/interface/", line 119, in data write(list(data[i:i + block_size])) File "/usr/local/lib/python3.6/dist-packages/luma/core/interface/", line 128, in _write_large_block self._bus.i2c_rdwr(self._i2c_msg_write(self._addr, [self._data_mode] + data)) File "/usr/local/lib/python3.6/dist-packages/smbus2/", line 637, in i2c_rdwr ioctl(self.fd, I2C_RDWR, ioctl_data) TimeoutError: [Errno 110] Connection timed out Because the luma.oled library just uses the linux kernel i2c interface like the /dev/i2c-1, so it is more likely a bug related to kernel.
  11. Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter. Anyone else is having these problems with the mainline 5.4.28 kernel build?
  12. Device: Orange Pi +2e. Environment one 16GB SD Card and 16GB eMMC onboard. Output from Armbianmonitor attached. The eMMC device onboard is always detected as mmcblk2. Irrespective of whether SD Card is present or not or if you boot from SD Card or eMMC. This is observed only on 20.05 and 20.08 builds. It does not happen on 20.02 build. [ 3.769548] sun8i-h3-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pc not found, using dummy regulator [ 3.781702] mmc0: host does not support reading read-only switch, assuming write-enable [ 3.784384] mmc0: new high speed SDHC card at address aaaa [ 3.785778] mmcblk0: mmc0:aaaa JULIE 14.8 GiB [ 3.790317] mmcblk0: p1 [ 3.790822] mmc1: new high speed SDIO card at address 0001 [ 3.795670] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB [ 3.915829] mmc2: new DDR MMC card at address 0001 [ 3.917341] mmcblk2: mmc2:0001 AJTD4R 14.6 GiB [ 3.918284] mmcblk2boot0: mmc2:0001 AJTD4R partition 1 4.00 MiB [ 3.919325] mmcblk2boot1: mmc2:0001 AJTD4R partition 2 4.00 MiB [ 3.922791] mmcblk2: p1 [ 4.143718] usb 6-1: new full-speed USB device number 2 using ohci-platform --Rajesh
  13. In the FriendlyARM thread;t=1427&amp;p=5685#p5685 we did try to use A64 images from the Pine64 or the BananaPi M64 with the NanoPi A64. The last times we did that with less success - OK Sytem is running but Network/Sound has to added via USB. No suppport for the onboard devices But today a user did wrote that - with the actual stable Pine64-image ( Armbian_5.69_Pine64_Debian_stretch_next_4.19.13 ) WiFi is useable. So I flasded the Pine64-image to a MicroSDCard and did boot. Additiionally I did see with "aplay -l" the HDMI and the analog Sound-device. But ethernet isnt "connected" right via the .dtb armbian inside can see the ethernet-part of the SoC (set IP and see MAC) and the external RTL8122E Phy blinks the Link and Transfered-Packets via LED.... My first idea was to edit the Pine64 DTB to match the NanoPI A64 DTB in the ethernet-part - but with these Pins & PHandle's I did get stuck BUT my second idea did work much better, because in the armbian-build-system I also did see the sun50i-a64-nanopi-a64.dtb So I checked the board-config-file for the pine64.conf ( under ./build/config/boards/ ) - there is an entry for a defconfig file and the armbin-build-system has also a defonfig file for the nanopi-a64 ./build/cache/sources/u-boot/v2018.11/configs/nanopi_a64_defconfig while the NanoPi A64 isnt (official) supported by the Meneu-System of the armbian-build-system. So I copied ./build/config/boards/pine64.conf to ./build/config/boards/nanopia64.conf and did edit it like in the following way: # A64 quad core 512MB-2GB SoC GBE BOARD_NAME="NanoPiA64" BOARDFAMILY="sun50iw1" BOOTCONFIG_DEFAULT="sun50iw1p1_config" BOOTCONFIG="nanopi_a64_defconfig" # MODULES="sunxi_codec sunxi_i2s sunxi_sndcodec 8723bs" MODULES_NEXT="" # KERNEL_TARGET="default,next,dev" CLI_TARGET="bionic,stretch:next" DESKTOP_TARGET="xenial:default" # CLI_BETA_TARGET="" DESKTOP_BETA_TARGET="" and did compile for the NanoPi A64 with ./ EXPERT="yes" in ./build/ Now I could select the NanoPi A64 (falsely) as supported board and did select DEV (armbian 5.71 with Kernel 4.20) I did build the console and the Desktop-version. In the console-version I was happy to see eth0 & wlan0 working, but the HDMI and analog soundsystem is missing (which was visible in Pine64 next 4.19.13) So there was no need for a RTL8211E-driver (because its only a PHY) like I did read before at In the Desktop-version the GUI did start without problems (not fast, but useable) - like on a older pinebook (a64) build Maybe DEV was "too much"? I will try the NEXT for my NanoPi A64 File Or maybe the nanopi A64 dtb isnt correct on the "sound-part"?
  14. I have a 1 GB Renegade board and downloaded Armbian_19.11.3_Renegade_buster_current_5.3.11 image to install. Noticed it was only 510MB of RAM. Relevant extracts from serial log: U-Boot 2017.09-armbian (Nov 19 2019 - 00:09:05 +0100) Model: Firefly ROC-RK3328-CC DRAM: 510 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 5.3.11-rockchip64 System load: 0.10 0.14 0.06 Up time: 2 min Memory usage: 22 % of 472MB IP: CPU temp: 44°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Nov 23 22:48:50 2019 Using armbian-config I downgraded to kernel 4.4.198 and I now have 919MB of RAM. U-Boot 2017.09-armbian (Nov 19 2019 - 00:01:47 +0100) Model: Firefly ROC-RK3328-CC DRAM: 1022 MiB ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to Armbian Buster with Linux 4.4.198-rockchip64 System load: 0.10 0.09 0.03 Up time: 2 min Memory usage: 8 % of 919MB IP: CPU temp: 43°C Usage of /: 5% of 29G [ General system configuration (beta): armbian-config ] Ray
  15. Today I swapped my old Neo2 against a Neo2 LTS 1GB in my NAS case - so I had a old Neo2 512MB free for the black Aluminum-OLED-case which I got in a drawer. Now I did try to activate the OLED in ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi64 Linux npi-neo2-27 4.19.4-sunxi64 #6 SMP Fri Nov 30 14:02:43 +03 2018 aarch64 GNU/Linux First (like on a i2c-clock" I activated i2c0 in armbian-config: root@npi-neo2-27( armbian-config System --> Hardware --> [*] i2c0 After the reboot I checked for the i2c-OLED-device and got: root@npi-neo2-27( apt install i2c-tools root@npi-neo2-27( i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- After some trial and error(-messages) I did found the following dependencies for compiling/installing the software for the OLED-Board: apt-get install python-setuptools libjpeg-dev After that I did the normal "5 Enable NanoHat-OLED manually" from with root@npi-neo2-27( cd /home/guido root@npi-neo2-27( git clone root@npi-neo2-27( cd NanoHatOLED root@npi-neo2-27( ./ And after the next reboot the OLED-Display did work
  16. This topic has been discussed earlier but there is not concrete mechanism explained to achieve this. Ideally I would like to display a boot logo or boot splash during startup. The device is Orange Pi Plus 2e. As per experience and as mentioned on this forum earlier plymouth was not useful in this case. I tried to set logo="enabled" in /boot/armbianEnv.txt but this doesn't help. When Armbian loads for first time on the device from the image downloaded from this site, it displays 'Initializing Boot Loader' logo image. Pretty cool!!! Can we have something like this for a custom image displayed each time on reboot. I understand that this will be displayed only till kernel loads, but that is good enough of me. I can settle with this limited functionality, but am lost on how to do this. Any pointers or suggestion will be highly appreciated. Stay safe! Regards -R
  17. From reading through the forums I cobbled together what I thought might work for getting spi nor to boot, but it fails: Activate the spi-jedec-nor overlay in /boot/armbianEnv.txt : overlays=spi-jedec-nor param_spinor_spi_bus=0 Then, after reboot, "cat /proc/mtd" should produce something like this : dev: size erasesize name mtd0: 00200000 00001000 "spi0.0" Here is where it fails - I just get the heading, with no mtd0: 00200000 00001000 "spi0.0". Should I be using a different param_spinor_spi_bus? I assume that once that works, the following will work? apt-get install mtd-utils cat /usr/lib/linux-u-boot-next-orangepizeroplus_5.38_arm64/sunxi-spl.bin /usr/lib/linux-u-boot-next-orangepizeroplus_5.38_arm64/u-boot.itb > /usr/lib/linux-u-boot-next-orangepizeroplus_5.38_arm64/u-boot-sunxi-with-spl.bin flashcp /usr/lib/linux-u-boot-next-orangepizeroplus_5.38_arm64/u-boot-sunxi-with-spl.bin /dev/mtd0
  18. Hello, I am trying to use g_serial but it does not work. I'm using fresh install of armbian (Armbian_5.38_Orangepilite_Debian_stretch_next_4.14.14.7z), with apt-get update/apt-get upgrade/armbianconfig Install headers. Linux orangepilite 4.14.15-sunxi #28 SMP Mon Jan 29 07:24:48 CET 2018 armv7l GNU/Linux This is the overlay I use to enable OTG: sudo /usr/sbin/armbian-add-overlay usbotg.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "otg"; status = "okay"; }; }; }; After rebooting OPi there are several errors like this in syslog musb_g_ep0_irq 712: SetupEnd came in a wrong ep0stage out/status The other computer is running Ubuntu 16.04 LTS I use small USB hub (full speed only) between my PC and OPi lite but if I make direct connection the errors are same. If I unplug and plug USB cable between OrangePi Lite and my computer (or if I plug the cable after OPi boots) I get same errors. I got same errors when trying with .g_ether usb 7-2.1: new full-speed USB device number 4 using uhci_hcd usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: new full-speed USB device number 5 using uhci_hcd usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: device descriptor read/64, error -71 usb 7-2.1: new full-speed USB device number 6 using uhci_hcd usb 7-2.1: device not accepting address 6, error -71 usb 7-2.1: new full-speed USB device number 7 using uhci_hcd usb 7-2.1: device not accepting address 7, error -71 usb 7-2-port1: unable to enumerate USB device The result of sudo armbianmonitor -u is here Regards
  19. Hi, I'm here again, the quarantine is almost over (sadly 'cause here in italy we are a bunch of a****le) and I finally get rid of my kodi 17 on retrorangepi 4.2 (old) that give me a lot of problems (with wifi connection lost, scraper that didn't update, and freeze, not for sure a problem with retrorangepi itself). so... I have something in my mind now that I'm back to home with my new FTTH internet connection. I want to setup an armbian image with or withot desktop for octoprint Armbian with 5.4 kernel (xfce debian) is really slow and temperature (with heatsink) don't go under 60°C on idle, with retrorangepi based on Debian Jessie, temps go from 45°C to 50°C on idle. So maybe - MAYBE - the problem could be the kernel? If so, because I don't care about security in this particular case (I need OPI just to execute octoprint on local), Could downgrade kernel (by using a legacy version) bring to an improvement on performance/temp? and give me the possibility to install package like octoprint or deluge? or some dependancy are linked to the kernel version? I know that maybe it will be a stupid question, but I'm wasting a lot of time with this board, because I'm so stubborn (and broke). thank you
  20. as described in: it's possible to use meson HW video codec now, but in the URL, not very clear, does any one know how to use it?
  21. If anyone has troubles with HDMI when using 5.x kernels, and has enough skills to recompile an armbian, give this a try : And then either answer here, or in the bug report :
  22. Hello, Wish a good health everyone nowadays! I'm using Orange Pi PC Plus with small aluminium heatsink running Armbian Buster (mainline kernel 5.4.y). SD Card is Samsung EVO Plus 32gb. The CPU governor was set to 480 to 1200, conservative. The system are fresh, just after install. After ~5 minutes of idle uptime temperature comes to 85 and up. Is that heatsink are not good enough? And the second issue I've faced - too quiet sound output from AV-out. The most quiet is Chromium, it is nasty quiet. Sound from local video files in mpv player are bit(2 times) louder both from mp4 and webm, also mp3. Have not tested HDMI(because my display have only DVI). And when I tested it again before posting, Bluetooth A2DP audio stopped working with my phone. The sound from phone over BT was bit louder, than from Chromium, same as in mpv player. Thanks, Paul
  23. Hello,Respected Developers: I'm an Orange Pi user.In the process of using the armbian, I encountered serious problems. My Control Board is Orange Pi PC Plus.Armbian is "ARMBIAN 5.59 stable Ubuntu 18.04.1 LTS 4.14.65-sunxi" I installed jdk and mysql.And run a JAVA program.I set a time zone for Asia-Chongqing,The system language is Chinese,I use three serial ports. When running for a period of time,There will be bugs.About one to three days. The specific phenomena are as follows: 1.Run "date",the time is 1978. 2.Mysql occupy cpu 195%, occupy mem 27%,systemd occupy cpu 34%,Another systemd occupy cpu 14% ,systemd-jo+ occupy cpu 39%. 3.eth0‘s ip disappear,Unable to connect remotely from the network for ssh.I only use serial port to connect. 4.I can't use the reboot command to restart,I input "reboot",It didn't respond. Time automatically changed to 1978. I hope you can help me solve this problem,Thanks very much.
  24. Hello, I am trying to communicate with a mcp2515 breakout (8Mhz oscillator) on an Orange Pi Pc+ I have modified the breakout following info on Raspberry Pi: HowTo/Quickstart MCP2515 to keep logic level @3v I have two other nodes composed by two Arduinos, with same (not modified) breakout, one that transmits the other receives. I have successfully tested the first breakout (used on OPi) with an Arduino (powered by 3.3v and 5v on TJA1050). It lets me think that hardware is OK. Below photos of wiring (nb: orange wire becomes red, is wired near TJA1050 = 5v): It seems I have the same results with (edited) user_overlay and the compiled one provided in zador.blood.stained's post dmesg| grep 'can\|mcp\|spi' [ 6.701431] mcp251x spi0.0 can0: MCP2515 successfully initialized. [ 28.455699] can: controller area network core (rev 20170425 abi 9) [ 28.471752] can: raw protocol (rev 20170425) The controller seems well seen, I can bring up the can0 interface: sudo ip link set can0 type can bitrate 125000 triple-sampling on sudo ifconfig can0 up ifconfig can0 can0: flags=193<UP,RUNNING,NOARP> mtu 16 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 but candump is mute although the Arduino receiver displays messages from Arduino transmitter. And cansend do not give error but I could not see this messages on Arduino receiver. Does someone would have an idea of what I am missing ?
  25. Hi! New to the forums, this is my first post. I've been trying out some of the pre-built Armbian images on my Orange Pi Zero to get a taste for the OS and it's perfect for my purposes, however I've noticed something odd about the current mainline images that's possibly a small oversight. I browsed the forums before posting and noticed that TV Out functionality has been disabled by default on H3-based boards due to an interference with HDMI output on mainline, which is naturally understandable. There's only one small problem - the same patch has been applied to H2+ boards which lack an HDMI Out altogether. I've explored the image currently provided (the latest Buster/mainline download) and noticed that it too is set to output to HDMI which isn't on the board and isn't supported by the SoC. As such, the board can only operate as headless when those pre-built images are used, which is naturally less than ideal. There *was* a patch available that solved this issue on mainline, however it's rather old, no longer maintained and doesn't work on the latest builds. I'm currently compiling my own image based on the legacy kernel which apparently still supports TV Out by default, but I wanted to ask if it'd be possible for me to adjust the configuration of the current images to simply enable it on what's readily available. I did check /boot/ in search of Script.bin, but the file was not available and armbianEnv.txt doesn't seem to give me the option to change modes, and even if it did, it probably wouldn't change things if the output is disabled altogether. Do you have any advice? I'd very much like to use the latest kernel rather than the legacy one, if possible.