Hi leo, That’s my problem. After I enabled optee OS, the device got hung in booting BL32 and cannot boot to Android OS. So I just want to use recovery mode to reflash my Hikey back. When I got this board, the USB OTG worked well. It can be recognized by adb and fastboot.
Yes, bootROM uses the UART0 as output logs. But entering BL1, UART3 is used to output logs, right? So for my case, after comand “python hisi-idt.py -d /dev/ttyUSB0 --img1=l-loader.bin” is finished, the device got hung in bootROM and does not run into stage 1 bootloader?
And for the USB OTG not found issue, itseems something wrong with my PC, the USB OTG can be recognized for a very short while, as the following dmesg log.
[ 2734.123494] usb 1-1: new full-speed USB device number 34 using xhci_hcd
[ 2734.141135] usb 1-1: New USB device found, idVendor=12d1, idProduct=3609
[ 2734.141147] usb 1-1: New USB device strings: Mfr=1, Product=4, SerialNumber=0
[ 2734.141154] usb 1-1: Product: \xffffffe3\xffffff84\xffffffb0㌲㔴㜶㤸
[ 2734.141158] usb 1-1: Manufacturer: 䕇䕎䥎
[ 2734.142091] option 1-1:1.0: GSM modem (1-port) converter detected
[ 2734.142797] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 2734.711244] usb 1-1: USB disconnect, device number 34
[ 2734.711413] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 2734.711431] option 1-1:1.0: device disconnected