TDA4APE-Q1: Need support for JTAG unlock using Trace32

Hello,

For unlocking and debugging TDA4APE with TRACE32 there are ~2 general paths. 

• The common path which most developers will follow is a 'functional boot path' and this requires the use of TI firmware on the M4 boot processors.  The unlock happens based on credentials embedded in the bootimage, however, there is an option to unlock at runtime (post firmware running).   This application note describes this common usage:  
  • https://www.ti.com/lit/ug/sprujc1/sprujc1.pdf
    • https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_cert_format.html
    • https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/runtime_debug.html
    • https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_ap_data_transfer.html 
• There is also a less common method to unlock which is useful for running bare metal images and board level unit tests.

TI does have some example CMMs as does Lauterbach (standard sieve for all cores).  The scripts can be used for either case.  I'll attach a zip of scripts here, the password is "CMM".   If you are unfamiliar with TRACE32 its probably fastest to engage with their support to get their bare metal examples running.

• /cfs-file/__key/communityserver-discussions-components-files/791/2727.cmm_2D00_tda4vh_5F00_j784s4.7z
  • Scripts are shared between j784s4 and j742s2.  Edit the file is_soc_J784S4_or_J742S2.cmm to match your target type. 

Hi Richard,

Thanks so much for your info. I could open the JTAG connection and established the debug session with TDA4APE.

Now I'm facing with some other challenges. That I have a question:

1. I'm experienced with TDA4 GP variants. On GP, I powered them with No-boot mode. Then I could load TI FS Firmware and start primary M4 core (with TIFS) by using the debugger. Can I do the same thing with HS variant? Can I use GP TI FS firmware binary for HS?

Thanks and regards,

Dan

Hello Dan,

Glad you are progressing on TDA4APE.