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 · 22 comments

Comments

Projects
None yet
8 participants
@procount

procount commented Mar 2, 2017

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

@pelwell

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

procount commented Mar 2, 2017

No worries. Thanks.

@PythonSmith

This comment has been minimized.

PythonSmith commented Mar 18, 2017

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

This comment has been minimized.

Contributor

pelwell commented Mar 18, 2017

What is the Revision number in /proc/cpuinfo?

@PythonSmith

This comment has been minimized.

PythonSmith commented Mar 18, 2017

`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

This comment has been minimized.

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

This comment has been minimized.

Contributor

popcornmix commented Mar 18, 2017

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

and check if things change.

@pelwell

This comment has been minimized.

Contributor

pelwell commented Mar 18, 2017

This will only work if your boardrev is currently unprogrammed.

@PythonSmith

This comment has been minimized.

PythonSmith commented Mar 18, 2017

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

This comment has been minimized.

PythonSmith commented Mar 18, 2017

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

@PythonSmith

This comment has been minimized.

PythonSmith commented Mar 19, 2017

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

This comment has been minimized.

Contributor

pelwell commented Mar 19, 2017

Can you run vcgencmd otp_dump and post the output?

@PythonSmith

This comment has been minimized.

PythonSmith commented Mar 19, 2017

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

This comment has been minimized.

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

This comment has been minimized.

Ruffio commented Apr 3, 2017

@procount, @pelwell Can this issue be closed?

@pelwell pelwell closed this Apr 3, 2017

@Jelmer-H

This comment has been minimized.

Jelmer-H commented Apr 24, 2018

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

This comment has been minimized.

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

This comment has been minimized.

blucmal commented Aug 19, 2018

Another with same issue will try noobs then post back

@acassis

This comment has been minimized.

acassis commented Aug 29, 2018

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

@pelwell

This comment has been minimized.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment