Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. I try to use DS1302 RT Clock for my Orange Pi One that uses armbian. I connected this way: DS3102 VCC -> OrangePi pin 2 ( 5V ) DS3102 GND -> OrangePi pin 9 ( GND ) DS3102 CLK -> OrangePi pin 3 ( TWI0_SDA ) DS3102 DAT -> OrangePi pin 5 ( TWI0_SCK ) I added i2c0 to overlays of /boot/armbianEnv.txt and rebooted. Now when I run "sudo i2cdetect -y 0", I get nothing: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Do you have any idea what should I do to make this work? Any help is appreciated. Thank you
  3. Yesterday
  4. In case you experience instability, read at the download page what you have to do.
  5. T3+ updated to latest kernel, logs: http://ix.io/1MNl iperf ping Absolutely no network problems.
  6. Which O.S and version are you using? Can you share the link to download?
  7. I would check the schematics of the BPi W2 (assuming that those boards are more or less reference design at this part).. Maybe check CS pin during boot? or soldering a logic analyzer to sniff?
  8. next, default -> 4.14.127 dev -> 5.1.15 apt update & apt upgrade
  9. I see now that I gave you wrong instructions, sorry. Uploads for packages that are common to all go to "debs" and script redistribute / link across all different variants. Only distribution specific packages goes into sub dirs ... tree is the same as in build script, which is also behind handling this. I also forgot to mention that it would be best to compile from "cosmetics" branch where a few bugs has been fixed. I'll fix this in next hour. Any input here to help merging or closing is valuable: https://github.com/armbian/build/pulls https://github.com/armbian/build/issues
  10. I'm trying to get a smaller LCD working on my Win Plus (again, I had it before but was on Jessie I think, old at least). You need to use the BCM numbers from gpio readall and map to the physical pins the seller usually gives. For example my screen use pin 18 and 22 for DC and reset, so they map to 68 and 230 for Win Plus (but now I get SPI timing out, at least the pins do "mount" now, when I was trying BCM values for the Lite it's running on - 71 and 2 - I got an error on pins). (These pinouts used in /etc/modprobe.d/fbtft.conf). Sorry for bit confused reply, hope it helps. -- Edit: I was following the same guide you sent also (and all others I could find, plus the older ones I used before) so I guess you took the same steps - After raising max frequency - /boot/armbianEnv.txt -> param_spidev_max_freq=16000000 - (I dont think I changed anything else at least) I got rid of errors from dmesg but the screen is still blank (white) on Win. Edit2: Tried on another sd card (strectch, earlier was on a bionic build), now I again get the same error, SPI timing out and max_freq didnt help this time. Checking what other settings I could have messed with but I'm pretty sure only other thing I changed was the framebuffer used from 8 to 0 or back. Edit3 (and last): I tried the bionic card again, error was back so I dont know why it disappeared. Still no progress beyond this point, if I figure something out I'll update or reply again.
  11. I'm having exactly the same problem as MartyPG13. Mine arrived yesterday and I'm using an image meant for La Potato which is meant to work.
  12. Hi, yes, you can see the boot process from serial. you can follow the instruction in our wiki. After the serial terminal ready, you can press the reset button to see the boot process since very beginning. You should see something like: U-Boot SPL 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-17.10.4 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from MMC1 U-Boot 2018.11-armbian (Jan 20 2019 - 20:02:45 -0800) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) MMC: mv_sdh: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment Model: Helios4 Board: Helios4 SCSI: MVEBU SATA INIT Target spinup took 0 ms. SATA link 1 timeout. AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq led only pmp fbss pio slum part sxs Net: Warning: ethernet@70000 (eth1) using random MAC address - 52:fc:90:b3:be:70 eth1: ethernet@70000 Hit any key to stop autoboot: 3 2 1 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1979 bytes read in 104 ms (18.6 KiB/s) ## Executing script at 03000000 Boot script loaded from mmc 220 bytes read in 86 ms (2 KiB/s) 19717 bytes read in 353 ms (53.7 KiB/s) 4714605 bytes read in 852 ms (5.3 MiB/s) 5460016 bytes read in 1037 ms (5 MiB/s) ## Loading init Ramdisk from Legacy Image at 02880000 ... Image Name: uInitrd Created: 2019-02-07 11:42:01 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4714541 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02040000 Booting using the fdt blob at 0x2040000 Using Device Tree in place at 02040000, end 02047d04 Starting kernel ... But i think you won't see that screen. LED8 near power inlet indicate the input voltage, if it's blink (nothing fancy here, just LED connected to 12V) then it's a hardware problem. most probably the power adapter.
  13. Does grepping your kernel log for "NIC Link is" reveal an unusual number of entries? I experienced odd behaviour when connecting to/through a FritzBox (using multiple devices over Ethernet) a while back. When devices connected to any port set to "Green Mode" the link would seem to drop frequently when idle. The link would come up again when traffic arrived at either end, but a bunch of security protocols timed-out in the process and some applications failed in strange ways. Saturating the link would result in a transfer stall followed by the link going down and then coming back up in 100Mbps mode. Continued saturation would even cause it to go down and come back up at 10Mbps... but at that point data transfer stopped. Software resetting of the link failed to restore it to 1Gbps — it required the power cycling of either the FritzBox or the device. For some utterly unfathomable reason, the link was least stable on Port 4. Port 3 was half as unstable. Port 2 was about 1/10th as unstable. Port 1 was completely stable. However, since all local traffic had to use at least two LAN ports I ended up with instability regardless of whether I was on the sending or receiving end. Forcing all four LAN ports into "Power Mode" — regardless of whether they needed to be there or not — solved the problem.
  14. @imikei Youve not mentioned which box you have.... However I think you may end up needing to reset it back to factory (if its not even booting to the internal Android OS anymore), so Booting Problems section of this post. Once thats done, if youre sure your using the correct DTB for your box, Id suggest trying an earlier build of Armbian or one with a different kernel version to see if that gets you working. Im guessing you mean username/password at the initial text screen where you log in as root and change the passwords etc.
  15. @balbes150 Is there any existing scripting to make u-boot/kernel/image or it has to be make?
  16. looks promising. Surprised that they included dual display output. I wonder what the Performence of the videocore VI will be like.
  17. If I convert DTB to DTS (and back) and add this: /* There's the BT part of the AP6256 connected to that UART */ &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; uart-has-rtscts; status = "okay"; bluetooth { compatible = "brcm,bcm4345c5"; clocks = <&rtc 1>; clock-names = "lpo"; device-wakeup-gpios = <&r_pio 1 2 GPIO_ACTIVE_HIGH>; /* PM2 */ host-wakeup-gpios = <&r_pio 1 1 GPIO_ACTIVE_HIGH>; /* PM1 */ shutdown-gpios = <&r_pio 1 4 GPIO_ACTIVE_HIGH>; /* PM4 */ max-speed = <1500000>; }; }; And copy https://github.com/orangepi-xunlong/OrangePiH6_external/tree/master/ap6256 to: /lib/firmware/brcm/(BCM4345C5.hcd) Am I correct that it will it work then? (I'm using a OPi3)
  18. Dear Armbian team, I am using debian stretch with orange pi PC ( Linux orangepipc 4.19.38-sunxi #5.83 SMP Fri May 3 23:33:25 CEST 2019 armv7l GNU/Linux ). At the moment by default when I press the power button, it shutdowns the orangepi pc, and I have to plug off/on the power supply to reboot the device. I would like to modify this behavior, to program custom actions when the button is pressed. If possible it would be nice to be able to distinguish between short press and long press. I tried without success to follow the manual instructions, and add the custom overlay gpio-button.dts. Also tried the acpi package approach without access. Could you please help me on this issue? Best regards, Etienne
  19. Thanks, I don't know how to do that and I'm not a "dts/dtb expert". Is there any guide on how to get this going? (not just bluetooth, als odts/dtb in generally). I'm interested and eager to learn but don't know where to start with this. Edit: I have absolutely no idea what I'm doing... But found this out looking at the schematics: PIN Define CFG PL10 BT-WIFI-ON 1 PM0 WL-WAKE-AP 0 PM1 BT-WAKE-AP 0 PM2 AP-WAKE-BT 1 PM3 WL-REG-ON 1 PM3 BT-REG-ON 1 I also found out that the schematics are the same as the AP6255. Edit2: Also found this topic.... Maybe if I convert DTB to DTS (and back) and add this: /* There's the BT part of the AP6256 connected to that UART */ &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; uart-has-rtscts; status = "okay"; bluetooth { compatible = "brcm,bcm4345c5"; clocks = <&rtc 1>; clock-names = "lpo"; device-wakeup-gpios = <&r_pio 1 2 GPIO_ACTIVE_HIGH>; /* PM2 */ host-wakeup-gpios = <&r_pio 1 1 GPIO_ACTIVE_HIGH>; /* PM1 */ shutdown-gpios = <&r_pio 1 4 GPIO_ACTIVE_HIGH>; /* PM4 */ max-speed = <1500000>; }; }; And copy https://github.com/orangepi-xunlong/OrangePiH6_external/tree/master/ap6256 to: /lib/firmware/brcm/(BCM4345C5.hcd) Am I correct that it will it work then? (I'm using a OPi3)
  20. so reboots would work now on clusterboards if i update?
  21. 5.1.0-1111-ayufan tag. Kernel crash when PCIE card is installed (thus pcie host root complex initialize). Will try previous tags soon, BTW, if anyone successfully run the "mainline" kernel with PCIE cards? [ 161.895780] io scheduler mq-deadline registered [ 161.897340] io scheduler kyber registered [ 161.911264] io scheduler bfq registered [ 162.136905] vcc5v0_host: supplied by vcc5v0_usb [ 162.740884] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 162.746764] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found [ 162.750391] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found [ 163.280713] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 163.284059] rockchip-pcie f8000000.pcie: MEM 0xfa000000..0xfbdfffff -> 0xf0 [ 163.286820] rockchip-pcie f8000000.pcie: IO 0xfbe00000..0xfbefffff -> 0xf0 [ 163.302884] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00 [ 163.305119] pci_bus 0000:00: root bus resource [bus 00-1f] [ 163.306968] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff] [ 163.310027] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus add) [ 163.542130] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reg [ 163.560746] SError Interrupt on CPU5, code 0xbf000002 -- SError [ 163.560932] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G L 5.1.0-3 [ 163.561051] Hardware name: Pine64 RockPro64 (DT) [ 163.561157] pstate: 60000085 (nZCv daIf -PAN -UAO) [ 163.561258] pc : rockchip_pcie_rd_conf+0x1e8/0x280 [ 163.561356] lr : rockchip_pcie_rd_conf+0x214/0x280 [ 163.561440] sp : ffff00001004b7f0 [ 163.561527] x29: ffff00001004b7f0 x28: 0000000000000000 [ 163.561800] x27: 0000000000000000 x26: 0000000000000000 [ 163.562047] x25: 0000000000000004 x24: ffff800004de13c0 [ 163.562275] x23: 0000000000000000 x22: ffff8000f61d6800 [ 163.562499] x21: ffff00001004b894 x20: 0000000000100000 [ 163.562718] x19: 0000000000000000 x18: 0000000000000000 [ 163.562936] x17: 00000000250ca3fe x16: 000000009ae7c865 [ 163.563154] x15: ffffffffffffffff x14: ffff00001153d6c8 [ 163.563374] x13: ffff8000ec3df91c x12: ffff8000ec3df190 [ 163.563592] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 163.563811] x9 : ff72646268756463 x8 : 00000000000003bd [ 163.564030] x7 : 0000000000000000 x6 : 0000000000000001 [ 163.564248] x5 : ffff00001060f630 x4 : 0000000000000000 [ 163.564466] x3 : 0000000000000000 x2 : 0000000000c00008 [ 163.564686] x1 : ffff000017c00008 x0 : 0000000000000000 [ 163.564961] Kernel panic - not syncing: Asynchronous SError Interrupt [ 163.565098] CPU: 5 PID: 1 Comm: swapper/0 Tainted: G L 5.1.0-3 [ 163.565196] Hardware name: Pine64 RockPro64 (DT) [ 163.565276] Call trace: [ 163.565367] dump_backtrace+0x0/0x168 [ 163.565452] show_stack+0x24/0x30 [ 163.565535] dump_stack+0xac/0xd4 [ 163.565617] panic+0x150/0x2e8 [ 163.565705] __stack_chk_fail+0x0/0x28 [ 163.565798] arm64_serror_panic+0x80/0x8c [ 163.565884] do_serror+0x11c/0x120 [ 163.565968] el1_error+0x84/0xf8 [ 163.566064] rockchip_pcie_rd_conf+0x1e8/0x280 [ 163.566164] pci_bus_read_config_dword+0xb8/0x108 [ 163.566271] pci_bus_generic_read_dev_vendor_id+0x40/0x1b8 [ 163.566368] pci_bus_read_dev_vendor_id+0x58/0x88 [ 163.566464] pci_scan_single_device+0x84/0xf8 [ 163.566556] pci_scan_slot+0x44/0x108 [ 163.566653] pci_scan_child_bus_extend+0x5c/0x350 [ 163.566749] pci_scan_bridge_extend+0x37c/0x518 [ 163.566849] pci_scan_child_bus_extend+0x204/0x350 [ 163.566945] pci_scan_root_bus_bridge+0x60/0xd0 [ 163.567042] rockchip_pcie_probe+0x5ec/0x718 [ 163.567135] platform_drv_probe+0x58/0xa8 [ 163.567223] really_probe+0x1f0/0x3d8
  22. Batmah

    G16 TVBOX

    Armbian 5.89 21-06-2019 mSD card 8Gb all devices are recognized however, the LTE modem does not work. Also, the installation of the operating system on emmc from the configurator was unsuccessful. On emmc, partitions are created, files are there, the booting starts and then "no root fs"
  23. espressoBIN is a decent choice - good performance at a decent price, and a community here on Armbian that can support it The ClearFogs are a step up, even though their on an older ARMv7A Armada - the 8K is newer and is ARMv8, but not sure where the BSP support is there. There's been a trio of QC-Atheros IPQ-40xx devices recently announced, and they have integrated 802.11ac dual band radios - but most of them are somewhat tight - e.g. to get best performance out of them, one has to use the QSDK, which is built on an older version of OpenWRT - there is support for some IPQ40xx in OpenWRT 18.06 and Master, but I'm not sure it's stable enough yet for daily-driver use on the WiFi (ath10k drivers are under heavy development, and there's issues with the Switch outside of typical setup - see DSA on this chip over on OpenWRT forums...) I was starting to develop a fairly open board based on AR9331/AR9531 - not ARM based, as these are MIPS cores, but the SOC is very well documented, and strong OpenWRT support, but that got set aside when work stepped up and my free time was reduced quite a bit.
  24. Add Raspberry Pi 4 with USB 3.0 adapter! RTL8153 works OOB on linux Modem <-> SBC <-> Switch <-> Devices. 900+ with NAT on multiple SBCs.
  25. Last week
  26. Well, My router is a ZTE ZXHN H267N V1.0. Spending some hours into the router..., but, Unfortunatelly, I cannot see any Isolation option nor VLAN mappings.... The fact is that ports are called LAN1, LAN2, LAN3,... no more options than settings these interfaces on/off. Well, I will use a switch for conecting the OPIZs to one an only router LAN interface. Thanks all for your support
  1. Load more activity