Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PiZeroW device tree #758

Closed
procount opened this issue Mar 2, 2017 · 37 comments
Closed

PiZeroW device tree #758

procount opened this issue Mar 2, 2017 · 37 comments

Comments

@procount
Copy link

procount commented Mar 2, 2017

Where is bcm2708-rpi-0-w.dtb ? It is not being pulled into the NOOBS build.

@pelwell
Copy link
Contributor

pelwell commented Mar 2, 2017

There is currently a temporary solution in place based on the B+ DTS (like Zero). The next build is likely to contain the dedicated DTB and the firmware to load it.

@procount
Copy link
Author

procount commented Mar 2, 2017

So if I understand you correctly, the current firmware will use the B+ DTB on the Pi0W?
I ask because I built my fork of NOOBS and bcm2708-rpi-0-w.dtb was not present, but it is in the downloadable NOOBS zip file. Currently, I don't have a Pi0W to test it on, so I wanted to make sure it would work. I guess copying bcm2708-rpi-0-w.dtb would do no harm and probably would not be used until the next firmware is released?

@pelwell
Copy link
Contributor

pelwell commented Mar 2, 2017

The bcm2708-rpi-0-w.dtb in the NOOBS zip is there in error and almost certainly is not being used (sudo vcdbg log msg |& grep dtb will tell you for certain). Sorry for any confusion.

@procount
Copy link
Author

procount commented Mar 2, 2017

No worries. Thanks.

@PythonSmith
Copy link

I think this is somehow related:
I'm using Raspbian Jessie Light from the 2017-03-02 on the RPiZero W.
It boots fine however the file /sys/firmware/devicetree/base/name says the device is a RPiB Rev 2.
It also can't find it's Wifi-Adapter wlan0 (ifconfig -a, iwconfig)

@pelwell
Copy link
Contributor

pelwell commented Mar 18, 2017

What is the Revision number in /proc/cpuinfo?

@PythonSmith
Copy link

`pi@raspberrypi:~ $ cat /proc/cpuinfo
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 : BCM2708
Revision : 000f
Serial : 00000000f46969e7
`

@pelwell
Copy link
Contributor

pelwell commented Mar 18, 2017

Interesting. I don't have the code in front of me but I would guess that your board revision hasn't been programmed - f is the default value. Or perhaps it is an unrecognised number that the firmware has sanitised. Again, I'm going to have check the source.

@popcornmix
Copy link
Contributor

popcornmix commented Mar 18, 2017

@PythonSmith can you add to config.txt
force_board_rev=0x9000c0

and check if things change.

@pelwell
Copy link
Contributor

pelwell commented Mar 18, 2017

This will only work if your boardrev is currently unprogrammed.

@PythonSmith
Copy link

The first value didnt work, bootloop with periodic ACT blink and had a lightning on the screen
The second value just blinks randomly and does blackscreen after the first color screen

@PythonSmith
Copy link

I just found this table: http://elinux.org/RPi_HardwareHistory
0x9000c1 also didn't work

@PythonSmith
Copy link

Is there any work around?
I tried loading "bcm2708-rpi-0-w.dtb" with U-Boot however it just hangs at Booting the kernel.
"bcm2708-rpi-b.dtb" is working without problems. I'm really happy that I have this new Pi however without its Wifi capability it is pretty useless for me. (Because it is just a Pi Zero)

@pelwell
Copy link
Contributor

pelwell commented Mar 19, 2017

Can you run vcgencmd otp_dump and post the output?

@PythonSmith
Copy link

pi@raspberrypi:~ $ sudo vcgencmd otp_dump > otp_dump.txt

08:00000000
09:00000000
10:00000000
11:00000000
12:00000000
13:00000000
14:00000000
15:00000000
16:24280000
17:1020000a
18:1020000a
19:ffffffff
20:ffffffff
21:ffffffff
22:ffffffff
23:ffffffff
24:ffffffff
25:ffffffff
26:ffffffff
27:00000000
28:f46969e7
29:0b969618
30:00000000
31:00000000
32:00000000
33:00000000
34:00000000
35:00000000
36:00000000
37:00000000
38:00000000
39:00000000
40:00000000
41:00000000
42:00000000
43:00000000
44:00000000
45:00000000
46:00000000
47:00000000
48:00000000
49:00000000
50:00000000
51:00000000
52:00000000
53:00000000
54:00000000
55:00000000
56:00000000
57:00000000
58:00000000
59:00000000
60:00000000
61:00000000
62:00000000
63:00000000
64:00000000
65:00000000
66:00000000

@pelwell
Copy link
Contributor

pelwell commented Mar 19, 2017

Thanks. As we suspected, for some reason your Pi has not been programmed correctly at manufacturing. Fortunately this is a very rare occurrence; unfortunately it has happened to you.

Your best course of action is to return it to your supplier as faulty. You will need a Return Merchandise Authorisation - you can point them at this thread if they need confirmation of the fault.

@Ruffio
Copy link

Ruffio commented Apr 3, 2017

@procount, @pelwell Can this issue be closed?

@pelwell pelwell closed this as completed Apr 3, 2017
@Jelmer-H
Copy link

I have exactly the same issue witt the same output for vcgencmd otp_dump with my brand new Pi Zero W. Is this a faulty batch? is there any way to program the unit manually instead of requesting an RMA?

@pelwell
Copy link
Contributor

pelwell commented Apr 24, 2018

Although technically possible, reprogramming in the field would require us to divulge some secret keys, so unfortunately the answer is effectively no.

@blucmal
Copy link

blucmal commented Aug 19, 2018

Another with same issue will try noobs then post back

@acassis
Copy link

