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.

TDA3: TDA3x Users Guide Demo

Part Number: TDA3

Hi, Everyone

I have a question about VisionSKD of TDA3x.

I see VisionSDK Users guide.
(This users guide is v02.09. but I use v02.12.00 now)

processors.wiki.ti.com/.../VisionSDK_UserGuide_TDA3xx.pdf

I success QSPI and SD boot.
but It does not work on CCS.

Please see 3.5 Load using CCS and 3.6 Run the demo.

I connect each cores and Load program to each cores like 3.5 Load using CCS.
but I do not see comment on Tera Term after Every cores run.

Actually I try to use gel file of default and TDA3xx_multicore_reset.gel
but I do not see any more on TeraTerm.

Is it possible to use in 3.6 Demo using CCS ?
If yes, Can you tell me any advise?

Best regards
Hiroyasu

  • Hello Hiroyasu,

    1. Please share contents of gel file output when connecting to cortex M4 core 0

    2.  Confirm you have enabled VISION_SDK_CONFIG flash in the TDA3xx_multicore_reset.gel file

    3. Check you have latest version of gel.

    Regards,

    Prasad

  • Hi, Prasad

    Thank you for your reply.

    I use TDA3xx_multicore_reset.gel

    TDA3xx_multicore_reset.gel

    I download this gel file from this URL below:

     


    and Let me talk about this gel file setting for Cortex_M4_IPU1_C0.

    After M4_IPU1_C0 connection,  I do not know how to use.

    Script → IPU Unicache and A-MMU configures → Config_MMU

    → Script → TDA3x Multicore Initialization → TDA3xx_MULTICORE_EnableAllCores

    and Every cores connected.

    but After this operation, I try to load program, but I got error.

    Can you tell me how to set for GEL file?

    Best Regards
    Hiroyasu

  • Hiroyasu,

    Your gel file setting (snapshot) is wrong. You need to give TDA3xx_cortexM4_startup.gel as initialization script. This file will load all other gel files, one of which has on target connect function. So basically it would run all required functions when you connect IPU1_0.

  • Hi, Prasad

    Thank you for your reply.
    I already set TDA3xx_cortexM4_startup.gel.
    I could load program and run. but I do not see comment in TeraTerm.

    and I want to know how to set TDA3xx_multicore_reset.gel.

    It is described in Users Manual below:

    ===============
    To install the new GEL versions, you need to extract the zip to
    <CCS_INSTALL_DIR>/ccsv6/ccs_base
    ===============

    I extract zip file for gel file.
    Can you tell me we need other operation for TDA3xx_multicore_reset.gel?

    Best Regards
    Hiroyasu
  • Hello Hiroyasu,

    when you load TDA3xx_cortexM4_startup.gel, you would get "misc. module configuration" in scripts menu. Can you run function on target connect under this menu and share output of gel for this function.

    Also another issue can be your DDR not configured correctly. In CCS memory browser type address 0x80000000 and check by continuously refreshing if memory is stable.

  • Hi, Prasad

    I think memory is O.K. when I access 0x80000000.
    and Is it O.K. to operate for TDA3xx_multicore_reset.gel ?

    and I share with output of gel file when I run Script → TDA3x Misk Module configuration.

    =======================
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence Begins ... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> A device reset occurred <<<---
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG1.0 device detected =========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG1.0 device detected =========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: --->>> All Control module lock registers are UNLOCKED <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> Changing RTI1 reaction type to avoid RTI1 resetting the device after 3 minutes... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> Starting IPU A-MMU configurations... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> IPU A-MMU configuration completed. <<<---
    Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR and DPLL configuration Based on Package selection pin status(Sysboot[7]) <<<---
    Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
    Cortex_M4_IPU1_C0: GEL Output: --->>> 15x15 Package Detected(SYSBOOT[7]=0)... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPPNOM in progress... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 clock config in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL already locked, now unlocking
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP_DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 initialization starts (TI 15x15 EVM)... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 Initialization is in progress ... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in DONE!
    Cortex_M4_IPU1_C0: GEL Output: Launch full leveling
    Cortex_M4_IPU1_C0: GEL Output: Updating slave ratios in PHY_STATUSx registers
    Cortex_M4_IPU1_C0: GEL Output: as per HW leveling output
    Cortex_M4_IPU1_C0: GEL Output: HW leveling is now disabled. Using slave ratios from
    Cortex_M4_IPU1_C0: GEL Output: PHY_STATUSx registers
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 532MHz Initialization is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for Vision Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for RGMII usage on EVM Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW MDIO Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW MDIO Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW RGMII0 Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW RGMII0 Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for RGMII usage on EVM Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for Vision Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence DONE !!!!! <<<---
    Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Cortex_M4_IPU1_C0: GEL Output: For STM based tracing on TI EVMs,
    Cortex_M4_IPU1_C0: GEL Output: run 'TDA3x EVM I2C EXPANDER CONTROL -> Enable_Trace_Pins()' function from Scripts menu on M4/CS_DAP_DebugSS
    Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence Begins ... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> A device reset occurred <<<---
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG1.0 device detected =========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx PG1.0 device detected =========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx GP Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ========= TDA3xx 15x15 Device detected ===========
    Cortex_M4_IPU1_C0: GEL Output: ==================================================
    Cortex_M4_IPU1_C0: GEL Output: --->>> All Control module lock registers are UNLOCKED <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> Changing RTI1 reaction type to avoid RTI1 resetting the device after 3 minutes... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> Starting IPU A-MMU configurations... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> IPU A-MMU configuration completed. <<<---
    Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR and DPLL configuration Based on Package selection pin status(Sysboot[7]) <<<---
    Cortex_M4_IPU1_C0: GEL Output: ------------------------------------------------------------------------------------------
    Cortex_M4_IPU1_C0: GEL Output: --->>> 15x15 Package Detected(SYSBOOT[7]=0)... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPPNOM in progress... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> CORE DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 clock config in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL already locked, now unlocking
    Cortex_M4_IPU1_C0: GEL Output: --->>> PER DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP_GMAC DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP DPLL OPP 0 clock config is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DSP DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> EVE_VID_DSP_DPLL OPP 0 is DONE!
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 initialization starts (TI 15x15 EVM)... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 Initialization is in progress ... <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in progress...
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL already locked, now unlocking....
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR DPLL clock config for 532MHz is in DONE!
    Cortex_M4_IPU1_C0: GEL Output: Launch full leveling
    Cortex_M4_IPU1_C0: GEL Output: Updating slave ratios in PHY_STATUSx registers
    Cortex_M4_IPU1_C0: GEL Output: as per HW leveling output
    Cortex_M4_IPU1_C0: GEL Output: HW leveling is now disabled. Using slave ratios from
    Cortex_M4_IPU1_C0: GEL Output: PHY_STATUSx registers
    Cortex_M4_IPU1_C0: GEL Output: --->>> DDR3 532MHz Initialization is DONE! <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for Vision Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin All Pad Configuration for RGMII usage on EVM Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW MDIO Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW MDIO Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Begin GMAC_SW RGMII0 Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End GMAC_SW RGMII0 Pad Configuration <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for RGMII usage on EVM Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx End All Pad Configuration for Vision Platform <<<---
    Cortex_M4_IPU1_C0: GEL Output: --->>> TDA3xx Target Connect Sequence DONE !!!!! <<<---
    Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Cortex_M4_IPU1_C0: GEL Output: For STM based tracing on TI EVMs,
    Cortex_M4_IPU1_C0: GEL Output: run 'TDA3x EVM I2C EXPANDER CONTROL -> Enable_Trace_Pins()' function from Scripts menu on M4/CS_DAP_DebugSS
    Cortex_M4_IPU1_C0: GEL Output: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    =======================

    Best Regards
    Hiroyasu
  • Hello Hiroyasu,

    Gel file output looks correct, though not sure why it is run twice (i believe one is when you connect core and other you ran misc. config manually). After running this, i assume you run "enable all cores" function from multicore gel file.

    If with too it is failing-

    1. Please halt each core and share the snapshot

    2. Please confirm you are checking output on UART3

    3. There is below note in VSDK user guide, are you making sure you are following these steps?

    IMPORTANT NOTE: Binary for Cortex_M4_IPU1_C0 MUST be loaded before Cortex_M4_IPU1_C1 since IPU1-0 does MMU config for the complete IPU1 system. Other binaries can be loaded in any order

  • Hi, Prasad

    I run enable all cores after misc. config

    1. I share with snapshot

    First before run

    After run amd halt

    2.I select UART3

    3. I Load Cortex_M4_IPU1_C0 → Cortex_M4_IPU1_C1

    and Users Manual says below:

    ===============
    To install the new GEL versions, you need to extract the zip to 
    <CCS_INSTALL_DIR>/ccsv6/ccs_base
    ===============

    I share with snapshot.

    Is it correct?

    Best Regards
    Hiroyasu

  • Hello Hiroyasu,

    All steps you following are correct. As seen from second CCS snapshot, IPU1_0 is waiting in IPC attach meaning waiting for some core to come up. 

    Why in before running snapshot you are not loading binary on IPU0_1 and EVE? 

  • Hi,Prasad

    I'm sorry IPU1_C1 is my mistake.
    Actually I load program for IPU1_C1

    but I already vision_sdk_arp32_1_release.xearp32F for EVE.

    ○vision_sdk_arp32_1_release.xearp32F
    C:\VISION_SDK_02_12_01_00\vision_sdk\binaries\tda3xx_evm_bios_all\vision_sdk\bin\tda3xx-evm

    Is it correct ?

    After I load, EVE run automatically.
    and CCS shows "no symbols" when I halt.

    Best Regards
    Hiroyasu
  • Hiroyasu,

    Some issue with EVE MMU. Normally after loading binary EVE should halt at main like other cores.
    When EVE starts running automatically, please check contents of registers 0x6208_1018, 0x6208_101C and 0x6208_1048 from IPU

    Share the contents.
  • Hi, Prasad

    I'm sorry. It was late.
    I checked these register below.

    0x62081018 = 0x00000000
    0x6208101C = 0x00000000
    0x62081048 = 0x00000180

    Best Regards
    Hiroyasu
  • Hiroyasu,

    Is this after EVE code is loaded and it is in 'running' state (not halting)?

  • Hi, Prasad

    I got this value after EVE run and halt.

    Best Regards
    Hiroyasu
  • Hello Hiroyasu,

    Is it possible to share here VSDK multicore gel and your EVE map file?
    Or else please mail me both.
  • Hi, Prasad

    I'm sorry. It was late.

    It was solve.
    I reset DSP1 and DSP2 and EVE core after connect and It is working.
    Thank you for your support !!

    Best Regards
    Hiroyasu