|
15 | 15 | Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved. |
16 | 16 |
|
17 | 17 | Scanning USB buses for supported XDS110 devices... |
18 | | - ``` |
19 | 18 |
|
20 | | -<<<< Device 0 >>>> |
| 19 | + <<<< Device 0 >>>> |
| 20 | +
|
| 21 | + VID: 0x0451 PID: 0xbef3 Device Name: XDS110 Embed with CMSIS-DAP Version: |
| 22 | + 3.0.0.13 Manufacturer: Texas Instruments Serial Num: L4100652 Mode: Runtime |
| 23 | + Configuration: Standard |
21 | 24 |
|
22 | | -VID: 0x0451 PID: 0xbef3 Device Name: XDS110 Embed with CMSIS-DAP Version: |
23 | | -3.0.0.13 Manufacturer: Texas Instruments Serial Num: L4100652 Mode: Runtime |
24 | | -Configuration: Standard |
| 25 | + Found 1 device. |
25 | 26 |
|
26 | | -Found 1 device. |
| 27 | + ``` |
27 | 28 |
|
28 | | -``` |
29 | | -In this example, my LaunchPad's XDS110 has a serial number of `L4100652`. |
| 29 | + In this example, my LaunchPad's XDS110 has a serial number of `L4100652`. |
30 | 30 |
|
31 | | -- Start a new Code Composer Studio Workspace. This can be named anything you |
32 | | -would like. But it is recommended that you use a blank workspace. |
| 31 | +- Start a new Code Composer Studio Workspace. This can be named anything you |
| 32 | + would like. But it is recommended that you use a blank workspace. |
33 | 33 |
|
34 | | - |
| 34 | +  |
35 | 35 |
|
36 | | -- Create a new Target Configuration File by selecting `File` >> `New` >> |
37 | | -`Target Configuration File`. This file can also be exported from UniFlash |
38 | | -with the `download ccxml` function. |
| 36 | +- Create a new Target Configuration File by selecting `File` >> `New` >> |
| 37 | + `Target Configuration File`. This file can also be exported from UniFlash |
| 38 | + with the `download ccxml` function. |
39 | 39 |
|
40 | | - |
| 40 | +  |
41 | 41 |
|
42 | | -- Name the new ccxml file a useful name. Here I use the XDS110 serial number |
43 | | -from before. Leave the Location as the shared location and click `Finish` to |
44 | | -create the file. |
| 42 | +- Name the new ccxml file a useful name. Here I use the XDS110 serial number |
| 43 | + from before. Leave the Location as the shared location and click `Finish` to |
| 44 | + create the file. |
45 | 45 |
|
46 | | - |
| 46 | +  |
47 | 47 |
|
48 | | -- In the new ccxml, select the `Connection` and the `Board or Device`. This may |
49 | | -be different for your setup, but all LaunchPads will use the `Texas |
50 | | -Instruments XDS110 USB Debug Probe` for the target connection. And the and a |
51 | | -`CC1352R1F3` is mounted on the `CC1352R1_LAUNCHXL` LaunchPads. Builds for |
52 | | -other LaunchPads should use the corresponding SoC name. |
| 48 | +- In the new ccxml, select the `Connection` and the `Board or Device`. This |
| 49 | + may be different for your setup, but all LaunchPads will use the |
| 50 | + `Texas Instruments XDS110 USB Debug Probe` for the target connection. And |
| 51 | + the and a `CC1352R1F3` is mounted on the `CC1352R1_LAUNCHXL` LaunchPads. |
| 52 | + Builds for other LaunchPads should use the corresponding SoC name. |
53 | 53 |
|
54 | | - |
| 54 | +  |
55 | 55 |
|
56 | | -- Now set the XDS110 serial number in the advanced tab of the ccxml. First |
57 | | -select the `Advanced` tab at the bottom of the window. Then select the Debug |
58 | | -Probe in the connection tree. Then select `Select by serial number` in the |
59 | | -`Debug Probe Selection`. Then enter the serial number from `xdsdfu` earlier |
60 | | -in the `Enter the serial number` text field. Finally click `Save` to save |
61 | | -your ccxml. |
| 56 | +- Now set the XDS110 serial number in the advanced tab of the ccxml. First |
| 57 | + select the `Advanced` tab at the bottom of the window. Then select the Debug |
| 58 | + Probe in the connection tree. Then select `Select by serial number` in the |
| 59 | + `Debug Probe Selection`. Then enter the serial number from `xdsdfu` earlier |
| 60 | + in the `Enter the serial number` text field. Finally click `Save` to save |
| 61 | + your ccxml. |
62 | 62 |
|
63 | | - |
| 63 | +  |
64 | 64 |
|
65 | | -- Clicking `Test Connection` with the LaunchPad connected will cause a JTAG |
66 | | -Integrity scan with the Debug Probe. This is a nice way to check that your |
67 | | -ccxml is setup correctly. |
| 65 | +- Clicking `Test Connection` with the LaunchPad connected will cause a JTAG |
| 66 | + Integrity scan with the Debug Probe. This is a nice way to check that your |
| 67 | + ccxml is setup correctly. |
68 | 68 |
|
69 | | - |
| 69 | +  |
70 | 70 |
|
71 | | -- Now open the Debug Configurations dialog to setup a new debug configuration. |
72 | | -Select `Run` >> `Debug Configurations...`. |
| 71 | +- Now open the Debug Configurations dialog to setup a new debug configuration. |
| 72 | + Select `Run` >> `Debug Configurations...`. |
73 | 73 |
|
74 | | - |
| 74 | +  |
75 | 75 |
|
76 | | -- Create a new launch configuration from the default CCS launch configuration. |
77 | | -Select `Code Composer Studio - Device Debugging` and then create a new launch |
78 | | -configuration with the `New launch configuration` button. |
| 76 | +- Create a new launch configuration from the default CCS launch configuration. |
| 77 | + Select `Code Composer Studio - Device Debugging` and then create a new |
| 78 | + launch configuration with the `New launch configuration` button. |
79 | 79 |
|
80 | | - |
| 80 | +  |
81 | 81 |
|
82 | | -- Name your new configuration. Update the `Target Configuration` field with the |
83 | | -ccxml you created earlier. Click `Apply` to save the launch configuration. |
| 82 | +- Name your new configuration. Update the `Target Configuration` field with |
| 83 | + the ccxml you created earlier. Click `Apply` to save the launch |
| 84 | + configuration. |
84 | 85 |
|
85 | | -Once the launch configuration is created you do not need to re-create it |
86 | | -every time. The Debug session can be started with the `Debug` button in the |
87 | | -`Debug Configurations` dialog, or by selecting `Run` >> `Debug History` >> |
88 | | -`<launch configuration name>`. |
| 86 | + Once the launch configuration is created you do not need to re-create it |
| 87 | + every time. The Debug session can be started with the `Debug` button in the |
| 88 | + `Debug Configurations` dialog, or by selecting `Run` >> `Debug History` >> |
| 89 | + `<launch configuration name>`. |
89 | 90 |
|
90 | | - |
| 91 | +  |
91 | 92 |
|
92 | | -- Now that the Debug session is started we can connect to the target. Make sure |
93 | | -that the right Debug Probe is selected in the `Debug` window and click |
94 | | -`Connect Target`. |
| 93 | +- Now that the Debug session is started we can connect to the target. Make |
| 94 | + sure that the right Debug Probe is selected in the `Debug` window and click |
| 95 | + `Connect Target`. |
95 | 96 |
|
96 | | - |
| 97 | +  |
97 | 98 |
|
98 | | -- The target MCU is connected. The MCU is halted on connection by default. |
99 | | -Select the `Load Program...` option to select the ELF image to load. |
| 99 | +- The target MCU is connected. The MCU is halted on connection by default. |
| 100 | + Select the `Load Program...` option to select the ELF image to load. |
100 | 101 |
|
101 | | - |
| 102 | +  |
102 | 103 |
|
103 | | -- Navigate to the ELF file |
104 | | -(`${connectedhomeip}/examples/lock-app/cc13x2_26x2/out/debug/chip-cc13x2_26x2-lock-example.out` |
105 | | -file) in the `Load Program` dialog. Click `OK` to begin loading the target. |
| 104 | +- Navigate to the ELF file |
| 105 | + (`${connectedhomeip}/examples/lock-app/cc13x2_26x2/out/debug/chip-cc13x2_26x2-lock-example.out` |
| 106 | + file) in the `Load Program` dialog. Click `OK` to begin loading the target. |
106 | 107 |
|
107 | | - |
| 108 | +  |
108 | 109 |
|
109 | | -- After loacating the source file for `main.cpp` we can step through the code |
110 | | -as it executes. |
| 110 | +- After loacating the source file for `main.cpp` we can step through the code |
| 111 | + as it executes. |
111 | 112 |
|
112 | | - |
| 113 | +  |
113 | 114 |
|
114 | 115 | [ccs]: https://www.ti.com/tool/CCSTUDIO |
115 | | -``` |
0 commit comments