Part Number: TDA4VM
Hello TI Team,
We are currently evaluating wake-up timing performance on a TDA4 (Jacinto 7) platform for a commercial truck application and would appreciate clarification on wake-up feasibility and optimization strategies.
Background
Our customer has a regulatory requirement that the system must become operational within 6 seconds from the moment the ignition signal is triggered (push-button start). The timing begins at ignition assertion.
Our current internal estimate for full system wake-up is approximately 8–10 seconds, depending on configuration. Based on our analysis so far, achieving 6 seconds appears challenging.
Questions – Wake-Up Feasibility
-
From TI’s experience, is a 6-second wake-up time achievable on TDA4?
-
What are typical wake-up times for:
-
Cold boot (full power-on reset)?
-
Deep sleep wake?
-
-
Are there recommended configuration strategies to minimize wake-up time?
-
Are there reference measurements or benchmarks available for wake-up timing?
Questions – Partial / Staged Initialization
To meet the 6-second requirement, we are exploring whether a staged or partial initialization approach is possible.
Specifically:
-
Is it possible to bring up essential functionality first (camera pipeline and display output) before full Linux services and all subsystems are fully initialized?
-
Can CSI, display subsystem, and potentially the Ethernet switch be initialized independently or earlier in the boot process?
-
Is it possible for the MCU/R5 domain to control or enable essential features before the A72/Linux domain is fully operational?
-
If staged initialization is not supported, what would be the fastest achievable time to enable camera + display functionality?
Our goal is to minimize perceived startup time while remaining within architectural constraints of the device.
Any guidance or recommended fast-boot strategies for automotive applications would be greatly appreciated.
Thank you for your support.

