data

Members
  • Content Count

    89
  • Joined

  • Last visited

About data

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    nürnberg
  • Interests
    Linux, embedded stuff, networking and ham radio

Recent Profile Visitors

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

  1. @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
  2. @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)
  3. @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.
  4. 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?
  5. There was no load on the Lite2. I just keep it on to see how stable it is.
  6. 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?
  7. 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?
  8. Have the changes been updated also in the Lite2 version?
  9. 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...
  10. So, does this mean the current nightly for the Lite2 may most likely work if I use a 'legacy' dtb?
  11. @dolphs Which image have you used?
  12. Probably you have to wait a little bit longer. The latest nightly is still from the 7th/8th at this moment...
  13. @Igor Thank you very much for your efforts! Will this be incorporated in the Lite2 image as well from tormorrow?
  14. Orange Pi Lite2 affected as well: After upgrading to the latest nightly (Jun-01), it does not boot anymore :(
  15. Great, thank you! Once I've tried it, I'll report back here.