fsergeys
Posts: 2
Joined: Mon Dec 18, 2017 12:35 pm

Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Mon Dec 18, 2017 12:46 pm

Hi All,

I running into a problem with pi3-miniuart-bt. Only partial switch of UART.

My need: bluetooth enabled and adafruit gps on UART 14 15
Board: pi3 zero W
Raspbian version: latest stretch
Kernel: 4.9.59+

What have I changed:
/boot/config.txt
enable_uart=1
dtoverlay=pi3-miniuart-bt

/boot/cmdline.txt
Removed : serial0,115200

sudo systemctl stop [email protected]
sudo systemctl disable [email protected]

Rebooted

sudo apt-get install gpsd gpsd-clients
sudo killall gpsd
sudo gpsd /dev/ttyAMA0 -F /var/run/gpsd.sock
cgps -s

=> Works perfectly

HOWEVER: bluetooth: no adaptor found
sudo hcitool dev
Devices:
sudo bluetoothclt
list => nothing ...

I'm out of options ... what else can I check ??

Many thanks in advance

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1911
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Mon Dec 18, 2017 3:04 pm

1. What is in /lib/systemd/system/hciuart.service?
2. Does /usr/bin/btuart exist?
3. What do get from running "ls -l /dev/serial*"?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1911
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Mon Dec 18, 2017 3:07 pm

By the way, you shouldn't have to disable the systemd getty service because it takes its cue from the kernel command line; removing "console=serial0,..." should be sufficient.

Foxhind
Posts: 4
Joined: Wed Dec 05, 2018 10:30 am

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 10:35 am

Hi all, I've got same issue today.

Code: Select all

● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; disabled)
   Active: failed (Result: exit-code) since Ср 2018-12-05 13:21:52 MSK; 12min ago
  Process: 1418 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

дек 05 13:21:52 pp-mitino-1 btuart[1418]: Initialization timed out.
дек 05 13:21:52 pp-mitino-1 btuart[1418]: bcm43xx_init
дек 05 13:21:52 pp-mitino-1 systemd[1]: hciuart.service: control process exited, code=exited status=1
дек 05 13:21:52 pp-mitino-1 systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
дек 05 13:21:52 pp-mitino-1 systemd[1]: Unit hciuart.service entered failed state.
Actual content of my confs:

/lib/systemd/system/hciuart.service

Code: Select all

[Unit]
Description=Configure Bluetooth Modems connected by UART
ConditionPathIsDirectory=/proc/device-tree/soc/[email protected]/bt_pins
Before=bluetooth.service
After=dev-serial1.device

[Service]
Type=forking
ExecStart=/usr/bin/btuart

[Install]
WantedBy=multi-user.target
/boot/config.txt

Code: Select all

# For more options and information see
# http://rpf.io/configtxtreadme
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
enable_uart=1
dtoverlay=pi3-miniuart-bt
# dtoverlay=pi3-disable-bt
/boot/cmdline.txt

Code: Select all

dwc_otg.lpm_enable=0  console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Any ideas?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1911
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 3:08 pm

What model of Pi are you using?

Are there any error messages in the kernel log?

Code: Select all

$ dmesg -l err
If that doesn't show anything relevant, just use "dmesg". Either way, post the output.

Foxhind
Posts: 4
Joined: Wed Dec 05, 2018 10:30 am

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 4:25 pm

PhilE wrote:
Wed Dec 05, 2018 3:08 pm
What model of Pi are you using?
Pi 3 Model B 1GB a02082 / Raspbian 8.

Part of /proc/cpuinfo:

Code: Select all

model name: ARMv7 Processor rev 4 (v7l)
Hardware: BCM2835
Revision: a02082
$dmesg -l err

Code: Select all

[    0.277466] bcm2835-aux-uart 3f215040.serial: could not get clk: -517
[   13.910679] brcmfmac: brcmf_cfg80211_stop_ap: setting INFRA mode failed -7
I disabled Wi-Fi access point to use Pi as client of existing Wi-Fi network (it works).

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1911
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 4:27 pm

I think it would be better if you post the whole of the output of "dmesg", just in case some significant message is appearing at a lower logging level.

Foxhind
Posts: 4
Joined: Wed Dec 05, 2018 10:30 am

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 5:14 pm

