In my use case, it would be helpful if the FTDI USB to serial and JTAG
device could be powered from the mini-USB connector's 5V power, like
the USB hub is, and that the rest of the board could be configured to
only accept power from the external power supply connection.
Currently, the 3.3V for the FTDI device is generated in the TPS65217
and is the same power rail that supplies the ARM SoC. So, the FTDI
chip and the ARM SoC get powered together, either both are powered or
neither is powered.
I'd like to be able to connect my BeagleBone to my host PC, open my
serial terminal, and then power on the BeagleBone ARM SoC. In this
way, I can observe x-loader and u-boot running from a cold boot. With
the current configuration, either I miss the cold boot and I can press
the reset button to observe a warm reset, or I have to manually hold
the reset button down when connecting the USB cable and launching my
serial terminal (this feat requires 3 hands - 2 to type, 1 to hold
reset button). This 3 hand maneuver is required because the FTDI
device won't be recognized as a serial port by the host PC until it is
powered, and I usually can't launch a serial terminal if no serial
port exists.
My desire would mean that a 5V to 3.3V dc-dc converter would be needed
and its sole purpose in life would be to provide power to the FTDI
chip. Its addition would increase the cost of the BeagleBone and
possibly also the required board size / space, so that it could fit.
There would also need to be a reasonable way (removal of a 0-ohm
resistor?) of keeping the present power configuration (either USB or
external 5V can power entire BeagleBone) or using my desired power
configuration.
I understand the tradeoff being made. I don't disagree with the
current design for the common BeagleBone use case, but my use case is
one where observing and interacting with x-loader / u-boot from cold
boot is desired.
Thanks!