Robert LabTeam

I have noticed a very weird problem: connection works for some time (several hours or sometimes days) and then stops. Once it stopped working (connection between my mobile app and OrangePi) I have checked on the board: - ping 8.8.8.8 - OK - ping (router IP) - OK - ping (broadcast ) - FAILED - ping (PC or any other device connected to the network) - FAILED In all cases, Wireshark captures the ping requests. Once I tried to ping OrangePi board from my PC, I see in&out ping packet on OPI board by Wireshark. It seems like some lower layer or router (the same on two different) blocks the outgoing connection. Ideas? (WiFi power management off, no firewall) What helps: - turn on/off wifi adapter. What I have noticed - route -n shows one additional entry: 192.168.31.0 0.0.0.0 255.255.255.0 U ... when the outgoing connection works. So it seems that somehow my IP routing table changed How? Diagnosis information is here(armbianmonitor returns that it cannot be uploaded due to network issues, but it worked): http://ix.io/1DEO (Network/firewall problem detected. Not able to upload debug info.)

And the same command on Samsung memory (eMMC was detected): [ 0.000000] Kernel command line: root=UUID=8591b60d-2481-4c21-806f-a9146bdb782f rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=cd93fc55-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1 [ 1.223368] [mmc]: SD/MMC/SDIO Host Controller Driver(v1.111 2015-4-13 15:24) Compiled in Nov 22 2017 at 13:44:04 [ 1.223406] [mmc]: get mmc0's sdc_power is null! [ 1.223436] [mmc]: get mmc1's sdc_power is null! [ 1.223445] [mmc]: get mmc1's 2xmode ok, val = 1 [ 1.223454] [mmc]: get mmc1's ddrmode ok, val = 1 [ 1.223484] [mmc]: get mmc2's sdc_power is null! [ 1.223493] [mmc]: get mmc2's 2xmode ok, val = 1 [ 1.223502] [mmc]: get mmc2's ddrmode ok, val = 1 [ 1.223516] [mmc]: MMC host used card: 0x7, boot card: 0x0, io_card 2 [ 1.227308] [mmc]: sdc0 power_supply is null [ 1.339175] mmc0: new high speed SDHC card at address aaaa [ 1.339742] mmcblk0: mmc0:aaaa SC16G 14.8 GiB [ 1.342545] mmcblk0: p1 [ 1.343211] mmcblk mmc0:aaaa: Card claimed for testing. [ 1.343227] mmc0:aaaa: SC16G 14.8 GiB [ 1.344811] [mmc]: sdc2 power_supply is null [ 1.464544] mmc2: new high speed DDR MMC card at address 0001 [ 1.465129] mmcblk1: mmc2:0001 8WPD3R 7.28 GiB [ 1.465380] mmcblk1boot0: mmc2:0001 8WPD3R partition 1 4.00 MiB [ 1.465617] mmcblk1boot1: mmc2:0001 8WPD3R partition 2 4.00 MiB [ 1.466642] mmcblk1: p1 [ 1.469477] mmcblk1boot1: unknown partition table [ 1.471042] mmcblk1boot0: unknown partition table [ 1.471271] mmcblk mmc2:0001: Card claimed for testing. [ 1.471284] mmc2:0001: 8WPD3R 7.28 GiB [ 1.472856] [mmc]: sdc1 power_supply is null [ 1.528224] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.529882] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.531514] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.534440] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 1.631553] mmc1: new high speed SDIO card at address 0001 [ 8.337376] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 11.001099] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 11.070301] dummy_sdmmc: probe of mmc1:0001:1 failed with error -123 [ 11.070349] dummy_sdmmc: probe of mmc1:0001:2 failed with error -123 [ 11.070557] mmc1: card 0001 removed [ 11.070816] [mmc]: sdc1 power_supply is null [ 11.074947] [mmc]: sdc1 power_supply is null [ 11.127956] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 11.129516] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 11.131107] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 11.133882] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 11.224041] mmc1: new high speed SDIO card at address 0001 [ 11.240329] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter [ 11.240449] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter

