LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 11-12-2020, 05:59 AM   #31
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled

Hi Mara,

I have a problem with the bluetooth adapter on the Raspberry Pi 3.
The interface appears when listing it with hciconfig, but then I try to bring it up, I get:

Code:
Can't init device hci0: Connection timed out (110)
And in dmesg, I get the following messages:
Code:
Bluetooth: hci0: command 0xfc18 tx timeout 
Bluetooth: hci0: BCM: failed to write update baudrate (-110)
Bluetooth: hci0: Failed to set bitrate
Bluetooth: hci0: command 0x0c03 tx timeout
Bluetooth: hci0: BCM: Reset failed (-110)
 
Old 11-12-2020, 11:44 AM   #32
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
Hi wowbaggerHU,

Аnd using blueman, how does bluetooth behave?

Code:
ls /dev | grep -P 'serial|ttyS|ttyAMA'
also try to remove the rule 50-uart.rules in /etc/udev/rules.d and reboot.
 
1 members found this post helpful.
Old 11-13-2020, 01:04 AM   #33
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Аnd using blueman, how does bluetooth behave?
Well, its sub-modules, like blueman-adapters exists with an error message saying "No adapter(s) found"

Quote:
Code:
ls /dev | grep -P 'serial|ttyS|ttyAMA'
There is a /dev/serial0 symlink, which points to /dev/ttyS0, however /dev/ttyAMA0 does not exist.

Quote:
also try to remove the rule 50-uart.rules in /etc/udev/rules.d and reboot.
I just tested this, and it did not solve the problem unfortunately. The error messages are the same as before, and the only difference is that /dev/serial0 does not exist after the reboot, but that is likely due to the udev rules we disabled.

Pehaps some config.txt magic is necessary to enable bluetooth, and turn off the serial interface?

PS: dl.fail.pp.ua seems to be down at the moment.

Last edited by wowbaggerHU; 11-13-2020 at 01:05 AM.
 
Old 11-13-2020, 07:37 AM   #34
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
so yes no ttyAMA0 interface
try adding to config.txt:
Code:
core_freq=250
and check in the system should be ttyS0 and ttyAMA0

next add
Code:
dtoverlay=miniuart-bt
and check

next add
Code:
earlycon=uart8250,mmio32,0x3f215040
earlycon=pl011,mmio32,0x3f201000
also at all stages it is desirable to see dmesg
 
1 members found this post helpful.
Old 11-15-2020, 10:25 AM   #35
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Hi Mara,

