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/1667336/am263p4-doubt-regarding-variables-getting-updated-live-without-pausing-the-debugger/6428903Fri, 24 Jul 2026 22:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e367383e-8279-4322-851f-6576904a4cc4FleenorHi Rishabh, Yes, this is possible by opening the &quot;Threads&quot; dropdown in the debug panel, right click any of the cores and select &quot;Show All Cores&quot;. Start the code execution on the Cortex_R5_0 core, then connect to the CS_DAP_0 core to view the variables in real time without needing to pause/suspend the R5 core executing the code. You also need to make sure the &quot;Continuous Refresh&quot; function is turned on in the Watch dropdown: The CS_DAP &quot;Debug Access Port&quot; provides access to view the variable values instead of relying on the CPU core to read the values which requires the code to be paused as you&#39;ve noticed. Please try this out and let us know if this solution works for you. Best Regards, Zackary Fleenorhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667377/tmdsemu200-u-error-2131/6428807Fri, 24 Jul 2026 20:30:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6c9634b6-42df-437e-a9df-e243b667bbd1AJ FavelaHi, Can you confirm which device you are attempting to connect to? Kind regards, AJ Favelahttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1665838/tmdsemu110-u-tmdsemu110-u-nonfunctional/6428397Fri, 24 Jul 2026 14:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f2668ff8-866f-4191-91f1-3e351101cff9FleenorHi Saad, Yes, this information does help. However, getting more information about the setup will help us with further debug. If you could provide answers for the questions below, we can continue to move forward towards a resolution. If you check, &quot;Apple menu → About This Mac → System Report…&quot; does the probe populate on the list of connected hardware? What version of Code Composer Studio are you running? What versions of the XDS FW are running on both debug probe devices? When the error occurs, does UniFlash recognize and detect the XDS110 probe, or does it fail to detect it altogether? Best Regards, Zackary Fleenorhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667377/tmdsemu200-u-error-2131Fri, 24 Jul 2026 11:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1496ce25-1f73-4ef5-b16e-76d2710981e9M R TyagiPart Number: TMDSEMU200-U Theese is an Error -2131 (Unable to access device register) which indicate that Code Composer Studio (CCS) is communicating successfully with the XDS200 debugger, but the debugger cannot establish a stable connection with the target chip on your card.TMDSEMU200-UAerospace &amp; Defensehttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667045/mspm33-sdk-mcan-module-and-filters/6428124Fri, 24 Jul 2026 10:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d79bb389-b6ff-47a4-8852-fc6d74552dbdXiaodong LIHi Sebastien Le Diour I will check in detailed and reply to you in the next week Thankshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1662719/mspm33-sdk-eeprom-management/6428110Fri, 24 Jul 2026 10:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:aa4e6e7b-b06f-4bea-9634-e448cc6175dbSebastien Le DiourisHello Xiaodong, I integrated your remarks, and unfortunatly, same result [13]warning #10247-D: creating output section &quot;.text&quot; without a SECTIONS specification [14]warning #10247-D: creating output section &quot;.data&quot; without a SECTIONS specification [15]warning #10247-D: creating output section &quot;.bss&quot; without a SECTIONS specification [16]warning #10247-D: creating output section &quot;.cinit&quot; without a SECTIONS specification [17]warning #10247-D: creating output section &quot;.rodata&quot; without a SECTIONS specification [18]warning #10247-D: creating output section &quot;.intvecs&quot; without a SECTIONS specification [19]warning #10247-D: creating output section &quot;.stack&quot; without a SECTIONS specification [20]warning #10210-D: creating &quot;.stack&quot; section with default size of 0x800; use the -stack option to change the default size Thankshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667336/am263p4-doubt-regarding-variables-getting-updated-live-without-pausing-the-debuggerFri, 24 Jul 2026 09:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:be804b42-a3d6-4bdc-9f26-43a777dd8ca0Rishabh Kumar BhaktaPart Number: AM263P4 Hi ti team is there any way can i watch my global values being updated in real time instead of pausing it to watch the latest value. I am using the ccs 20.4.1 versionAM263P4https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667045/mspm33-sdk-mcan-module-and-filters/6428073Fri, 24 Jul 2026 09:23:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a6da8523-ed41-4f7a-9298-cad489b79f2eSebastien Le DiourisHello Xiaodong, thanks for all these presicions Regarding the filters adding, do you mean I have to add this: before: static const DL_MCAN_StdMsgIDFilterElement gMCAN0StdFiltelem = { .sfec = 0x1, .sft = 0x1, .sfid1 = 4, .sfid2 = 2024, }; after: static const DL_MCAN_StdMsgIDFilterElement gMCAN0StdFiltelem = { .sfec = 0x1, .sft = 0x1, .sfid1 = 3, .sfid2 = 4, .sfid 3 = 45, .sfid 4 = 2024, ... .sfid X = YYYY, }; other structures shall be updated ? Thankshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1662719/mspm33-sdk-eeprom-management/6428070Fri, 24 Jul 2026 09:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ed544876-03d7-4ee4-8296-ebdf360a5537Xiaodong LIHi Sebastien Le Diour The linker is generating these warnings because of a subtle syntax issue in your SECTIONS block: the empty curly braces {} . In the TI Linker command language, adding empty braces tells the linker: &quot;Create this section, but place absolutely nothing inside it.&quot; Because of this, the actual code and data compiled from your files (like .text from main.c ) cannot fit into your defined sections. The linker is forced to ignore your directives, create its own default sections from scratch, and throw the #10247-D warnings. How to Fix It 1. Remove the empty curly braces {} For standard sections, you should either remove the braces completely or use the correct syntax to inherit input sections. Omitting the braces completely is the cleanest way. 2. Fix the Stack option syntax The warning #10210-D indicates that --stack_size=256 wasn&#39;t recognized by your specific toolchain version. It expects -stack or --stack . Corrected Linker Script Here is the corrected version of your linker script. It removes the empty braces and fixes the alignment/stack configuration: -uinterruptVectors --stack=256 /* Fixed: Changed from --stack_size to --stack */ MEMORY { FLASH (RX) : origin = 0x10000000, length = 0x000FFFFF SRAM (RWX) : origin = 0x30000000, length = 0x0003FFFF DATA_FLASH (RW) : origin = 0x80000000, length = 0x00008000 /* 32KB high-endurance region */ BCR_CONFIG (R) : origin = 0x80101800, length = 0x000003FF BSL_CONFIG (R) : origin = 0x80101C00, length = 0x000003FF } SECTIONS { /* Removed {} from all standard allocations */ .intvecs : palign(16) &gt; 0x10000000 .text : palign(16) &gt; FLASH .const : palign(16) &gt; FLASH .cinit : palign(16) &gt; FLASH .pinit : palign(16) &gt; FLASH .rodata : palign(16) &gt; FLASH .ARM.exidx : palign(16) &gt; FLASH .init_array : palign(16) &gt; FLASH .binit : palign(16) &gt; FLASH /* TI Ramfunc configuration */ .TI.ramfunc : load = FLASH, palign(16), run = SRAM, table(BINIT) /* EEPROM Emulation Emptiness flag NOLOAD is correct without braces */ .eeprom_section : &gt; DATA_FLASH, type = NOLOAD .vtable : &gt; SRAM .args : &gt; SRAM .data : &gt; SRAM .bss : &gt; SRAM .sysmem : &gt; SRAM .stack : &gt; SRAM (HIGH) .BCRConfig : &gt; BCR_CONFIG .BSLConfig : &gt; BSL_CONFIG .DataBank : palign(16) &gt; DATA_FLASH } Why this works: .text : palign(16) &gt; FLASH : This tells the linker to gather all .text input sections from your compiled object files, align them to a 16-byte boundary, and place them into FLASH . --stack=256 : Matches the exact option the linker was looking for, which will resolve the final warning and properly restrict your stack size to 256 bytes. Clean your project and try rebuilding it. Let me know if you encounter any new compilation errors or if your EEPROM variables aren&#39;t mapping to .eeprom_section properly! Thanks!https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1662719/mspm33-sdk-eeprom-management/6428022Fri, 24 Jul 2026 08:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c593d300-204e-4291-ada7-5a894e5b1edbSebastien Le DiourisHello, any news ? Thankshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667045/mspm33-sdk-mcan-module-and-filters/6427920Fri, 24 Jul 2026 06:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:480a883e-421b-47a0-ac31-699aa8875394Xiaodong LIThe warning message explains that the SysConfig interface currently only supports setting up one hardware filter element directly in the GUI. If you change the input number, SysConfig will alert you that it cannot auto-generate code for additional elements refer to: MSPM33C321A: MSPM33 configuration support needed How to Add More Filters To filter for more than two IDs, you must bypass the GUI constraints and implement them directly in your user application code during peripheral initialization: Calculate and Allocate Enough Message RAM : In the SysConfig interface, ensure your Message RAM Configuration allocates a large enough memory block for your maximum filter count. Each standard ID filter element requires 1 word (4 bytes) of Message RAM. For example, if you plan to use 8 filters in code, make sure your total filter elements memory allocation spans at least 32 bytes. Add Filters in Your Code : Open your application initialization source file (usually where your CAN setup functions run right after Board_init() ). Manually populate the additional filter structures using your SDK driver APIs (such as DL_MCAN_setStdMsgFilterElement for MSPM0 or similar functions depending on your specific TI MCU). Write these extra elements directly into the Message RAM offsets sequential to your first GUI-configured filter. Current GUI Setup Breakdown Filter Element Configuration : It is set to route matched frames directly to Rx FIFO 0 . Filter Type : You have selected Dual ID filter for SFID1 or SFID2 . This specific type uses a single filter element slot but lets you match exactly two distinct IDs ( 3 or 4 ). Any message with standard identifier 0x03 or 0x04 will pass through to your FIFO.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1660320/mspm33-sdk-adc-management-and-assigned-pin/6426872Thu, 23 Jul 2026 14:16:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ddf1fb08-132a-4599-9b29-7c40e3f06c25Erik VaughnI&#39;m glad it works now! I&#39;ll go ahead and close out this thread.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1665838/tmdsemu110-u-tmdsemu110-u-nonfunctional/6426846Thu, 23 Jul 2026 13:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b614c256-9afa-445a-b7e9-9d62f6c26f84Saad Thabit49Hi Zackary, Thank you for your response. To save everyone time, we had purchased two units. One of them works perfectly, while the other does not function at all. Both units are being tested on the same system and laptop, using the exact same versions and setup by the same person. Given this, it appears the issue is isolated to the specific hardware unit rather than the system configuration or software. I hope this makes sense, let me know if you have other questions.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1660320/mspm33-sdk-adc-management-and-assigned-pin/6426809Thu, 23 Jul 2026 13:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a7d5efb4-e649-4537-9a1b-42d9ee7b5ebbSebastien Le DiourisHello Erik, sorry for the delay of my response, but sorry no, because now it workshttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1667045/mspm33-sdk-mcan-module-and-filtersThu, 23 Jul 2026 13:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6d70342b-4fd9-43a8-90a6-94ba9d76c885Sebastien Le DiourisPart Number: MSPM33-SDK Other Parts Discussed in Thread: MSPM33C321A , SYSCONFIG Hello, I am working on MSPM33C321A eval board, especially on MCAN module. I have several messages to monitor but I see the .syscfg file, limits the number of filters at 2 only: Here, only message with ID 3 and 4 will be filtered. How can I do to add filters (means more messages which can monitor) ? ThanksMSPM33C321AMSPM33-SDKSYSCONFIGhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1666386/uniflash-uniflash-9-6-ccs-debugserver-dslite-fails-with-boost-filesystem-create_directories-when-windows-username-contains-non-ascii-characters/6425782Wed, 22 Jul 2026 18:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0e4f05dd-7306-45ca-af3d-33a13d2913b3KiHello, Can you try enabling the Windows option to Unicode UTF-8 support as mentioned in this FAQ: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_faqs.html#are-non-alphanumeric-unicode-characters-supported Thanks kihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1665964/codecomposer-where-should-gitignore-go/6425357Wed, 22 Jul 2026 14:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b7c4677e-7bd1-4875-a77e-dc82689f435fKeith BarkleyThanks, I had accidentally saved it in the project directory, I just copied the .gitignore I had into the root of the workspace and it worked.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1666494/am6442-r5-core-global-variable-view-refresh-in-debug-mode/6424993Wed, 22 Jul 2026 08:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:84cb2a38-f020-4e12-b267-c361e6d7a1efTushar ThakurHi Bhaskar, Please try the steps mentioned at RE: AM2432: Unable to View Global Variables While Debugging AM2432 Chip with CCS in Windows Environment Regards, Tusharhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1666494/am6442-r5-core-global-variable-view-refresh-in-debug-modeWed, 22 Jul 2026 07:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:955bf737-80be-49dd-8196-6df6c6c4e93cBhaskar ReddyPart Number: AM6442 Further to below link, is there any update in CCS that makes the viewing of global expressions added to watch window or memory window refresh continuosly. https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1313986/tmds64evm-am6442 As of now, I need to halt manually or with a breakpoint to be able to see the value in global expression or memory.power deliveryAM6442https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1666386/uniflash-uniflash-9-6-ccs-debugserver-dslite-fails-with-boost-filesystem-create_directories-when-windows-username-contains-non-ascii-charactersWed, 22 Jul 2026 00:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8d0f2159-013b-4012-a06c-5b7e0dec82bf승현 박Part Number: UNIFLASH Other Parts Discussed in Thread: TMS320F280039C Environment OS: Windows 11 Pro (64-bit) User account: Windows username contains Korean (non-ASCII) characters UniFlash: 9.6.0.5764 CCS: Latest CCS (same issue) Device: TMS320F280039C Emulator: XDS110 (or your actual emulator) I cannot use either CCS or UniFlash to connect to or program my F280039C device. Both CCS and UniFlash fail before attempting to connect to the target. The problem appears to occur inside DebugServer (DSLite). [ Error ] Version: 9.6.0.5764 Executing the following command: &gt; &quot;...DebugServer\bin\DSLite&quot; flash flash --config ... --list-cores boost::filesystem::create_directories: [system:123]: &quot;C:\Users\?\ti&quot;, &quot;C:\Users\?&quot; If this continues, please run fsclean or set TI_APPDATA_DIR to directory you have permissions to access The Korean username is displayed as &quot;?&quot;. It appears DebugServer cannot create its working directory because the Windows user profile contains non-ASCII characters. I verified that: DSLite itself launches correctly. The .ccxml file is valid. The project path contains only ASCII characters. The error occurs before any JTAG connection. The same problem occurs in CCS and UniFlash. I also tried all of the following environment variables: TI_APPDATA_DIR USERPROFILE HOME TEMP TMP HOMEDRIVE HOMEPATH But, The error remains exactly the same. *Questions* Is this a known limitation or bug in UniFlash 9.6 / DebugServer? Is there any workaround without creating a new Windows account that has an ASCII-only username? Is there a newer DebugServer or patch that correctly supports Unicode Windows usernames? Why does TI_APPDATA_DIR appear to be ignored? Thank you.UniFlashTMS320F280039C