[ 0.000000] Kernel command line: root=UUID=8591b60d-2481-4c21-806f-a9146bdb782f rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=cd93fc55-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1 [ 1.213356] [mmc]: SD/MMC/SDIO Host Controller Driver(v1.111 2015-4-13 15:24) Compiled in Nov 22 2017 at 13:44:04 [ 1.213395] [mmc]: get mmc0's sdc_power is null! [ 1.213424] [mmc]: get mmc1's sdc_power is null! [ 1.213434] [mmc]: get mmc1's 2xmode ok, val = 1 [ 1.213443] [mmc]: get mmc1's ddrmode ok, val = 1 [ 1.213473] [mmc]: get mmc2's sdc_power is null! [ 1.213483] [mmc]: get mmc2's 2xmode ok, val = 1 [ 1.213492] [mmc]: get mmc2's ddrmode ok, val = 1 [ 1.213505] [mmc]: MMC host used card: 0x7, boot card: 0x0, io_card 2 [ 1.217283] [mmc]: sdc0 power_supply is null [ 1.329173] mmc0: new high speed SDHC card at address aaaa [ 1.329733] mmcblk0: mmc0:aaaa SC16G 14.8 GiB [ 1.332534] mmcblk0: p1 [ 1.333183] mmcblk mmc0:aaaa: Card claimed for testing. [ 1.333199] mmc0:aaaa: SC16G 14.8 GiB [ 1.334782] [mmc]: sdc2 power_supply is null [ 1.472884] mmc2: unrecognised EXT_CSD revision 8 [ 1.472905] mmc2: error -22 whilst initialising MMC card [ 1.473035] [mmc]: sdc2 power_supply is null [ 1.477145] [mmc]: sdc2 power_supply is null [ 1.567456] mmc2: unrecognised EXT_CSD revision 8 [ 1.567488] mmc2: error -22 whilst initialising MMC card [ 1.567643] [mmc]: sdc2 power_supply is null [ 1.571824] [mmc]: sdc2 power_supply is null [ 1.675883] mmc2: unrecognised EXT_CSD revision 8 [ 1.675919] mmc2: error -22 whilst initialising MMC card [ 1.676074] [mmc]: sdc2 power_supply is null [ 1.680111] [mmc]: sdc2 power_supply is null [ 1.804071] mmc2: unrecognised EXT_CSD revision 8 [ 1.804109] mmc2: error -22 whilst initialising MMC card [ 1.804260] [mmc]: sdc2 power_supply is null [ 1.808537] [mmc]: sdc1 power_supply is null [ 1.858522] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.860256] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.862010] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.865025] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 1.868606] mmc1: queuing unknown CIS tuple 0x81 (9 bytes) [ 1.965277] mmc1: new high speed SDIO card at address 0001 [ 8.127876] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 10.695377] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 10.850354] dummy_sdmmc: probe of mmc1:0001:1 failed with error -123 [ 10.850409] dummy_sdmmc: probe of mmc1:0001:2 failed with error -123 [ 10.850649] mmc1: card 0001 removed [ 10.850954] [mmc]: sdc1 power_supply is null [ 10.855213] [mmc]: sdc1 power_supply is null [ 10.907235] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 10.908787] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 10.910345] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 10.913116] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 10.916502] mmc1: queuing unknown CIS tuple 0x81 (9 bytes) [ 11.002973] mmc1: new high speed SDIO card at address 0001 [ 11.019839] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter [ 11.019933] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter Here you go.

I am sure - I have 100 pcs of this boards. Sold already 1000 with KLM8G1GETF - no issues. The latest batch has different memory chip and I do not see this memory in fdisk -l. The old boards indicate eMMC memory.

Issue found! Orange PI changed eMMC from KLM8G1GETF to KLM8G1WEPD. The difference is eMMC 5.0 vs 5.1 and maybe more. The key things is that Armbian (checked using 5.35 and the latest one) does not see this memory (fdisk -l)!! I have noticed it on OPI0 Plus 2 H3. PCB boards are the same, only memory model no. difference. Someone solved it or noticed the same? Confused 🤨

Hi guys, I am using bluetooth (AP6212) and it works pretty well. After several hour of open connection I lost signal and need to reconnect. But I can't. Bluetoothctl returns "No default controller available", however one minute before it worked I tried to restart bluetooth service, rfkill (soft and hardware does not lock anything) , but the problem still exist. Only reboot can back the module to work. Is there any other way to restart the module without reboot?

