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.

J721EXCPXEVM: CCS Setup for J721E

Part Number: J721EXCPXEVM

Tool/software:

I am following the CCS setup for J721EXCP01EVM   Common processor board for Jacinto 7 processor following the procedure from the link  

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j721e.html

I am working on windows 64 bit machine 

I am getting error in 6.3.2. Step 3 from the above link

Getting the below error when running the java script which was seen on the CCS Scripting console :

loadJSFile("D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js")
Connecting to DMSC_Cortex_M3_0!
Fill R5F ATCM memory...
Writing While(1) for R5F
Loading DMSC Firmware ... D:/TI_SDK/ti-processor-sdk-rtos-j721e-evm-10_01_00_04/packages/ti/drv/sciclient/soc/sysfw/binaries/ti-fs-firmware-j721e-gp.bin
Could Not Open File C:\LegacyApp\ti\ccs1240\ccs\eclipse\D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\packages\ti\drv\sciclient\soc\sysfw\binaries\ti-fs-firmware-j721e-gp.bin for reading: Unable to open file (D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js#118)
js:> loadJSFile("D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js")
Connecting to DMSC_Cortex_M3_0!
Fill R5F ATCM memory...
Memory verification failed at address 0x61000000 (D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js#111)

How do I resolve the Memory verification failed error . 

  • Hi,

    Could Not Open File C:\LegacyApp\ti\ccs1240\ccs\eclipse\D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\packages\ti\drv\sciclient\soc\sysfw\binaries\ti-fs-firmware-j721e-gp.bin for reading: Unable to open file (D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js#118)

    Did you make any changes after these logs to address the issue?

    js:> loadJSFile("D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js")
    Connecting to DMSC_Cortex_M3_0!
    Fill R5F ATCM memory...
    Memory verification failed at address 0x61000000 (D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\pdk_jacinto_10_01_00_25\packages\ti\drv\sciclient\tools\ccsLoadDmsc\j721e\launch.js#111)

    Do you receive this error every time you try to run the launch.js script after booting?

    Could you please double check and ensure you have followed the following step to set the GEL script to load on the DMSC M3 core.

    Thanks,

    Neehar

  • Hi , 

    Yes I have ensured to set the path to the gel script browsing the below path in my C drive where I have the CCS installed.

    ${CCS_INSTALL_PATH}/ccs_base/emulation/gel/J721E_DRA829_TDA4VM/gel/J721E.gel

    Error:
    Could Not Open File C:\LegacyApp\ti\ccs1240\ccs\eclipse\D:\TI_SDK\ti-processor-sdk-rtos-j721e-evm-10_01_00_04\packages\ti\drv\sciclient\soc\sysfw\binaries\ti-fs-firmware-j721e-gp.bin

    After this error I tried to rerun the JavaScript again without any change.

    But I am not sure why both the C: drive path where CCS is installed and the D: drive path where the
    SDK is placed is being concatenated above to find the ti-fs-firmware-j721e-gp.bin file.
    Is there any way to reset the memory or get this working ?


    Also the switches SW8 and SW9 should be in No Boot Mode correct ?
    SW8[1-8] = 1000 1000
    SW9[1-8] = 0111 0000
    • Documentation says

    • Edit the variable “pdkPath” with the absolute path of the pdk package, i.e ${PSDK_RTOS_PATH}/pdk_jacinto_{version}/packages

    pdkPath should be till ${PSDK_RTOS_PATH}/pdk_jacinto_{version}/   only since that is how it is refered in the launch.js script. 

    With this issue is resolved.