renedis

Members
  • Content Count

    16
  • Joined

  • Last visited

About renedis

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You need to change the DTB file to version 5.88.190601 - 5.1.5 Located on the SD card: /boot/dtb-5.1.7-sunxi64/allwinner/sun50i-h6-orangepi-3.dtb That fixed it for me on 5.88 dev 5.17. Version linux-dtb-dev-sunxi64 version 5.90.190630 should work too, but I've not tested it. Check post:
  2. You guys are making it your self pretty hard
  3. Thanks mate for taking the time and effort!
  4. 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)
  5. 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)
  6. Tried to do something with bluetooth, but "hcitool" and "bluetoothctl" tells me that there is no bluetooth controller. Anybody got this working yet?
  7. / _ \| _ \(_) |___ / | | | | |_) | | |_ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Debian Stretch with Armbian Linux 5.1.7-sunxi64 System load: 0.02 0.01 0.00 Up time: 8:04 hours Memory usage: 9 % of 1997MB IP: x.x.x.x CPU temp: 46°C Usage of /: 69% of 7.1G Everything is working now, I've installed to eMMC. Thanks everyone for working on this! The OPi3 is pretty fast too!
  8. [ o.k. ] Writing U-boot bootloader [ /dev/loop0 ] [ o.k. ] Done building [ /orangepi/build/output/images/Armbian_5.89_Orangepi3_Debian_stretch_dev_5.1.7.img ] [ o.k. ] Runtime [ 33 min ] [ o.k. ] Repeat Build Options [ ./compile.sh BOARD=orangepi3 BRANCH=dev RELEASE=stretch BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no ] OK, so building my own image worked.. But it still isn't working on my OPi3. Can anyone please provide a working IMG (5.88.190601 - 5.1.5)? Or tell me how to change the dtb file?
  9. There is a new update from PiHole that should fix this issue.
  10. Have you tried to install lm-sensors and run "sensors" to see what sensors are available?
  11. What has this to do with Armbian? But hey... Google automaticly converts the date/time scheme when you import. Just do it via the webGUI of Google.
  12. You'll probably need something like a buck converter. 12V HDD's can get power hungry when they spin-up. Up to 15W each.
  13. Had the same question. Thanks!
  14. It feels like it takes forever.. +- 40 min on a Intel i5 6500 with 16GB memory.. Memory is not really important, it's CPU intensive.
  15. NanoPi M4 or RockPro64 indeed. A OrangePI 3 would do the job also if the PCI-E was OK.