You are right. However is still shares the same integrated circuit, so WiFi can interrupt BT. I disabled almost all network services. I am wondering if there is a way to set TX output from this module? Maybe it is not set to max. I noticed that if I reduce router output power, it drops connection more often. Maybe, the wifi module attempts to reconnect or repeat some packets and it takes too much time for the module. The problems is also that simple restart bt (on/off) does not help if I got "Invalid command" error while trying to pair the device. I need to reboot. Is there any way to do it without reboot?

Hi, I use OPI0+. Bluetooth works well when using WiFi as a client. In access point I got an error like"Invalid command" "ConnectionAttemptFailed". Is there any way to fix it?

Hi, I am using Bluetooth and WiFi in the same time. Bluetooth is using for a whole time and WiFi 1 time per minute. So, I don't need WiFi connection very fast and do need most of network services. Due usage of AP6210 module, WiFi and BT shares the same communication channel (UART). I continuously send data (1Mbps) via Bluetooth. WiFi is used by my app 1 time per minute.The problem is that Bluetooth drops communication for about second. Reducing BT speed does not help. I noticed that when I download file from OPI board,that drops occurs much often. It seems that WiFi has a higher priority than BT in communication. Strange thing is that when I don't use WiFi network, it still drops randomly. I think some services in background use network. Is there any way to set WiFI connection less important than Bluetooth communication or you have different ideas?

Hi! I am trying to set sudo chmod 777 /sys/class/leds/red_led/brightness It works, but after restart the system reverts my changes. I think there is some init file that changes it. Any tip?

I would love to use something faster...the current script shows 75 minutes, but it took about 35 min. I use SanDisk SDHC 10 class A1. I am looking forward enhanced script.

Thanks, I will try it soon. I am wondering if it is some fault that nand-sata-install takes 75 minutes to transfer 4744MB...maybe is there a way to speed up rsync or replace to different command? Any ideas?

Hi I am trying to prepare SD card that I will be able to copy the same image to several boards: - I have my final OS on EMMC of "mother" board(installed with nand-sata-install), - copy os to SD card using dd if=...of=.., so I got .img file How to clone emmc content to another boards? I know I can use nand-sata -install (preprare my final OS on SD card and the copy to all boards), but it is not quick way. Raw copy is much faster. Any ideas? Of course dd if=my.img of=/emmc does not work - some problem with boot.

Hi @lex, To reach 60 FPS, or more, just changa VTS/HTS value. I created some tool (I launch it in DevC++) that shows what is the end FPS and some other parameters. Just play with the registers: #define MCLK (20*1000*1000) --> usually 24 MHz is used #define MCLK_DIV 1 #define REG_3034 0x18 #define REG_3037 0x4 #define REG_3036 (4*20) #define REG_3035 0x11 #define REG_3108 0x01 And VTS /HTS values here: hts_high = 0x07; // 0x380c hts_low =0xf4; // 0x380d vts_high = 0x07; //0x380e, vts_low = 0xac; //0x380f I have also noticed that almost all drivers are not appropriate for OV5640 (it seems they wrtitten based on OV5642 software application note - for example max lines is different for both sensors: 1964/1968). I found this doc for OV5640 and fixed some things. You can also find there 90 FPS for VGA configuration: https://wenku.baidu.com/view/6b48a191f90f76c661371afa.html main.cpp

Hi guys, I am trying to make autostart of my app, but the app is launched by bash script that automatically launch the app again when crashed: (it finds the latest application version and then launch...then it is waiting for crash , rerun and wait again) - when I placed this script in /etc/profile.d, my system got stuck on my application view without loading desktop (and other needed services). #!/bin/bash sleep 30 while true do str=`ls /home/lufa/Shared/QT/xxxx* | sort -n -t _ -k 2 | tail -n1` if [ ! `pgrep $str` ] ; then $str fi sleep 30 done Thus, I added autostart.sh.desktop file in ~/.config/autostart/ like this: [Desktop Entry] Type=Application Name=Autostart Exec="/home/lufa/Shared/autostart.sh" Hidden=false NoDisplay=false X-GNOME-Autostart-enabled=true Unfortunately my app was not automatically launched Any ideas? I assume that the progblem is GUI app. I got from crontab log - "QXcbConnection: Could not connect to display" - despiting I put "sleep 30" in my bash screipt to wait for ready Desktop.