iamdrq

Members
  • Content Count

    15
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by iamdrq

  1. Because default firmware include default mac, Please download the file and replace the default firmware file: /lib/firmware/brcm/BCM4345C5.hcd,then reboot
  2. Look like you install image and dtb correctly,but you edit armbianEnv.txt not correctly or put overlay-user files not correctly.(Oh,I see my previous post,I spell error,should 'sudo apt install bluez') Yes,this is not easy for simple user.I edit dts include bluetooth and not need add 'overlay-user',so: restore your armbianEnv.txt install following dtb files reboot And should see: root@orangepi4:~# dmesg |grep Blue [ 3.982085] Bluetooth: Core ver 2.22 [ 3.982126] Bluetooth: HCI device and connection manager initialized [ 3.982135] Bluetooth: HCI socket layer initialized [ 3.982140] Bluetooth: L2CAP socket layer initialized [ 3.982150] Bluetooth: SCO socket layer initialized [ 3.988355] Bluetooth: HCI UART driver ver 2.3 [ 3.988359] Bluetooth: HCI UART protocol H4 registered [ 3.990827] Bluetooth: HCI UART protocol Broadcom registered [ 4.341819] Bluetooth: hci0: BCM: chip id 130 [ 4.342164] Bluetooth: hci0: BCM: features 0x0f [ 4.344286] Bluetooth: hci0: BCM4345C5 [ 4.344299] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000 [ 5.045748] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0038 root@orangepi4:~# hciconfig hci0: Type: Primary Bus: UART BD Address: 43:45:C5:00:1F:CA ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:397051100 acl:654339 sco:0 events:741 errors:0 TX bytes:42146 acl:432 sco:0 commands:258 errors:0 OrangePi4-Image-dtb-v2.zip
  3. Oh,my error,I add bluetooth by dts,bluetooth will auto finish on boot,so don't need install bluetooth by armbian-config(because armbian-config use brcm_patchram_plus,it conflicts with the dts way). so you need use armbian-config remove bluetooth,then 'apt install bluz',and reboot And can you show me 'sudo dmesg | grep Blue',I want to make sure that you have placed the file correctly
  4. Please back up your old files. There is Image and dtb and overlays and bt firmware. OrangePi4-Bluetooth-Mic.zip
  5. About the Orangepi 4 's bluetooth chip AP6256,I read hci how get bluetooth mac address from 'https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/bluetooth/btbcm.c',the origin firmware file /lib/firmware/brcm/BCM4345C5.hcd include default mac address '43:45:C5:00:1F:AC',it is cause driver mark it 'HCI_QUIRK_INVALID_BDADDR',so I use hex editer change the default mac to '43:45:C5:00:1F:CA',you can use this firmware file replace /lib/firmware/brcm/BCM4345C5.hcd and not need do 'btmgmt --index 0 public-addr 11:22:33:44:55:66' set bluetooth mac after boot. BCM4345C5.hcd
  6. @piter75 Maybe the mic need fix,I see the OrangePi_4_schematic_v1.3.pdf,I found MIC_IN1P not link to IN1P.It causes the recording to be abnormal. This is a dts overlay,I tested recording better,I am not sure it is correct(because orangepi4 include two mic,one from board,one from jack). mic-opi4.dts
  7. well,it useable with or without headless,so just do as you like
  8. iamdrq

    Orange pi 4

    Yes,please back up your old files orangepi4-sound-bt.zip
  9. iamdrq

    Orange pi 4

    the orangepi4-rt5651.patch include rt5651.c, so not only need use dts overlay. Do you use the patch rebuild kernel ?
  10. Yes,the orange pi 4's bluetooth also fixed. the main line kernel support bcm bt chip,so I use the kernel driver and not use brcm_patchram_plus file do this. the 'wireless-wlan' and 'wireless-bluetooth' in dts,it is from rockchip's net/rfkill/rfkill-bt.c and net/rfkill/rfkill-wlan.c and this not found in main line kernel,so 'wireless-wlan' and 'wireless-bluetooth' should remove or disable,and wifi be driver by sdio node in dts. the bluetooth will be driver by uart->bluetooth->compatible = "brcm,bcm4345c5"(serial@ff180000->bluetooth->compatible = "brcm,bcm4345c5") and the kernel config should enable CONFIG_SERIAL_DEV_BUS=y CONFIG_SERIAL_DEV_CTRL_TTYPORT=y CONFIG_BT_HCIUART_BCM=y CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y but have a little problem,need do 'btmgmt --index 0 public-addr 11:22:33:44:55:66' set bt mac after boot,otherwise hciconfig will show 'DOWN RAW',someone konw fix this? I did some dts over and hope this can help armbian fix bluetooth-opi4.dts linux-rockchip64-current.config
  11. Oh,I fixed this problem spend 2 weeks,I finally heard sound from 3.5 mm jack (this jack is OMTP otherwise need keep press headphone button) I see this topic,and I compair https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/codecs/rt5640.c and https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/codecs/rt5651.c,this rt5651 not enable mclk and orangepi4"s rt5651 linked i2s1,the i2s1's SCLK_I2S_8CH parent not SCLK_I2S1_8CH defult and need set alsamixer in following(also use alsactl save this alsamixer state): amixer set 'HPO L' on amixer set 'HPO R' on amixer set 'HPOVOL L' on amixer set 'HPOVOL R' on amixer set 'HPO MIX HPVOL' on amixer set 'OUT MIXL DAC L1' on amixer set 'OUT MIXR DAC R1' on amixer set 'Stereo DAC MIXL DAC L1' on amixer set 'Stereo DAC MIXR DAC R1' on And I not familiar with electronics,I did some patch and hope this can help armbian fix fix-i2s1-clk.patch orangepi4-rt5651.patch orangepi4-i2s_8ch_mclk.dts Armbian applied this patch to 'Armbian build system' and with minor tweaks,you can use it by 'Armbian build system' latest branch.
  12. iamdrq

    Orange pi 4

    I cant get orangepi4's audio to work too,and I try adjust alsamixer get some noise from headphone,I try fix it a week,but got nothing,maybe i2c1 work,i2s1 not work ? someone fixed the audio ?
  13. I found a way to fix this problem: https://patchwork.kernel.org/patch/10856989/
  14. I try Armbian's OrangepiA64 Win Mainline Linux 4.19,But jack sound don't work always,I try many a time.Finally,I decide build image from mainline linux 5.0,Yes,Everything ok except usb,all usb port don't work. root@OrangepiWin:~# lsusb Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@OrangepiWin:~# dmesg |grep -i usb [ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait rootfstype=ext4 console=ttyS0,115200 panic=10 consoleblank=0 loglevel=8 ubootpart=bc38bc54-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 1.246421] usbcore: registered new interface driver usbfs [ 1.246464] usbcore: registered new interface driver hub [ 1.246526] usbcore: registered new device driver usb [ 2.098070] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO [ 2.121669] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.121877] ehci-platform 1c1a000.usb: EHCI Host Controller [ 2.121902] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1 [ 2.122960] ehci-platform 1c1a000.usb: irq 18, io mem 0x01c1a000 [ 2.136047] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00 [ 2.136278] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01 [ 2.136289] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.136298] usb usb1: Product: EHCI Host Controller [ 2.136306] usb usb1: Manufacturer: Linux 5.1.0-rc1+ ehci_hcd [ 2.136314] usb usb1: SerialNumber: 1c1a000.usb [ 2.136837] hub 1-0:1.0: USB hub found [ 2.137502] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.137697] ohci-platform 1c1a400.usb: Generic Platform OHCI controller [ 2.137718] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2 [ 2.138053] ohci-platform 1c1a400.usb: irq 19, io mem 0x01c1a400 [ 2.200240] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.01 [ 2.200251] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.200260] usb usb2: Product: Generic Platform OHCI controller [ 2.200268] usb usb2: Manufacturer: Linux 5.1.0-rc1+ ohci_hcd [ 2.200276] usb usb2: SerialNumber: 1c1a400.usb [ 2.200728] hub 2-0:1.0: USB hub found [ 2.201701] usbcore: registered new interface driver usb-storage [ 2.205401] usbcore: registered new interface driver usbhid [ 2.205406] usbhid: USB HID core driver [ 2.264122] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO [ 4.206938] ehci-platform: probe of 1c1b000.usb failed with error -22 [ 4.213806] ohci-platform: probe of 1c1b400.usb failed with error -22 [ 4.220636] usb_phy_generic usb_phy_generic.2.auto: usb_phy_generic.2.auto supply vcc not found, using dummy regulator [ 4.231665] musb-hdrc musb-hdrc.3.auto: MUSB HDRC host driver [ 4.237423] musb-hdrc musb-hdrc.3.auto: new USB bus registered, assigned bus number 3 [ 4.245478] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01 [ 4.253752] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.260979] usb usb3: Product: MUSB HDRC host driver [ 4.265946] usb usb3: Manufacturer: Linux 5.1.0-rc1+ musb-hcd [ 4.271691] usb usb3: SerialNumber: musb-hdrc.3.auto [ 4.277118] hub 3-0:1.0: USB hub found [ 4.295367] usb0-vbus: disabling This line Armbian also show in log: sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO I think this problem is related to fallow two line: [ 4.206938] ehci-platform: probe of 1c1b000.usb failed with error -22 [ 4.213806] ohci-platform: probe of 1c1b400.usb failed with error -22 I found 1c1b000.usb 1c1b400.usb in dts of OrangepiWin usb: usb@1c1b000 { compatible = "allwinner,sun50i-a64-ehci", "generic-ehci"; reg = <0x1c1b000 0x100>; interrupts = <0x0 0x4a 0x4>; clocks = <0x2 0x2d 0x2 0x2b 0x2 0x5d>; resets = <0x2 0x16 0x2 0x14>; phys = <0x20 0x1>; phy-names = "usb"; status = "okay"; } usb@1c1b400 { compatible = "allwinner,sun50i-a64-ohci", "generic-ohci"; reg = <0x1c1b400 0x100>; interrupts = <0x0 0x4b 0x4>; clocks = <0x2 0x2d 0x2 0x5d>; resets = <0x2 0x16>; phys = <0x20 0x1>; phy-names = "usb"; status = "okay"; }; Somebody meet this problem ?