# Get the source code from the CLO website

Source: [https://docs.qualcomm.com/doc/80-41102-1/topic/get-the-source-code-from-the-clo-website.html](https://docs.qualcomm.com/doc/80-41102-1/topic/get-the-source-code-from-the-clo-website.html)

For the simulation project, users need to organize the directory structure to fulfill the
            building requirements.

If getting the source code from CLO website, the structure should
            be:

    simulation_env
    ├── legato
    │   ├── 3rdParty
    │   │   ├── jansson         <- https://git.codelinaro.org/clo/le/legatoproject/legato-3rdParty-jansson.git branch: caf_migration/refs/tags/20.04.0
    │   │   └── Kconfiglib      <- https://git.codelinaro.org/clo/le/legatoproject/Kconfiglib.git branch: caf_migration/refs/tags/20.04.0
    │   └── legato-af           <- https://git.codelinaro.org/clo/le/legato-af.git branch: telaf.lnx.1.1
    ├── sdk                     <- https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/snaptel-sdk.git branch: telsdk.lnx.2.0.r11-rel
    ├── telaf                   <- https://git.codelinaro.org/clo/le/platform/TelAF.git branch: telaf.lnx.1.1
    ├── telaf-pa-default        <- https://git.codelinaro.org/clo/le/platform/telaf-pa-default.git telaf.lnx.1.1
    └── telaf-pa                <- https://git.codelinaro.org/clo/le/platform/telaf-pa.git telaf-pa.lnx.1.0Copy to clipboard

Customers can get the source code from CLO website with the following
            command:

    wget -qO- https://git.codelinaro.org/clo/le/platform/TelAF/-/raw/telaf.lnx.1.1/simulation/setup_simulation.sh | shCopy to clipboard

Users should enter the 'simulation\_env' directory and update all projects they expect.
            Qualcomm provides the 'patch\_me.json' to support this feature.

Users can change their branches and put some patch-set into this JSON file.

The template is as follows:

    {
        "telaf" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name" : "telaf.lnx.1.1",
            "Commit-ID": "70dfcdf2270ecf5a22af238a30386de815daf3d8",
            "Description": "taf_25.06.00",
            "Patch-Cmd-List": []
        },
        "telaf-pa" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name" : "telaf-pa.lnx.1.0",
            "Commit-ID": "da16561eada9f1662195a20d79033c2df994d0a1",
            "Description": "taf_25.05.00",
            "Patch-Cmd-List": []
        },
        "telaf-pa-default" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name" : "telaf.lnx.1.1",
            "Commit-ID": "9f5b2ef2074979a268342923157fafe0ba60c634",
            "Description": "taf_25.06.00",
            "Patch-Cmd-List": []
        },
        "legato/legato-af" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name": "telaf.lnx.1.1",
            "Commit-ID": "ca088c1eb182ab9044164c03c7023936a74afbce",
            "Description": "taf_25.06.00",
            "Patch-Cmd-List": []
        },
        "legato/3rdParty/jansson" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name": "caf_migration/refs/tags/20.04.0",
            "Commit-ID": "cfed4c57d3deffab23e2e368d264a4087afc46ab",
            "Patch-Cmd-List": []
        },
        "legato/3rdParty/Kconfiglib" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name": "caf_migration/refs/tags/20.04.0",
            "Commit-ID": "ae147b3d2727b222653183b5abf77e38c052b595",
            "Patch-Cmd-List": []
        },
        "sdk" : {
            "Remote-Repo-Name": "origin",
            "Remote-Branch-Name": "telsdk.lnx.2.0.r11-rel",
            "Commit-ID": "3663c660388fa4dbf167f7f74fa7989c6b167be6",
            "Description": "POST CS[1]",
            "Patch-Cmd-List": []
        }
    }Copy to clipboard

For instance, if users want to change the SDK simulation TAG (or Commit-ID) for different
            test cases, there are two ways to do that:

1. Go to the 'sdk' directory and use the `git` command to switch the
                branch to the commit you want.
2. Change the JSON file (patch\_me.json), go to the 'simulation\_env' directory, and use
                the `make update-all` command.

The steps look as follows:

    cd simulation_env
      
    # If required, change the patch_me.json
      
    make update-all
     
    # If you want to update the special project
     
    make update-<project-name>
     
    # For examples
    make update-telaf
    make update-legato
    make update-sdkCopy to clipboard

Additional helpful commands:

    # Show help page
    make help
     
    # Check the branch information
    make listCopy to clipboard

**Parent Topic:** [Use TelAF simulation](https://docs.qualcomm.com/doc/80-41102-1/topic/use-telaf-simulation.html)

Last Published: Aug 06, 2026

[Previous Topic
Change storage location of the docker data (optional)](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/change-storage-location-of-the-docker-data-optional.md) [Next Topic
Build TelAF simulation docker images](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/build-docker-image-for-telaf-simulation.md)