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.

CCS/TDA3XEVM: Getting Started with TDA3x EVM board

Part Number: TDA3XEVM

Tool/software: Code Composer Studio

I'm trying to get code running non a TDA3X EVM board.  In a previous thread, I unsuccessfully tried to flash code onto the board.  I've now ordered  XDS200 probe so I'm hoping to get an installation working and download+debug code using the probe.

Starting fresh, I've done the following on a Windows 7 64-bit laptop:

1. I downloaded Code Composer Studio 8.0.0.00016 from software-dl.ti.com/.../CCS8.0.0.00016_win32.zip

2. I downloaded PROCESSOR-SDK-VISION from www.ti.com/.../PROCESSOR-SDK-TDAX

3.I added the xdc tools directory to the PATH environmental variable (C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core if it matters).

4. I added/changed two lines in C:\PROCESSOR_SDK_VISION_03_03_00_00\vision_sdk\build\Rules.make

MAKECONFIG?=tda3xx_evm_bios_all

BUILD_OS ?= Windows

5. I added/changed two lines in C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\drivers\pdk_01_09_00_17\packages\ti\build\Rules.make

export OS ?= Windows_NT
SDK_INSTALL_PATH ?= c:/PROCESSOR_SDK_VISION_03_02_00_00
export BOARD ?= tda3xx-evm (changed it from tda2xx-evm)
export SOC ?= tda3xx (changed it from tda2xx)

6. I added one line to make sure the ipc_PATH value was correct in C:\PROCESSOR_SDK_VISION_03_03_00_00\vision_sdk\build\tools_path.mk

ipc_PATH ?= /PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/ipc_3_45_00_00

7. Following the instructions at http://processors.wiki.ti.com/index.php/PDK/PDK_TDA_Building_The_Package, 

gmake -s allcores BOARD=tda3xx-evm

but it didn't work, giving the error message "target 'allcores' not found"

8. Continuing with the instructions, I tried:

gmake -s allcores_clean BOARD=tda3xx-evm

This ran for a half hour or so and worked in that it ran to completion.  There were many success and fail messages along the way, but I'm hoping maybe the fail messages were related to things not needed for my board/libraries/functions.

9. I continued with builds from "Getting Started":

gmake depend

This runs for 5-10 minutes and seems to work.

10. Continuing with "Getting Started", I run:

gmake > store_output_messages.txt

And this fails, freezing up until I hit Ctrl-C to break.  (I left it running over the weekend to make sure it was frozen.)  Shortly, I will send "store_output_messages.txt" so you can see the messages that appear.  I will also send "output_displayed_at_command_prompt.txt" so you can see the messages that appear at the command prompt.  It appears to freeze up while it's running the following command:

C:/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/xs xdc.tools.configuro --generationOnly -o C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda3xx_evm_bios_all/obj/vision_sdk/tda3xx-evm/arp32_1/release/vision_sdk_configuro -t ti.targets.arp32.elf.ARP32_far -p ti.platforms.evmTDA3XX:EVE_1 -r release -c C:/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/arp32_1.0.7 -b C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/tda3xx/config_arp32.bld --cfgArgs "{mode: \"\", coreName:\"EVE-1\", platformMem: \"DDR_MEM_512M\"}" MAIN_APP_eve1.cfg

  • output_displayed_at_command_prompt.txt
    C:\PROCESSOR_SDK_VISION_03_03_00_00\vision_sdk\build>gmake > store_output_messages.txt
    C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda3xx_evm_bios_all/obj/app_alg_plugins/tda3xx-evm/66/release/GAlignLUT_tda3xx.oe66' given more than once in the same rule.
    C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda3xx_evm_bios_all/obj/app_alg_plugins/tda3xx-evm/66/release/GAlignExt_tda3xx.oe66' given more than once in the same rule.
    C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda3xx_evm_bios_all/obj/app_alg_plugins/tda3xx-evm/66/release/GAlignLUT_tda3xx.oe66' given more than once in the same rule.
    C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `C:/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda3xx_evm_bios_all/obj/app_alg_plugins/tda3xx-evm/66/release/GAlignExt_tda3xx.oe66' given more than once in the same rule.
          8 [main] sh 9956 C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x29C740 - 0x2A0000, Win32 error 487
          8 [main] sh 9956 C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x29C740 - 0x2A0000, Win32 error 487
       1777 [sig] sh 9956 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
          3 [main] sh 9740 C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x29C740 - 0x2A0000, Win32 error 487
          3 [main] sh 9740 C:\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x29C740 - 0x2A0000, Win32 error 487
          7 [main] sh 9916 child_info::sync: wait failed, pid 9740, Win32 error 1812
    
          7 [main] sh 9916 child_info::sync: wait failed, pid 9740, Win32 error 1812
    
       1520 [main] sh 9916 fork: child -1 - died waiting for longjmp before initialization, retry 8, exit code 0x1000000, errno 11   1520 [main] sh 9916 fork: child -1 - died waiting for longjmp before initialization, retry 8, exit code 0x1000000, errno 11
    
    C:/Users/SPICKE~1.INT/AppData/Local/Temp/make8612-1.sh: Cannot fork: Resource temporarily unavailable

  • Hi,

    I did not get it, do you want to build vision sdk or pdk? It seems you are using PDK userguide to build vision sdk.
    Please use TDA3x Vision SDK user guide from the vision_sdk/docs folder to get the build instructions for building vision sdk.

    Rgds,
    Brijesh
  • Sorry.  I incorrectly thought the PDK was a prerequisite.  I removed everything and started over from scratch.  I read through the VisionSDK_Getting_Started_Guide.pdf and then the VisionSDK_UserGuide_TDA3xx.pdf. I followed the instructions which seemed to follow the same procedure as before except this time not doing any of the PDK stuff:

    1. Install CCS.

    2. Install the vision SDK.

    3. Install the A15 compiler at correct location.  (I did this the first time but forgot to list it.)

    4. Change the environment PATH variable and adjusted Rules.make

    5. gmake -s -j depend      (This seemed to work fine, as it had before.)

    6. gmake                (This failed again at the same location.)

    gmake froze up again at the same spot, i.e. running C:/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/xs xdc.tools.configuro

  • Hi Scott,

    As I had pointed in one of the previous threads you should remove -j and try i.e. first do gmake -s depend and then gmake -s.
    In 5th point you have mentioned that you are changing SDK path to PROCESSOR_SDK_VISION_03_02_00_00 whereas you are trying to build 3.03. You should set the path appropriately.
    Also can do a "which gmake" to see which gmake are you using.

    Regards,
    Rishabh
  • Thank you.  Removing the -j worked this time and I have been successful.  I'm not sure why, but "gmake -s -j depend" appeared to work but apparently it didn't making the "gmake -s" fail.  But when I re-ran with "gmake -s depend", followed by "gmake -s" everything worked correctly.  

    I appreciate the help you've given me.  Thank you.

  • Hi Scott,

    Glad to know that the issue is resolved. Kindly mark the post that answers the query as "This resolved my issue".

    Regards,

    Rishabh