acassis commented Aug 29, 2018

Please help us, explain how to flash a firmware in the WiFi chip to fix it.

@pelwell
Copy link
Contributor

pelwell commented Aug 30, 2018

This is nothing to do with the WiFi chip - the OTP that stores the identity of the BCM2835 (B, B+, Zero, ZeroW etc.) and multiple keys has not been programmed. This is unfortunately a return-to-manufacturer fault.

@Pricem586
Copy link

I have the same issue but mine has line 28 and 29 slightly different:
28: ac07a139
29: 53f85ec6
Is mine faulty too?

@pelwell
Copy link
Contributor

pelwell commented Jan 1, 2019

Rows 28 and 29 are the serial number and its inverse, so we would expect them to be different. This also highlights that some OTP programming has been successful, but not all, meaning that your Pi is indeed faulty (underbaked, really).

@Pricem586
Copy link

Thank you for the prompt reply. I have contacted my distributor for advice on a return. Have a Happy New Year.

@Goritmi
Copy link

Goritmi commented Mar 13, 2019

I've also experiencing the same problem... But my lines at 16,27,28,29 and 30 are different...
16: 6c280000
27: 00005050
28: 6efca8b0
29: 9103574f
30: 00900c1

@StephenTurley
Copy link

I'm having the same problem. Guess I have to return it. =(

@StephenTurley
Copy link

.08:00000000
09:00000000
10:00000000
11:00000000
12:00000000
13:00000000
14:00000000
15:00000000
16:24280000
17:1020000a
18:1020000a
19:ffffffff
20:ffffffff
21:ffffffff
22:ffffffff
23:ffffffff
24:ffffffff
25:ffffffff
26:ffffffff
27:00000000
28:90cdf785
29:6f32087a
30:00000000
31:00000000
32:00000000
33:00000000
34:00000000
35:00000000
36:00000000
37:00000000
38:00000000
39:00000000
40:00000000
41:00000000
42:00000000
43:00000000
44:00000000
45:00000000
46:00000000
47:00000000
48:00000000
49:00000000
50:00000000
51:00000000
52:00000000
53:00000000
54:00000000
55:00000000
56:00000000
57:00000000
58:00000000
59:00000000
60:00000000
61:00000000
62:00000000
63:00000000
64:00000000
65:00000000
66:00000000

For reference*

@pelwell
Copy link
Contributor

pelwell commented Sep 10, 2019

Yes, unfortunately.

@mrouillard
Copy link

mrouillard commented Nov 19, 2019

Dear @pelwell, would you mind looking at my data below? I fear that I have the same issue as @PythonSmith (for the second time in a row, a brand new PiZeroW I just received):
cpuinfo:

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		: 000000005d48d8be
Model		: Raspberry Pi Zero W Rev 1.1

vcgencmd otp_dump:

08:00000000
09:00000000
10:00000000
11:00000000
12:00000000
13:00000000
14:00000000
15:00000000
16:24280000
17:1020000a
18:1020000a
19:ffffffff
20:ffffffff
21:ffffffff
22:ffffffff
23:ffffffff
24:ffffffff
25:ffffffff
26:ffffffff
27:00005050
28:5d48d8be
29:a2b72741
30:009000c1
31:00000000
32:00000000
33:00000000
34:00000000
35:00000000
36:00000000
37:00000000
38:00000000
39:00000000
40:00000000
41:00000000
42:00000000
43:00000000
44:00000000
45:00000000
46:00000000
47:00000000
48:00000000
49:00000000
50:00000000
51:00000000
52:00000000
53:00000000
54:00000000
55:00000000
56:00000000
57:00000000
58:00000000
59:00000000
60:00000000
61:00000000
62:00000000
63:00000000
64:00000000
65:00000000
66:00000000

@pelwell
Copy link
Contributor

pelwell commented Nov 19, 2019

@mrouillard Your OTP looks fine to me. The key indicator is row 30 which holds the revision code. Yours says 9000c1, which is a rev 1.1 Zero W, but /proc/cpuinfo already told you that.

What symptoms are you seeing to make you think there was a problem?

@mrouillard
Copy link

Thanks for the quick answer!
The symptom was being able to list wifi networks using "sudo iwlist wlan0 scan" but never connecting to any of them despite two of them being set in my wpa_supplicant.conf.

However, in the meantime I found an issue in the wpa_supplicant.conf file that I had put on the sdcard: one SSID was enclosed by ” instead of straight double quotes. Argh. I feel ashamed.
So actually, I have only one faulty Pi Zero W (the oldest I had). The brand new one is fine. My bad, sorry for the trouble, and thanks again for your reactivity.

@comicsansgreenki
Copy link

comicsansgreenki commented Dec 23, 2019

Lost all wireless capabilities on my Pi 0 W just today.
Had to type this one out, didn’t have a USB-Ethernet on hand.

08-15: 00000000

16: 24280000

17: 1020000a

18: 1020000a

19-26: ffffffff

27: 00005050

28: bb635847

29: 449ca7b8

30: 009000c1

31-66: 00000000

@pelwell
Copy link
Contributor

pelwell commented Dec 23, 2019

That also looks normal.

@comicsansgreenki
Copy link

Ok, Thanks for the fast reply. Will continue my journey for a solution.

@jkober
Copy link

jkober commented Nov 27, 2021

Hello, my raspberry pi zero does not recognize the camera "raspberry pi camera rev 1.3" I have raspbian lite installed

@pelwell
Copy link
Contributor

pelwell commented Nov 30, 2021

This issue was closed nearly 2 years ago. Open a new issue, explaining what you have done, what you are expecting to happen and what actually happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests