C2000 microcontrollers forum - Recent Threads

LP-AM13E230: Debugger stopped working

Ari Mendes — Thu, 21 May 2026 13:56:28 GMT

Part Number: LP-AM13E230

Hi,

My LP-AM13E230 board was working normally and suddenly, after loading a firmware, the IDE failed to load the firmware and displayed the following messages:

CS_DAP_0: Error connecting to the target: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 20.5.0.3920)

Texas Instruments XDS110 USB Debug Probe/CS_DAP_0 Error connecting to the target: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 20.5.0.3920)

I tested it on another computer, with another project, and the failure persisted. I connected an external XDS110 to connector J7, and it continued to display the same error message.

The firmware that was loaded last continued to work, so the microcontroller should not be damaged.

What could be causing this failure and is there a way to fix it without replacing the microcontroller?

Ari

RE: LP-AM13E230: Debugger stopped working

Ari Mendes — Fri, 22 May 2026 18:04:42 GMT

Hi Nilabh,

I managed to do it; you need to right-click on the AM13E23019.ccxml file and choose the "Start Project-less Debug" option. This enables the Scripts menu in CCS. Following the instructions in the link, the debugger on my LP-AM13E230 started working again.

Thanks

Ari

TMS320LF2407A: TMS320LF2407A: Timing issue when writing to external peripherals

Kyle Molter — Thu, 14 May 2026 13:18:28 GMT

Part Number: TMS320LF2407A

Hello,

I have a board using a 2407APGES TI chip. We have had these boards in use for years now with no issue. In the last few years we started having new issues that we were able to isolate down to the TI chip itself.

The issue occurs when using the OUT instruction to write to an external peripheral.

The following process produces this issue:

Write to peripheral using OUT
Load a new data page using LDP
Load a value into accumulator using LACC

On a few of our boards (~5%), the LACC will not load the accumulator properly and the accumulator will instead be loaded with the value written by the OUT

I believe this indicates a bus corruption/timing issue

I cannot find in the 2407A reference manuals anything specifically about execution timing with the OUT instruction

This procedure works fine on most of our boards, but we do receive boards that cannot properly function because of this behavior

RE: TMS320LF2407A: TMS320LF2407A: Timing issue when writing to external peripherals

AJ Favela — Fri, 22 May 2026 16:49:22 GMT

Hi,

Unfortunately, we are no longer able to support any development activity on this device. We have attempted to consolidate our resources in this FAQ, but highly recommend the customer consider one of our newer devices which offer better performance, cost, software, ease-of-use, support, etc. such as F28002x or F280013x or view our whole portfolio here: C2000 real-time microcontrollers | TI.com

[FAQ] Can someone help support questions on the TMS320F240/TMS320F241/TMS320F243 or LF240xA/LC240xA devices?

Kind regards,
AJ Favela

TMS320F280039: CLA trigger source CLA_TRIGGER_SDFM1DRINT1,2,3,4 not working

Oliver Fuchs — Fri, 08 May 2026 11:48:03 GMT

Part Number: TMS320F280039

I intend to handle the filter results of SDFM1 Filter1 by the CLA. So the CLA task needs to be triggered for every data ready interrupt of SDFM1 Filter1. Obviously, the command to set the correct trigger source should be:

CLA_setTriggerSource(CLA_TASK_1, CLA_TRIGGER_SDFM1DRINT1);

But the CLA task never gets triggered even though I enable the SDFM interrupt:

SDFM_enableInterrupt(SDFM1_BASE, SDFM_FILTER_1, SDFM_DATA_FILTER_ACKNOWLEDGE_INTERRUPT);

and also reset the Interrupt Flags to get a triggering edge:

SDFM_clearInterruptFlag(SDFM1_BASE, SDFM_FILTER_1_NEW_DATA_FLAG | SDFM_MAIN_INTERRUPT_FLAG);

By the way, I find it very confusing, that the interrupt is sometimes called "Data Ready" and sometimes "Filter Acknowledge". There should be a unique naming convention in the C2000ware.

The CLA task is triggered correctly when choosing this interrupt instead:

CLA_setTriggerSource(CLA_TASK_1, CLA_TRIGGER_SDFM1DRINT1);

