It varies and you can't always find the same price. The last price I paid for Nanos on Amazon was 5 for $17. Aliexpress is cheaper than that (that's where they're usually under $3), but I can't always wait that long.
[R]ecent update to the Raspberry Pi 4 bootloader
(...) enables data over the USB-C port
Am I reading this right that RPi4 has five usable USB ports, i.e. unlike earlier models, port on bottom left of the board can carry data along with power? This is awesome!
USB-C includes a USB-2 management channel in addition to the high-bandwidth lanes. It is used for things like advanced power delivery negotiation. On the Raspberry Pi 4, the USB-C port has no high-bandwidth lanes, and it only uses passive power negotiation.
> USB-C includes a USB-2 management channel in addition to the high-bandwidth lanes. It is used for things like advanced power delivery negotiation.
No, all the power delivery negotiation in USB-C, both the basic one using only passive resistor values and the advanced one using the USB-PD protocol, is through the configuration channel pins, which is a separate pair of pins completely independent from the USB 2.0 pins in the middle. (The configuration channel is implemented incorrectly on the Raspberry Pi 4, however; it shorts together the pins, while they should be separate, so it fails with advanced cables which use both pins; and when powered through a source other than the USB-C connector, it incorrectly sources 5V to the USB-C port even when it shouldn't.)
Archive.is doesn't like that cloudflare doesn't give them information about the subnet the query came from, so they give a bad reply to cloudflare. (https://news.ycombinator.com/item?id=19828317)
Using dumb cables avoids one of the issues (configuration channel pins shorted together), but not the other one (sourcing power even when the configuration channel says it shouldn't source power).
That is, the workaround is both "use only dumb cables (which use only one of the CC pins)" and "never connect to a USB-C device which might source power while the rpi is being powered by something other than the USB-C".
> "never connect to a USB-C device which might source power while the rpi is being powered by something other than the USB-C"
Wouldn't this actually apply to a lot of use-cases of the project in the linked blog?
The whole point is connecting the RPi as a peripheral of a laptop, i.e. a power-sourcing host. if you do that, you'll also likely be tempted to use an external power supply for the Pi as the USB's supply is limited. It's important to note that this will lead to problems.
> ... make a connected USB storage device that offers some sort of additional sync services for the data stored on it (maybe over wifi?)
There used to be a KS funded case built around a Pi and an HDD that would act as an external storage when plugged to a USB port and would work as Kodi based media player once booted and connected to an HDMI port.
If anybody knows if this can be done DIY style with minimal cable mess I am all ear :).
The last time i checked it needed gadget kernel driver support and root, a showstopper for me...
Apart from that, great concept: load your 5+ cd images onto your 64+ gb android and be done (win10, ubuntu, debian, grml, kali, bios update cd image, etc) and forget about your usb drive collection...
I thought modern android required the gadget driver anyway? I’m pretty I was able to use it without root but it was (supposedly) less reliable without it.
Once I didn't have any USB sticks handy and didn't know about DriveDroid, so I used Servers Ultimate to host a TFTP server so I could PXE boot the netboot.xzy image from my phone to my laptop then download+install Arch Linux.
In the Nerves project (Elixir thing for embedded linux) it is used to be able to power, SSH to the device and push new firmware changes without needing to reimage the SD card. Already used that a lot with the zero and 3A.
Source: Compiled and connected a mouse/keyboard firmware running on an ATtiny861a using internal RC oscillator.