• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 485 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

J784S4XEVM: Request Lauterbach cmm script for MCU R5F debug and A72 debug

Karuppusamy Subiramaniam
Intellectual 410 points
Part Number: J784S4XEVM
Other Parts Discussed in Thread: UNIFLASH, TDA4VM, AM69, TDA4VH

Hi Team,

We are using the J784S4XEVM board for development purpose.

We want to flash the image from external lauterbach so we need a .cmm script for the same. so could you please guide us to get the cmm script.

Thanks & Regards,

Karuppusamy Subiramaniam

karuppusamy.subiramaniam@aptiv.com

Mobile: +91-9344292810

  • 0
    TI__Mastermind 20505 points

    Hello,

    The typical flow for putting an image into flash is SDK dependent.  The image format for a given software component is tightly coupled with the software which is being launched.  The SDKs tend to offer two methods, one method uses TI's uniflash tool where initial images are downloaded over a uart and flashed.  The other method usually involves placing a boot image on an SD card then using SDK specific software to burn an image.  For example the Linux SDKs uboot can get and quickly burn large images.   You should reference the dev flow in the SDK you are using for the smoothest flow.

    It is possible to place images into flash using TRACE32 from Lauterbach however you will need to specify where you want to place the images.   Lauterbach has drivers for all the flash types which you can get from their support.   TI does have early TRACE32 CMM scripts used with the J784S4EVM which I will attach in a 7zip file.  The zip has the password of "TRACE32".  Flashing outside of the SDK with JTAG will require you to pull out the right images for a given SDK release and add the burn address into the TRACE32 commands.

    I recommend looking at the J7/TDA4 flashing application note https://www.ti.com/lit/an/spracy5/spracy5.pdf if you want to directly flash images.  This note is written for the TDA4VM device but if you substitute paths in the CMM scripts I've attached for those in the note you can use it to directly burn flashes with TRACE32.

    /cfs-file/__key/communityserver-discussions-components-files/791/8424.cmm_2D00_tda4vh_5F00_j784s4.7z

    In addition to the TI example CMM scripts, Lauterbach support will have TDA4VH/AM69 CMM scripts which you can get from them.  Most TRACE32 specific tool questions are best addressed by Lauterbach.
    For R5 debug, it depends on which software you are debugging.  Bare metal debug can be done by direct attaching to the correct R5 core using the _J784S4_r5.cmm script.  If you are looking to run a JTAG launched FreeRTOS example you might look at using the pdk_launch_freertos_r5.cmm script.  Use of PDK targeted scripts does require a user to alter the scripts to insert the paths to PDK images (test, firmware).  Notes on what to change is at the top of scripts and in readmes.
    Regards,
    Richard W.
  • 0 in reply to Richard Woodruff
    Intellectual 410 points

    Hi ,

    Thanks for the info.

    One more query.

    In J784S4 EVM We noticed, it is having the on board debugger and option to use the external JTAG based debugger.

    May i know how to select the external debugger?. 

    Thanks & Regards,

    Karuppusamy Subiramaniam

    karuppusamy.subiramaniam@aptiv.com

    Mobile: +91-9344292810

  • 0 in reply to Karuppusamy Subiramaniam
    TI__Mastermind 20505 points

    Hello Karuppusamy,

    When an external debugger with a standard MIPI-60 header is plugged in the JTAG signals are mux'ed to the MIPI-60 away from the onboard XDS110.  If you inspect the schematic for the board side of the MIPI-60, one can see pin 58 is used to signal an external connection pulling down the MIPI_DETECT connected  to the JTAG_MUX_SEL.
    Regards,
    Richard W.
  • 0 in reply to Richard Woodruff
    Intellectual 410 points

    Hi Richard Woodruff,

    Thanks for the input.