However, this is not what I want, because I use this interrupt already for modulator fault exceptions.

How can I configure the CLA to only trigger on the data ready interrupt and not on the general SDFM1 interrupt? Obviously, the CLA was designed to be able to distinguish this, because you can configure all of these SDFM1 interrupts:

CLA_TRIGGER_SDFM1INT = 95U, //!< CLA Task Trigger Source is SDFM1INT
CLA_TRIGGER_SDFM1DRINT1 = 96U, //!< CLA Task Trigger Srce is SDFM1DRINT1
CLA_TRIGGER_SDFM1DRINT2 = 97U, //!< CLA Task Trigger Srce is SDFM1DRINT2
CLA_TRIGGER_SDFM1DRINT3 = 98U, //!< CLA Task Trigger Srce is SDFM1DRINT3
CLA_TRIGGER_SDFM1DRINT4 = 99U, //!< CLA Task Trigger Srce is SDFM1DRINT4

However, only the first one (CLA_TRIGGER_SDFM1INT) is really working. I tried all four data ready interrupts and they fail to trigger the CLA. How can I fix that?

RE: TMS320F280039: CLA trigger source CLA_TRIGGER_SDFM1DRINT1,2,3,4 not working

Ryan Davitt — Fri, 22 May 2026 16:36:36 GMT

Hello, Oliver.

It looks like the problem here may be caused by a System Control (SysCtl) register default value. Page 290 in the tech reference manual refers to this register set that I believe is influencing which interrupt line the data ready interrupt is being fed through:

In short, this "SDFM type" register defaults to Type 0, which combines the Data Ready conditions "with the fault conditions on the SDFM interrupt line" (i.e. SDFM1INT). Type 1 causes the DR condition to "not generate the SDFMINT" and instead "generates a separate data read interrupts" (i.e. SDFM1DRINTx).

If you're using a DriverLib project, you can run the following code to switch the SDFM type into Type 1, and the DR interrupt line should now be generating an interrupt on the DR condition:

SysCtl_configureType(SYSCTL_SDFMTYPE, 1, 0);

Alternatively, you can write a 1 in the 0th bit of the SDFMTYPE register via bit field commands.

Best,

Ryan

RE: LAUNCHXL-F2800157: Need Guidance on Configuring SCI Boot Mode for Firmware Reprogramming (F2800157)

AJ Favela — Fri, 22 May 2026 16:34:49 GMT

Hi,

The expert is currently out of office. Please expect a delay in response until they return next week.

Kind regards,
AJ Favela

LAUNCHXL-F2800157: Need Guidance on Configuring SCI Boot Mode for Firmware Reprogramming (F2800157)

Md Kamarudheen — Fri, 22 May 2026 09:07:56 GMT

Part Number: LAUNCHXL-F2800157

Hi Support Team,

I am working on the TMS320F2800157 device, and I am trying to implement firmware reprogramming through SCI (UART) using TI’s Flash Programmer tool.

I am new to this boot configuration concept, so I need some guidance to understand how to correctly use SCI boot mode.

What I have understood so far:

Boot ROM code is factory programmed and cannot be modified
SCI bootloader is already present inside Boot ROM
Flash programming is done using:
- flash_programmer.exe
- kernel file
- application (.hex / .txt) file

My confusion / questions:

1. How to enable SCI boot mode

I am not clear how to actually make the device enter SCI boot mode:

Should I configure something in software?
Or is it only done using GPIO pins (hardware)?
How exactly should I set GPIO24 and GPIO32 on my board?

2. SCI peripheral selection

During SCI boot, which SCI module is used?
Is it always SCIA?
Can we configure to use another SCI (like SCIB)?

3. GPIO pin mapping for SCI

Which pins are used for SCI RX and TX during boot?
Are these fixed in Boot ROM?
Or do we need to configure them separately?

4. Relationship between SCI boot and Flash Programmer

My understanding is:

First, device should already be in SCI boot mode
Then flash_programmer.exe sends kernel and application

[emoticon:97e6a2de815c416a844278b15ca80e77] Is this correct?
Or does the tool itself put the device into SCI boot mode?

5. Complete practical flow (request for guidance)

Could you please explain the correct sequence step-by-step for:

