https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/Before making a post please check the <a href="http://processors.wiki.ti.com/index.php/Category:CCS%20">CCS wiki</a> which contains detailed documentation, tutorials and FAQs. en-USTelligent Community 13https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693133/codecomposer-request-for-license-for-code-composer-studio-5-3-and-code-composer-6-0-1-spectrum-digital-xds560-v2-usb-stmTue, 27 Oct 2026 18:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c2635bd0-f682-4b7e-9871-bb32d0679226Benjamin HlophePart Number: CODECOMPOSER Other Parts Discussed in Thread: TMS320C6701 Dear Sir/Madam, I am using Code Composer Studio 5.3 and had a problem with getting a license to be able to do debugging a TMS320C6701 DSP system. I am connecting using the Spectrum Digital XDS560 V2 USB STM. When I switched to Code Composer Studio 6.0.1 I am able to connect and start a debug session, but as soon as I hit the first breakpoint in main(), I get a no license error from Code Composer Studio 6.0.1 requiring a license because we are using the Spectrum Digital XDS560 v2 USB STM. Here is the screen shot of the error.CodeComposerTMS320C6701https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693048/tms320f2808-q1-can-tmdsemu110-u-be-used-for-tms320f2808/6522672Tue, 27 Oct 2026 16:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:22b8486d-650c-4883-84c1-f7f54f96737dAnBerHi Ki, Thanks a lot for confirming! I am copying some info for the customer on how to use the on-board XDS110: https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1018803/launchxl-f280049c-used-as-standalone-xds110-to-program-legacy-c2000 Using the LAUNCH-XL should be comparable as using use the LP-XDS110 . LP-XDS110 has a different connector, but might be easier to use (smaller): https://dev.ti.com/tirex/explore/node?isTheia=false&amp;node=A__ALFqIj4dX6S.TZRERoSphA__xdsdebugprobes__FUz-xrs__LATESThttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693048/tms320f2808-q1-can-tmdsemu110-u-be-used-for-tms320f2808/6522488Tue, 27 Oct 2026 14:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a7bbc50e-3ce8-41ae-a6d7-3c53a9ddd501KiHello, The product page is often missing information regarding device support. The XDS110 should support all F28x devices. [quote userid=&quot;4466&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693048/tms320f2808-q1-can-tmdsemu110-u-be-used-for-tms320f2808&quot;]-Can XDS110 JTAG Debug Probe (TMDSEMU110-U) support also TMS320F280x (like F2808)?[/quote] I tried using my XDS110 with my F2808 board in CCS v12. I was able to connect to the target without issue: [quote userid=&quot;4466&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693048/tms320f2808-q1-can-tmdsemu110-u-be-used-for-tms320f2808&quot;]-Could the On-board XDS110 debug probe of the LAUNCHXL-F28P55X be used also?[/quote] I do see an XDS110 out connector on the launchpad so I guess it is possible to use it if the relevant jumpers on J101 are removed, as long as the pins for 4-pin JTAG are available. This is more of a hardware question for the device experts. Thanks kihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693067/tms320f28035-v6-3Tue, 27 Oct 2026 14:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5cf986e4-4fec-4608-8ebf-958e581d4f3eCarl KlaesPart Number: TMS320F28035 I have an old board with a TMS320F28035 processor. The application code was developed in CCSv6.3. I am having considerable issues trying to get my code imported and running in V20.5.0.28__1.11.0. There used to be a page to download and install older CCS versions. I can&#39;t find it now. Can anyone provide a link? Thx!HybridTMS320F28035electric &amp; powertrain systemshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1689567/ccstudio-theia-ai-assistant-base-url-issue/6522436Tue, 27 Oct 2026 14:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:741202f6-56b7-409b-9cb4-7e1390b29ec3Ki[quote userid=&quot;290290&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1689567/ccstudio-theia-ai-assistant-base-url-issue/6522409&quot;]For security reason, neither LiteLLM nor OpenRouter are allowed by my IT departement[/quote] I can emphasize. My IT department blocks most everything too (though we use have a LiteLLM setup for our local AI setup). We need to constantly request exceptions which is difficult to get approved - even for our testing purposes!https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1689567/ccstudio-theia-ai-assistant-base-url-issue/6522409Tue, 27 Oct 2026 13:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6d385b64-d191-4ad8-a6a4-98f90368fd95Gildas ROLLANDHi, For security reason, neither LiteLLM nor OpenRouter are allowed by my IT departementhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1693048/tms320f2808-q1-can-tmdsemu110-u-be-used-for-tms320f2808Tue, 27 Oct 2026 13:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5628d052-44ee-4c50-a525-55224d879d58AnBerPart Number: TMS320F2808-Q1 Other Parts Discussed in Thread: TMDSEMU110-U , LP-XDS110 Team, I just would like to double check: -Can XDS110 JTAG Debug Probe (TMDSEMU110-U) support also TMS320F280x (like F2808)? TMS320F280x is not listed as supported platform: https://www.ti.com/tool/TMDSEMU110-U#supported-products is not listed as not supported platform: https://www.ti.com/tool/TMDSEMU110-U#description -Could the On-board XDS110 debug probe of the LAUNCHXL-F28P55X be used also? -If yes can it be used on CCS 10.x, 11.x, 12.x for F2808? -Apart from XDS200 what are the other JTAG emulator alternatives for F280x? Thanks in advance, AnberTMS320F2808-Q1LP-XDS110TMS320F2808Aerospace &amp; DefenseLAUNCHXL-F28P55XTMDSEMU110-Uhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691066/uniflash-urgent-uniflash-9-7-0-msp-fet-detection-failure-production-impact/6522257Tue, 27 Oct 2026 10:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7910a22d-cee6-4709-a5d0-9ba572bf37f7Gianni BenninkHello TI Support Team, I would like to provide an update regarding our ongoing MSP-FET detection issue. Following your recommendation, I installed Code Composer Studio 21.0.1 to investigate whether the MSP-FET could be detected outside UniFlash. Unfortunately, the issue is still not resolved. Code Composer Studio testing I performed the following steps: Installed and updated Code Composer Studio 21.0.1 on a Windows 11 production desktop. Connected the MSP-FET programmer via USB. Opened the Connected Targets panel and refreshed the list. Created a new target configuration (.ccxml). Selected TI MSP430 USB1 as the connection. Selected MSP430AFE253 as the target microcontroller. Reviewed the Basic and Advanced target configuration settings. Results: The Connected Targets panel remains empty, even after refreshing. No probe ID, serial number or connection information is displayed. The target configuration editor recognizes MSP430AFE253 as a selectable device. However, the Debuggable CPUs section displays &quot;Not Found&quot;. No successful hardware connection has been established through CCS. We have not attempted to program or erase the target through CCS. Previous troubleshooting findings Our earlier investigation showed the following: The MSP-FET is recognized by Windows with USB VID_2047 and PID_0014. The MSP Application UART and MSP Debug Interface appear as COM ports. MSP430 Flasher 1.3.20 was previously able to initialize the MSP-FET, communicate with the target and identify the MSP430AFE253. UniFlash 9.7.0 fails to detect the MSP-FET. The standalone MSPAutoDetector.exe included with UniFlash reports: &quot;COM4: Could not open the device.&quot; The detector also reports &quot;fets&quot;:1 , suggesting that it identifies the presence of a FET but fails during communication or initialization. We previously observed different MSP430.dll versions between the working MSP430 Flasher utility and the UniFlash installation. We have not established whether this difference is related to the failure. Important additional observation Last week, the same MSP-FET programmer temporarily worked again on another PC. However, the issue has now returned, and the programmer is no longer working reliably on that computer either. This intermittent behavior makes the root cause particularly difficult to identify. Questions for TI Could you please advise on the following? Is an empty Connected Targets panel in CCS 21 expected for an MSP-FET, or should the probe appear automatically? Does the &quot;Debuggable CPUs: Not Found&quot; message indicate missing device support, an invalid target configuration or an actual probe detection problem? Is there a TI-supported diagnostic utility or procedure to verify MSP-FET communication independently of UniFlash and CCS? Could this behavior be related to the MSP430 debug driver, USB communication or a compatibility issue between the installed tools? Are there any known issues involving MSP-FET detection on Windows 11 with UniFlash 9.7.0 or CCS 21? This issue is affecting our production environment, so we would appreciate your assistance in identifying the root cause and providing an officially supported solution. We can provide additional logs, screenshots and diagnostic results if required. Thank you for your support. Best regards, Giannihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691317/mspm0g3519-mspm0g3519-compare1-timerperiod-cannot-set-to-32bit-max-0xffffffff---limited-to-16bit-0xffff/6522226Tue, 27 Oct 2026 10:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:30527546-f7db-4308-b5fe-7eab8633c46eJanz BaiHello Satoshi, What is user&#39;s environment? and I found that you also mentioned &quot;CLI&quot; in your post, what is that? Now this issue can&#39;t reproduced on TI side, it shows that our CCS tool doesn&#39;t has bug about this function, at least in Windows environment. And about the information you provided and your requirement of tests, it may use much time for us, if it needs us to check and confirm your guess on our side. BR, Janz Baihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691317/mspm0g3519-mspm0g3519-compare1-timerperiod-cannot-set-to-32bit-max-0xffffffff---limited-to-16bit-0xffff/6521777Tue, 27 Oct 2026 01:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bdda4daa-5e6c-45f0-a368-ffd4f5012199Satoshi KawaguchiHello Janz, I conducted additional resarches as follows: -------------------------------------------------- 1. Investigation Details and Results -------------------------------------------------- 1-1. Configurable range when the TIMER module is assigned to TIMG12 (checked in the GUI) With BUSCLK = 80 MHz TIMA : 12.5ns to 819.2us (12.5ns x 65536) TIMG : 25ns to 1.64ms (25ns x 65536) TIMG12: 12.5ns to 53.69s (12.5ns x 0xFFFFFFFF) -&gt; With TIMER, assigning TIMG12 allows periods exceeding 16 bits to be set. 1-2. Inquiry to TI and reproduction status - The &quot;16-bit limit&quot; is not reproduced in TI&#39;s environment. - In the user&#39;s environment, the same build error occurs even when a new empty project is created and only TIMER-COMPARE is enabled. -&gt; It is unlikely to be a problem with project-specific settings. The cause of the difference lies either in the user&#39;s environment (state of SysConfig/SDK) or in your reproduction procedure (e.g., GUI vs. CLI). (Not yet identified.) 1-3. Verification after creating a new project - The error also occurs when a new project is created and only the COMPARE module is enabled. -&gt; Judged to be a defect that occurs in the COMPARE module alone. 1-4. Adding console.log(e) to TIMER&#39;s isHighResolutionCapable and building in CCS - The same TypeError as in COMPARE appears (via getValue / getTimerClockFreq). - However, the build completes successfully. 1-5. Adding [HRC] logs to TIMER (inst.$name, $assign, $suggestSolution, keys of peripheral, $solution) and building in CCS [During &quot;Running script...&quot;] - First 4 calls: exceptions. $solution = undefined ($assign = TIMG12 is set). - Last 4 calls: no exceptions ($solution is resolved, and peripheralName can be read). [From &quot;Validating...&quot; to &quot;Generating Code&quot;] - No [HRC] calls during &quot;Validating...&quot;. - Two calls immediately after &quot;Generating Code&quot;, both without exceptions (resolved). -&gt; In TIMER, $solution changes from unresolved to resolved partway through &quot;Running script...&quot;, and remains resolved from then on. The 32-bit determination is ultimately used, so no error occurs. 1-6. Adding the same [HRC] logs to COMPARE and building in CCS - All 4 [HRC] calls raised exceptions. $solution = undefined ($assign = TIMG12 is set). - The &quot;later resolved calls&quot; seen in TIMER do not exist. - No [HRC] calls appear after &quot;Validating...&quot;. - The following error appears at &quot;Validating...&quot; (when 65537 is set): timerPeriod: Valid number of edge is between [0,65535] -&gt; In COMPARE, $solution remained unresolved in every evaluation that could be observed, and the false result (treated as 16-bit) is considered to have been used for validation. 1-7. Observations in the GUI (user report) - When PinMux is set to something other than TIMG12 and 65537 or more is entered in Number of Edges to Detect, the SysConfig tool (GUI) displays an error. - When set to TIMG12, no error appears in the GUI. -&gt; This indicates that the TIMG12 determination works correctly in the GUI (returns true). -------------------------------------------------- 2. Conclusions -------------------------------------------------- (1) Confirmed facts - Although $assign = &quot;TIMG12&quot; is set, there are occasions during the CLI build when $solution is undefined inside isHighResolutionCapable. This is common to both TIMER and COMPARE. - In TIMER, $solution is resolved partway through &quot;Running script...&quot;, and subsequent evaluations use the 32-bit determination, so the build passes. - In COMPARE, according to the logs, no evaluation in which $solution is resolved ever appears before proceeding to &quot;Validating...&quot;, resulting in the 16-bit upper-limit error. - The ccp0 pin is not involved. (The same symptom occurs with the Event Trigger setting.) (2) Presumptions (unverified) - It is highly likely that there is a difference in evaluation timing: in the GUI, evaluation happens with $solution already resolved, whereas in the CLI build, evaluation happens while it is unresolved. (This has not been directly confirmed by outputting console.log on the GUI side.) The reason your environment does not reproduce the issue could also be explained if you checked in the GUI. - From the observation that the GUI shows an error for anything other than TIMG12 and no error for TIMG12, it cannot be asserted that &quot;the branching between TIMG12 and others is working correctly&quot;, because a difference in evaluation timing would produce the same observation. (3) Unresolved points - Why $solution is not resolved in COMPARE (solver execution order, or the handling of $assign). - The cause of the difference between TIMER, where it is resolved partway through, and COMPARE, where it is not. COMPARE differs from TIMER in that its peripheral has a ccp0Pin entry, but whether this has any effect remains only a weakly supported conjecture. ======== Then, (1)Please check console.log() results by editing isHighResolutionCapable() of CompTimerMSPM0.syscfg.js in the SDK and building your project. (2)Please find the reason $solution is resolved in TIMER module, whereas not resolved in COMPARE in spite of being used for validation. BR, Satoshi Kawaguchihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691946/tms320vc33-need-code-composer-v4-10/6521394Mon, 26 Oct 2026 17:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a073e733-b7a3-4643-a94b-1ca91cfeb5f4KiThis issue was resolved via private E2E message.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/6520822Mon, 26 Oct 2026 09:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2e2e9eca-23c3-429c-9f9d-44b39564397bXiaodong LIHi Samrat Thank you for sharing the revised schematic. I have thoroughly reviewed the changes. The primary fatal issues that blocked your JTAG communication have been successfully corrected: VDDC core voltage pins (87 &amp; 115) are now tied together with the proper decoupling capacitor network ( C13 and C14 ), ensuring the internal 1.2V digital core logic can now power up and come out of reset. RBIAS (pin 59) is now correctly terminated to GND via a 4.7kΩ resistor ( R12 ), stabilizing the internal PHY circuitry. JTAG lines ( TMS , TDI , TCK ) now have the recommended external strong pull-up/pull-down resistors ( R5 , R6 , R10 ), significantly improving signal integrity. OSC0 jumper is a great addition for flexible grounding configuration if the main internal oscillator is bypassed. A few final recommendations for your PCB Layout &amp; Hardware assembly phase: VDDC Capacitor Value: For C13 , please populate it with a 3.3&#181;F low-ESR ceramic capacitor (rather than 2.2&#181;F ) to align fully with TI&#39;s recommended guidelines for the TM4C129x family. Component Placement: During PCB layout, ensure the smaller 0.1&#181;F capacitors ( C14 for VDDC, and C1, C2, C7, C8 for VDD) are placed as close as physically possible to their respective MCU pins to minimize trace inductance. RTC Crystal (X1): Ensure your firmware explicitly configures PM1 and PM2 to their alternative XOSC0/XOSC1 functions to read the 32.768 kHz clock correctly if you are utilizing the Hibernation module. This revised schematic looks solid and ready for the next phase. if you needed, Please let me know how the first boot and JTAG connection go after you implement these hardware changes! Thankshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691317/mspm0g3519-mspm0g3519-compare1-timerperiod-cannot-set-to-32bit-max-0xffffffff---limited-to-16bit-0xffff/6520768Mon, 26 Oct 2026 08:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:291375e6-0be4-4900-9768-47b5dc608de2Janz BaiHello Satoshi, I am also very interested in what happened on your side, but I can&#39;t reproduce your issue on my side using the same configuration with you, so I think our Sysconfig or CCS or SDK doesn&#39;t have bug on this case. What do you want me to help to do further, you can tell me. BR, Janz Baihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691317/mspm0g3519-mspm0g3519-compare1-timerperiod-cannot-set-to-32bit-max-0xffffffff---limited-to-16bit-0xffff/6520650Mon, 26 Oct 2026 06:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4febf6ca-84e7-4136-aa49-b8db97b92abcSatoshi KawaguchiHello Janz, Thank you for resarching. I also conducted my own investigation, as follows. I added console.log(e) inside the catch block of CompTimerMSPM0.syscfg.js, changed “Number of Edges to Detect” from 65536 to 65537, and built the project. The following exception was thrown during the build. === Running script... TypeError: Cannot read properties of undefined (reading &#39;peripheralName&#39;) at isHighResolutionCapable (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:240:58) at Object.getValue (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:292:8) at cb (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:83:24) at withDeprecatedAccess (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\deprecatedAccessGuard.ts:14:10) at disableScriptingForCallback (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\scripting\scriptingGuard.ts:26:10) at metaContentFunction (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:82:5) at expensiveFunction (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:97:99) at memo (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:19:17) at getValueMemo (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:98:37) at o.get (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:91:14) TypeError: Cannot read properties of undefined (reading &#39;peripheralName&#39;) at isHighResolutionCapable (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:240:58) at Object.getValue (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:292:8) at cb (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:83:24) at withDeprecatedAccess (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\deprecatedAccessGuard.ts:14:10) at disableScriptingForCallback (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\scripting\scriptingGuard.ts:26:10) at metaContentFunction (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:82:5) at expensiveFunction (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:97:99) at memo (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:19:17) at getValueMemo (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\utils\memos.ts:98:37) at o.get (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\configurables\configurableMgr.ts:91:14) TypeError: Cannot read properties of undefined (reading &#39;peripheralName&#39;) at isHighResolutionCapable (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:240:58) at getTimerCountBitRes (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:316:8) at Object.validate (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:1311:39) at K.validate (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:641:16) at iteratee (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\instanceContainers\module.ts:158:55) at baseEach (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11) at Function.each (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:9409:52) at A.validate (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\instanceContainers\module.ts:158:5) at iteratee (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\metaEnvironment\runtimeContext.ts:341:6) at Pt (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11) TypeError: Cannot read properties of undefined (reading &#39;peripheralName&#39;) at isHighResolutionCapable (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:240:58) at getTimerCountBitRes (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:316:8) at Object.validate (C:\ti\mspm0_sdk_2_11_00_07\source\ti\driverlib\.meta\compare\CompTimerMSPM0.syscfg.js:1312:79) at K.validate (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\objectManagers\moduleInstance.ts:641:16) at iteratee (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\instanceContainers\module.ts:158:55) at baseEach (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11) at Function.each (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:9409:52) at A.validate (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\instanceContainers\module.ts:158:5) at iteratee (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\src\pinmux\services\metaEnvironment\runtimeContext.ts:341:6) at Pt (C:\ti\sysconfig_1.26.2\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11) Validating... [0]error: TMG12_EdgeCount(/ti/driverlib/COMPARE) timerPeriod: Valid number of edge is between [0,65535] === The exception was raised via getValue (line 292) and via validate (lines 1311 and 1312) through getTimerCountBitRes (line 316). Next, I removed console.log(e) and instead added output of inst.peripheral, $solution, inst.$name, $assign, and $suggestSolution. The code after the change is as follows. === function isHighResolutionCapable(inst) { console.log(&quot;[HRC] inst.$name =&quot;, inst.$name); console.log(&quot;[HRC] $assign =&quot;, inst.peripheral &amp;&amp; inst.peripheral.$assign); console.log(&quot;[HRC] $suggestSolution =&quot;, inst.peripheral &amp;&amp; inst.peripheral.$suggestSolution); try{ return ((/TIMG12/.test(inst.peripheral.$solution.peripheralName))) }catch (e) { console.log(&quot;peripheral =&quot;, JSON.stringify(inst.peripheral &amp;&amp; Object.keys(inst.peripheral))); console.log(&quot;$solution =&quot;, inst.peripheral &amp;&amp; inst.peripheral.$solution); return false } } === As a result, the following was output after building. === Running script... [HRC] inst.$name = TMG12_EdgeCount [HRC] $assign = TIMG12 [HRC] $suggestSolution = Any peripheral = [&quot;$interface&quot;,&quot;$solution&quot;,&quot;$name&quot;,&quot;$assign&quot;,&quot;$assignAllowConflicts&quot;,&quot;$suggestSolution&quot;,&quot;ccp0Pin&quot;] $solution = undefined [HRC] inst.$name = TMG12_EdgeCount [HRC] $assign = TIMG12 [HRC] $suggestSolution = Any peripheral = [&quot;$interface&quot;,&quot;$solution&quot;,&quot;$name&quot;,&quot;$assign&quot;,&quot;$assignAllowConflicts&quot;,&quot;$suggestSolution&quot;,&quot;ccp0Pin&quot;] $solution = undefined [HRC] inst.$name = TMG12_EdgeCount [HRC] $assign = TIMG12 [HRC] $suggestSolution = Any peripheral = [&quot;$interface&quot;,&quot;$solution&quot;,&quot;$name&quot;,&quot;$assign&quot;,&quot;$assignAllowConflicts&quot;,&quot;$suggestSolution&quot;,&quot;ccp0Pin&quot;] $solution = undefined [HRC] inst.$name = TMG12_EdgeCount [HRC] $assign = TIMG12 [HRC] $suggestSolution = Any peripheral = [&quot;$interface&quot;,&quot;$solution&quot;,&quot;$name&quot;,&quot;$assign&quot;,&quot;$assignAllowConflicts&quot;,&quot;$suggestSolution&quot;,&quot;ccp0Pin&quot;] $solution = undefined Validating... [0]error: TMG12_EdgeCount(/ti/driverlib/COMPARE) timerPeriod: Valid number of edge is between [0,65535] === Based on the above, I think the following. (1) inst.$name, $assign, and $suggestSolution were TMG12_EdgeCount, TIMG12, and Any, respectively. (2) Although peripheral.$assign = &quot;TIMG12&quot; is specified in the .syscfg, inst.peripheral.$solution is undefined inside isHighResolutionCapable. As a result, the catch block returns false, and the 16-bit limit error (0 to 65535) occurs. (3) This empty state seems to persist inside validate as well. (4) It is still unclear why $solution is not populated (whether it is the solver’s execution order or the handling of $assign). BR, Satoshi Kawaguchihttps://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/6520299Sat, 24 Oct 2026 11:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fbd71732-d87a-4920-abbf-e558e043d285Samrat TikonePlease check my revised schematic, I have ensured decoupling capacitors and all pull ups on concerned lines,also on osc0 pin I have placed a jumper so that we can ground it when desired.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/6520152Fri, 23 Oct 2026 20:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:927c317d-19c3-405f-ae36-8e00e081f1d7KiThanks for trying. I has escalated this issue to engineering. Do you have any kind of security software like antivirus, etc running on that machine?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/6519546Fri, 23 Oct 2026 09:32:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:45850e99-dcab-460e-82ab-88bee716b7bbClemens KutzOkay, I tried --disable-gpu-sandbox now, no change. I still only see this blank splash screen and it never finishes loading.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691390/mspm33-sdk-state-of-emulated-eeprom-sector/6519232Fri, 23 Oct 2026 03:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3144dc07-650e-4af7-bedd-7497a6343045Ella TangHi Sebastien Le Diouris, 1. During Erase / Write Phase If a sector is physically damaged (e.g., endurance limit reached, charge trap failure), the Flash operation will fail or timeout. For example, when use erase / write function, they can return t he status of the current command , which can also be got from DL_FlashCTL_getCommandStatus() function. DL_FlashCTL_getFailureStatus() function can return the type of command failure. If it returns DL_FLASHCTL_FAIL_TYPE_VERIFY_ERROR , it means the hardware verification failed right after the write/erase, which strongly indicates a NOK sector. 2. During Read Phase If the data inside a sector is corrupted due to bit flips, reading it will trigger the hardware ECC DED (Double-Bit Error Detection) and enter NMI_Handler. We have an example in M33 SDK, which can be taken as a reference. examples/nortos/LP_MSPM33C321A/driverlib/flashctl_ecc_error_injection Hope this can help you. Thanks! Best Regards. Ella Tanghttps://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/6518953Thu, 22 Oct 2026 19:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:efdf94b0-04de-4eda-8839-d1259ffb8ec9KiCan you try --disable-gpu-sandbox instead?https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1691946/tms320vc33-need-code-composer-v4-10/6518833Thu, 22 Oct 2026 17:30:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:26770646-567c-42c5-8811-7dd77f1f19c1KiHello, Please start a E2E private conversation to discuss further with details regarding if you (or your) organization once had a license in the past. Thanks ki