Platform Information:
Working reference:
Issue description:
sudo ./uuu_imx_android_flash.sh -f imx95 -e -t emmcuuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.201
New USB Device Attached
Start Cmd: SDPS: boot -f "u-boot-imx95-evk-uuu.imx"
Fail HID(W): LIBUSB_ERROR_NO_DEVICE (-4)Host dmesg output:
usb 1-5: New USB device found, idVendor=1fc9, idProduct=015d
Product: OO Blank 95
Manufacturer: NXP SemiConductor Inc
usb 1-5: USB disconnect, device number 119
usb 1-5: new high-speed USB device number 120 using xhci_hcd
usb 1-5: New USB device found, idVendor=1fc9, idProduct=015d
usb 1-5: USB disconnect, device number 120
usb 1-5: new high-speed USB device number 121 using xhci_hcd
usb 1-5: New USB device found, idVendor=1fc9, idProduct=015dBehavior observed:
connect → disconnect → reconnect loopAdditionally observations:
Device correctly enters SDP mode:
idVendor=1fc9, idProduct=015d (i.MX95 SDP)Failure occurs immediately after:
SDPS: boot commandDisconnect happens during:
ROM → U-Boot handoffKey findings:
I found following issues with this workaround:
I suspect possible root cause is:
Possible reasons:
ADB shell output regards to board details:
fsl,imx95-19x19-evk1.1 → B0ttyLP0 → console
ttyLP4 → available
Expected behavior:
UUU flashing should proceed with SDPS → SDPV → FBK → partition flashing with no USB disconnect.
Questions:
Thanks for the reply.
I don't know exactly the problem at my end but somehow I can live with Android 14 automotive boot.
But i have experienced the BT module does not enable from automotive UI.
I have few questions for Android automotive 14:
Hello,
I couldn't test it on Linux but I did it successfully on Windows host machine through the CMD, Definitely pre-build u-boot image works fine, I had an issue the first time but after disconnecting and connecting again the USB the image was flashed as expected with UUU 1.5.201, please see below:
First try
Second try
Hello,
I hope someone had a try at Ubuntu environment as i mentioned in my first post. If so let me know if flash works and also Bluetooth works or crash is observed because both are happening at my end.
Currently my Android 14 flash works fine for eMMC but Bluetooth enable from UI gives me crash in adb logcat. Same is attached here for reference.
I need help as bluetooth working is mandatory for my work. I can share more logs if required if BT module is not initialized at boot.