PI Zero W - no bluetooth device found in raspbian

[mantabernd]

Good evening!

I got a brand new raspberry pi zero w and installed the latest version of raspbian jessie on it.
Unfortunately I don't get bluetooth to work. It always tells me "no adapter found"

Wifi works with no problems.

bluetoothctl also does not find any bluetooth adapters.

Is there a special trick with it or do I maybe have a broken pi?

Regards and thanks for your help!
Mantabernd

[mantabernd]

Another point...

when I power up the raspberry I get the following error:

[FAILED] Failed to start Configure Blutooth modems connected by UART

Does this have something to do with my problem?

I already activated "serial" in raspi-config. This is UART, right?

When I enter systemctl status hciuart.service it tells me that something was wrong with btuart.

Any idea?

[mantabernd]

Hmm nobody any idea? Are there no Zero W users out there who wants to use bluetooth?

[ktb]

Hmm nobody any idea? Are there no Zero W users out there who wants to use bluetooth?

I don't have a PiZW.

Did you install Raspbian Jessie or Raspbian Jessie Lite?

I can't remember if there was anything extra I had to install or configure on Jessie Lite to get Bluetooth working on my Pi3B. On Raspbian Jessie with the Pixel desktop environment, it should just work.

[mantabernd]

I tried both, Jessie with Pixel Desktop and Lite.

My actual configuration is Jessie Pixel Desktop, but booted into CLI.

Today I started using I2C and Uart via ttyS0, both worked fine. It's seriously just this stupid bluetooth what keeps my project stuck

[Douglas6]

I'm afraid I don't have a Pi0W. It sounds to me like one of two things: bad hardware, or a glitch in the latest Raspbian release. Hardware malfunctions are rare, but you'd think we would have heard of a major glitch by now.

[mikerr]

Fresh Raspbian Lite install:

Code: Select all

hciconfig -a
hci0:   Type: BR/EDR  Bus: UART
        BD Address: B8:27:EB:61:6D:77  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        RX bytes:717 acl:0 sco:0 events:42 errors:0
        TX bytes:1532 acl:0 sco:0 commands:42 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: 'raspberrypi'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous,
        HCI Version: 4.1 (0x7)  Revision: 0xb6
        LMP Version: 4.1 (0x7)  Subversion: 0x2209
        Manufacturer: Broadcom Corporation (15)

[Douglas6]

That would seem to rule out a problem with Raspbian.

[mantabernd]

Thank you guys for these replys.

You can find my output of hciconfig -a attached to this post.

As you can see serial0 goes to ttyS0 and serial 1 to ttyAMA0. This should be ok.
I just ordered a new PI Zero W and will check it out with the new one soon.

[mantabernd]

Fresh Raspbian Lite install:

@mikerr
Did you test it with Rpi 3 or Zero W?

[mikerr]

With a Pi Zero W

[mantabernd]

My new PI Zero W arrived and bluetooth works

Crazy... it's the same SD card, all same... now it's sure that my PI got a hardware bug.

Thank you for your fast support!

[MattManToo]

I'm having the same issue with my Pi Zero W. Initially it wouldn't boot (Just got the rainbow screen) but a change of memory card has dealt with that. However I am now seeing no Bluetooth adaptor with the same symptoms as mantabernd described. Not adding much info I know but at least it's not an isolated case.

[DougieLawson]

Reformat your SDCard and start with a fresh copy of NOOBS 2.3 or Raspbian 2017-03-02

[RaTTuS]

what does

Code: Select all

cat /proc/cpuinfo

say on the the bad PI0w

[kopiro]

I have the same issue.

Code: Select all

processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2835
Revision	: 9000c1
Serial		: 0000000026c33af8

[kopiro]

Okay, solved!

Just an

Code: Select all

apt-get upgrade

.

The firmware was out of date.

Now the LED on the board is blinking too

[mantabernd]

I had a closer look to the different PI Zero W's and figured that they were a bit different.
They definitely came out of different PCB productions because the colour of soldermask is a bit different. There is also a different way of printing the production week on it.

The working is from week 44/16, the not working one from 48/16.

@mikerr:
Can you verify your PI's production week and layout of printing please?



Regards
Bernhard

[mikerr]

Mine is from 48/16


Can't help but notice you have added the header pins on the bottom of your zero (not the normal top)
if you put a normal HAT on it that way around it may break something as the connections are reversed
and this is also your "faulty" pi ...

[mantabernd]

Thanks Mikerr for verifiying. This proofs that it got nothing to do with manufacturing date.

And yes I soldered the pin header on bottom because I will plug my pi later to a board what go the female connectors.
Don't worry, I didn't reverse polarity. This is not the reason. I think it's simply a hardware bug. Everything else works as expected. Uart, I2C, I2S, Bluetooth... maybe I will find the reason one day, maybe not.

[pietrushnic]

Hi,
it looks like RPiZW has hardware problems. I have 2 RPiZW and non of them show hci0 or any other BT interface (both are 44/16 version). More to that one of them suddenly lost WiFi. I compare boards on the same uSD card, so no difference in software.

The only reason I can think of is some ESD that destroyed RPi in weird way.

Any ideas for diagnosing root cause are welcome.

[Douglas6]

Start by imaging a new SD card with the latest version of Raspbian Stretch. That will rule out any hardware issue.