data

  • Posts

    93
  • Joined

  • Last visited

Everything posted by data

  1. Dear Igor, thank you for your reply. Is there any other H6 based OrangePi with a working audio-codec?
  2. Can someone please add support for the onboard microphone to armbian for the Lite2?! It is missing in armbian-config, there is no h6-analog-codec.dtbo in /boot/dtb/allwinner/overlay The microphone is wired up the same way as on the other h6 boards. Thank you very much!
  3. Any updates on this issue? I am getting also only USB 2 speed with the current nightly on the lite2.
  4. @rawaaw Great, works on nightly Linux orangepilite2 5.3.0-sunxi64 #5.97.190919 SMP Thu Sep 19 02:51:56 CEST 2019 aarch64 GNU/Linux from 4 days ago as well. I just missed the patchram command last time I tried. By the way, I am user data who wrote the post on April 27th And I am happy to see that my initial efforts finally led to success! So ladies and gentlemen, attached you'll find an archive with a working init-script for the ap6255 bluetooth chip. Move the included files to the according directories and modify the MAC-Address in /etc/default/ap6255 to your needs activate bluetooth with # service ap6255-bluetooth start check status: # service ap6255-bluetooth status enable on boot: # systemctl enable ap6255-bluetooth @Igor Include this in the upcoming snapshots please! And thanks to everybody who made this possible! ap6255_bluetooth.zip
  5. @rawaaw Good job. Have you tried if it is actually working? I don't get any results from hcitool scan And there is an error in dmesg when the device is initialized as described by you above: [ 3068.025249] Bluetooth: hci1: command 0x1003 tx timeout But I have the feeling we are almost there, at least for the OPi Lite2 When I try specific parameters for hciattach, I get the following: root@orangepilite2:~# hciattach /dev/ttyS1 bcm43xx 921600 noflow - bcm43xx_init Patch not found, continue anyway Set Controller UART speed to 921600 bit/s Device setup complete root@orangepilite2:~# hciconfig hci1 up Can't init device hci1: Connection timed out (110)
  6. @dziobak Thank you very much for your reply. Prior to running the script, I changed to regulator.4 as suggested in your post above. Once I've tried different voltages I'll let you know the results.
  7. Since I had no better idea, I tried stabilitytester as suggested: The lite2 freezes always when stabilitytester reaches this: TEST Freq: 816 MHz Soc temp: 40.92 ℃ CPU Freq: 816 MHz CPU Core: 960 mV TEST Freq: 888 MHz Soc temp: 40.59 ℃ CPU Freq: 888 MHz CPU Core: 960 mV TEST Freq: 1080 MHz Soc temp: 42.13 ℃ CPU Freq: 1080 MHz CPU Core: 960 mV TEST Freq: 1320 MHz Soc temp: 52.48 ℃ CPU Freq: 1320 MHz CPU Core: 960 mV I added additional cooling and now, it reboots instead of freeze So is this a voltage related issue?
  8. There was no load on the Lite2. I just keep it on to see how stable it is.
  9. On the Lite2, I am experiencing a complete freeze every few (1-3) days. This is happening since the past two or three weeks The system stops responding and I have to power off and on again. There is nothing in any of the logs. It's as if one would pull the plug. Can this be related to the modified voltages?
  10. Ok, Lite2 boots fine now with the current updates. From what I see, uart1 is now enabled by default and listed as ttyS1 in dmesg. Any idea, why I still can not enable bluetooth via hciattach /dev/ttyS1 ... ? How can I test if uart1 is actually working?
  11. Have the changes been updated also in the Lite2 version?
  12. In order to make bluetooth work, you need to check if uart1 is declared properly in the dts/dtb and enabled. Then proceed with hcitool...
  13. So, does this mean the current nightly for the Lite2 may most likely work if I use a 'legacy' dtb?
  14. Probably you have to wait a little bit longer. The latest nightly is still from the 7th/8th at this moment...
  15. @Igor Thank you very much for your efforts! Will this be incorporated in the Lite2 image as well from tormorrow?
  16. Orange Pi Lite2 affected as well: After upgrading to the latest nightly (Jun-01), it does not boot anymore :(
  17. Great, thank you! Once I've tried it, I'll report back here.
  18. Lite2 has an AP6255 connected to UART1
  19. Do you know if these patches are included in the current lite2 built?
  20. @megi I noticed I already had the firmware for ap6255 at /lib/firmware on the lite2 but I am still not able to attach the device to uart1 How have you managed to configure uart1? Or are there some relevant differences in the kernel which haven't been ported to the lite2 built yet?
  21. So were you able to configure the device using hciattach?
  22. hciattach is what you are asking for. e.g. $ sudo hciattach /dev/ttyS1 bcm43xx 921600 noflow - Can you attach the firmware to this thread?
  23. With the boot-issue now resolved, the last nightly enables overlay-support for uart1. This is one more step towards working bluetooth on the lite2 and Orange Pi 3. Anyone interested is invited to do further testing. So far, I can enable the uart1 overlay either in armbianEnv.txt or via armbian-config. This gives us /dev/ttyS1 - at least it's there in dmesg and /dev/ttyS1 exists. Since the bluetooth module is connected via uart1, the next steps are to attach it. From my understanding, this needs the hci_uart module, which can be loaded via $ sudo modprobe hci_uart In addition, the btbcm module is required but this should be already loaded. So 'sudo modprobe btbcm' should not be necessary. You can verify if it is loaded via: $ lsmod | grep btbcm This in place, we should be able to attach the uart-port using hciattach. Now this is the point, where I am stuck. Typically, you do something along $ sudo hciattach /dev/ttyS1 bcm43xx 921600 noflow - However, I tried a couple of different baudrates as well as with and without flow-control without success. According to a couple of related posts, on success, one should see that the firmware is being loaded at this point. Any ideas or suggestions?