• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 325 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Target configuration for AM3715 on XDS100v2

Erik Duysters
Prodigy 110 points
Other Parts Discussed in Thread: AM3715, AM3517

I'm searching for a target configuration file in Code Composer Studio v5 for the AM3715 (Mistral EVM board) using the XDS100v2 JTAG emulator.

Has someone created such a file yet or have more details on it?

Thanks

  • 0
    TI__Expert 5215 points

    Erik,

    I believe the am3517 is not yet a supported device within the target config list. Check out the CCSv5 Advanced Workshop - this will guide you to creating a target config for the am3715 w/ an xds100v2. Start at slide 26.

  • 0 in reply to Michael Risley
    Prodigy 110 points

    I've followed the Advanced Workshop and it seems to connect:

    Cortex_A8_0: GEL Output: The code download over AHB is turned OFF.

    Cortex_A8_0: GEL Output: CPU Reset callback function has fired 

    Cortex_A8_0: GEL Output: OMAP 32K Watchdog Timer is disable

    Cortex_A8_0: GEL Output: Setup PRCM clock configuration IIA 

    Cortex_A8_0: GEL Output:  CORE_DPLL_CLK = 663.771 MHz 

    Cortex_A8_0: GEL Output:  CORE_CLK = 331.8855 MHz 

    Cortex_A8_0: GEL Output:  L3_CLK = 165.9427 MHz 

    Cortex_A8_0: GEL Output: MM01: mDDR Samsung K4X51323PC - 512 Mbit(64MB) on CS0, 4M x 32bit x 4Banks

    Cortex_A8_0: GEL Output: SDRC initilization for mDDR_Samsung_K4X51323PC completed 

     

    However, when I want to start debugging it fails with:

    Cortex_A8_0: Trouble Writing Memory Block at 0x48004c10 on Page 0 of Length 0x4: (Error -1065 @ 0x48004C10) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.470.0) 

    I've checked on forums and apparently most of these issues are related to clocking.

    Probably there is still a difference between 3715 and 3517 (I'm using the Mistral_Omap35xx_CortexA8.gel) I need to find out.