2370824_en-US

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

2370824_en-US

2370824_en-US

i.MX95 19x19 EVK (B0) – Android 16 UUU Flash Failure (USB Disconnect at SDPS Stage)

Platform Information:

  • Board: NXP i.MX95 19x19 EVK
  • SoC Revision: B0 (rev 1.1)
  • Android Version: Android 16 (prebuilt BSP images)
  • Build Type: Android Automotive
  • Host OS: Ubuntu
  • UUU Version: 1.5.201
  • Boot Mode: Download mode (SW7 = 1001)
  • USB Setup:
    • Using OTG/device port
    • Direct connection (no hub)
    • Verified cable and port working

Working reference:

  • Android 14 (custom build) flashes successfully using the same setup
  • Android 16 (prebuilt BSP images) fails during flashing

    This does confirmed that USB hardware and cable are correct, Boot mode and connection are correct & Issue is specific to Android 16 BSP.

Issue description:

When flashing Android 16 images using:
 
sudo ./uuu_imx_android_flash.sh -f imx95 -e -t emmc
The flashing fails at the SDPS boot stage, with an immediate USB disconnection. The error is:
uuu (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=015d

Behavior observed: 

connect → disconnect → reconnect loop

Additionally observations:

  • Device correctly enters SDP mode:

idVendor=1fc9, idProduct=015d (i.MX95 SDP)
  • Failure occurs immediately after:

SDPS: boot command
  • Disconnect happens during:

ROM → U-Boot handoff

Key findings:

Using Android 14 U-Boot: (u-boot-imx95-evk-uuu.imx) - Flashing Android 16 images works successfully
 
Current workaround:
  • Replace Android 16 U-Boot with Android 14 U-Boot
  • Flash Android 16 images

I found following issues with this workaround:

  • About page shows Android 14
  • Bluetooth not working

I suspect possible root cause is:

Android 16 u-boot-imx95-evk-uuu.imx appears to be incompatible with the i.MX95 19x19 EVK (B0)
 

 Possible reasons:

  • Incorrect DDR configuration in U-Boot
  • Wrong defconfig (board mismatch)
  • USB initialization issue in SPL/U-Boot
  • Regression in Android 16 U-Boot BSP

ADB shell output regards to board details:

Device Tree: 

fsl,imx95-19x19-evk

SoC Revision: 

1.1 → B0

UART Devices:

ttyLP0 → console
ttyLP4 → available


Expected behavior:

UUU flashing should proceed with SDPS → SDPV → FBK → partition flashing with no USB disconnect.

Questions:

  1. Is there a known issue with Android 16 U-Boot for i.MX95 EVK (B0)?
  2. Is there an updated or patched U-Boot version recommended for Android 16?
  3. Are there known changes between A14 and A16 U-Boot impacting:
    1. DDR initialization
    2. USB/SDPS boot
  4. Should a different defconfig be used (other than imx95_19x19_evk_defconfig)?
  5. Is there a validated Android 16 Automotive release for this board? If no then which one is the latest available android alpha release for android automotive?
Re: i.MX95 19x19 EVK (B0) – Android 16 UUU Flash Failure (USB Disconnect at SDPS Stage)

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:

  1. s this expected behavior on i.MX95 Android (GKI), i.e., Bluetooth UART drivers being built-in instead of modules?
  2. If so, what is the correct way to validate Bluetooth bring-up (since .ko is not available)?
  3. Are there any required DTS or firmware configurations specific to i.MX95 for BT initialization?
Re: i.MX95 19x19 EVK (B0) – Android 16 UUU Flash Failure (USB Disconnect at SDPS Stage)

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

Oswalag_0-1779826913858.png

Second try

Oswalag_1-1779827070215.png



Re: i.MX95 19x19 EVK (B0) – Android 16 UUU Flash Failure (USB Disconnect at SDPS Stage)

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.

タグ(1)
評価なし
バージョン履歴
最終更新日:
昨日
更新者: