I have RPi 3 model B rev 1.2 and couple of questions

Dears,

I’m pretty new to RPi world and OSMC. Just bought RPi 3 model B rev 1.2 and I’m wondering about some hardware stuff.

Here is the lshw output:

description: Computer
product: Raspberry Pi 3 Model B Rev 1.2
serial: 00000000df595951
width: 32 bits
*-core
description: Motherboard
physical id: 0
capabilities: brcm_bcm2837 brcm_bcm2836
*-cpu:0
description: CPU
product: cpu
physical id: 0
bus info: cpu@0
size: 1200MHz
capacity: 1200MHz
capabilities: cpufreq
*-cpu:1 DISABLED
description: CPU
product: cpu
physical id: 1
bus info: cpu@1
size: 1200MHz
capacity: 1200MHz
capabilities: cpufreq
*-cpu:2 DISABLED
description: CPU
product: cpu
physical id: 2
bus info: cpu@2
size: 1200MHz
capacity: 1200MHz
capabilities: cpufreq
*-cpu:3 DISABLED
description: CPU
product: cpu
physical id: 3
bus info: cpu@3
size: 1200MHz
capacity: 1200MHz
capabilities: cpufreq
*-memory
description: System memory
physical id: 4
size: 747MiB
*-usbhost
product: DWC OTG Controller
vendor: Linux 4.9.29-10-osmc dwc_otg_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 4.09
capabilities: usb-2.00
configuration: driver=hub slots=1 speed=480Mbit/s
*-usb
description: USB hub
vendor: Standard Microsystems Corp.
physical id: 1
bus info: usb@1:1
version: 2.00
capabilities: usb-2.00
configuration: driver=hub maxpower=2mA slots=5 speed=480Mbit/s
*-usb:0
description: Generic USB device
product: SMSC9512/9514 Fast Ethernet Adapter
vendor: Standard Microsystems Corp.
physical id: 1
bus info: usb@1:1.1
version: 2.00
capabilities: usb-2.00
configuration: driver=smsc95xx maxpower=2mA speed=480Mbit/s
*-usb:1
description: Mass storage device
product: Ultra
vendor: SanDisk
physical id: 2
bus info: usb@1:1.2
logical name: scsi0
version: 1.00
serial: 4C530001280402110401
capabilities: usb-2.10 scsi emulated
configuration: driver=usb-storage maxpower=224mA speed=480Mbit/s
*-disk
description: SCSI Disk
product: Ultra
vendor: SanDisk
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 1.00
serial: 4C530001280402110401
size: 57GiB (62GB)
capabilities: removable
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
*-medium
physical id: 0
logical name: /dev/sda
size: 57GiB (62GB)
capabilities: partitioned partitioned:dos
configuration: signature=00053864
*-volume:0
description: EXT4 volume
vendor: Linux
physical id: 1
logical name: /dev/sda1
logical name: /
version: 1.0
serial: f958505c-b155-420b-b60b-1bea81454160
size: 54GiB
capacity: 54GiB
capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=1970-01-01 01:01:22 filesystem=ext4 lastmountpoint=/ modified=1970-01-01 01:00:04 mount.fstype=ext4 mount.options=rw,noatime,discard,stripe=1024,data=ordered mounted=1970-01-01 01:00:04 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
logical name: /dev/sda2
version: 1
serial: 6398d9f8-a1ab-4b42-9f34-02444f53fb8c
size: 3GiB
capacity: 3GiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap label=paging00 pagesize=4096
*-usb:2
description: Mass storage device
product: USB FLASH DRIVE
vendor: TOSHIBA
physical id: 4
bus info: usb@1:1.4
logical name: scsi1
version: 1.10
serial: 0060E049DF6AE061214906C2
capabilities: usb-2.00 scsi emulated
configuration: driver=usb-storage maxpower=300mA speed=480Mbit/s
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/sdb
size: 28GiB (30GB)
capabilities: partitioned partitioned:dos
configuration: logicalsectorsize=512 sectorsize=512 signature=00053864
*-volume
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: scsi@1:0.0.0,1
logical name: /dev/sdb1
logical name: /home/osmc/Music
version: 1.0
serial: f958505c-b155-420b-b60b-1bea81454160
size: 26GiB
capacity: 28GiB
capabilities: primary journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=1970-01-01 01:01:22 filesystem=ext4 lastmountpoint=/home/osmc/Music modified=2017-11-06 22:12:44 mount.fstype=ext4 mount.options=rw,relatime,discard,stripe=1024,data=ordered mounted=2017-11-06 22:12:44 state=mounted
*-network:0
description: Wireless interface
physical id: 2
logical name: wlan0
serial: b8:27:eb:0c:0c:04
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=brcmfmac driverversion=7.45.41.46 firmware=01-f8a78378 ip=192.168.255.254 multicast=yes wireless=IEEE 802.11
*-network:1
description: Ethernet interface
physical id: 3
logical name: eth0
serial: b8:27:eb:59:59:51
size: 100Mbit/s
capacity: 100Mbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=smsc95xx driverversion=22-Aug-2005 duplex=full firmware=smsc95xx USB 2.0 Ethernet ip=192.168.1.20 link=yes multicast=yes port=MII speed=100Mbit/s

