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/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295997Fri, 03 Apr 2026 13:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2ba170e0-e630-4164-8ddb-94265d6dd426Matt KukuckaHello, I recommend checking out the Emulation/JTAG chapter in the datasheet, specifically: Best, Matthttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632413/am6442-am64x-evm-error-loading-out-file-to-r5f0_0-with-uniflash/6295969Fri, 03 Apr 2026 12:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:05a64731-b90a-4a10-85d5-19c5b45c41c0Jomy Paul P SHi Dinesh, I will test this on my setup and get back to you with an update. Regards, JOMYhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware/6295936Fri, 03 Apr 2026 10:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3ab62bf8-4c40-489d-8ae1-999b769d042fMadhav SoniThanks, this clarifies my confusion. I understand now that for TDA4APE-Q1 / J742S2 , the officially validated flow is CCS 12.4 , and in CCS the recommended board selection is J784S4_TDA4VH . I also understand that firmware can run correctly on TDA4APE-Q1 as long as I stay within the components actually present on TDA4APE.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632620/mspm0g3519-ccs-20-5-compiling-and-linking-paths-broken-despite-being-shown-correctly-in-explorer/6295897Fri, 03 Apr 2026 09:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f39dde47-ccee-4215-9693-cb19763da39dGary GaoSome of the file location path and name are changed in the latest SDK compared with the old ones. If you want to use the latest CCS and SDK, recommend to import an empty project and copy the source files and header files into the empty project. And modify the file path as needed when some error happen.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware/6295886Fri, 03 Apr 2026 08:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2cf01f6e-a754-44d0-8bba-41e34537d408Doredla Sudheer KumarHi, [quote userid=&quot;693083&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware&quot;]1. Is J784S4_TDA4VH the officially recommended board selection for TDA4APE-Q1 in CCS 12.4?[/quote] Yes. TDA4VH is superset for TDA4APE. You can also refer to CCS Setup details from TDA4APE SDK User Guide. https://software-dl.ti.com/jacinto7/esd/j742s2-processor-rtos-sdk/11_02_00_06/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j742s2.html [quote userid=&quot;693083&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware&quot;]2. Will firmware compiled for J784S4_TDA4VH run correctly on TDA4APE-Q1 hardware without any issues?[/quote] Yes as memory is still same but, there are few components removed in TDA4APE compared to TDA4VH. If you would like to test any of example from TI SDK, you can refer to SDK from below. www.ti.com/.../TDA4APE-Q1 [quote userid=&quot;693083&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware&quot;]3. Are there any TDA4APE-Q1-specific GEL files or linker command files that I should use instead of the J784S4_TDA4VH defaults?[/quote] Yes, you can use the file from the SDK. https://www.ti.com/tool/download/J742S2-PROCESSOR-RTOS-SDK [quote userid=&quot;693083&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware&quot;]4. Is CCS 20.x officially supported or validated with J742S2-PROCESSOR-RTOS-SDK v11.02.00.06?[/quote] No, official supported and validated CCS version with SDK is 12.4. [quote userid=&quot;693083&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmware&quot;]5. Are there any known issues or limitations when using CCS 20.x for bare-metal R5F firmware development on TDA4APE-Q1? 6. Will the J742S2 RTOS SDK makefiles and build scripts work correctly with CCS 20.x toolchain paths, or will path modifications be required?[/quote] CCS 20.x is not validated from the SDK team. Gel script in SDK may not be compatible to CCS 20.x Best Regards, Sudheerhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1633164/tda4ape-q1-ccs12-4-vs-ccs20-x-for-tda4ape-q1-j742s2-correct-board-selection-and-version-compatibility-for-r5f-bare-metal-firmwareFri, 03 Apr 2026 06:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5ae50535-4c5d-4660-8472-a8e850805866Madhav SoniPart Number: TDA4APE-Q1 Other Parts Discussed in Thread: TDA4VH Hi TI Team, I have a couple of important questions. I am developing bare-metal R5F firmware for TDA4APE-Q1 (J742S2 family) using J742S2-PROCESSOR-RTOS-SDK v11.02.00.06 on Windows 11. --- Setup --- CCS Version : 12.4.0.00007 SDK : J742S2-PROCESSOR-RTOS-SDK v11.02.00.06 Target Core : MCU_Cortex_R5_0_0 OS : Windows 11 --- Question 1: Correct Board Selection in CCS 12.4 --- In CCS 12.4, there is no dedicated TDA4APE-Q1 option in the New CCS Project wizard, so I selected J784S4_TDA4VH as a workaround. 1. Is J784S4_TDA4VH the officially recommended board selection for TDA4APE-Q1 in CCS 12.4? 2. Will firmware compiled for J784S4_TDA4VH run correctly on TDA4APE-Q1 hardware without any issues? 3. Are there any TDA4APE-Q1-specific GEL files or linker command files that I should use instead of the J784S4_TDA4VH defaults? --- Question 2: CCS 20.x Compatibility --- CCS 20.x has native TDA4APE-Q1 device support in the Project Wizard, which is cleaner than the J784S4_TDA4VH workaround in CCS 12.4. 4. Is CCS 20.x officially supported or validated with J742S2-PROCESSOR-RTOS-SDK v11.02.00.06? 5. Are there any known issues or limitations when using CCS 20.x for bare-metal R5F firmware development on TDA4APE-Q1? 6. Will the J742S2 RTOS SDK makefiles and build scripts work correctly with CCS 20.x toolchain paths, or will path modifications be required? Thank you for your support. Madhav SoniTDA4APE-Q1TDA4VHhttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295414Thu, 02 Apr 2026 21:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d5ebb8c0-498d-49a0-af72-df6af39fbc78Arun NHello Matt Kukucka , Thanks Matt. Unfortunately, I cannot share the schematic, but all the 5 pins are (TDI, TDO, TRST, TMS and TCK) are used. IS there anything that I need to crosscheck and I can let you know if that is the case?https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295331Thu, 02 Apr 2026 20:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ccb5c074-7c2c-41f3-a83b-1d2cda1fe327Matt KukuckaHello, I assumed so too, otherwise you wouldn&#39;t be able to connect in the first place . Can you also share your JTAG schematic? I want to confirm it obeys the datasheet&#39;s recommendations. Best, Matthttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295328Thu, 02 Apr 2026 20:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:75564bbf-1c77-4087-a983-67fdbe86473fArun NNo, I am using the XDS110 debugger, I tagged the wrong device, I assume so.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295273Thu, 02 Apr 2026 20:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9dcc0904-4dd4-4784-8076-7d3f636b6292Matt KukuckaHello, Are you using the XDS110-ISO debugger? If so, please note that it does not support 5-pin JTAG (with TRSTn) -- F2807x devices require TRSTn. [quote userid=&quot;686760&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295260&quot;]I will try that and update you. Do you think it is necessary to update the CCS version, or it could potentially cause this?[/quote] If the error doesn&#39;t occur all the time, it&#39;s most likely caused by something else (like external noise, possible application interference, etc.). Generally, we recommend users to use the latest drivers/CCS to rule out any issues that may have been resolved already. Best, Matthttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6295260Thu, 02 Apr 2026 19:55:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5f83c5a2-7110-42a6-a7df-65161969ae32Arun NThank you Matt Kukucka for the info. It is a custom board with C2000 family chip TMS320F2807x. It&#39;s not occurring all the time, but it&#39;s showing up when debugging over long time. I will try that and update you. Do you think it is necessary to update the CCS version, or it could potentially cause this? .https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1629526/ccstudio-theia-sysconfig-where-do-i-turn-off-warnings-ulp-info-during-compile-build/6295161Thu, 02 Apr 2026 18:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:266ba700-4395-4641-b3bd-3fa4db6220e6Steve Wenneryes this case can close...thank you!https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1629526/ccstudio-theia-sysconfig-where-do-i-turn-off-warnings-ulp-info-during-compile-build/6295108Thu, 02 Apr 2026 17:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:eda56bd4-dc89-4b9a-aabe-fc470490c596KiDid the suggestion I made earlier help? [quote userid=&quot;393571&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1629526/ccstudio-theia-sysconfig-where-do-i-turn-off-warnings-ulp-info-during-compile-build/6293477&quot;]I was getting mixed up with the other case Ihave open and not being able to jump to functions.[/quote] I also replied to that thread and mentioned a workaround. It seemed to help in my case. Thanks kihttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register/6294924Thu, 02 Apr 2026 15:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3c8e0c8f-251c-49d4-a135-ec1bf7089876Matt KukuckaHello, Which device are you encountering this issue on? Below is what we generally recommend for this error code: Source: https://www.ti.com/lit/an/spracf0/spracf0.pdf [quote userid=&quot;686760&quot; url=&quot;~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632137/xds110iso-evm-icepick_c_0-error-connecting-to-the-target-error--2131-0x0-unable-to-access-device-register&quot;]Version: 20.2.0.12__1.8.0[/quote] CCS is now at version 20.5. Please download the latest here: https://www.ti.com/tool/CCSTUDIO#downloads Best, Matthttps://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632620/mspm0g3519-ccs-20-5-compiling-and-linking-paths-broken-despite-being-shown-correctly-in-explorer/6294770Thu, 02 Apr 2026 14:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f78fa851-0f1c-493c-809f-30d2218e6331Ken AyreRetracing my steps and recreating &quot;shell project&quot;.... It is probably a complication that importing a demo forces roll back and reference to older tools. I can&#39;t unselect the Sysconfog and compiler installs or select newer versions already present (I did a total remove and re-install of all the most recent to avoid version conflicts)https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632413/am6442-am64x-evm-error-loading-out-file-to-r5f0_0-with-uniflash/6294769Thu, 02 Apr 2026 14:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f8bb91c8-0246-4336-a03e-abdcae4a33ecRavilla DineshHi Jomy, JTAG UniFlash is my requirement. https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/latest/exports/docs/api_guide_am64x/EXAMPLES_DRIVERS_SBL_JTAG_UNIFLASH.html -&gt; refered this. On CCS debug option the console prints are visible in CCS window, But while doing ospi flashing process we are not getting any terminal prints and don&#39;t know how to validate. JTAG Uniflash Menu -&gt; sbl_ospi_linux.release.hs_fs.tiimage boot from OSPI. JTAG Uniflash Menu -&gt; benchmark_demo_am64x-evm.appimage user build application. [FLASH WRITER] Application exited !!! All tests have passed!! After flashing powered off the board and changed the boot switches to OSPI boot and powering on the board. But image booting is not happening. baud rate - 115200 Thanks &amp; Regards, Ravilla Dinesh.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632926/msp430-flasher-code-composer-issue-with-msp430g2553Thu, 02 Apr 2026 13:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:dcfd76e1-cfa2-4f88-9983-e0bc97236cf5Luigi QuagliaPart Number: MSP430-FLASHER Other Parts Discussed in Thread: CCSTUDIO , MSP430G2553 , MSP430FR2476 Hi, Following the suggestion from my previous request, I have downloaded and installed the latest version of Code Composer Studio. Here are the version details: Version: 20.5.0.28__1.11.0 Default VS Code API: 1.102.3 Extensions: Includes @ccs/ccstudio 20.5.0, @theia/ai-anthropic, and others (full list provided below). Using this version (as well as previous ones) with the MSP430G2553 , I am experiencing an issue during the debug phase: whenever the processor hits a breakpoint, it resets. To prevent this, I am currently forced to disable the Watchdog Timer (WDT) during emulation. This is very inconvenient and prevents me from performing a comprehensive debug of the application. I previously used the Eclipse-based Code Composer Studio (up to version 10) without any issues. I have also used this device for many years with IAR Embedded Workbench and never encountered this problem; it has only started appearing with the recent versions of CCS. Please note that my program is developed entirely in Assembly . I have also experienced the same issue with the MSP430FR2476 . I am attaching the debug configuration file from my current CCS setup. Is there a specific setting I can use to prevent the Watchdog from resetting the device during a breakpoint without having to manually disable it in the code? Best Regards Luigimsp430g2553CCSTUDIOmsp430-flasherMSP430FR2476https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1632620/mspm0g3519-ccs-20-5-compiling-and-linking-paths-broken-despite-being-shown-correctly-in-explorer/6294644Thu, 02 Apr 2026 12:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:da77d81e-46ca-494b-ba81-a3f6d63e904cKiIt is likely the device change and/or SDK version change. It looks like an issue with include search paths. I will bring this thread to the attention of the device/SDK experts for further assistance.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1631107/am2434-am2434-data-abort-on-ldrexd-during-64-bit-atomic-write-to-shared-msram/6294233Thu, 02 Apr 2026 06:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:621c33b3-e505-4fa0-b9aa-249a676c1466Meet ThakarHi Eli, I tested this at my end, and I was able to reproduce this at my end. So it seems like AM2434 interconnect/AXI bus does not support the Global Exclusive Monitor, so only the local exclusive monitor for Cortex-R5 core is available for am243. As the local monitor is present on the R5 core, these ldrexd and strexd instructions will be valid for R5 internal memories like TCM and caches but not for MSRAM. You can utilize the Spinlock module for this as well: https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/11_02_00_24/exports/docs/api_guide_am243x/DRIVERS_SPINLOCK_PAGE.html Best Regards, Meet.https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1629568/ccstudio-theia-intellisense-----can-t-find-functions/6293583Wed, 01 Apr 2026 20:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8ef7d20f-2e14-48f4-8aa7-278d9e20b840KiEngineering has found a workaround in the meantime. Please see the workaround section of the above link.