I looked at the hardware surrounding the FT232RL chip and realized that without a USB serial cable the chip reset line was being pulled low and driving this chip into reset. So I attached a 10K pull-up from R216 to Vcc and that fixed the problem. I have booted over a dozen times with and without a USB serial cable and it has not failed a single time.
I don't know if this means there is a problem with the bootloader software waiting for FT232RL to come out of reset or if the hardware should not be pulling the reset line low when a cable isn't attached, I just know this fixed the problem. The chip data sheet shows the current hardware layout for a self-powered configuration, which seems correct. So I wonder if it's more likely that u-boot hangs looking for some sort of response from the FT232RL chip.
I looked at the hardware surrounding the FT232RL chip and realized that without a USB serial cable the chip reset line was being pulled low and driving this chip into reset. So I attached a 10K pull-up from R216 to Vcc and that fixed the problem. I have booted over a dozen times with and without a USB serial cable and it has not failed a single time.
I don't know if this means there is a problem with the bootloader software waiting for FT232RL to come out of reset or if the hardware should not be pulling the reset line low when a cable isn't attached, I just know this fixed the problem. The chip data sheet shows the current hardware layout for a self-powered configuration, which seems correct. So I wonder if it's more likely that u-boot hangs looking for some sort of response from the FT232RL chip.
Anybody have any ideas?
--Matt