Setting up hardware (GPIO / connections)
Making the device enter SCI boot mode
Running flash programmer
Sending kernel and application

Goal:

My goal is to successfully implement firmware update through SCI, and I want to understand the correct configuration and flow from scratch.

I would really appreciate any guidance, example references, or documents for beginners.

Thanks & Regards,
MD Kamarudheen

RE: TMS320F28P659DK-Q1: SCI: Receiving incorrect data

AJ Favela — Fri, 22 May 2026 16:34:28 GMT

Hi,

The expert is currently out of office. Please expect a delay in response until they return next week.

Kind regards,
AJ Favela

TMS320F28P659DK-Q1: SCI: Receiving incorrect data

Torsten Robitzki — Fri, 22 May 2026 10:27:28 GMT

Part Number: TMS320F28P659DK-Q1

Hi,

I configure SCI-B on a P659DK8 to communicate with 9600 baud, no parity, one stop bit. The transmission works flawless, every byte is transmitted with 10 bits (one start bit, 8 data bits and one stop bit).

One the receiving side, a FTDI to USB adapter is used to respond. According to the logic analyzer, the data is also send with 10 bits per byte.

Both on the receiving end and the transmitting and, the logicalyser uses the same decoder settings and decodes the stream with 10 bits per byte
Measing the baudrate over the transmitting package (32 bytes) and the receiving side (10 bytes), reveiles the very same baudrate of 9600.4 baud

However, the µC seems to interpret the incomming data stream incorrectly. When I look at the receiving data on the line and compare that with the data that is actually received by the SCI peripheral, the data is shifted by one bit per byte.

The peripheral seems to not expect a stop bit.

I have not seen any register configuration, that would describe the different behavior on the transmitting and receiving side of the peripheral. I have not found any errata that would describe this issue, I've read the "My C2000 SCI is not Transmitting and/or Receiving data correctly, how do I fix this?" FAQ.

What could be the problem here?

Best regards
Torsten

P.S.:

I've measured the transmission baudrate, by measuring from the start of the first start bit until the start of the last stop bit. The transmitted data contains 32 bytes, so the entired seqence has 319 bits. The measure sequence length is 33227µs. => 104.16µs

Same on the receiving side: 10 bytes are transmitted, length of the entire period is 10312µs => 104.16µs

One the receiving side, one the wire I see the byte sequence: 0x00, 0x02, 0x01, 0x01, 0x05, 0x25, 0xB3, 0x83, 0xFE, 0x00. The C2000 SCI peripheral, however only received 9 bytes: 0x00, 0x81, 0x40, 0xA0, 0x50, 0x69, 0x1b, 0xf3, 0x00

When I compare the first 5 bytes, it seems like the first byte is received correctly, the second one is shifted by one bit, the third by 2 and so on:

0000 0000, 0100 0000, 1000 0000, 1000 0000, 1010 0000
0000 0000, 1000 0001, 0000 0010, 0000 0101, 0000 1010

TMS320F280039C: TMS320F280039C ADCC3 input pulled down during power event – Sample and Hold current question

Jang Kiyoung — Tue, 12 May 2026 14:19:15 GMT

Part Number: TMS320F280039C

Hello,

I am using TMS320F280039C and have a question about ADC Sample and Hold behavior on ADCC3.

PS_ON is an external switch signal and can be Low or Floating.
PS_ON is pulled up to 3.3 V through a 100 kohm resistor.
PS_ON_IN is used to sense PS_ON and is connected to ADC channel ADCC3 (ACQPS = 10).

Observed behavior is that when PS_ON is floating at 3.3 V and the main DCDC output (12V_main) turns off, PS_ON cannot maintain 3.3 V and temporarily drops close to 0 V, then rises again.
When PS_ON_IN is disconnected from the ADC pin (left open), PS_ON remains stable at 3.3 V.
This means the issue occurs only when ADCC3 is connected.

Based on the TRM input model for ADCC3, the total ADC input capacitance is about 11.3 pF and Ron is about 860 ohms.
With ACQPS = 10, the ADC Sample and Hold operation requires significantly more current than the 33 µA that can be supplied by a 100 kohm pull‑up.

My questions are:

