--> it does.So, to reiterate, on the Pi3B, with both OTP bits set (two commands used in config.txt at power on), the OTP dump should give:
--> it does.With no SDCard, confirm that USB boots.
--> It does not, tested on 2 different rpi3b's.If you pull GPIO26 high, no connection (or low) to GPIO22, it should boot from USB, regardless of the presence or absence of SDCard.
Please read the first post on the topic / Because the whole wil be potted in epoxy and I want a disaster-recovery option as this is a first batch of 60 pi's and I'm afraid of my over-the-air-updating-skillsI'm not sure why you're doing this stuff - what's the point?
Please read the 1st, second, seventh, ninth post on the topic / It does not matter, there is no change. According to the documentation it should not boot at all if you leave the pins alone but there is no change, it still boots as normal off sd-card.https://www.raspberrypi.org/documentati ... ootflow.mdWhich pins are you pulling high (3V3) or low (GND)?
Yes.Are you sure you've found the right ones on the header?
Did that (maybe 5 times, on 2 pi's), the correct pins are pulled to the correct state.Leave your connections in place after your RPi boots and run gpio readall or raspi-gpio get to see the state of the pins.
I guess so, it looks like you have reached that stage.pietjepuk1001 wrote: Do you know to whom I could escalate this issue ? the firmware section on github maybe ?
You're the first.
Wow. Well done Phil, what a fantastic response. That program_gpio_bootmode needs some massive health warnings in the documentation if there's a chance it can really "brick" your RPi.PhilE wrote: ↑Sun Oct 15, 2017 8:17 pmpietjepuk1001, I think you've found a bug. The code which handles program_gpio_bootmode ends up setting the wrong bits in the OTP. Bit 19 (0x00080000) at offset 17 (and 18 for redundancy) enables the GPIO bootmode selection, while bit 20 (0x00100000) selects the high bank (39-43). By setting bit 20 instead of bit 19 the firmware has not enabled GPIO bootmode but has prevented you from successfully using it in the future on your Pi 3B.
PM me with your postal address and we'll send you a replacement. In the meantime we'll push out a fixed firmware and you should remove "program_gpio_bootmode" from the card image in the affected Pi unless you want to brick it if you ever update.
Hi ptkatch .. I'm sorry.. but these are called One Time Programmable for a reason.. They are "fuses".ptkatch wrote: ↑Fri Nov 10, 2017 12:54 amYes, please add warning to https://www.raspberrypi.org/documentati ... ootflow.md ASAP,
I fall into the same trap today
So to get corrected firmware all I need is to update kernel to 4.9.60, correct?
Thanks for the prompt issue fix.