• Content Count

  • Joined

  • Last visited

About mantabernd

  • Rank

Recent Profile Visitors

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

  1. Hi, I'm looking for a working OS Image for Nano Pi Neo Air for using I2S, SPI and Bluetooth (AP6212). Is there a release I can use "out of the box" for this? Regards Bernhard
  2. Hi, I'm using my NanoPi NeoAir as a bluetooth streaming sink and as a webserver for several configurations and monitoring of the device. Bluetooth works fine as long as I don't disable the powersafe mode of wifi. Even in powersafe mode the bluetooth performance is not the best. If I disable wifi at all the bluetooth performance is great. My system is: Ubuntu 16.04.3 LTS 4.11.2 iwconfig: wlan0 IEEE 802.11 ESSID:"Teebeutel" Mode:Managed Frequency:2.412 GHz Access Point: 2C:41:38:FB:D7:30 Bit Rate=54 Mb/s Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=43/70 Signal level=-67 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 how I disable powersafe: sudo /sbin/iwconfig wlan0 power off Bluetooth is barely usable when powersafe is off... Any idea? Is this a driver problem? Thanks for your support. Regards Bernhard
  3. Got anybody here a idea where the 1500000 bit/s come from? It's not a regular baud rate and AP6212a datasheet tells me that this chip can handle up to 3 Mbps. So why can't I use 3000000 bit/s? Regards
  4. I found a patch regarding this: Can you please tell me how to install this patch?
  5. Maybe it's already enough to set GPIOA7 and GPIOA8 to a high level... Unfortunately I can't find any information how to set them as a output with pullup. Do you have any idea how to change the .dts file from my prev post?
  6. I guess I need to create my own overlay, or? I found this .dts file for uart3 on Allwinner H3: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/aliases"; __overlay__ { serial3 = "/soc/serial@01c28c00"; }; }; fragment@1 { target = <&uart3>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <&uart3_pins>; status = "okay"; }; }; }; How to insert the custom GPIOs here?
  7. I'm using Nano Pi Neo Air. AP6212a is located on ttyS3. It's working under 3.4 kernel. BT-WAKE-AP and AP-WAKE-BT is a good hint. Thank you for this! Can you tell me how I activate these pins in DT? I guess you are talking about Pins PA7 and PA8? Thanks for your help.
  8. Hi, I'm trying to use bluetooth with the Mainline 4.11.9-sun8i armbian kernel (I also tried 4.11.7-sun8i). I activated ttyS3 (uart3) in armbianEnv.txt: verbosity=1 logo=disabled console=serial overlay_prefix=sun8i-h3 rootdev=UUID=59c35982-ddad-4bf0-8b72-a8974bfe88a6 rootfstype=ext4 overlays=uart3 spi-spidev param_uart3_rtscts=1 param_spidev_spi_bus=0 Unfortunately hciconfig -a does not find any device. I already tried to set the baudrate but no chance to get bluetooth alive: service bluetooth stop rfkill unblock all echo "0" > /sys/class/rfkill/rfkill0/state echo "1" > /sys/class/rfkill/rfkill0/state echo " " > /dev/ttyS3 hciattach /dev/ttyS3 bcm43xx 1500000 flow hciconfig hci0 up brings: bcm43xx_init Initialization timed out. Can't get device info: No such device root@nanopiair:~# Any idea whats going wrong here? Regards Bernhard
  9. I'm glad it's working now for you. I'm still not happy with the bluetooth performance. Poor connection quality and sound streaming does not work really smooth. I'm now trying to get it done with 4.11 kernel, unfortunately the bluetoothchip is not working at all with this kernel....
  10. Thank you for your fast reply. I kinda got it working. I thought it's enough to set the uart speed once but you need to make it on every boot. So I wrote startscript what sets the uart speed to 1500000 bit/s and it's working without timeouts. It's not my goal yet because the AP6212a datasheet says that it's possible to work with 3000000 bit/s. Unfortunately I'm not able to set this speed. Furthermore Bluteooth audio streaming is not running very stable. I know it from Raspberry Pi with 4.x kernel and it was really easy and smooth. It seems that it's a problem connected to 3.4 kernel. Can you give me any info about how to activate blutooth on 4.x kernel? I already tried to make it work but with 4.x mainline release you don't have this fex file to activate the hardware modules. I got stucked with building a new device tree. Maybe you can give me some more info about it? Do you know when a 4.x kernel will be officially available for Nano Pi Neo Air? Thanks a lot Regards Bernhard
  11. Good evening, I'm using a NanoPi Neo Air for streaming audio via bluetooth to a I2S sink. It's working in general but the audio data breaks away every second. It's always a on/off. I'm pretty sure it's connected to the speed between H3 - AP6212a but I'm not able to get it to work propably. I set the UART ttyS3 speed to 1500000 bit/s: My Fexedit looks like that: [bt_para] │ │bt_used = 1 │ │bt_uart_id = 3 │ │bt_uart_baud = 1500000 │ │bt_rst_n = port:PG13<1><default><default><0> │ │bt_wake = port:PA08<1><default><default><0> │ │bt_host_wake = port:PA07<0><default><default><0> │ │bt_host_wake_invert = 0 and I changed the AP6212a speed like this: systemctl stop bluetooth.service cp /lib/firmware/ap6212/bcm43438a1.hcd /etc/firmware/ap6212/4343A0.hcd echo "0" > /sys/class/rfkill/rfkill0/state echo "1" > /sys/class/rfkill/rfkill0/state echo " " > /dev/ttyS3 hciattach /dev/ttyS3 bcm43xx 1500000 bcm43xx_init Set Controller UART speed to 1500000 bit/s Flash firmware /etc/firmware/ap6212/4343A0.hcd Set Controller UART speed to 1500000 bit/s Device setup complete I already tried to go up 3000000 bit/s but the firmware flashing process stucks when I try it. Any idea why my I2S audio bus can't deliver the whole data? Regards Bernhard EDIT: output of hciconfig -a: root@nanopiair:~# hciconfig -a hci0: Type: BR/EDR Bus: UART BD Address: 43:29:B1:55:01:01 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:520 acl:0 sco:0 events:23 errors:0 TX bytes:1090 acl:0 sco:0 commands:23 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'nanopiair' Class: 0x00041c Service Classes: Unspecified Device Class: Audio/Video, Portable Audio HCI Version: 4.1 (0x7) Revision: 0xf2 LMP Version: 4.1 (0x7) Subversion: 0x2122 Manufacturer: Broadcom Corporation (15)