• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 396 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.

SK-AM62B-P1: Setting up CCS for M4 debugging/profiling

Ayman Ghanem
Prodigy 170 points

Part Number: SK-AM62B-P1

Tool/software:

I'm trying to setup CCS for debugging and profiling my code on M4 running FreeRTOS. I downloaded CCS and the SDK as well as the clang compiler. I was able to build the Hello_World example on Friday and successfully loaded it on the M4 of my AM62x dev board. However, when I tried that today, I'm getting this error "Unknown module:File" when I try to debug or flash the image. Any idea what that is pointing to?

The error seems to be coming from cc_base/cloudagent/src/module.js

Do I need cloud agent? I'm running CCS on my Windows system, and it is directly connected to the XDS100 port on the AM62x board.

Thanks.

Ayman

  • 0
    TI__Guru 64348 points

    Hi ,

    Can you please provide steps to replicate the issue at our end?

    Only seeing the above error message doesn't give much information for debugging the issue.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 170 points

    I'm not really sure what changed on my side since Friday when I was able to run the hello_world after setting up CCS. All I do is I right-click on the project in the explorer and do "Rebuild project", then when that completes, I do "Debug project F5" which results in that error right away. Below is my launch.json file. Also, when I right-click on project -> Properties -> Debug, I see that message there too "Unknown module: File". Any idea what should I see there under the Debug entry? I found this thread from 6 years ago that talks about the same error but not clear to me how it was resolved. I'm not using CloudAgent, but when I searched the install directory I found that message coming from cc_base/cloudagent/src/module.js, so not sure if CloudAgent is involved, although I never installed it or changed any related settings. Sorry I can't be more specific.

    launch.json

    =========

    {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos",
                "type": "ccs-debug",
                "request": "launch",
                "projectInfo": {
                    "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos",
                    "resourceId": "/hello_world_am62x-sip-sk_m4fss0-0_freertos"
                },
                "launchSettings": {
                    "coresToLoadForProjectLaunch": [
                        "BLAZAR_Cortex_M4F_0"
                    ]
                }
            }
        ]
    }


    CCS/MSP432P401R: Unknown Module: File debug error when trying to run gpio_toggle_output example project - Code Composer Studio forum - Code Composer StudioTm︎ - TI E2E support forums

  • 0 in reply to Ayman Ghanem
    TI__Guru 64348 points

    Please try the below steps.

    1. Open Debug view in CCS, navigate to Debug View. Launch the target configuration file.

    2. Connect to the core and load the binary.

    More details can be found at CCS_LAUNCH 

  • 0 in reply to Tushar Thakur
    Prodigy 170 points

    That doesn't work. Still get the same error when I start to debug. I think there is a problem with this version of CCS (20.3.1.5_1.9.1). Here is the procedure I followed to reproduce the problem:

    1. Completely uninstall CCS and remove everything under c:/ti/cs2031

    2. Remove the workspace_ccstheia directory under c:/Users/my_user

    3. Re-install CCS_20.3.1

    4. When CCS starts, I create a new project (hellow_world for M4 with FreeRTOS)

    5. Build the hello_wrold example

    6. Debug project. This will result in an error because it doesn't like the two commented lines in launch.json (see attached lanuch.json that's created by default).

    7. I removed the two commented lines, and the "Debug project" now works and I get the print on my M4 console.

    8. Close CCS

    9. Start CCS and try to debug the project again. Now I get the "Unknown module:File" error.

    10. I tried that sequence 3 times. After a new install, I remove the two comments from launch.json and I can debug the project. Then, I close CCS and start it again and debug fails with that error. So, am I missing something between the first run after a new install and subsequent restart of CCS?

    -Ayman

    Default launch.json with comments

    {
        // Use IntelliSense to learn about possible attributes.
        // Hover to view descriptions of existing attributes.
        "version": "0.2.0",
        "configurations": [
            {
                "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos",
                "type": "ccs-debug",
                "request": "launch",
                "projectInfo": {
                    "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos",
                    "resourceId": "/hello_world_am62x-sip-sk_m4fss0-0_freertos"
                }
            }
        ]
    }
  • 0 in reply to Ayman Ghanem
    TI__Guru 64348 points

    Your configuration (launch.json) file should look like below.

    {
    "version": "0.2.0",
    "configurations": [
        {
            "name": "board.ccxml",
            "type": "ccs-debug",
            "request": "launch",
            "targetConfig": "${targetConfigFolder}\\board.ccxml"
        },
        {
            "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos_ti-arm-clang",
            "type": "ccs-debug",
            "request": "launch",
            "projectInfo": {
                "name": "hello_world_am62x-sip-sk_m4fss0-0_freertos_ti-arm-clang",
                "resourceId": "/hello_world_am62x-sip-sk_m4fss0-0_freertos_ti-arm-clang"
            }
        }
    ]
}

    Modify your launch.json. Replace the name of *ccxml file with the appropriate file name. Let us know if this works.