On Tue, Jan 7, 2025 at 12:30 PM Rogan Dawes lists@dawes.za.net wrote:
That would explain it, then! :facepalm:
I tested to access the console via usbacm and it worked on my imx28evk:
--- a/configs/mx28evk_defconfig +++ b/configs/mx28evk_defconfig @@ -70,3 +70,5 @@ CONFIG_USB_GADGET_VENDOR_NUM=0x0525 CONFIG_USB_GADGET_PRODUCT_NUM=0xa4a5 CONFIG_CI_UDC=y CONFIG_USB_GADGET_DOWNLOAD=y +CONFIG_USB_FUNCTION_ACM=y +CONFIG_BOOTDELAY=100
First, I booted via normal serial console and run:
=> setenv stderr usbacm && setenv stdout usbacm && setenv stdin usbacm && saveenv
Then booted again, and I saw on the console:
U-Boot 2025.01-dirty (Jan 07 2025 - 16:10:42 -0300)
CPU: Freescale i.MX28 rev1.2 at 454 MHz BOOT: SSP SD/MMC #0, 3V3 DRAM: 128 MiB Core: 91 devices, 13 uclasses, devicetree: separate NAND: 2048 MiB MMC: MXS MMC: 0 Loading Environment from MMC... Reading from MMC(0)... OK In: usbacm Out: usbacm Err: usbacm
Then, on another PC window:
sudo picocom -b 115200 /dev/ttyACM0
And the console can be seen there.