Sure. Full dmesg output:

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.35-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1014 SMP Fri Jun 30 14:47:43 BST 2017
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x3a800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 241664
[    0.000000] free_area_init_node: node 0, pgdat 80c6ee40, node_mem_map b9faa000
[    0.000000]   Normal zone: 2124 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 241664 pages, LIFO batch:31
[    0.000000] percpu: Embedded 14 pages/cpu @b9f64000 s25600 r8192 d23552 u57344
[    0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 239540
[    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0  console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 936296K/966656K available (7168K kernel code, 484K rwdata, 2012K rodata, 1024K init, 778K bss, 22168K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
    lowmem  : 0x80000000 - 0xbb000000   ( 944 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80800000   (8160 kB)
      .init : 0x80b00000 - 0x80c00000   (1024 kB)
      .data : 0x80c00000 - 0x80c79014   ( 485 kB)
       .bss : 0x80c7b000 - 0x80d3da64   ( 779 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000009] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000025] Switching to timer-based delay loop, resolution 52ns
[    0.000335] Console: colour dummy device 80x30
[    0.001223] console [tty1] enabled
[    0.001277] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001346] pid_max: default: 32768 minimum: 301
[    0.001706] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001749] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002771] Disabling cpuset control group subsystem
[    0.002965] CPU: Testing write buffer coherency: ok
[    0.003033] ftrace: allocating 22390 entries in 66 pages
[    0.055365] CPU0: update cpu_capacity 1024
[    0.055435] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.055534] Setting up static identity map for 0x100000 - 0x100034
[    0.057780] CPU1: update cpu_capacity 1024
[    0.057788] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.058503] CPU2: update cpu_capacity 1024
[    0.058510] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.059178] CPU3: update cpu_capacity 1024
[    0.059185] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.059268] Brought up 4 CPUs
[    0.059440] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.059470] CPU: All CPU(s) started in HYP mode.
[    0.059496] CPU: Virtualization extensions available.
[    0.060319] devtmpfs: initialized
[    0.071313] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.071634] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.071696] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.072260] pinctrl core: initialized pinctrl subsystem
[    0.073184] NET: Registered protocol family 16
[    0.075441] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.084291] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.084339] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.084512] Serial: AMBA PL011 UART driver
[    0.086411] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.086956] uart-pl011 3f201000.serial: could not find pctldev for node /soc/[email protected]/uart0_pins, deferring probe
[    0.087320] irq: no irq domain found for /soc/[email protected] !
[    0.155964] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
[    0.157834] SCSI subsystem initialized
[    0.158011] usbcore: registered new interface driver usbfs
[    0.158112] usbcore: registered new interface driver hub
[    0.158227] usbcore: registered new device driver usb
[    0.164920] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
[    0.166316] clocksource: Switched to clocksource arch_sys_counter
[    0.213193] VFS: Disk quotas dquot_6.6.0
[    0.213303] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.213530] FS-Cache: Loaded
[    0.213795] CacheFiles: Loaded
[    0.225981] NET: Registered protocol family 2
[    0.226927] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.227065] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.227275] TCP: Hash tables configured (established 8192 bind 8192)
[    0.227388] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.227455] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.227691] NET: Registered protocol family 1
[    0.228124] RPC: Registered named UNIX socket transport module.
[    0.228156] RPC: Registered udp transport module.
[    0.228184] RPC: Registered tcp transport module.
[    0.228211] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.229156] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.231466] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.247623] FS-Cache: Netfs 'nfs' registered for caching
[    0.248625] NFS: Registering the id_resolver key type
[    0.248675] Key type id_resolver registered
[    0.248703] Key type id_legacy registered
[    0.251158] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.251316] io scheduler noop registered
[    0.251346] io scheduler deadline registered (default)
[    0.251657] io scheduler cfq registered
[    0.257332] BCM2708FB: allocated DMA memory fa910000
[    0.257386] BCM2708FB: allocated DMA channel 0 @ bb80f000
[    0.266086] Console: switching to colour frame buffer device 82x26
[    0.273558] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.277466] bcm2835-aux-uart 3f215040.serial: could not get clk: -517
[    0.280802] bcm2835-rng 3f104000.rng: hwrng registered
[    0.283218] vc-cma: Videocore CMA driver
[    0.285576] vc-cma: vc_cma_base      = 0x00000000
[    0.287975] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.290243] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.292603] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    0.312095] brd: module loaded
[    0.323004] loop: module loaded
[    0.325095] Loading iSCSI transport class v2.0-870.
[    0.327792] usbcore: registered new interface driver smsc95xx
[    0.329931] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.560035] Core Release: 2.80a
[    0.562091] Setting default values for core params
[    0.564218] Finished setting default values for core params
[    0.766795] Using Buffer DMA mode
[    0.768919] Periodic Transfer Interrupt Enhancement - disabled
[    0.771161] Multiprocessor Interrupt Enhancement - disabled
[    0.773394] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.775584] Dedicated Tx FIFOs mode
[    0.778051] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xba904000 dma = 0xfa904000 len=9024
[    0.782487] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[    0.793824] dwc_otg: Microframe scheduler enabled
[    0.793869] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058ef90
[    0.796165] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058f300 length 36
[    0.798484] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
[    0.800852] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.803169] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.805530] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.807871] Init: Port Power? op_state=1
[    0.810128] Init: Power Port (0)
[    0.812505] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.814816] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.817136] usb usb1: Product: DWC OTG Controller
[    0.819383] usb usb1: Manufacturer: Linux 4.9.35-v7+ dwc_otg_hcd
[    0.821652] usb usb1: SerialNumber: 3f980000.usb
[    0.824727] hub 1-0:1.0: USB hub found
[    0.826965] hub 1-0:1.0: 1 port detected
[    0.829699] dwc_otg: FIQ enabled
[    0.829703] dwc_otg: NAK holdoff enabled
[    0.829707] dwc_otg: FIQ split-transaction FSM enabled
[    0.829721] Module dwc_common_port init
[    0.829961] usbcore: registered new interface driver usb-storage
[    0.832287] mousedev: PS/2 mouse device common for all mice
[    0.835357] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.837917] bcm2835-cpufreq: min=600000 max=1200000
[    0.840560] sdhci: Secure Digital Host Controller Interface driver
[    0.842875] sdhci: Copyright(c) Pierre Ossman
[    0.845398] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[    0.849988] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.852527] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.857580] ledtrig-cpu: registered to indicate activity on CPUs
[    0.860225] hidraw: raw HID events driver (C) Jiri Kosina
[    0.862883] usbcore: registered new interface driver usbhid
[    0.865340] usbhid: USB HID core driver
[    0.868586] vchiq: vchiq_init_state: slot_zero = 0xba980000, is_master = 0
[    0.872800] Initializing XFRM netlink socket
[    0.875336] NET: Registered protocol family 17
[    0.877975] Key type dns_resolver registered
[    0.880787] Registering SWP/SWPB emulation handler
[    0.883938] registered taskstats version 1
[    0.886734] vc-sm: Videocore shared memory driver
[    0.889240] [vc_sm_connected_init]: start
[    0.892160] [vc_sm_connected_init]: end - returning 0
[    0.899596] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.906964] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 220, base_baud = 50000000) is a 16550
[    0.912631] sdhost: log_buf @ ba907000 (fa907000)
[    0.986343] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.991054] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.993542] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.046504] Indeed it is in host mode hprt0 = 00021501
[    1.109054] of_cfs_init
[    1.111491] of_cfs_init: OK
[    1.114251] Waiting for root device /dev/mmcblk0p2...
[    1.127097] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.130919] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.131318] random: fast init done
[    1.136860] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.141923] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.177934] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.185633] mmc0: new high speed SDHC card at address aaaa
[    1.188705] mmcblk0: mmc0:aaaa SS16G 14.8 GiB
[    1.193783]  mmcblk0: p1 p2
[    1.246355] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.248795] Indeed it is in host mode hprt0 = 00001101
[    1.250984] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.251028] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.258852] devtmpfs: mounted
[    1.319563] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[    1.321495] mmc1: new high speed SDIO card at address 0001
[    1.486643] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.489299] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.492751] hub 1-1:1.0: USB hub found
[    1.495405] hub 1-1:1.0: 5 ports detected
[    1.631607] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    1.637479] systemd[1]: Detected architecture 'arm'.
[    1.759725] NET: Registered protocol family 10
[    1.763823] systemd[1]: Inserted module 'ipv6'
[    1.770927] systemd[1]: Set hostname to <pp-mitino-1>.
[    1.816400] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.956759] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.959473] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.965069] smsc95xx v1.0.5
[    2.060044] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:99:4c
[    2.215883] systemd[1]: Cannot add dependency job for unit regenerate_ssh_host_keys.service, ignoring: Unit regenerate_ssh_host_keys.service failed to load: No such file or directory.
[    2.224142] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    2.235842] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    2.241926] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.247919] systemd[1]: Starting Remote File Systems (Pre).
[    2.254601] systemd[1]: Reached target Remote File Systems (Pre).
[    2.778329] systemd-udevd[148]: starting version 215
[    3.109892] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    3.448994] usbcore: registered new interface driver brcmfmac
[    3.519264] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.609316] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[    3.871985] systemd-journald[145]: Received request to flush runtime journal from PID 1
[    4.970624] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    4.970670] brcmfmac: power management disabled
[    5.410746] tun: Universal TUN/TAP device driver, 1.6
[    5.410755] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[    6.029163] Adding 102396k swap on /var/swap.  Priority:-1 extents:2 across:217084k SSFS
[    6.067661] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.067839] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.245348] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[    7.557880] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    7.558506] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[    9.114220] uart-pl011 3f201000.serial: no DMA platform data
[   13.169551] ip_tables: (C) 2000-2006 Netfilter Core Team
[   13.247422] nf_conntrack version 0.5.0 (15360 buckets, 61440 max)
[   13.910679] brcmfmac: brcmf_cfg80211_stop_ap: setting INFRA mode failed -7
[  166.749136] random: crng init done

