Thank you for the clarification and for providing the specific documentation references. I appreciate you pointing out the official Toradex datasheet section and the NXP Android Quick Start Guide details.
Current Documentation Status
Based on the available information sources, the i.MX95 Verdin EVK documentation appears to be under restricted access. As mentioned in our community discussions, “the iMX95 EVK documentation is under NDA so you will need to request that on the NXP site” (1). This explains why the specific boot configuration details you’re referencing from the datasheet aren’t available in my current documentation set.
Android Support Status
The current status shows Android as “Coming Soon” for the i.MX95 Verdin EVK (2). While the hardware specifications indicate Android will be “Supported via Partners” (2), this suggests the Android implementation may still be in development or requires specialized partner support.
USB Disconnection During SDPS Transition
The USB disconnection issue you’re experiencing during the SDPS to U-Boot transition, particularly the “disabled by hub (EMI?), re-enabling…” message, suggests a hardware-level USB enumeration problem rather than a software configuration issue. This type of behavior often occurs when:
- The USB device changes its configuration during boot transitions
- Power consumption spikes during the boot process
- EMI interference affects USB communication
- The host USB controller resets the connection
Recommended Next Steps
Given the NDA-restricted documentation and the specialized nature of Android flashing on the i.MX95 EVK:
-
Access NDA Documentation: Follow the process to Sign an NDA with NXP to access the complete i.MX95 EVK documentation (1)
-
Early Access Community: Once you have a valid NDA, you’ll be given access to the “iMX95 EVK Early Access Toradex community” (1) where you can get specialized support for this specific hardware
-
Partner Network: Since Android is listed as “Supported via Partners” (2), consider engaging with our partner network for Android-specific integration support
-
Hardware Investigation: For the USB disconnection issue, you might want to try:
- Different USB cables and ports
- External powered USB hubs
- Different host machines to isolate EMI issues
The fact that you’re following the official NXP documentation precisely suggests this may be a known limitation or require specific workarounds that are documented in the NDA-protected materials.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.