SPRADI3 June 2024 AM625 , AM62P , AM67 , AM67A , AM68 , AM68A , AM69 , AM69A , DRA829J , DRA829J-Q1 , DRA829V , DRA829V-Q1 , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM-Q1 , TDA4VP-Q1 , TDA4VPE-Q1
In the best situation, the issue reproduces on a TI EVM on the latest SDK version available. This way, TI engineers can replicate the issue locally and make progress without requiring back-and-forth with the customer. Unfortunately, users have custom hardware and custom software which can be proprietary and impossible to share. Furthermore, the issue sometimes only replicates in a production system where the system is under a high load and requires a much more complex setup than is feasible to recreate. These complications cause a remote replication of the issue to be cumbersome.
But if there is low overhead to port the application to the TI EVM and reproduce the issue there, this greatly speeds up the investigation and is worthwhile to explore depending on the level of urgency. Otherwise, the investigation continues on the custom hardware.