Is it possible that the ADCC3 Sample and Hold operation or internal analog structure can discharge an externally pulled‑up signal during a power event such as main output turn‑off?
With a high source impedance (100 kohm pull‑up), is ADC input voltage droop an expected behavior?
What source impedance or circuit topology does TI recommend when sensing a status signal like PS_ON using the ADC?

Thank you for your support.

RE: TMS320F280039C: TMS320F280039C ADCC3 input pulled down during power event – Sample and Hold current question

AJ Favela — Fri, 22 May 2026 16:33:11 GMT

Hi,

The expert is currently out of office. Please expect a delay in response until they return next week.

Kind regards,
AJ Favela

RE: LAUNCHXL-F2800157: Need Guidance on Configuring SCI Boot Mode for Firmware Reprogramming (F2800157)

Md Kamarudheen — Fri, 22 May 2026 15:18:53 GMT

Thank you for your previous response and for explaining the default SCI boot approach using boot pins.

I understand that:

Boot mode can be selected using GPIO pins
SCI boot can be used for firmware update via Flash Programmer
After programming, the device can be switched back to Flash boot

✅ My Requirement (Clarification Needed)

In my application, the board will be deployed inside a system, and it is not feasible to manually change boot pins (GPIO24 / GPIO32) for firmware updates.

So I would like to follow this approach:

➡️ Always boot from Flash
➡️ Application runs normally
➡️ Whenever firmware update is required, the application itself should trigger the update process
➡️ Device should receive new firmware over SCI and update Flash

✅ My Questions

1. Recommended Approach

Is the correct approach to implement a custom bootloader in Flash for this use case?
Is this the recommended method for production systems?

2. Available TI Examples / Firmware

Are there any ready-to-use bootloader examples provided by TI for:
- SCI-based firmware update (UART)
- Application-triggered reprogramming (IAP – In Application Programming)
If yes, could you please share:
- Example project paths in C2000Ware
- Relevant application notes or documentation

3. Tools for Firmware Update

In this approach (Flash boot + custom bootloader):
- Which tools are recommended for sending firmware?
Can we still use:
- flash_programmer.exe
  OR
- Do we need to develop a custom host tool (e.g., Python / UART-based)?

4. Bootloader Flow Clarification

Is the following understanding correct:
1. Boot ROM always boots from Flash
2. Bootloader (stored in Flash) executes first
3. Bootloader checks for update request (SCI/CAN/flag)
4. If update requested → receives firmware and programs Flash
5. Otherwise → jumps to application

👉 Please confirm if this is the correct implementation flow.

5. SCI Configuration in Bootloader

For implementing SCI-based update:
- Should we use standard SCIA peripheral initialization in software?
- Are there any restrictions or recommended pin configurations?

✅ End Goal

My goal is to implement a robust firmware update mechanism over SCI without changing boot pins, suitable for deployed systems.

RE: LP-AM13E230: Debugger stopped working

Ari Mendes — Fri, 22 May 2026 13:44:56 GMT

Hi Nilabh,

The solution corresponding to the link you sent depends on the DSSM script in the "Scripts" menu of CCS.

My CCS installation doesn't have anything in the "Scripts" menu. Does this need to be installed later?

Ari

TMS320F280025: Subject: Guidance Required for ESMO Parameter Tuning in DMC_LEVEL_2 (TIDM_02010_DMPFC)

Navaneeth Kumar — Fri, 22 May 2026 12:40:12 GMT

Part Number: TMS320F280025

Hi TI Team,

We are using the following MotorControl SDK solution:

C:\ti\c2000\C2000Ware_MotorControl_SDK_5_04_00_00\solutions\tidm_02010_dmpfc

Currently, we are working in DMC_LEVEL_2 and running a compressor PMSM motor successfully.

Attached observations: software issues report.docx

Issues facing in driver/solution

Please suggest the recommended tuning approach and parameter changes.

Thanks & Regards,
Navaneeth kumar

LAUNCHXL-F28P65X: Limitation on interrupt frequency of ePWM modules

Benjamin Soulas — Fri, 22 May 2026 12:07:20 GMT

Part Number: LAUNCHXL-F28P65X

Hello,

My goal is to generate a 500kHz PWM signal, whose duty cycle is updated every period by reading from a LUT with a CLA task.

I tried several approaches for that:

First using the cla_ex4_pwm_control example, by slightly modifying the example CLA task and setting the frequencies of both ePWM modules to 500kHz. This did not work as the CLA task was not triggered at all, it worked on lower frequencies though, around 170kHz at most.
Then I tried simplifying the example by using a single ePWM module, in up-count mode, with an interrupt to the CLA task when TBCTR = ZERO. I got the same behaviour as before, with a max frequency of around 170kHz.
I used a CPUTIMER at 500kHz instead of the ePWM module (which is still used for the actual output signal). This works perfectly, but is not ideal as I might need the timer in something else later.
I tried taking the second attempt, but in up-down instead of up-count mode. With a CLA task trigger at TBCTR = ZERO, and a shadow register load at TBCTR = PRD. This worked slightly better with a maximum frequency of around 300kHz.

The actual CLA task is very small, with an estimated 20-30 CPU cycles to complete.

Is anyone aware of an hardware limitation on the maximum frequency one can use the ePWM interrupt ?

Thanks in advance,

Best regards,

Benjamin

RE: LAUNCHXL-F28P65X: Limitation on interrupt frequency of ePWM modules

Benjamin Soulas — Fri, 22 May 2026 12:15:45 GMT

It seems I cannot edit my post, so some more informations I forgot on the post:

- The main issue I found while debugging is that the ePWM interrupt is not triggering the CLA task, this task works as I can call it with CLA_forceTasks(). By reading the registers while in debug, I can see that the ePWM counter is updating, and the interrupt is being triggered from the ePWM side.

- Trying to trigger a standard CPU ISR instead of a CLA task gives the same results in term of frequency as stated above.

RE: TMS320F28P559SG-Q1: TMS320F28P559SG2-Q1: XCP Monitor & Tune Timeout Error with Flash Boot

Nilabh Anand — Fri, 22 May 2026 12:04:06 GMT

Hi Divyesh,

There is no know errata from our side.

Please reach out to matlab support team as well for this.

TMS320F28P559SG-Q1: TMS320F28P559SG2-Q1: XCP Monitor & Tune Timeout Error with Flash Boot

Divyesh Lodariya — Thu, 14 May 2026 05:59:12 GMT

Part Number: TMS320F28P559SG-Q1

I am writing to report an issue with XCP-based Monitor & Tune (External Mode) on the TMS320F28P559SG2-Q1 using MATLAB R2024b and CCS.

Hardware & Software Setup:

MCU: TMS320F28P559SG2-Q1 (512KB Flash, custom board)

MATLAB: R2024b (24.2)

C2000 Microcontroller Blockset: Latest

CCS: 12.7.0

C2000Ware: 5.02.00.00

CGT: TI C28x CGT 22.6.0 LTS

XCP Transport: XCP on Serial (SCI-A, GPIO28/GPIO29)

Issue Description:

When using Monitor & Tune with Boot From Flash enabled, MATLAB throws the following error:

Error: External Mode Open Protocol Connect command failed

Caused by:

Could not connect to target application: XCP internal error:

timeout expired, in response to XCP CONNECT command

Key Observations:

Normal Deploy & Run works perfectly — firmware runs correctly from Flash when Monitor & Tune is not used.
Same model works on F28P550SJ9(LaunchPad MCU) — Monitor & Tune with Flash Boot works without any issues on the SJ9 variant (1MB Flash, 64KB dedicated bank).
SG2 variant has no 64KB Flash Bank — The F28P559SG2 has only 512KB Flash (2×256KB banks) with no dedicated 64KB bank. We suspect the XCP stack or its boot stub requires this 64KB Flash bank which is unavailable on SG2.

Questions:

Does XCP Monitor & Tune with Flash Boot require the 64KB dedicated Flash bank that is present in SG9 but absent in SG2? If yes, is there a workaround to redirect XCP sections to main Flash banks on SG2?
Is there a custom linker CMD file configuration recommended for XCP on devices without the 64KB Flash bank?
Is F28P559SG2 officially supported for XCP-based Monitor & Tune with Flash Boot in MATLAB R2024b C2000 Blockset?
Are there any known errata or limitations for XCP on the 64-pin LQFP package variant?
Any guidance or example linker configuration for XCP on SG2 would be greatly appreciated.

Flash_test.zip

Best Regards,

Divyesh Lodariya

RE: LAUNCHXL-F2800157: Need Guidance on Configuring SCI Boot Mode for Firmware Reprogramming (F2800157)

Torsten Robitzki — Fri, 22 May 2026 11:24:21 GMT

By default, the boot mode is defined by the boot mode pins. However, you can configure in the OTP (one time prom) to have a different set of boot options and a different set of boot pins.

Usually, you want to boot from flash (aka not boot, but just start the firmware from flash). In case of a firmware update, you would have to set the boot pins to boot from SCI and reset the device. Then, you can upload the new firmware, change the boot pins back to boot from flash and reset the device.

Alternatively, you could use a custom bootloader, that for example boots all the time from flash, waits after a reset on the serial line for a certain time and if no command for firmware update is received, just starts the existing firmware.

RE: TMS320F28379D: Issue Converting Float to String for SCI (UART) Transmission on C2000

Deepan V — Fri, 22 May 2026 11:20:31 GMT

Hi,

Thank you for sharing the project file. I will try out on my setup and let you know.

Regards,

Deepan

TMS320F28379D: Issue Converting Float to String for SCI (UART) Transmission on C2000

Deepan V — Sat, 04 Apr 2026 05:27:10 GMT

Part Number: TMS320F28379D

Hi TI Team,

I am working with a C2000 device ([TMS320F28379D]) and using the SCI (UART) peripheral for serial communication.

Initially, I verified that SCI transmission is working correctly by sending normal strings. I was also able to convert integer values to strings and transmit them successfully.

After that, I tried to transmit floating-point values by first converting them into strings using sprintf and then sending them over SCI.

However, when I did this, I started observing abnormal system behavior. To isolate the issue, I then tried a simpler test by just printing the float using printf:

But even this did not work correctly. The output is empty, whereas the same is working fine for integer values.

From this, it seems:

SCI (UART) itself is working fine (verified with strings and integers)
The issue starts specifically when handling float values
Even basic float printing using printf is not working
Additionally, using sprintf with "%f" seems to affect system behavior

I also checked in Code Composer Studio for any option to enable float support (such as printf-related settings), but I could not find any such option.

Could you please help with:

Whether float support is available in C2000?
Why using sprintf with "%f" could lead to abnormal system behavior?
How to correctly enable or handle float-to-string conversion in this case?
Recommended method to safely transmit float values over SCI?

Thanks in advance for your support.

F29H85X-SOM-EVM: Issue while importing CSD example available in TIFS_F29_V26 sdk

Shashank Bikkanuri — Fri, 22 May 2026 10:47:32 GMT

Part Number: F29H85X-SOM-EVM

Hi,

I am getting the error shown in the following picture while importing the Combined Services Demo example available in TIFS_F29_V26 SDK. I suspect the issue is related to the flash linker command file. How can I resolve this issue?

Regards,

Shashank

F29H859TU-Q1: Can we use 5V GPIO as SENT communication?

Shuqing Zhou — Fri, 22 May 2026 10:13:15 GMT

Part Number: F29H859TU-Q1

Hi team,

I ask this for my customer

in our datasheet, it says it can some GPIO can tolerate the 5V, can it used as SENT communication?

If can, do we have the recommand schematic design for this?

BRs

Shuqing

TMS320F28P650DK: ECAP Signal Monitoring

Haobo Zhang — Thu, 30 Apr 2026 22:56:26 GMT

Part Number: TMS320F28P650DK

Hi TI support team,

On the F28P65x eval board, I am trying to use an eCAP module to generate an interrupt when an external input signal has a positive pulse width greater than 100000 clock cycles. I used a function generator to inject a constant square wave on GPIO16. I saw that the eCAP module generated an interrupt, with the interrupt flag set to 1026 (0x402), after the code started. However, the interrupt fired only once with the constant-pulsed input. Is anything required to clear MUNIT_1_ERROR_EVT2 besides the interrupt flag? The following are my SysConfig settings for eCAP and the ISR code snippet.

Thanks,

Haobo