Quote:
Originally Posted by sndwvs View Post
Code:
core_freq=250
and check in the system should be ttyS0 and ttyAMA0
Code:
# dmesg -T | grep -iE '(tty|blue|uart|AMA)'
[Sun Nov 15 15:41:45 2020] Kernel command line: root=/dev/mmcblk0p2 ro rootwait rootfstype=ext4 init=/sbin/init console=ttyS0,115200n8 earlyprintk console=tty1 loglevel=4 coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1
[Sun Nov 15 15:41:45 2020] printk: console [tty1] enabled
[Sun Nov 15 15:41:45 2020] Serial: AMBA PL011 UART driver
[Sun Nov 15 15:41:46 2020] printk: console [ttyS0] disabled
[Sun Nov 15 15:41:46 2020] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 61, base_baud = 31250000) is a 16550
[Sun Nov 15 15:41:46 2020] printk: console [ttyS0] enabled
[Sun Nov 15 15:41:46 2020] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 66, base_baud = 0) is a PL011 rev2
[Sun Nov 15 15:41:46 2020] serial serial0: tty port ttyAMA0 registered
[Sun Nov 15 15:41:52 2020] Bluetooth: Core ver 2.22
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI device and connection manager initialized
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI socket layer initialized
[Sun Nov 15 15:41:52 2020] Bluetooth: L2CAP socket layer initialized
[Sun Nov 15 15:41:52 2020] Bluetooth: SCO socket layer initialized
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI UART driver ver 2.3
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI UART protocol H4 registered
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI UART protocol Three-wire (H5) registered
[Sun Nov 15 15:41:52 2020] Bluetooth: HCI UART protocol Broadcom registered
[Sun Nov 15 15:41:52 2020] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
[Sun Nov 15 15:41:52 2020] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
[Sun Nov 15 15:41:52 2020] uart-pl011 3f201000.serial: no DMA platform data
[Sun Nov 15 15:41:53 2020] Bluetooth: hci0: BCM: chip id 94
[Sun Nov 15 15:41:53 2020] Bluetooth: hci0: BCM: features 0x2e
[Sun Nov 15 15:41:53 2020] Bluetooth: hci0: BCM43430A1
[Sun Nov 15 15:41:53 2020] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
[Sun Nov 15 15:41:53 2020] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch
[Sun Nov 15 15:41:55 2020] Bluetooth: hci0: command 0xfc18 tx timeout
[Sun Nov 15 15:42:03 2020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[Sun Nov 15 15:42:05 2020] Bluetooth: hci0: command 0x0c03 tx timeout
[Sun Nov 15 15:42:07 2020] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Sun Nov 15 15:42:07 2020] Bluetooth: BNEP filters: protocol multicast
[Sun Nov 15 15:42:07 2020] Bluetooth: BNEP socket layer initialized
[Sun Nov 15 15:42:14 2020] Bluetooth: hci0: BCM: Reset failed (-110)
[Sun Nov 15 15:42:16 2020] Bluetooth: hci0: command 0xfc18 tx timeout
[Sun Nov 15 15:42:24 2020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[Sun Nov 15 15:42:24 2020] Bluetooth: hci0: Failed to set baudrate
[Sun Nov 15 15:42:26 2020] Bluetooth: hci0: command 0x0c03 tx timeout
[Sun Nov 15 15:42:34 2020] Bluetooth: hci0: BCM: Reset failed (-110)
# ls -l /dev | grep -P 'serial|ttyS|ttyAMA'
crw-rw---- 1 root dialout   4,  64 Jan  1  1970 ttyS0
Quote:
next add
Code:
dtoverlay=miniuart-bt
and check
the system did not boot, when this option was active (not commented out) in config.txt
I also tried setting enable_uart to 0 or 1, but it did not matter when dtoverlay=miniuart-bt was active.

Is there any point in trying the third set of config options, now that we see that dtoverlay=miniuart-bt does not work?
 
Old 11-15-2020, 10:51 AM   #36
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
try not to use u-boot replacing in /boot/config.txt
Code:
#kernel=u-boot.bin
kernel=Image
the logs show that the interfaces are initialized:
Code:
[Sun Nov 15 15:41:46 2020] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 61, base_baud = 31250000) is a 16550
[Sun Nov 15 15:41:46 2020] printk: console [ttyS0] enabled
[Sun Nov 15 15:41:46 2020] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 66, base_baud = 0) is a PL011 rev2
[Sun Nov 15 15:41:46 2020] serial serial0: tty port ttyAMA0 registered
and on the other core there are these interfaces?

try in /boot/uEnv.txt change 8250.nr_uarts=1 to 8250.nr_uarts=6 or delete it altogether.
 
1 members found this post helpful.
Old 11-15-2020, 11:05 AM   #37
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
try not to use u-boot replacing in /boot/config.txt
Code:
#kernel=u-boot.bin
kernel=Image
Yes, after changing this, the system at least boots normally.