User avatar
bensimmo
Posts: 3470
Joined: Sun Dec 28, 2014 3:02 pm
Location: East Yorkshire

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 5:18 pm

What GPS are you using that needs the PL01 UART.
None that I have used even at higher refresh rates ahve had a problem on the miniUART.

Especially when Bluetooth will benefit more from the full UART.

Switch it all back go from there.

DirkS
Posts: 9505
Joined: Tue Jun 19, 2012 9:46 pm
Location: Essex, UK

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 6:23 pm

bensimmo wrote:
Wed Dec 05, 2018 5:18 pm
What GPS are you using that needs the PL01 UART.
That's only mentioned in the top post (from last year)
This a different user and (s)he has not mentioned GPS anywhere.

User avatar
bensimmo
Posts: 3470
Joined: Sun Dec 28, 2014 3:02 pm
Location: East Yorkshire

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 6:29 pm

I assumed as it was a reply with 'same issue', it was also GPS based.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1911
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Wed Dec 05, 2018 6:45 pm

I think the problem is that you haven't read the help entry for the pi3-miniuart-bt:

Code: Select all

$ dtoverlay -h pi3-miniuart-bt
Name:   pi3-miniuart-bt

Info:   Switch Pi3 Bluetooth function to use the mini-UART (ttyS0) and restore
        UART0/ttyAMA0 over GPIOs 14 & 15. Note that this may reduce the maximum
        usable baudrate.
        N.B. It is also necessary to edit /lib/systemd/system/hciuart.service
        and replace ttyAMA0 with ttyS0, unless you have a system with udev rules
        that create /dev/serial0 and /dev/serial1, in which case use
        /dev/serial1 instead because it will always be correct. Furthermore,
        you must also set core_freq=250 in config.txt or the miniuart will not
        work.

Usage:  dtoverlay=pi3-miniuart-bt

Params: <None>
Add "core_freq=250" to config.txt and try again. You can ignore the bit about editing the systemd service because Raspbian has the necessary udev rules.

Foxhind
Posts: 4
Joined: Wed Dec 05, 2018 10:30 am

Re: Bluetooth does not find adaptor after overlay=pi3-miniuart-bt

Thu Dec 06, 2018 6:18 am

PhilE wrote:
Wed Dec 05, 2018 6:45 pm
Add "core_freq=250" to config.txt and try again. You can ignore the bit about editing the systemd service because Raspbian has the necessary udev rules.
It works now, thank you!
PhilE wrote:
Wed Dec 05, 2018 6:45 pm
I think the problem is that you haven't read the help entry for the pi3-miniuart-bt:
Yes. My bad.

Return to “Device Tree”