-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
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. |
So if I understand you correctly, the current firmware will use the B+ DTB on the Pi0W? |
The bcm2708-rpi-0-w.dtb in the NOOBS zip is there in error and almost certainly is not being used ( |
No worries. Thanks. |
I think this is somehow related: |
What is the Revision number in /proc/cpuinfo? |
`pi@raspberrypi:~ $ cat /proc/cpuinfo Hardware : BCM2708 |
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. |
@PythonSmith can you add to config.txt and check if things change. |
This will only work if your boardrev is currently unprogrammed. |
The first value didnt work, bootloop with periodic ACT blink and had a lightning on the screen |
I just found this table: http://elinux.org/RPi_HardwareHistory |
Is there any work around? |
Can you run |
pi@raspberrypi:~ $ sudo vcgencmd otp_dump > otp_dump.txt
|
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. |
I have exactly the same issue witt the same output for |
Although technically possible, reprogramming in the field would require us to divulge some secret keys, so unfortunately the answer is effectively no. |
Another with same issue will try noobs then post back |
Please help us, explain how to flash a firmware in the WiFi chip to fix it. |
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. |
I have the same issue but mine has line 28 and 29 slightly different: |
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). |
Thank you for the prompt reply. I have contacted my distributor for advice on a return. Have a Happy New Year. |
I've also experiencing the same problem... But my lines at 16,27,28,29 and 30 are different... |
I'm having the same problem. Guess I have to return it. =( |
.08:00000000 For reference* |
Yes, unfortunately. |
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):
vcgencmd otp_dump:
|
@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? |
Thanks for the quick answer! 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. |
Lost all wireless capabilities on my Pi 0 W just today. 08-15: 00000000 16: 24280000 17: 1020000a 18: 1020000a 19-26: ffffffff 27: 00005050 28: bb635847 29: 449ca7b8 30: 009000c1 31-66: 00000000 |
That also looks normal. |
Ok, Thanks for the fast reply. Will continue my journey for a solution. |
Hello, my raspberry pi zero does not recognize the camera "raspberry pi camera rev 1.3" I have raspbian lite installed |
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. |
Where is bcm2708-rpi-0-w.dtb ? It is not being pulled into the NOOBS build.
The text was updated successfully, but these errors were encountered: