• Content Count

  • Joined

  • Last visited

  1. maracuja

    Orange Pi Zero Plus 2 Temperature issue

    I have removed the stickers from the board and placed the antenna differently so the metal piece would not touch any chip. But still... 1.8W current draw. I have tested a third board. All boards have the same configuration, same revision 1.0, and a usb extension board attached. One board draws 1.3-1.4W, one draws 1.4-1.5W, and the strange one draws 1.8W. The 2 "normal" boards reach ~45°C after 40 minutes (temp. seems stable). The strange board reaches ~53°C after 11 minutes, ~57°C after 18 minutes ~60°C after 26 minutes ~61°C after 40 minutes
  2. I have perfectly equal Orange Pi Zero Plus 2 H3 boards in their original case - booting from eMMC. Test conditions are: WiFi Hotspot enabled, HDMI off, CPU idle, CPU governor: performance, CPU freq. 240MHz - 1.1 GHz, kernel 4.14.84 Xiaomi Mi5 Charger as psu, 2.4A usb cable armbianmonitor gives me a temp of ~50°C on one board (idle@1.1GHz) and a temp of 65°C on the other board (same conditions, CPU starts throttling here to ~960 MHz). The temp gets so high, that after an apt-get update/upgrade and reboot the opizero plus2 would not boot with an error msg that the temp is too high. The temp seems to be correct more or less, since also the power consumption is significantly higher. While the 50°C board draws ~1.5W, the 65°C board draws ~1.8W. I have no explanation for this...
  3. maracuja

    AP6212 in Mainline

    Currently - for Armbian Stretch / OPIZeroPlus2-H3 - the files in /lib/firmware/ap6212/fw_bcm43438a1.bin and /lib/firmware/brcm/brcmfmac43430-sdio.bin are not identical. WiFi works with both of them, but when using /lib/firmware/ap6212/fw_bcm43438a1.bin ping times improve! One more thing: When using the ap6212 driver, 14 wifi channels are supported. When using the driver in the brcm folder, though, only 11 wifi channels are supported. Conclusion: out of the box Armbian Stretch uses the wrong driver for OPIZeroPlus2-H3 - resulting in bad ping times, and reduced number of wifi channels.
  4. Just for the sake of completeness: I've changed the init script for AP6212, I've inserted this:
  5. I could make some tiny progress: First I checked the orange pi zero plus 2 schematics to be sure it is using UART1 for Bluetooth. Yes it is. Then I had a look at the current device tree - somebody wrote that there should be 2 addresses in the pinctrl-0 entry. Mine had only 1 address. I decompiled /boot/dtb-4.14.65-sunxi/sun8i-h3-orangepi-zeroplus2.dtb and had a look at the entry serial@01c28400 This is what is loooks like Here you can see pinctrl-0 looks okay. So it must be the overlay that messes this up. I also looked at the uart1 overlay file (decompiled it) but all these things are new to me, so I gave up on it. But something different looked promising: The status field is "okay", so it is enabled, right in the /boot/dtb-4.14.65-sunxi/sun8i-h3-orangepi-zeroplus2.dtb I guess I don't even need an overlay to enable it then? So knowing that the overlay messes the pinctrl-0 entry up, and guessing that I don't even need it, I just removed the uart1 overlay from the /boot/armbianEnv.txt and rebooted. Now the output of my script looks like this: Before it only said "Initialization timed out" with no UART speed output or Flash firmware output. It's still not working... 1) I copied BCM43430A1.hcd from some site on the internet, having the same MD5 hash as a user that claims it's been working on this orange pi. Maybe I should've used the original one shipped with armbian... (which had a different MD5 hash)... now I've restored the original file (simply by deleting it, the init script copies the original one over) - but same result 2) I've also removed param_uart1_rtscts=1 from armbianEnv.txt - I don't know if this affects anything...
  6. I can only offer to test setup instructions on the boards I have, if anyone has recommendations. I'd be glad to post the results here. If Bluetooth is working on some boards with the same chip (AP6212A) then it should actually work on the Zero Plus2 H3 too.
  7. Well, it would be a good hint to put a remark in the download section of Armbian - at least for the Orange Pi Zero Plus2. When downloading Armbian it does not say anything about Bluetooth being completely dysfunctional.
  8. Hello... I've got an Orange Pi Zero Plus 2 H3 with Armbian Stretch. Kernel: 4.14.70-sunxi armbianEnv.txt: I did: cp -a /lib/firmware/ap6212/fw_bcm43438a1.bin /lib/firmware/brcm/brcmfmac43430-sdio.bin dmesg when searching for "brcm" gives me: [ 8.123186] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001 [ 8.256708] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 8 2016 15:31:47 version (A1 Station/P2P) FWID 01-3621395e es6.c5.n4.a3 In /etc/default/ap6212 I have: PORT=ttyS1 But the script /etc/init.d/ap6212-bluetooth is failing... with the error "Initialization timed out." Is there any "how-to" for the Orange Pi Zero Plus 2 to get Bluetooth working?