Code:
root@raspberry-pi-3:~# ls -l /dev | grep -P 'serial|ttyS|ttyAMA'
crw-rw---- 1 root dialout 204,  64 Jan  1  1970 ttyAMA0
root@raspberry-pi-3:~# dmesg -T | grep -iE '(tty|blue|uart|AMA|serial)'
[Sun Nov 15 16:58:20 2020] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  root=/dev/mmcblk0p2 ro rootwait nofont selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 elevator=noop snd-bcm2835.enable_compat_alsa=0
[Sun Nov 15 16:58:20 2020] printk: console [tty0] enabled
[Sun Nov 15 16:58:20 2020] Serial: AMBA PL011 UART driver
[Sun Nov 15 16:58:21 2020] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[Sun Nov 15 16:58:21 2020] uart-pl011 3f201000.serial: there is not valid maps for state default
[Sun Nov 15 16:58:21 2020] uart-pl011 3f201000.serial: cts_event_workaround enabled
[Sun Nov 15 16:58:21 2020] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 66, base_baud = 0) is a PL011 rev2
[Sun Nov 15 16:58:21 2020] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 61, base_baud = 31250000) is a 16550
[Sun Nov 15 16:58:21 2020] serial serial0: tty port ttyS0 registered
[Sun Nov 15 16:58:23 2020] Bluetooth: Core ver 2.22
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI device and connection manager initialized
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI socket layer initialized
[Sun Nov 15 16:58:23 2020] Bluetooth: L2CAP socket layer initialized
[Sun Nov 15 16:58:23 2020] Bluetooth: SCO socket layer initialized
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI UART driver ver 2.3
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI UART protocol H4 registered
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI UART protocol Three-wire (H5) registered
[Sun Nov 15 16:58:23 2020] Bluetooth: HCI UART protocol Broadcom registered
[Sun Nov 15 16:58:24 2020] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
[Sun Nov 15 16:58:24 2020] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
[Sun Nov 15 16:58:24 2020] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Sun Nov 15 16:58:24 2020] usb usb1: SerialNumber: 3f980000.usb
[Sun Nov 15 16:58:24 2020] Bluetooth: hci0: BCM: chip id 94
[Sun Nov 15 16:58:24 2020] Bluetooth: hci0: BCM: features 0x2e
[Sun Nov 15 16:58:24 2020] Bluetooth: hci0: BCM43430A1
[Sun Nov 15 16:58:24 2020] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
[Sun Nov 15 16:58:24 2020] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch
[Sun Nov 15 16:58:24 2020] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sun Nov 15 16:58:25 2020] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sun Nov 15 16:58:25 2020] usb 1-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[Sun Nov 15 16:58:27 2020] Bluetooth: hci0: command 0xfc18 tx timeout
[Sun Nov 15 16:58:35 2020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[Sun Nov 15 16:58:37 2020] Bluetooth: hci0: command 0x0c03 tx timeout
[Sun Nov 15 16:58:39 2020] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Sun Nov 15 16:58:39 2020] Bluetooth: BNEP filters: protocol multicast
[Sun Nov 15 16:58:39 2020] Bluetooth: BNEP socket layer initialized
[Sun Nov 15 16:58:46 2020] Bluetooth: hci0: BCM: Reset failed (-110)
[Sun Nov 15 16:58:48 2020] Bluetooth: hci0: command 0xfc18 tx timeout
[Sun Nov 15 16:58:56 2020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[Sun Nov 15 16:58:56 2020] Bluetooth: hci0: Failed to set baudrate
[Sun Nov 15 16:58:58 2020] Bluetooth: hci0: command 0x0c03 tx timeout
[Sun Nov 15 16:59:06 2020] Bluetooth: hci0: BCM: Reset failed (-110)
[Sun Nov 15 16:59:53 2020] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Sun Nov 15 17:00:54 2020] Bluetooth: hci0: command 0xfc18 tx timeout
[Sun Nov 15 17:01:02 2020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[Sun Nov 15 17:01:02 2020] Bluetooth: hci0: Failed to set baudrate
[Sun Nov 15 17:01:04 2020] Bluetooth: hci0: command 0x0c03 tx timeout
[Sun Nov 15 17:01:12 2020] Bluetooth: hci0: BCM: Reset failed (-110)
root@raspberry-pi-3:~# cat /boot/uEnv.txt 
verbosity=4
console=both
extraargs=coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1
fdtfile=bcm2837-rpi-3-b.dtb
rootdev=/dev/mmcblk0p2
8250.nr_uarts=6
root@raspberry-pi-3:~# cat /boot/config.txt 
# See /boot/overlays/README for all available options

# Our kernels are located on a Linux partition. Chainload U-Boot to load them.
#kernel=u-boot.bin
kernel=Image

# Use 32 MB for GPU for all RPis (Min 16 - Max 192 MB)
# We don't need that much memory reserved for it, because we drive most hardware
# from Linux, not the VPU OS
gpu_mem=32

arm_64bit=1

# Turbo mode: 0 = enable dynamic freq/voltage - 1 = always max
force_turbo=0
# Start in turbo mode for 30 seconds or until cpufreq sets a frequency
initial_turbo=30

# DO NOT overvoltage manually to not void warranty!
over_voltage=0

# Fix mini UART input frequency, and setup/enable up the UART.
enable_uart=1
core_freq=250

# Disable warning overlays as they don't work well together with linux's graphical output
avoid_warnings=1

# This overlay fixes divergences between the RPi device tree and what
# upstream provides
dtoverlay=upstream

# overscan is only needed on old TV sets and if analog gear is in the chain (e.g. DPI)
disable_overscan=1
dtoverlay=miniuart-bt,krnbt=on

[pi3]
# These are not applied automatically? Needed to use respective upstream drivers.
dtoverlay=vc4-kms-v3d,cma-default
dtoverlay=dwc2

[all]
dtparam=i2c_arm=on
dtparam=spi=on
dtparam=audio=on
root@raspberry-pi-3:~#
Quote:
and on the other core there are these interfaces?
I believe the output above may have already answered this question.

Originally there was nothing UART related in uEnv.txt. I just put 8250.nr_uarts=6 there.

Last edited by wowbaggerHU; 11-15-2020 at 11:08 AM.
 
Old 11-15-2020, 11:20 AM   #38
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
I did not quite understand at what point everything worked.
8250.nr_uarts=1 is in the extraargs line

if the kernel is loaded immediately, changing u-boot.bin means something is wrong with the kernel/dtb, you need to try another kernel kernel-bcm2837-5.7.6-aarch64-2mara.txz.

Last edited by sndwvs; 11-15-2020 at 11:33 AM.
 
Old 11-15-2020, 12:03 PM   #39
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
8250.nr_uarts=1 is in the extraargs line
Yes, you are absolutely right, I missed that part. So the last time 1 was active, now I tried with 6, but that did not make any difference, the error messages stayed the same.
With the setting removed from uEnv.txt, nothing changed.

Quote:
if the kernel is loaded immediately, changing u-boot.bin means something is wrong with the kernel/dtb, you need to try another kernel kernel-bcm2837-5.7.6-aarch64-2mara.txz.
Yes, I was using 5.9.2, but I guess I'll grab/build a new image with a newer/older kernel, and tools.
 
Old 11-16-2020, 02:34 AM   #40
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
wowbaggerHU, a board rpi 3b or rpi 3b plus?
Code:
cat /proc/device-tree/compatible

Last edited by sndwvs; 11-16-2020 at 02:42 AM.
 
Old 11-16-2020, 04:10 AM   #41
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
wowbaggerHU, a board rpi 3b or rpi 3b plus?
Code:
cat /proc/device-tree/compatible
It's a model B.

Code:
raspberrypi,3-model-bbrcm,bcm2837
 
Old 12-28-2020, 10:57 AM   #43
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Hi sndwvs,

I tried again with a new build of Slarm64, this time with kernel 5.9.13.
The system booted up fine, but after a successful login on X, I was greeted by a white screen, with a black cursor, and that was it. No other visible features were present on the screen.
I tried to switch to the console, and went to runlevel 3, and tried to manually start X.
The result was the same, but at least I got some X error messages in Xorg.0.log saying:
Code:
(EE) modeset(0): Failed to make 1920x1080x32bpp GBM bo
(EE) glamor: Failed to allocate 1920x1080 FBO fue to GL_OUT_OF_MEMORY
(EE) glamor: Expect reduced performance
I tried setting the video memory to 64 MB from the default 32 MB in /boot/config.txt but that did not help either.
Plus Bluetooth still doesn't seem to work.
 
Old 12-28-2020, 11:06 AM   #44
sndwvs
Member
 
Registered: Aug 2014
Posts: 892

Original Poster
Rep: Reputation: Disabled
Hi wowbaggerHU,

let's see dmesg and Xorg.0.log

try and restart X
Code:
cat <<EOF>/etc/X11/xorg.conf.d/20-device.conf 
Section "Device"
     Identifier  "Device0"
     Driver      "modesetting"
     Option      "PageFlip" "off"
EndSection
EOF
Quote:
Originally Posted by wowbaggerHU View Post
Plus Bluetooth still doesn't seem to work.
we need to understand this is a kernel or bootloader problem,
1 that you need to take a known working kernel with dtb and boot through u-boot, if everything also works, then there is a problem with the kernel or dtb.

Last edited by sndwvs; 12-28-2020 at 01:43 PM.
 
Old 12-29-2020, 02:56 AM   #45
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 177

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Hi wowbaggerHU,

let's see dmesg and Xorg.0.log
Okay, I attached the logs:
0 is the default dmesg, without being logged in into X.
1 are the logs of the machine after logging into X.
2 are the logs of the machine after adding your 20-device.conf, restarting X, and logging in.

I raised the video memory in config.txt to 96 MB, but that doesn't seem to make much difference.
In case "2", all the difference your settings made, was that the backfground was now black, and there was a very small white rectangle in the top left corner.

PS: AFAIK the GUI was working around the time kernel 5.9.2 was being shipped along images-build-kit.
Attached Files
File Type: txt dmesg.out.0.txt (26.6 KB, 4 views)
File Type: txt dmesg.out.1.txt (91.1 KB, 2 views)
File Type: txt dmesg.out.2.txt (89.0 KB, 2 views)
File Type: txt Xorg.1.log.txt (39.5 KB, 6 views)
File Type: txt Xorg.2.log.txt (37.5 KB, 4 views)

Last edited by wowbaggerHU; 12-29-2020 at 07:11 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Raspberry Pi 4 bcm2711 (aarch64) sndwvs Slackware - ARM 36 03-25-2021 01:55 PM
LXer: Raspberry Pi: Combine a Raspberry Pi with up to 4 Raspberry Pi Zeros for less than US$50 with the Cluster HAT LXer Syndicated Linux News 0 07-05-2019 12:03 PM
LXer: AArch64 Called For Merging To GCC Trunk LXer Syndicated Linux News 0 10-23-2012 05:42 PM
LXer: ARM64/AArch64 Support Going Into Linux 3.7 Kernel LXer Syndicated Linux News 0 10-02-2012 06:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 08:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration