Code Composer Studio forum - Recent Threads

TMS320VC5509A: Programming Instructions

Nandith R — Mon, 13 Apr 2026 07:19:14 GMT

Part Number: TMS320VC5509A

Hi,
I'm working on a project involving the TMS320VC5509A microcontroller along with BlackHawUSB100v2 debugger. I tried to flash the code to the hardware by selecting Run -> Load{} from Code Composer Studio version_6.1.3. But did not find the code programmed. So could you please guide me through the instructions on how to flash a code to it.

RE: TMS320VC5509A: Programming Instructions

Nandith R — Tue, 28 Apr 2026 09:44:52 GMT

Hi Ming,

Thank you for sharing the document link. It will definitely help me understand the booting methodology and how to implement it.

However, my current requirement is to program my application into the external flash (part number: AT45DB642). Could you please guide me on the procedure for writing the application to this external flash? It would also be very helpful if you could share any sample code for the same.

Best regards,
Nandith R

AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

Ravilla Dinesh — Tue, 21 Apr 2026 16:21:51 GMT

Part Number: AM6442

Hi TI Team,

I am working on an AM64x-based custom board using RT- Linux SDK, and I have a question regarding ePWM configuration, pin availability, and EHRPWM_SOCA usage.

In the SoC-level DTSI (main dtsi), I see that ePWM instances EPWM0 to EPWM8 are defined and enabled. When I tested the same software on the TI EVM board, I was able to configure and run the ePWM modules successfully.

However, on my custom board, only a limited number of pins are routed out, and no EPWM0 to EPWM8 pins are physically available.

My requirement is as follows:

I need to use EHRPWM_SOCA.
The signal frequency requirement is ~40 MHz
I initially expected to drive this as a pin signal, similar to EPWM outputs

custom board pins:

TRM AM64x Sitara™ Processors :

Can we use EHRPWM_SOCA to drive a 40 MHz external signal?

Thanks & Regards,
Ravilla Dinesh.

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

Vinuchandran A V — Tue, 28 Apr 2026 08:26:34 GMT

Hi Ravilla,

I assume you are still not getting the required frequency.

Can you please let me know how did you arrive on the device 119?

After looking into this in deep, it will be difficult to generate 40Mhz using SYSCLKOUT0. You can generate either 50Mhz or 25Mhz with it.

SYSCLKOUT0 not very flexible, if you need to generate 40 Mhz, you'll have to reprogram MAIN_0 PLL HSDIV4 Divider, which is unlikely, as it will affect the other peripherals which are using it.

And you'll have to use either one of the following parent clock.

123 (DEV_BOARD0_CLKOUT0_IN): The input muxed clock.
124 (_PARENT_HSDIV4_16FFT_MAIN_0_HSDIVOUT4_CLK5): Parent option 1.
125 (_PARENT_HSDIV4_16FFT_MAIN_0_HSDIVOUT4_CLK10): Parent option 2.

The best option to generate 40Mhz is using the ePWM itself, if you have access to any one of the 18 configurable ePWM pins.

Your next best bet will be to use TIMER_IO4 on C17. But since the internal functional clock is 250Mhz, there is no integer divisor which can perfectly yield 80Mhz (timer needs to toggle at 80Mhz: one for rising edge and one for falling edge)

Also, unlike CLKOUT0 (which outputs a clock as soon as the clock framework enables it), a DMTimer must be explicitly started by software. For more information, refer: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/DM-Timer.html

Regards,
Vinu

TMS320F2809: DSP/BIOS project fails to build in CCS 6.x, CCS 7.x, CCS 12.x

Tejal Gaikwad — Tue, 28 Apr 2026 08:02:28 GMT

Part Number: TMS320F2809

Hello,
I am trying to build a legacy C2000 DSP/BIOS project that was originally developed and built using CCS 3.0. I am now attempting to build the same project in Code Composer Studio (CCS) 6.0 and CCS 7.0 , but I am encountering multiple compilation errors related to bios_5_41_10_36 in standard TI header files.

AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

Ravilla Dinesh — Mon, 27 Apr 2026 13:48:38 GMT

Part Number: AM6442

Hi Team,

Board: custom board (am6442)
I am attempting to initialize an AM64x EVM using Code Composer Studio 12.8.1 and an XDS200 USB Debug Probe. The board is failing during the execution of the load_dmsc_hsfs.js script.

MAIN_Cortex_R5_0_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x40: (Error -1065 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 20.0.0.3178)
MAIN_Cortex_R5_0_0: File Loader: Verification failed: Target failed to write 0x00000000
MAIN_Cortex_R5_0_0: GEL: File: /home/asmgen2/ti/mcu_plus_sdk_am64x_10_01_00_32/tools/ccs_load/am64x/sciclient_ccs_init.release.out: Load failed.

Thanks & regards,
Ravilla Dinesh.

RE: AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

Tushar Thakur — Tue, 28 Apr 2026 04:04:48 GMT

The version of SDK you are using seems to be older. The latest version of the SDK is v12.00. The issue is already been fixed in newer versions of SDK.

Please refer https://www.ti.com/tool/download/MCU-PLUS-SDK-AM64X/12.00.00.27

RE: AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

Tushar Thakur — Tue, 28 Apr 2026 04:02:14 GMT

Hi,

Please try the steps mentioned in the AM6442: AM64 SoC Initialization Using CCS Scripting, does not work on EVM and custom board thread.

Also refer https://sir.ext.ti.com/jira/browse/EXT_SITMPUSW-18.

Regards,

Tushar

TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

yun long — Mon, 27 Apr 2026 14:43:18 GMT

Part Number: TMS320F2800156-Q1

Dear Expert,

I am using CCS 12.8.1 and Sysconfig 1.27 to develop TMS320F2800156 codes. When I compiled the progroam, I encountered an issue where the compiler could not find 280015x_codestartbranch.obj. As following:

line 29: error #10008-D: cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

Actually, the Sysconfig has automaticly included the Reference Source about f280015x_codestartbranch.asm file.

And when the project is compiled, the f280015x_codestartbranch.obj file is automaticly generated under Debug_F28200156 folder. Why the linker find the f280015x_codestartbranch.obj from device_F2800156, I didn't configurate any setting about using this folder for linking path.

I tried to add the the f280015x_codestartbranch.obj to the linking path,but still failed.

And I moved the f280015x_codestartbranch.obj file to /device_F2800156/ folder, works properly. But I couldn't rebuild.

I checked the .mk file. As following:

I found that the automatically generated makefile in subdir_vars.mk is incorrect, which leads to compilation and linking errors. By default, the system uses 280015x_codestartbranch.obj generated from the Referenced Source under the SysConfig directory, which results in an incorrect file path. I would like to know how to remove the Referenced Source under the SysConfig directory, or how to configure the compiler options so that the object file is generated in the correct path.

method 1

I want to remove the Referenced Source under the SysConfig directory to prevent it from generating file, and use local file.

method 2

I don't know why the compiler and linker not work properly. The link path is as following:

Please let me know how to solve this issue, Project file and make file is as follow :mk_file.zip

RE: TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

yun long — Tue, 28 Apr 2026 01:14:22 GMT

Hi Fleenor,

Thanks for your kind help. Actually, I am using C2000Ware 6.0.1, and TI C2000-CGT (Compiler) v22.6.2 LTS.

I tried all the methods you suggested, but none of them worked. In Sysconfig I counldn't find any option to remove/disable it so SysConfig no longer auto-generates this file. It is default configuration in version of 1.27.

Method3: I add the actual directory where f280015x_codestartbranch.obj is generated (e.g., ${BuildDirectory}) to the linker search path. It still doesn't work properly. It reports the error:

line 30: error #10008-D: cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

I think the main reason is that the system‑automatically generated compile and link paths are incorrect when a SysConfig file is added. How can I modify the system‑generated compilation paths. And we have no control over modifying the configuration inside SysConfig.

Just now, I discovered the root cause of the issue: the SysConfig file must be placed in the project root directory and cannot be located in any subfolder. If it is placed in any subfolder, the referenced paths will be incorrect.

I believe there is a design issue with TI’s approach, as the location of the SysConfig file impacts system file references.

If the source files in my project remain unchanged, but the driver files target two different devices—such as F280045 and F2800156—I would like to organize the system configuration (SysConfig) files by placing them into their respective folders. However, this causes build errors during compilation. This behavior appears to be a bug, and there is no documentation or warning that explains this limitation.

In addition, I found that when using two different devices, CCS does not automatically switch the compiler’s Variant and Core. When I switch between the two SysConfig files via different build configurations, I still need to manually use the “Switch Device” function inside SysConfig. Is there any other method available? I would like this device switching to be handled automatically through Build Configurations only, without relying on the SysConfig switch.

Recently, during extensive use of SysConfig, I have encountered multiple issues. These issues suggest that the tool may require further validation and refinement. They have significantly impacted development efficiency, and our ability to adjust the configuration is quite limited. Thank you for your help.

AM3357: CCS UniFlash v3.4.1 Compatibility Issue with U-Boot

Pooja Nagda — Mon, 13 Apr 2026 12:30:10 GMT

Part Number: AM3357

Hello,

We are currently using CCS UniFlash v3.4.1 for flashing AM3357.

After upgrading to a newer U-Boot version (u-boot-restore v2025.01), an issue has been observed where the RNDIS interface initializes successfully, but the BOOTP handshake does not complete. As a result, the flashing process does not start. The BOOTP handshake occurs after the ROM bootloader (ROM BL) has executed SPL.

A minimal U-Boot defconfig is being used, based on the new Driver Model (DM), replacing the legacy USB/ETH stack which is being phased out in U-Boot.

Here is the full defconfig:

CONFIG_ARM=y
CONFIG_ARCH_CPU_INIT=y
CONFIG_ARCH_OMAP2PLUS=y
CONFIG_TI_COMMON_CMD_OPTIONS=y
CONFIG_DEFAULT_DEVICE_TREE="am335x-sml-factory"
CONFIG_AM33XX=y
CONFIG_TARGET_AM335X_IEC61850_MODULE=y
# CONFIG_SPL_MMC is not set
CONFIG_SPL_DRIVERS_MISC=y
CONFIG_SYS_BOOTCOUNT_ADDR=0x80001000
CONFIG_SPL=y
CONFIG_TIMESTAMP=y
CONFIG_DISTRO_DEFAULTS=y
CONFIG_OF_BOARD_SETUP=y
CONFIG_BOOTCOMMAND="run findfdt; run init_console; setenv autoload no; bootp; if tftp ${scriptaddr} debrick.scr; then source ${scriptaddr}; fi"
CONFIG_LOGLEVEL=7
# CONFIG_SYS_CONSOLE_INFO_QUIET is not set
CONFIG_ARCH_MISC_INIT=y
CONFIG_SPL_SHOW_ERRORS=y
CONFIG_SPL_SYS_MALLOC=y
CONFIG_SPL_SYS_MALLOC_SIZE=0x800000
CONFIG_SPL_DISPLAY_PRINT=y
CONFIG_SPL_ETH=y
# CONFIG_SPL_FS_EXT4 is not set
# CONFIG_SPL_I2C is not set
CONFIG_SPL_MUSB_NEW=y
# CONFIG_SPL_NAND_SUPPORT is not set
CONFIG_SPL_NET=y
CONFIG_SPL_NET_VCI_STRING="AM335x U-Boot SPL"
# CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC is not set
CONFIG_CMD_SPL=y
# CONFIG_CMD_I2C is not set
# CONFIG_CMD_SETEXPR is not set
CONFIG_BOOTP_DNS2=y
CONFIG_CMD_MTDPARTS=y
# CONFIG_SPL_EFI_PARTITION is not set
CONFIG_OF_CONTROL=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
CONFIG_VERSION_VARIABLE=y
CONFIG_NET_RETRY_COUNT=10
CONFIG_BOOTP_SEND_HOSTNAME=y
CONFIG_SPL_OF_TRANSLATE=y
CONFIG_SPL_TI_SYSC=y
CONFIG_BOOTCOUNT_LIMIT=y
CONFIG_BOOTCOUNT_GENERIC=y
CONFIG_CLK=y
CONFIG_SPL_CLK=y
CONFIG_CLK_TI_CTRL=y
CONFIG_DFU_TFTP=y
CONFIG_DFU_RAM=y
CONFIG_USB_FUNCTION_FASTBOOT=y
# CONFIG_I2C is not set
CONFIG_MISC=y
# CONFIG_MMC_HW_PARTITIONING is not set
CONFIG_MTD=y
CONFIG_PHY_MICREL=y
CONFIG_PHY_MICREL_KSZ8XXX=y
CONFIG_MII=y
CONFIG_DRIVER_TI_CPSW=y
CONFIG_TIMER=y
CONFIG_OMAP_TIMER=y
CONFIG_USB=y
CONFIG_DM_USB_GADGET=y
CONFIG_SPL_DM_USB_GADGET=y
CONFIG_USB_MUSB_HOST=y
CONFIG_USB_MUSB_GADGET=y
CONFIG_USB_MUSB_TI=y
CONFIG_USB_GADGET=y
CONFIG_SPL_USB_GADGET=y
CONFIG_USB_GADGET_MANUFACTURER="Texas Instruments"
CONFIG_USB_GADGET_VENDOR_NUM=0x0451
CONFIG_USB_GADGET_PRODUCT_NUM=0xd022
CONFIG_USB_ETHER=y
CONFIG_SPL_USB_ETHER=y
CONFIG_WDT=y
# CONFIG_SPL_WDT is not set
CONFIG_DYNAMIC_CRC_TABLE=y
CONFIG_RSA=y
CONFIG_LZO=y

It works with our own Linux only manufactory script. But the Windows CCS Uniflash does not work anymore.

For reference, Linux manufacturing logs, kernel dmesg output, and a full tcpdump network capture have been attached for comparison.

SML-MFG-Linux.dmesg.log

SML-MFG-Linux.log

ROM_SPL_UBOOT_LINUX_Capture.zip

Regards,

Pooja Nagda

RE: AM3357: CCS UniFlash v3.4.1 Compatibility Issue with U-Boot

Bin Liu — Mon, 27 Apr 2026 23:35:43 GMT

Hi, I will review your update once I am back in office.

RE: TMS320F280037C: TMS320F280037C .syscfg file

Matt Kukucka — Mon, 27 Apr 2026 20:20:08 GMT

But if you're just programming boot configurations, then Z2 boot configs takes priority over Z1 in the Boot ROM.

Best,
Matt

TMS320F280037C: TMS320F280037C .syscfg file

Jonathan Gregory — Mon, 27 Apr 2026 18:38:01 GMT

Part Number: TMS320F280037C

Hello! I am trying to use the .syscfg file in Code Composer Studio to force my microcontroller to boot from FLASH, regardless of the GPIO select pins.

I have two TI microcontrollers, the TMS320F280037C (stand alone) and the TMS320F280039C (on a launchpad board). I have the same workspace I am trying to upload to both units (minus the different linker files and Targetconfig files). I am using the same .syscfg file because the device seelction appears to include both devices. See below.

I am using the DCSM portion of the .syscfg file to attempt the boot from FLASH setting. See image below.

I am able to acheive the desired result on the TMS320F280039C using these settings. Once I restart the device, my program runs without having to re-upload the code as desired.

However, on the TMS320F280037C, I get this error below when flashing the code, even with a successful build.

I also am making sure I have the same information in the linker (.cmd) file. The .text in the FLASH is starting at BANK0_SEC0, just like for the TMS320F280039C, where it works fine.

Lastly, when I uncheck the DCSM portion of the .syscfg file, the code does flash to the TMS320F280037C, although not the desired boot from FLASH functionality.

So at this point, I beleive I have narrowed it down to the .syscfg file accessing memory that exists in for the TMS320F280039C, but not the TMS320F280037C; however, I am not able to find anything in the data sheets about what is going on.

Can you please point me in the right direction? Thank you!

RE: TMS320F280037C: TMS320F280037C .syscfg file

Matt Kukucka — Mon, 27 Apr 2026 20:18:58 GMT

Hello,

That depends on what you already configured in Z1. Z2 cannot access memory regions secured by Z1 and vice versa. When a memory region is secured by a zone, it becomes inaccessible via JTAG or any code running from memory not allocated to the same zone. Data reads or writes in these secure memory regions are permitted only by code secured by the same zone. If a memory region is secured by Z1, only code executing from Z1 can access it (read/write).

Best,
Matt

RE: TMS320F280037C: TMS320F280037C .syscfg file

Jonathan Gregory — Mon, 27 Apr 2026 19:52:10 GMT

Ohh, that is more involved than I initially thought. What I just did was uncheck the "Configure this Section" in ZONE 1 and copied those same settings for ZONE 2. This worked; the code compiled and flashed to the device with no errors. And now the code runs on start up. Does what I did make sense? There are no issues with that strategy right?

RE: TMS320F280037C: TMS320F280037C .syscfg file

Matt Kukucka — Mon, 27 Apr 2026 19:45:13 GMT

Hi Jonathan,

[quote userid="696922" url="~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1640797/tms320f280037c-tms320f280037c-syscfg-file/6325083"]This is why I am getting that error. To confirm, will using ZONE 2 override what got configured in ZONE 1?[/quote]

This is not true; the security mechanisms for both the zones are identical, but independent. The intention is that a third-party would be able to secure their code on the device in a distinct zone.

If Z1 of the DCSM is already secured (with CSMPSWDs) on the F280037C device, then you won't be able to re-program the Z1 DCSM region (0x78000 - 0x781FF) unless you unlock the CSM for Z1 beforehand. Once Z1 is unlocked, you can decrement the link pointer to use a different zone select block (ZSB) with new CSMPSWDs and secure regions defined.

Best,
Matt

RE: TMS320F280037C: TMS320F280037C .syscfg file

Jonathan Gregory — Mon, 27 Apr 2026 19:24:13 GMT

I think I may have actually figured out what is going on. It does not have to do with the .syscfg file. The 037C device already got flashed once before using the ZONE 1 of the OTP. This is why I am getting that error. To confirm, will using ZONE 2 override what got configured in ZONE 1?

RE: TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

Fleenor — Mon, 27 Apr 2026 17:04:07 GMT

Hi Yun,

The problem is a path mismatch in the auto-generated makefile. SysConfig automatically includes f280015x_codestartbranch.asm as a Referenced Source, which compiles the .obj file into your build configuration directory (e.g., Debug_F28200156/syscfg/). However, the linker command in subdir_vars.mk incorrectly looks for it in ./device_F2800156/ — a directory you never configured [1][2]. This is a known compatibility issue between SysConfig and C2000Ware versions.

Solutions

Method 1: Remove the Referenced Source and Use a Local File

This is the cleaner approach:

In SysConfig, locate the Referenced Source entry for f280015x_codestartbranch.asm and remove/disable it so SysConfig no longer auto-generates this file.
Manually add your own copy of f280015x_codestartbranch.asm directly to your CCS project (right-click project → Add Files) [3]. This ensures the .obj is generated in the correct build output directory and the makefile references the right path.
Clean and rebuild the project.

Method 2: Update Your Toolchain Versions

This issue is tied to SysConfig/C2000Ware compatibility. TI's release notes state explicitly:

"If using SysConfig 1.21 or newer, C2000Ware needs to be updated to v5.04." [4]

You're using SysConfig 1.27, so ensure you have:

Tool	Minimum Recommended Version
Code Composer Studio	12.8.0 ✅ (you have 12.8.1)
TI C2000-CGT (Compiler)	22.6.0.LTS
SysConfig	1.21.0 ✅ (you have 1.27)
C2000Ware	v5.04 or newer

Check your C2000Ware version — if it's older than v5.04, update it [4][5]. This is the most likely root cause of the incorrect path generation in the makefile.

Method 3: Quick Workaround (Linker Path Adjustment)

If you need an immediate fix while sorting out versions:

In CCS, go to Project Properties → Build → Linker → File Search Path.
Add the actual directory where f280015x_codestartbranch.obj is generated (e.g., ${BuildDirectory}/syscfg) to the linker search path.

Note: This is a workaround, not a permanent fix — the auto-generated makefile will continue to reference the wrong path on clean rebuilds.

Recommended Approach

Start with updating C2000Ware to v5.04+ since this directly addresses SysConfig compatibility issues with your toolchain versions. If the problem persists after updating, use Method 1 (remove the Referenced Source and add the file manually to your project).

To help refine this recommendation, it would be helpful to know:

What version of C2000Ware you currently have installed
Whether this project was freshly created or migrated from an older setup
Whether your linker command file (.cmd) is auto-generated by SysConfig or manually maintained

Best Regards,

Zackary Fleenor

TMS320LC548: Programation of a DSP TMS320LC549PGE-80

Ángel Santesmases — Mon, 27 Apr 2026 12:54:11 GMT

Part Number: TMS320LC548

Hello,

We have a board that uses a TMS320LC549PGE-80 and we need to program it. In the past, we used Code Composer Studio together with the XDS510 USB programmer.

Since the TMS320LC548PGE-80 is a similar device, we would like to know the recommended programming method for this DSP and whether it is compatible with version "49." Additionally, as the XDS510 USB programmer is now obsolete, we would appreciate any guidance on current supported tools.

Thank you in advance for your help.

Best regards,

Ángel

RE: TMS320LC548: Programation of a DSP TMS320LC549PGE-80

Mike Pridgen — Mon, 27 Apr 2026 13:47:34 GMT

Ángel,

You can use the same flow to program the TMS320LC549 that you used to program the TMS320LC548. However, please note that while the TMS320LC548 is still available (but marked as No Design Support Available from TI), the TMS320LC549 is now obsoleted.

If you do not have any XDS510 programmers available, the XDS110 Programmer also supports all C54x devices, including the TMS320LC54x devices.

Thanks,
Mike

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

Ravilla Dinesh — Mon, 27 Apr 2026 12:55:02 GMT

Hi Vinu,

I am working on the AM64x (AM642 EVM) using Processor SDK Linux RT 09.02.

I am trying to configure SYSCLKOUT0 (observed as clk:119 in clk_summary).

Pinmux configuration:
clkout0_pins_default: clkout0-default-pins {
pinctrl-single,pins = <
AM64X_IOPAD(0x0258, PIN_OUTPUT, 3) /* (C17) SYSCLKOUT0 */
>;
};

/ {
clkout0_ref: clkout0-ref-clk {
compatible = "simple-pm-bus"; /* ← KEY FIX from TI E2E */
#address-cells = <1>;
#size-cells = <1>;
ranges;

assigned-clocks = <&k3_clks 119 0>;
assigned-clock-parents = <&k3_clks 119 1>;
assigned-clock-rates = <40000000>;

pinctrl-names = "default";
pinctrl-0 = <&clkout0_pins_default>;
};
};

Clock summary output:
root@am64xx-evm:~# cat /sys/kernel/debug/clk/clk_summary | grep "clk:119"
clk:119:1 0 0 0 0 0 0 50000 Y
clk:119:0 0 0 0 0 0 0 50000 Y

Thanks & Regards,
Ravilla Dinesh.

RE: F29H850TU: can interrupt is not getting triggered.

Kunal Wasnik — Mon, 27 Apr 2026 08:08:07 GMT

Hi Sayali,

I saw the example does not support launchpad option out of the box.

I only see build configuration for

Flash & Ram (These correspond to control card and there may be additional changes which may be required.)

Typically for example having launchpad support output of the box we see launchpad configuration as shown below

Have you tried this :

* In syscfg migration will be needed, change the board to launchpad and select appropriate pinmux in mcan configuration in syscfg , any other options that might need fixing (You can refer the launchpad diagram present in sysfg or the schematics)

Let me know if this solves your issue.

Regards

Kunal.

F29H850TU: can interrupt is not getting triggered.

Sayali Deshmane — Fri, 24 Apr 2026 12:33:13 GMT

Part Number: F29H850TU

Hello Team,

I have configured the can interrupt in sysconfig.just trying to receive and transmit the data from can but interrupt is not getting triggered. in ISR just toggling LED.

TMS320F2809: Error installing DSP/BIOS (bios_5_41_10_36) in CCS 12.8.1 – RTSC/XDCTools dependency missing

Tejal Gaikwad — Mon, 27 Apr 2026 07:46:44 GMT

Part Number: TMS320F2809

Hello,

I am trying to install bios_5_41_10_36 and its corresponding xdctools package in CCS 6.0.0. When I add the product discovery path (C:/ti) and try to install it, I get the following error:

Cannot complete the install because one or more required items could not be found.
Missing requirement: Model Plug-in 3.16.3.36 requires 'bundle org.eclipse.help.appserver 0.0.0' but it could not be found.
Cannot satisfy dependency: RTSC/XDCTools 3.16.3.36 → org.eclipse.rtsc.xdctools.model 3.16.3.36.

Code Composer Studio forum - Recent Threads

TMS320VC5509A: Programming Instructions

RE: TMS320VC5509A: Programming Instructions

AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

TMS320F2809: DSP/BIOS project fails to build in CCS 6.x, CCS 7.x, CCS 12.x

AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

RE: AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

RE: AM6442: AM64x CCS Load Failure - "Verification failed: Target failed to write 0x00000000"

TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

RE: TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

AM3357: CCS UniFlash v3.4.1 Compatibility Issue with U-Boot

RE: AM3357: CCS UniFlash v3.4.1 Compatibility Issue with U-Boot

RE: TMS320F280037C: TMS320F280037C .syscfg file

TMS320F280037C: TMS320F280037C .syscfg file

RE: TMS320F280037C: TMS320F280037C .syscfg file

RE: TMS320F280037C: TMS320F280037C .syscfg file

RE: TMS320F280037C: TMS320F280037C .syscfg file

RE: TMS320F280037C: TMS320F280037C .syscfg file

RE: TMS320F2800156-Q1: Sysconfig and CCS compile failure with cannot find file "./device_F2800156/f280015x_codestartbranch.obj"

Solutions

Method 1: Remove the Referenced Source and Use a Local File

Method 2: Update Your Toolchain Versions

Method 3: Quick Workaround (Linker Path Adjustment)

Recommended Approach

TMS320LC548: Programation of a DSP TMS320LC549PGE-80

RE: TMS320LC548: Programation of a DSP TMS320LC549PGE-80

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

RE: F29H850TU: can interrupt is not getting triggered.

F29H850TU: can interrupt is not getting triggered.

TMS320F2809: Error installing DSP/BIOS (bios_5_41_10_36) in CCS 12.8.1 – RTSC/XDCTools dependency missing

AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.

RE: AM6442: AM64x: Understanding EHRPWM_SOCA vs physical pin output and 40 MHz requirement on custom board.