Hi Rogan, On Mon, Sep 25, 2023 at 6:52 AM Rogan Dawes <ro...@dawes.za.net> wrote: > > Hi Fabio, > > I used the following diff with "make mx28evk_defconfig", but unfortunately > still get absolutely nothing on the DUART when running "mxsloader u-boot.sb". > In fact, mxsloader returns immediately on trying to load my own u-boot.sb, > whereas it hangs when running the vendor u-boot.sb, I assume because the CALL > never returns. Additionally, there is no need to reset the board between > attempting a custom u-boot and the vendor u-boot, indicating that the > ROM-based SDP protocol handler is still running. This suggests that there is > something wrong with the format of the u-boot.sb file which the ROM-based SDP > protocol handler is rejecting, I would think?
I just tested loading u-boot.sb via mxsldr on my imx28-evk. I configured the boot jumpers to USB boot, turned on the board and then saw that it gets recognized by the host PC: $ dmesg .... [1710347.828895] usb 1-1: new high-speed USB device number 96 using xhci_hcd [1710347.977657] usb 1-1: New USB device found, idVendor=15a2, idProduct=004f, bcdDevice= 0.01 [1710347.977672] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1710347.977678] usb 1-1: Product: ROM Recovery [1710347.977682] usb 1-1: Manufacturer: Freescale,Inc. [1710347.979708] hid-generic 0003:15A2:004F.0014: hiddev0,hidraw1: USB HID v1.10 Device [Freescale,Inc. ROM Recovery] on usb-0000:00:14.0-1/input0 After that, I loaded the u-boot.sb via mxsldr: $ sudo ./mxsldr u-boot.sb Detected: i.MX28 Chip ID: 0x2800 Chip Revision: 0x0001 ROM Version: 0x0101 Protocol Version: 0x0100 Do you get these messages above (both the dmesg as well the messages after running mxsldr)? And in the console, I do see the U-Boot messages coming up: HTLLCLLC U-Boot 2023.10-rc4-00057-g4cb31a9f3560 (Sep 25 2023 - 09:49:04 -0300) CPU: Freescale i.MX28 rev1.2 at 454 MHz BOOT: USB #0 DRAM: 128 MiB Core: 89 devices, 12 uclasses, devicetree: separate NAND: 0 MiB MMC: MXS MMC: 0 Loading Environment from MMC... *** Warning - No block device, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0