Good day, I'm researching if it's possible to support a cheaper FT232BL-based EHCI usbdebug dongle like the already-supported FT232H -- to make EHCI debugging more accessible to the newcoming coreboot'ers -- and need the detailed logs (i.e. CONFIG_DEBUG_CONSOLE_INIT) to figure this out.
However, there's a major obstacle: because of "Pre-CBMEM romstage/ramstage console overflowed, log truncated", I couldn't get a complete EHCI initialization log. Increasing CONFIG_CONSOLE_CBMEM_BUFFER_SIZE doesn't help, because it is Pre-CBMEM.
I've already replaced its' dprintk messages with various acronyms (listed below), which has helped me to get more log, but this is not enough. Any ideas?
Could not reset EHCI controller.\n = RSTF! EHCI controller reset successfully.\n = RSTO. No device found in debug port %d\n = NDVP %d. EHCI controller halted successfully.\n = HLTS. EHCI controller is not halted. Reset may fail.\n = HLTF! EHCI could not be started.\n = SF! EHCI started.\n = SO. EHCI done waiting for port.\n = DWT. No device in EHCI debug port.\n = NDV. EHCI debug port enabled.\n = DPE. Could not probe gadget on debug port.\n = CPG. PORTSC #%d: %08x\n === P%d=%04x. debug_port: %d\n === dp=%d. n_ports: %d\n === np=%d.
Best regards, Mike Banon
On Sun, Oct 27, 2019 at 8:53 AM Mike Banon mikebdp2@gmail.com wrote:
Good day, I'm researching if it's possible to support a cheaper FT232BL-based EHCI usbdebug dongle like the already-supported FT232H -- to make EHCI debugging more accessible to the newcoming coreboot'ers -- and need the detailed logs (i.e. CONFIG_DEBUG_CONSOLE_INIT) to figure this out.
EHCI debug mode requires USB 2.0 High Speed (480 Mbps) device which FT232BL is not. That hardware can possibly provide console with GRUB payload but nothing earlier than that.
Kyösti
Thank you very much for your reply. Still curious about this "Pre-CBMEM log truncated" issue - how would you have solved it?
On Sun, Oct 27, 2019 at 10:08 AM Kyösti Mälkki kyosti.malkki@gmail.com wrote:
On Sun, Oct 27, 2019 at 8:53 AM Mike Banon mikebdp2@gmail.com wrote:
Good day, I'm researching if it's possible to support a cheaper FT232BL-based EHCI usbdebug dongle like the already-supported FT232H -- to make EHCI debugging more accessible to the newcoming coreboot'ers -- and need the detailed logs (i.e. CONFIG_DEBUG_CONSOLE_INIT) to figure this out.
EHCI debug mode requires USB 2.0 High Speed (480 Mbps) device which FT232BL is not. That hardware can possibly provide console with GRUB payload but nothing earlier than that.
Kyösti
On Sun, Oct 27, 2019 at 9:55 AM Mike Banon mikebdp2@gmail.com wrote:
Thank you very much for your reply. Still curious about this "Pre-CBMEM log truncated" issue - how would you have solved it?
It is called config PRERAM_CBMEM_CONSOLE_SIZE and I don't have a good value to give you, specially assuming AGESA with its convoluted CAR setup. Increase the config too much and it will fail to build, assume it to fail to boot way sooner. AGESA with SMP romstage is somewhat memory hungry and there is CAR no-eviction mode either.
As for that EHCI debug output: One could reduce its verbosity by removing retry loops and using a predefined fixed USB port (USBDEBUG_HCD_INDEX != 0). But only USB2 high-speed devices give interesting output there.
Kyösti
-
Kyösti Mälkki -
Mike Banon