03:06 <levd> hi all, I'm trying the U-Boot v2019.10 version. After getting tired of plugging out and in of SD cards each time recompiling U-Boot, I'm in despair needing the rockusb mode.

03:06 <levd> However, it is not easy to setup obviously. Run "rockusb 0 mmc 1" got "No USB device found\nUSB init failed: -19"

03:08 <levd> After checking the code, it failed at "usb_gadget_initialize(controller_index);" which failed uclass_get_device_by_seq(UCLASS_USB_GADGET_GENERIC, index, &dev) and uclass_get_device(UCLASS_USB_GADGET_GENERIC, index, &dev).

03:09 <levd> I run "dm uclass", showing no devices under "uclass 89: usb".

03:13 <levd> Really got stuck at the U-Boot device model. I grep the source code, finding the driver dwc3_generic_peripheral defines the driver of uclass UCLASS_USB_GADGET_GENERIC. But what device does the driver match? I'm really clueless.

03:14 <levd> Would anyone shed some light on this?

03:17 <levd> kevery: I find no defconfig of rockchip boards using rockusb. Some boards are not entering MaskRom mode easily. How did you guys do U-Boot maindevelopment in that situation?

03:34 <kevery> levd: some board enable rockusb in Kconfig instead of defconfig file. It will be better to enable recovery button to enter rockusb mode in U-Boot, but many boards do not have good support for this feature. Rockchip vendor U-Boot support this feature for most of boards.

03:40 <kevery> If the board not easy to enter MaskRom mode, you can try to :

03:40 <kevery> 2. if the U-Boot works, use 'emmc erase' cmd to erase data at 0x40 to force the chip enter Maskrom mode.

03:40 <kevery> 3. use 'ums' cmd in U-Boot to update file system based image.

03:40 <kevery> 1. use SD card instead(always make SD card has higher priority than eMMC at SPL or miniloader);

03:55 <levd> Thanks kevery, the tips are very useful. I'll make a comparison between vendor and mainline to figure rockusb out.

06:49 <levd> kevery: port some code from vendor u-boot to `evb-rk3399.c`, and turn on some DEBUG, the `rockusb 0 mmc 1` seems to have enter the loop. Yet the PC host does not see the gadget.

06:49 <levd> plz have a look at: https://pastebin.com/A4pHaPVF

06:53 <levd> also, `ums 0 mmc 1` have similar result.

15:44 <j45> kevery: regarding using arm-trusted-firmware mainline, you said 'We need to update "CONFIG_ROCKCHIP_SPL_RESERVE_IRAM=0x50000"'

15:44 <j45> what does it need to be updated to?

17:01 <sigmaris> j45: I believe u-boot requires this patch https://patchwork.ozlabs.org/patch/1173719/

17:01 <sigmaris> which does fix the issue with ATF master + u-boot v2019.10 on my board

18:12 <j45> sigmaris: thanks ;-)