Hi,
Refference: www.ti.com/.../spruh73 (SPQ)
SPQ figure 26.10 shows that devices are processed in order and if no device responds then the loop is dead.
SPQ table 26.7 SYSBOOT pins - page 5035. In this example SYSBOOT[4:0] are 11100b. The boot sequence is MMC1/MMC0/UART0/USB0 (i.e. eMMC/sdcard/serial console/USB0).
I have a BeagleBone Black revC (BBB). In this example, the eMMC is blank, no sdcard, UART0 (serial console) is connected to a host computer running minicom, USB is not connected. Upon applying power, I receive ‘CCCC…’. The ‘C’s continue indefinitely.
I have a custom board based upon the BBB revC. Same example, the eMMC is blank, no sdcard, UART0 (serial console) is connected to a host computer running minicom, USB is not connected. Upon applying power, I receive eight ‘CCCCCCCC’, then a pause for approximately 22 seconds, then another set of eight ‘CCCCCCCC’, the pause again. The sequence continues indefinitely.
SPQ section 26..1.9.5 UART BOOT Procedure mentions the ROM code will ping the host 10 times in 3s to start the x-modem transfer. If the host does not respond, UART boot will time out.
Q1. Does 'ping the host' mean to send a single 'C' to the console?
I am confused. The SPQ says the ROM code will try the eMMC (blank), then the sdcard (not inserted), then UART0 (console) 10 times, then USB0 and if none are availble dead loop. The SPQ does not say the device sequence will restart.
Q2. Why does the BBB continuiously send 'CCCC...' when the ROM code states is should only send 10 'C' one time and stop?
Q3. Why does my custom board send eight 'C', pause and repeat? What is the ROM code doing during the pause?
Q4. Does the ROM code restart the boot procedure if the last device does not respond?
Thank you,

