<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Code Composer Studio™︎</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/</link><description>Before making a post please check the &lt;a href="http://processors.wiki.ti.com/index.php/Category:CCS%20"&gt;CCS wiki&lt;/a&gt; which contains detailed documentation, tutorials and FAQs. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: TMS320F28P650DH: Flash Settings in Project Properties → Debug are saved to the first launch configuration in launch.json, not the selected build configuration</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696961/tms320f28p650dh-flash-settings-in-project-properties-debug-are-saved-to-the-first-launch-configuration-in-launch-json-not-the-selected-build-configuration/6542316</link><pubDate>Wed, 18 Nov 2026 13:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:017c5c98-ed7b-497a-9c03-47aa35b3face</guid><dc:creator>Ki</dc:creator><description>This is interesting. It looks like you have two projects - Bdc_cpu1 and Bdc_cpu2. Both project folders are in the root D: drive location. I see separate launches - Bdc_cpu1_DEBUG and Bdc_cpu1_FLASH. And I see each launch reference an out file from Bdc_cpu1 and Bdc_cpu2. I am guessing that you manually created these launches and then specified different out files for each CPU to auto load. That is fine. However it looks like you are trying to do a project debug launch with it. What I would recommended in this scenario is to create a project-less debug launch and associate the outfiles to each CPU in this launch. Then use this project-less debug launch instead. It is similar to what is shown below in the example in the user&amp;#39;s guide. A project-less launch causes less issues in such scenarios. Thanks ki</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: How to create a project</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6542295</link><pubDate>Wed, 18 Nov 2026 13:15:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:238f9b83-cc81-4280-a182-0a79004b7ec1</guid><dc:creator>Ki</dc:creator><description>Yes, the product is very new, just released last week. Because of that, and also the more limited feature set and device support, there has not been many users yet. [quote userid=&amp;quot;724530&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6541680&amp;quot;]At this time, I need to close all instances of VSCode.(Same with Theia? It occurred in SysConfig.)[/quote] Theia, while it is a VS Code like environment, is not VS Code (as you are aware) so they should not conflict.</description></item><item><title>Forum Post: RE: TMS320F28P551SG-FS: CCS/DSLite never erase or program Bank 4 on TMS320F28P551SG5 (ambiguous part entries in TMS320F28P551x.xml)</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691548/tms320f28p551sg-fs-ccs-dslite-never-erase-or-program-bank-4-on-tms320f28p551sg5-ambiguous-part-entries-in-tms320f28p551x-xml/6541867</link><pubDate>Wed, 18 Nov 2026 05:03:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1a3d8b64-b78a-4897-ba7f-c32b878bb703</guid><dc:creator>Arpit Varahmihir</dc:creator><description>Hi Thomas, [quote userid=&amp;quot;722740&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691548/tms320f28p551sg-fs-ccs-dslite-never-erase-or-program-bank-4-on-tms320f28p551sg5-ambiguous-part-entries-in-tms320f28p551x-xml&amp;quot;]Please fix the duplicate RegisterId entries in TMS320F28P551x.xml (distinct values for 256/320KB and 512/576KB, or an additional discriminator). Please also confirm what 0x721F7 / PARTIDL.FLASH_SIZE should be for the F28P551SG5.[/quote] I have raised an internal bug for the same. There is a mismatch in the TRM and .xml file =. The TRM table should have the correct values. Regards Arpit</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: How to create a project</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6541680</link><pubDate>Wed, 18 Nov 2026 00:31:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:38c3764f-8dd1-49a0-83c2-7637f9990802</guid><dc:creator>Takayuki Kato</dc:creator><description>It seems to be little support information and few downloads. (CCStudio for VS Code: 411 installs) This will be future consideration. Thanks your information. Note that while VSCode is also used at Nordic, it occasionally freezes during debugging. At this time, I need to close all instances of VSCode.(Same with Theia? It occurred in SysConfig.)</description></item><item><title>Forum Post: RE: TMS320F28P650DH: Flash Settings in Project Properties → Debug are saved to the first launch configuration in launch.json, not the selected build configuration</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696961/tms320f28p650dh-flash-settings-in-project-properties-debug-are-saved-to-the-first-launch-configuration-in-launch-json-not-the-selected-build-configuration/6541676</link><pubDate>Wed, 18 Nov 2026 00:22:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2e6fcf95-fdf1-4ba3-9bad-df24d8ffb6d5</guid><dc:creator>AN eunji</dc:creator><description>I’m sending the requested launch.json file. As you mentioned, JSON files can’t be attached, so I’ve attached it as a .txt file instead. e2e.ti.com/.../launch.txt</description></item><item><title>Forum Post: RE: TMS320F28P650DH: Flash Settings in Project Properties → Debug are saved to the first launch configuration in launch.json, not the selected build configuration</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696961/tms320f28p650dh-flash-settings-in-project-properties-debug-are-saved-to-the-first-launch-configuration-in-launch-json-not-the-selected-build-configuration/6541273</link><pubDate>Tue, 17 Nov 2026 17:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:521478ee-c932-4411-a74c-5bb8d87431fe</guid><dc:creator>Ki</dc:creator><description>[quote userid=&amp;quot;690399&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696961/tms320f28p650dh-flash-settings-in-project-properties-debug-are-saved-to-the-first-launch-configuration-in-launch-json-not-the-selected-build-configuration&amp;quot;]The project has two build configurations, FLASH and DEBUG, and \.theia\launch.json contains two launch configurations: cpu1_FLASH and cpu1_DEBUG .[/quote] There typically is just one launch for both configurations. Can you attach your launch.json file? You may need to change the extension to txt. Thanks ki</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: How to create a project</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6541016</link><pubDate>Tue, 17 Nov 2026 13:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9473959d-9564-4c9e-b1ac-a81493e24139</guid><dc:creator>Ki</dc:creator><description>[quote userid=&amp;quot;724530&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6540340&amp;quot;]I understood that I cannot replace VS Code with CCS Theia.[/quote] That is correct. CCS Thiea is a branch of VS Code and is its own IDE framework. Note that there is a new product called CCStudio for VS Code: https://www.ti.com/tool/CCSTUDIO-VSCODE It provides project build and debug support for TI devices as an extension to standard VS Code. Note that the underlying project build system and debugger is quite different and it only supports a limited number of device families. There is also a current limitation where you cannot import your existing CCS projects. Hence it is likely not an option for you yet, however we do plan on increasing the feature set and capabilities down the road so it is something to be aware of for the future: https://www.youtube.com/watch?v=RCdatQTU2P8</description></item><item><title>Forum Post: RE: TM4C1294NCPDT: TM4C1294NCPDT Custom PCB Cannot Be Programmed via EK-TM4C1294XL ICDI – JTAG Communication and Power Supply Verification</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1690660/tm4c1294ncpdt-tm4c1294ncpdt-custom-pcb-cannot-be-programmed-via-ek-tm4c1294xl-icdi-jtag-communication-and-power-supply-verification/6540691</link><pubDate>Tue, 17 Nov 2026 06:45:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2e0e8b5a-9b61-4baa-949c-0cf1e4e012c0</guid><dc:creator>Xiaodong LI</dc:creator><description>Hi Samrat, Congratulations on getting the second MCU programmed and running! Your A/B swap test is a textbook troubleshooting method, and your conclusion is spot-on—the first IC has almost certainly suffered physical hardware damage. Here is why the first IC likely failed and exhibited ~1.6 V on the TDO pin: 1. **Damage from Initial Power-Ups Without VDDC Decoupling:** When the first IC was powered up on the initial board revision with floating VDDC pins (no external LDO output capacitors), the internal 1.2 V LDO likely experienced severe oscillation or voltage overshoot. This can permanently damage the internal core logic or the JTAG TAP controller, preventing proper initialization. 2. **Damaged TDO Output Buffer / ESD Structure:** Measuring a mid-rail voltage (~1.6 V) on TDO while a known-good IC reads 3.3 V on the exact same circuit is a classic symptom of a partially damaged I/O output driver or a leaky internal ESD protection clamp. Aside from the initial LDO instability, this can also be caused by ESD handling or thermal stress during soldering/rework. 3. **Great Catch on the WAKE# Pin &amp;amp; Final Schematic Notes:** Adding the 100 kΩ pull-up resistor to the **WAKE#** pin was a crucial improvement—leaving WAKE# floating on TM4C129x devices can inadvertently trigger Hibernation mode and block JTAG access. *(Note: For future revisions, the 10 kΩ pull-down on TDO is not required by TI&amp;#39;s JTAG guidelines, though your current setup is clearly working well.)* Since this thread has been open for nearly a month and the issue appears to be resolved, I am going to close it now. If you are satisfied with the solution, please go ahead and click **&amp;quot;This resolved my issue&amp;quot;** (Solved). If you run into any new questions, please feel free to create a new thread and include a link to this post for reference. Best regards, Xiaodong</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: How to create a project</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6540340</link><pubDate>Mon, 16 Nov 2026 23:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:eed6dfe6-007e-4ddd-bd57-c48e651e687d</guid><dc:creator>Takayuki Kato</dc:creator><description>I understood that I cannot replace VS Code with CCS Theia. Thanks,</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: Only white screen with CCS Logo - GetVSyncParametersIfAvailable</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1690639/ccstudio-theia-only-white-screen-with-ccs-logo---getvsyncparametersifavailable/6540185</link><pubDate>Mon, 16 Nov 2026 21:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:afad8825-6c4e-403e-99ba-a698383934f2</guid><dc:creator>Ki</dc:creator><description>Thank you for sharing your finding. I discussed them with engineering. They did not expect the issue to happen with CCS 21.0.1 as additional improvements were made in that release to avoid such issues. I tried to simulate the issue without success. However that was on Windows. Perhaps this issue can occur on Linux. We will look for further areas to improve. Thanks ki</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: How to create a project</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6540172</link><pubDate>Mon, 16 Nov 2026 20:58:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9aa325bc-7c11-46d0-a1e2-842daf6b6faa</guid><dc:creator>Ki</dc:creator><description>[quote userid=&amp;quot;2210&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1695099/ccstudio-theia-how-to-create-a-project/6537668&amp;quot;]We will see if there is a way to do this with Theia.[/quote] Engineering investigated this issue and this option is not available in the Theia IDE framework that CCS is based on.</description></item><item><title>Forum Post: RE: F29H850DM: Exporting or ploting array in CCS</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697873/f29h850dm-exporting-or-ploting-array-in-ccs/6539989</link><pubDate>Mon, 16 Nov 2026 18:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:df40e197-5fbc-4e6a-ae0a-db923acab884</guid><dc:creator>Ki</dc:creator><description>[quote userid=&amp;quot;571219&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697873/f29h850dm-exporting-or-ploting-array-in-ccs&amp;quot;]For example, how to expert a array like float x[50]? I&amp;#39;d like to export all 50 values as float to a CSV for further processing.[/quote] There is an option to export. The option is fairly new and is missing from the documentation (which i will fix). You can export data to CSV: The format is limted to scalar however. [quote userid=&amp;quot;571219&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697873/f29h850dm-exporting-or-ploting-array-in-ccs&amp;quot;]In the meantime, how to plot this 50 values in the integrated Graph feature? For now the Graph features can only polt value against time, but not against the array index.[/quote] Did you try setting the Capacity size to 50 and then specifying the array for the expression and refresh the graph (or step)?</description></item><item><title>Forum Post: RE: F29H850DM: Exporting or ploting array in CCS</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697873/f29h850dm-exporting-or-ploting-array-in-ccs/6539838</link><pubDate>Mon, 16 Nov 2026 16:03:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:bfabb33a-4c17-4e33-a133-a0a85fbdcdc6</guid><dc:creator>Aishwarya Rajesh</dc:creator><description>Hi Hang, I do not think this feature is present on CCS natively, but I&amp;#39;ll let the CCS team confirm. We do offer the following tools to help log data that may be of interest: MCU Signal Sight MCU Mission Control Best Regards, Aishwarya</description></item><item><title>Forum Post: RE: CCSTUDIO-THEIA: Database file compile_commands.json generation from CCStudio ccs-server-cli</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693339/ccstudio-theia-database-file-compile_commands-json-generation-from-ccstudio-ccs-server-cli/6539823</link><pubDate>Mon, 16 Nov 2026 15:50:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:519fa721-5cfe-4a66-9c49-a73999fabfc9</guid><dc:creator>Ki</dc:creator><description>Sorry for the delay. I just wanted to let you know that there is a ticket for this request. I just had it synced publicly so you can track it: https://sir.ext.ti.com/jira/browse/EXT_EP-13787 Thanks ki</description></item><item><title>Forum Post: F29H850DM: Exporting or ploting array in CCS</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697873/f29h850dm-exporting-or-ploting-array-in-ccs</link><pubDate>Mon, 16 Nov 2026 06:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:eb371325-f99a-4bbf-b1b5-07164e255cc3</guid><dc:creator>Hang Yang</dc:creator><description>Part Number: F29H850DM Hi Team, How can we export and plot a array in the CCS21? For example, how to expert a array like float x[50]? I&amp;#39;d like to export all 50 values as float to a CSV for further processing. In the meantime, how to plot this 50 values in the integrated Graph feature? For now the Graph features can only polt value against time, but not against the array index. Regards, Hang</description><category domain="https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/tags/Industrial%2bAutomation">Industrial Automation</category><category domain="https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/tags/F29H850DM">F29H850DM</category></item><item><title>Forum Post: RE: TMDSEMU200-U: XDS200: Windows ARM64 Driver Support for Snapdragon-Based Laptops</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697160/tmdsemu200-u-xds200-windows-arm64-driver-support-for-snapdragon-based-laptops/6539117</link><pubDate>Sun, 15 Nov 2026 23:43:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:457ebe4c-cb7a-47a4-a54f-c08f3206496c</guid><dc:creator>Sang-il Nam</dc:creator><description>Thank you for your response. An increasing number of our business partners and customers are using PCs running Windows on ARM64. We hope TI will offer debug probes and kernel drivers that support this platform in the near future.</description></item><item><title>Forum Post: RE: TM4C1294NCPDT: TM4C1294NCPDT Custom PCB Cannot Be Programmed via EK-TM4C1294XL ICDI – JTAG Communication and Power Supply Verification</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1690660/tm4c1294ncpdt-tm4c1294ncpdt-custom-pcb-cannot-be-programmed-via-ek-tm4c1294xl-icdi-jtag-communication-and-power-supply-verification/6539073</link><pubDate>Sat, 14 Nov 2026 16:05:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:230752b9-34de-40b9-aa03-06b8c4969815</guid><dc:creator>Samrat Tikone</dc:creator><description>Hi Sir, I wanted to update you on the TM4C1294NCPDT programming issue and the changes I made to the circuit. I have two bare TM4C1294NCPDT ICs. Initially, I was unable to program the first IC, and CCS repeatedly showed an &amp;quot;Error connecting to the target&amp;quot; message. To investigate whether the issue was with the circuit or the MCU, I removed the first IC and replaced it with the second IC, keeping the same PCB, power supply, debugger and connections. The second IC was successfully detected and programmed without any issues. One important observation was the difference in TDO pin voltage: - First IC: TDO voltage was approximately 1.6 V. - Second IC: TDO voltage was approximately 3.3 V. This suggests that the first IC may have a problem with its JTAG/TDO interface or internal initialization. Since the second IC works with the same circuit, the first IC is now a strong suspect. I also made the following changes to the circuit: 1. WAKE pin: Connected to 3.3 V through a 100 kΩ pull-up resistor. 2. VDD supply: Added a 12.1 &amp;#181;F capacitor and two 10 &amp;#181;F capacitors between VDD and GND. 3. VDDA supply: Implemented a separate analog supply filtering circuit using a ferrite bead and capacitors between VDDA and GNDA. 4. RBIAS pin: Connected to GND through an approximately 4.87 kΩ resistor. 5. VDDC supply: Connected both VDDC pins together and provided a 3.3 &amp;#181;F capacitor network with a common ground reference. With these changes, the second IC is programming successfully. I wanted to share these observations and get your opinion on whether the first IC could have a damaged TDO output or an internal MCU initialization issue.</description></item><item><title>Forum Post: RE: F29H85X-SOM-EVM: F29H85x (C29x): read memory of a running core without halting it, as on C28x</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696775/f29h85x-som-evm-f29h85x-c29x-read-memory-of-a-running-core-without-halting-it-as-on-c28x/6538979</link><pubDate>Fri, 13 Nov 2026 22:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:43cd36ee-1796-4a3f-b3cd-cdb3e53e0cec</guid><dc:creator>Ki</dc:creator><description>Thanks for the extra details. The issue is not that real-time memory accesses are not working, it is an issue where you are attempting a non-intrusive connection to the debugger and attempting to perform real-time memory access. There looks to be some issue with the non-intrusive connection attempt. [quote userid=&amp;quot;608936&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696775/f29h85x-som-evm-f29h85x-c29x-read-memory-of-a-running-core-without-halting-it-as-on-c28x/6538162&amp;quot;]is there a supported way to attach to a running C29x core and read its memory without any halt? [/quote] This type of functionality is very device dependent. I will bring this thread to the attention of the device experts for further comment. Thanks ki</description></item><item><title>Forum Post: RE: TPS65994AE: TYPE-C no display</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1696192/tps65994ae-type-c-no-display/6538563</link><pubDate>Fri, 13 Nov 2026 14:03:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:59a79c5e-3368-4a87-972c-a0a279994441</guid><dc:creator>Christodulos Tsongas</dc:creator><description>Michael, So looks like the I2C2 is sending the HPD signal virtually over DataStatus. HPD high is being sent. Still would require: What reference design you are following? USB-PD logs I2C3 TPS66994CA configuration file But I think you may be able to change this behavior. Your P0_GPIO3 is setup to be the GPIO Mux = HPD_Tx. I would recommend doing the following: The reason I would recommend this is you can either choose virtual or physical options for HPD signaling. You cannot do both so keeping it virtual for the SoC enablement is correct. Using this GPIO Event will allow the GPIO to assert to whatever device needs this and avoids the virtual/physical HPD limitation. Are you using a specific retimer/redriver?</description></item><item><title>Forum Post: RE: CODECOMPOSER: On the F29 and CCS21.0.1, register view is unreliable</title><link>https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697462/codecomposer-on-the-f29-and-ccs21-0-1-register-view-is-unreliable/6538526</link><pubDate>Fri, 13 Nov 2026 12:57:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f01de2ab-ee9c-4223-941b-4f45870363cd</guid><dc:creator>Ki</dc:creator><description>Hello, [quote userid=&amp;quot;2713&amp;quot; url=&amp;quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1697462/codecomposer-on-the-f29-and-ccs21-0-1-register-view-is-unreliable&amp;quot;]Pranav (TI support) also responded &amp;quot;I have faced issues with the CCStudio register window not reflecting the actual status of the MCU. Usually, closing and reopening the window once or twice resolves this&amp;quot;.[/quote] I am not aware of this issue. Is there another forum thread that discusses this topic? Thanks ki</description></item></channel></rss>