Setting the OTP bit is--essentially--a hardware change. 4-10-2017 Raspbian is the software that will recognize that change.DMackG wrote:Just to be clear.....Do you still need the OTP even with Raspbian 4-10-2017?
That's not quite correct - the OTP bit is checked by the boot ROM inside the BCM2837 SoC to see whether it should attempt booting from USB. This is an earlier stage in the boot process - before Linux has started loading.W. H. Heydt wrote:Setting the OTP bit is--essentially--a hardware change. 4-10-2017 Raspbian is the software that will recognize that change.DMackG wrote:Just to be clear.....Do you still need the OTP even with Raspbian 4-10-2017?
That's part of why I said "essentially". Yes, setting a bit (so that the boot ROM will check for a bootable USB device if there is no bootable SD card (or eMMC) is really "software", or--more likely--"firmware", but since it's (a) a one time irreversible change, and (b) entirely internal to the SoC, it functions as a hardware change. And, indeed, it *is* a change to the hardware, albeit a very minor one.andrum99 wrote:That's not quite correct - the OTP bit is checked by the boot ROM inside the BCM2837 SoC to see whether it should attempt booting from USB. This is an earlier stage in the boot process - before Linux has started loading.W. H. Heydt wrote:Setting the OTP bit is--essentially--a hardware change. 4-10-2017 Raspbian is the software that will recognize that change.DMackG wrote:Just to be clear.....Do you still need the OTP even with Raspbian 4-10-2017?
As part of your exploration, you might take a look at the WD Labs "PiDrive Node Zero".linux_author wrote:good posts in this thread... i'm getting ready to explore USB [boot] filesystem support for the pi0 series (personally, i think this form factor is the future of the Raspberry Pi offerings - JMHO mind you)... i know others here are better versed in the effort...
willie
on the tiny-computing Gulf of Mexico
Yes WD Labs have created some great products: https://www.wdc.com/products/wdlabs/wd- ... -zero.htmlW. H. Heydt wrote:As part of your exploration, you might take a look at the WD Labs "PiDrive Node Zero".linux_author wrote:good posts in this thread... i'm getting ready to explore USB [boot] filesystem support for the pi0 series (personally, i think this form factor is the future of the Raspberry Pi offerings - JMHO mind you)... i know others here are better versed in the effort...
willie
on the tiny-computing Gulf of Mexico
tks, folks! placed an order for a node and enclosure - should be fun, especially with a pi0w!fruitoftheloom wrote:Yes WD Labs have created some great products: https://www.wdc.com/products/wdlabs/wd- ... -zero.htmlW. H. Heydt wrote:As part of your exploration, you might take a look at the WD Labs "PiDrive Node Zero".linux_author wrote:good posts in this thread... i'm getting ready to explore USB [boot] filesystem support for the pi0 series (personally, i think this form factor is the future of the Raspberry Pi offerings - JMHO mind you)... i know others here are better versed in the effort...
willie
on the tiny-computing Gulf of Mexico
I wasn't disputing that part of your statement, which is correct. The part that is not correct is where you state that Raspian 2017-04-10 is the software that recognises the OTP bit being changed.W. H. Heydt wrote:That's part of why I said "essentially". Yes, setting a bit (so that the boot ROM will check for a bootable USB device if there is no bootable SD card (or eMMC) is really "software", or--more likely--"firmware", but since it's (a) a one time irreversible change, and (b) entirely internal to the SoC, it functions as a hardware change. And, indeed, it *is* a change to the hardware, albeit a very minor one.
If the OTP bit were to be set as part of the masks in the chip manufacturing, no one would question that it was a hardware change. If it gets set as part of board manufacturing, most people would consider it to be a hardware change. The only time it's going to be debated is when the end user can "blow" the bit himself. So for all *practical* purposes, it's a change to the hardware. (This is not the place for the classic joke about what "for all practical purposes" means.)
All of this is, after all, where the line between software and hardware gets a little fuzzy.
How do I force BRANCH=next rpi-update ? Writing on /boot/config.txt ?ayttransfer wrote:Just a general notice to others looking into this USB booting. Once I forced another BRANCH=next rpi-update everything worked perfectly (using a SanDisk Ultra Fit USB 3.0 Flash Drive, 64 GB). I'm using my RPi3 normally without any need for an SD card. Further, other distributions besides Raspbian have also worked for me, including RetroPie and Ubuntu-MATE.
Did you edit /coot/config.txt (wrong) or /boot/cmdline.txt (correct) ?Nastanir wrote:I have tried to use USB boot and this is what happened. Suggestions are welcome.
1. Pi3 + 2017-04-10 Raspbian on a sd card, booted
2. Edited the /boot/config.txt, sudo reboot. No problem.
3. Shutdown, removed sd card. Booting with a Sandisk ultrafit 32GB drive having same software installed using dd.
4. Booting starts after few seconds, progressed and then stays stuck for at least 15min. Drive activity LED occasionally blinks.
5. Screen shot is below
I can boot with sd card without problem.
make sure that the /boot/cmdline.txt "root=" entry on your new 'boot usb drive' points to the second partition of your ultrafit... during the dd copy, an incorrect partition id will be copied from the sd card!Nastanir wrote:I have tried to use USB boot and this is what happened. Suggestions are welcome.
1. Pi3 + 2017-04-10 Raspbian on a sd card, booted
2. Edited the /boot/config.txt, sudo reboot. No problem.
3. Shutdown, removed sd card. Booting with a Sandisk ultrafit 32GB drive having same software installed using dd.
4. Booting starts after few seconds, progressed and then stays stuck for at least 15min. Drive activity LED occasionally blinks.
5. Screen shot is below
I can boot with sd card without problem.
Yeah, thanks!DougieLawson wrote:sudo apt-get update && sudo apt-get dist-upgrade will get you a 4.9.24+/4.9.24-v7+ kernel and that includes everything you need for USB booting.
According to the documentation the Pi will find all mass storage devices, then check each in turn for a bootcode.bin that it can boot from. This implies that if you have more than one bootable mass storage device then there is no way to select which one the Pi actually boots from, unless you can somehow ensure that one gets found first.ralphrmartin wrote:If I have 2 USB drives, is there a way to specify which one is used as the boot drive (the other one is used for backing up the boot drive, so both are bootable...)
Just to verify: I'm booting on a USB SSD since https://www.raspberrypi.org/blog/pi-3-b ... rage-boot/ was published but had the same problem that sudo apt-get update && sudo apt-get upgrade broke that booting.eaque wrote:Yeah, thanks!DougieLawson wrote:sudo apt-get update && sudo apt-get dist-upgrade will get you a 4.9.24+/4.9.24-v7+ kernel and that includes everything you need for USB booting.
I was asking because it messed up my RPi when I tried 2 months ago (it wasn't able to boot on the HDD).
Good to know !
without breaking my system again?DougieLawson wrote:sudo apt-get update && sudo apt-get dist-upgrade
Yes. rpi-update is not needed anymore.sihui wrote:May I switch towithout breaking my system again?DougieLawson wrote:sudo apt-get update && sudo apt-get dist-upgrade