My concerns are why most of the CPU cores have status DISABLED?
How to make them enabled… like permanently?

Second thing is Bluetooth. Do this model have one? I though so but I do not see any evidences.
Checked dmesg and lshw, tried to load some kernel modules (btbcm) but no luck… hciconfig shows only empty output. Maybe it is somehow disabled?

Please help…

Run sudo lshw than you will see Bluetooth wireless interface

Just a display issue of lshw
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=147268

Sorry, nope… I’m running lshw directly from root account…
Is there any other way to check if I have a bluetooth and how to enable it?

Sorry, I forgot that I have a USB Bluetooth plugged in (as the internal bluetooth has issues with A2DP)

Generally you don’t need to do anything to activate it, you just would need to set something in config.txt if you want to disable it.
Are you on the latest software version?

Yes, installed OSMC and update to the latest. But I really cannot track any evidences that there is
bluetooth inside :roll_eyes:
I wonder what is going on, the RPi is damaged somehow or what?

Can somebody with exactly the same RPi model check and see for bluetooth?

EVERY Raspberry pi 3 has Bluetooth. Did you look in Programs≥Myosmc>networking?

Yes I did, there is no Bluetooth section at all. Only Wired, Wireless and MySQL ^^

Confirmed BT working on a Rasberry Pi 3 Model B Rev. 1.2 (PN FERPI SSB35, Lot#161018). I use it for my BT Wedge keyboard only… I don’t know about A2DP.

Hello giulix,

Can you paste here your dmesg and lsmod outputs?
Many thanks in advance.

There you go…

OK, found the solution.

/usr/bin/hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -

This loads the firmware and sets the device.

Thanks you all for supporting.

That is run automatically – you shouldn’t need to run this yourself at boot.

Hello Sam,

I did couple of reboots and it looks like I need to run it manually :expressionless:
For testing purposes I mangled the /usr/bin/rpi-btuart adding touch /tmp/btuart and rebooting.
Looks like it is not run at boot… maybe in the past I have disabled some systemd service o.0.
Can you explain from where this script is executed?

Before you go too far into this it sounds like there may be something bad with your build. I’d perhaps suggest reimaging your SD card and starting over before you invest too much time into this install.

Too late… it would be much more time consuming to backup and restore all the stuff I have here on RPi :wink:
Temporary solution, I have added rpi-btuart to /etc/rc.local.

Looking at the systemd code, /usr/bin/rpi-btuart is run from brcm43xx.service, which is by default disabled (but was running on my Pi 3). So what kicked it off? AFAICT, brcm43xx.service is activated by the existence of /dev/serial1 and the directory /proc/device-tree/soc/gpio@7e200000/bt_pins.

Correct. It starts on:

ConditionPathIsDirectory=/proc/device-tree/soc/gpio@7e200000/bt_pins

Uhhhu strong amnesia here. I now recalled what I did:

● brcm43xx.service
Loaded: masked (/dev/null)
Active: inactive (dead)

All clear :smile:

But brcm43xx.service is disabled, so my reading of the code is that it gets run by bt-firmware.path, which only kicks off brcm43xx.service if /dev/serial1 exists. If correct, what’s the logic behind this?