C2000™︎ 微控制器论坛 - 最近的话题

TMS320F28377S: 板子上电程序不运行，下电后在快速上电程序能运行。

x y — Mon, 20 Jul 2026 09:14:08 GMT

Part Number: TMS320F28377S

板子上电程序不运行，下电后在快速上电程序能运行。

RE: TMS320F28377S: 板子上电程序不运行，下电后在快速上电程序能运行。

x y — Tue, 28 Jul 2026 10:00:23 GMT

现在是没有外部供1.2V ，1.2V 取自内部稳压器，上电程序不运行，复位和断电后快速上电程序能运行，不是电源斜率的问题，另外一块板子就能正常启动。我想知道这块板子的问题到底是啥

TMS320F2800157-Q1: TMS320F2800157-Q1 LIN Slave Node Example

Junping Zhai — Tue, 28 Jul 2026 09:32:13 GMT

Part Number: TMS320F2800157-Q1

Hi Experts:

Regarding the LIN peripheral of F2800157-Q1, are there any examples of LIN slave nodes that can comply with the LIN protocol?Could you provide an example related to this?Or provide me with a reference example?

Recently, the example I modified based on the SDK library has been having problems. The interruption cannot be triggered.new 2.c The code is shown in the attachment.

Best regards

Asa

RE: TMS320F2800157-Q1: TMS320F2800157-Q1 LIN Slave Node Example

Daniel — Tue, 28 Jul 2026 09:34:25 GMT

您好

已经收到了您的案例，调查需要些时间，感谢您的耐心等待

TMS320F28P650DK: TMS320F28P650DK7芯片关于clb和xbar的使用问题

Light — Sat, 25 Jul 2026 09:03:32 GMT

Part Number: TMS320F28P650DK

#define GPIO_11_GPIO11 0x00061600U
#define GPIO_11_EPWM6_B 0x00061601U
#define GPIO_11_SCIB_RX 0x00061602U
#define GPIO_11_OUTPUTXBAR7 0x00061603U
#define GPIO_11_EQEP1_B 0x00061605U
#define GPIO_11_SD4_D1 0x00061607U
#define GPIO_11_ESC_GPO3 0x0006160AU
#define GPIO_11_ESC_TX0_DATA1 0x0006160BU
#define GPIO_11_FSIRXB_CLK 0x0006160DU
#define GPIO_11_FSIRXA_D1 0x0006160EU
#define GPIO_11_PMBUSA_ALERT 0x0006160FU

#define GPIO_12_GPIO12 0x00061800U
#define GPIO_12_EPWM7_A 0x00061801U
#define GPIO_12_CLB_OUTPUTXBAR6 0x00061802U
#define GPIO_12_ADCSOCAO 0x00061803U
#define GPIO_12_EQEP1_STROBE 0x00061805U
#define GPIO_12_SCIA_TX 0x00061806U
#define GPIO_12_SD4_C2 0x00061807U
#define GPIO_12_EMIF1_A1 0x00061809U
#define GPIO_12_ESC_GPO4 0x0006180AU
#define GPIO_12_ESC_TX0_DATA2 0x0006180BU
#define GPIO_12_FSIRXC_D0 0x0006180DU
#define GPIO_12_FSIRXA_D0 0x0006180EU
#define GPIO_12_PMBUSA_CTL 0x0006180FU

#define GPIO_13_GPIO13 0x00061A00U
#define GPIO_13_EPWM7_B 0x00061A01U
#define GPIO_13_CLB_OUTPUTXBAR7 0x00061A02U
#define GPIO_13_EQEP5_STROBE 0x00061A03U
#define GPIO_13_EQEP1_INDEX 0x00061A05U
#define GPIO_13_SCIA_RX 0x00061A06U
#define GPIO_13_SD4_D2 0x00061A07U
#define GPIO_13_EMIF1_CS0N 0x00061A09U
#define GPIO_13_ESC_GPO5 0x00061A0AU
#define GPIO_13_ESC_TX0_DATA3 0x00061A0BU
#define GPIO_13_FSIRXC_D1 0x00061A0DU
#define GPIO_13_FSIRXA_CLK 0x00061A0EU
#define GPIO_13_PMBUSA_SDA 0x00061A0FU

#define GPIO_14_GPIO14 0x00061C00U
#define GPIO_14_EPWM8_A 0x00061C01U
#define GPIO_14_SCIB_TX 0x00061C02U
#define GPIO_14_EQEP5_INDEX 0x00061C03U
#define GPIO_14_LINA_TX 0x00061C05U
#define GPIO_14_OUTPUTXBAR3 0x00061C06U
#define GPIO_14_OUTPUTXBAR8 0x00061C07U
#define GPIO_14_ESC_GPO6 0x00061C0AU
#define GPIO_14_ESC_PHY1_LINKSTATUS 0x00061C0BU
#define GPIO_14_FSIRXC_CLK 0x00061C0DU
#define GPIO_14_EMIF1_D17 0x00061C0EU
#define GPIO_14_PMBUSA_SCL 0x00061C0FU

#define GPIO_15_GPIO15 0x00061E00U
#define GPIO_15_EPWM8_B 0x00061E01U
#define GPIO_15_SCIB_RX 0x00061E02U
#define GPIO_15_LINA_RX 0x00061E05U
#define GPIO_15_OUTPUTXBAR4 0x00061E06U
#define GPIO_15_CLB_OUTPUTXBAR8 0x00061E07U
#define GPIO_15_ESC_GPO7 0x00061E0AU
#define GPIO_15_EQEP5_A 0x00061E0BU
#define GPIO_15_FSIRXD_D0 0x00061E0DU
#define GPIO_15_EMIF1_DQM2 0x00061E0FU

根据以上的定义，GPIO15可以使用#define GPIO_15_OUTPUTXBAR4 0x00061E06U

或者#define GPIO_15_CLB_OUTPUTXBAR8 0x00061E07U两种方式，通过xbar路由到CLB中作为输出引脚。配置如下：

实际测试中，GPIO15通过GPIO_15_CLB_OUTPUTXBAR8这种方式，CLB5无法正常控制输出。

通过GPIO_15_OUTPUTXBAR4方式路由到CLB5的OUTLUT5进行输出，实测结果正常。

#include "board.h"

//*****************************************************************************
//
// Board Configurations
// Initializes the rest of the modules.
// Call this function in your application if you wish to do all module
// initialization.
// If you wish to not use some of the initializations, instead of the
// Board_init use the individual Module_inits
//
//*****************************************************************************
void Board_init()
{
EALLOW;

PinMux_init();
CLB_init();
CLB_OUTPUTXBAR_init();

EDIS;
}

这两种不同的方式有什么区别吗，对于GPIO12和GPIO13只有CLB_OUTPUTXBAR的路由方式怎么解决呢？

RE: TMS320F28P650DK: TMS320F28P650DK7芯片关于clb和xbar的使用问题

Daniel — Tue, 28 Jul 2026 06:46:43 GMT

您好

https://www.ti.com.cn/cn/lit/pdf/spruiz1

https://www.ti.com/lit/gpn/tms320f28p650dk

请结合datasheet中CLB以及TRM的CLB select部分说明，详细说明那些配置要求以及相关通路。请您参考。

RE: TMS320F28P650DK: TMS320F28P650DK7芯片关于clb和xbar的使用问题

Light — Tue, 28 Jul 2026 05:56:15 GMT

重点在于GPIO15通过GPIO_15_CLB_OUTPUTXBAR8这种方式，CLB5无法正常控制输出。通过GPIO_15_OUTPUTXBAR4方式路由到CLB5的OUTLUT5进行输出，实测结果正常。这里为什么不行，而且GPIO12和GPIO13只有CLB_OUTPUTXBAR的路由方式，导致这两个引脚无法使用clb5或者6控制输出

TMS320F2800137: 带死区的PWM，在duty为0时，为什么PWMB路输出一直为高电平

Aiden zhang — Fri, 24 Jul 2026 08:57:03 GMT

Part Number: TMS320F2800137

一组带死区功能的PWM，PWM原始信号输入选择A，设定ZERO：HIGH;CMPA:LOW

当CMPA =0是，示波器观察到PWMA输出一直为低电平（是想要的波形），PWMB输出一直为高电平（不是想要的波形，按我的理解应该是带死区的方波），请问为什么？

当duty=0时，蓝色圆框中的FED死区为什么不起作用，PWMB输出一直高电平。

RE: TMS320F2800137: 带死区的PWM，在duty为0时，为什么PWMB路输出一直为高电平

Daniel — Mon, 27 Jul 2026 08:36:46 GMT

您好

For this use-case, all three ePWM modules are set up for active high complementary signals. Meaning ePWMxA
remains as is with a rising edge delay (RED) and ePWMB has the same source signal as ePWMA, but it is
inverted with a falling edge delay (FED) instead of a rising edge delay. Figure 5-1 illustrates these two signals.
In order to set up these signal pairs, utilize the deadband submodule as it allows you to apply this scheme of
outputs along with many other signal pairs.
To begin, take a look at the deadband submodule, which is essentially a set of switches that work together to
achieve the desired output. S4 and S5 decide what the source signal is for the rest of the submodules: ePWMA
or ePWMB. Since you want the same source signal for both resulting ePWMA and ePWMB outputs, set both
switches to the ePWMA input. Next is S8, which is responsible for deciding which of the outputs will have RED
and FED or both applied to it. Only one channel, either A or B, can have both RED and FED.

在这部分说明为了能处理更多的信号而如此设计。这是对于这部分的说明

RE: TMS320F2800137: 带死区的PWM，在duty为0时，为什么PWMB路输出一直为高电平

Aiden zhang — Mon, 27 Jul 2026 08:21:12 GMT

谢谢你的回复。

这是按照这个完整的手册进行配置的TMS320F280013x Real-Time Microcontrollers Technical Reference Manual (Rev. B)，在Duty不为0时，我的输出波形PWMA、PWMB都是正常的，问题只出现在duty=0时，我觉得这是一个特殊情况。

你的链接我也看过了，文档里只展示了duty=36.8%的情况，并没有说明duty=0时会怎么样。希望你能验证一下duty=0时是否会出现PWMB一直高电平的问题。

RE: TMS320F28P650DK: TMS320F28P650DK7芯片关于clb和xbar的使用问题

Daniel — Mon, 27 Jul 2026 06:06:49 GMT

您好

[quote userid="143175" url="~/support/microcontrollers/c2000/f/c2000-microcontrollers-forum/1086511/tms320f28p650dk-tms320f28p650dk7-clb-xbar"]这两种不同的方式有什么区别吗，对于GPIO12和GPIO13只有CLB_OUTPUTXBAR的路由方式怎么解决呢？[/quote]

如图不同的渠道，详细参考以下链接中说明

https://www.ti.com.cn/cn/lit/ug/spruiz1b/spruiz1b.pdf?ts=1785121704638&ref_url=https%253A%252F%252Fwww.ti.com.cn%252Fproduct%252Fcn%252FTMS320F28P650DK

www.ti.com/.../sprad12a.pdf

RE: TMS320F28P650DK: F28P650DK6_176PTP芯片的CLB使用问题

Daniel — Mon, 27 Jul 2026 05:57:34 GMT

您好

[quote userid="143175" url="~/support/microcontrollers/c2000/f/c2000-microcontrollers-forum/1086303/tms320f28p650dk-f28p650dk6_176ptp-clb"]EPWM7和EPWM8的信号是否只能作为CLB5和6的输入源？[/quote]

https://www.ti.com.cn/cn/lit/ug/spruiz1b/spruiz1b.pdf

Table 8-3. Global Signals and Mux Selection (continued)

根据这部分看是这样的。

[quote userid="143175" url="~/support/microcontrollers/c2000/f/c2000-microcontrollers-forum/1086303/tms320f28p650dk-f28p650dk6_176ptp-clb"]
}如果配置使用CLB1的话，outlut5可以控制GPIO15的输出，但是CLB5却无法控制，这是为什么？[/quote]

8.3.4 CLB Output Signal Multiplexer

这部分有详细说明。

TMS320F28P650DK: F28P650DK6_176PTP芯片的CLB使用问题

Light — Fri, 24 Jul 2026 08:48:12 GMT

Part Number: TMS320F28P650DK

void main(void)
{
Device_init();
Device_initGPIO();

Interrupt_initModule();
Interrupt_initVectorTable();

SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_CLB1);

Board_init();

initTILE5(CLB5_BASE);

CLB_enableCLB(CLB5_BASE);

CLB_setOutputMask(CLB5_BASE, CLB_OUTPUT_00 | CLB_OUTPUT_02 | CLB_OUTPUT_12 | CLB_OUTPUT_13, true); //<> OUTLUT 使能
//
// Enable Global Interrupt (INTM) and realtime interrupt (DBGM)
//
EINT;
ERTM;

// GPIO_writePin(15, 1); //<> 初始化低电平

while(1)
{
asm(" NOP");
}
}如果配置使用CLB1的话，outlut5可以控制GPIO15的输出，但是CLB5却无法控制，这是为什么？EPWM7和EPWM8的信号是否只能作为CLB5和6的输入源？

RE: TMS320F2800137: 带死区的PWM，在duty为0时，为什么PWMB路输出一直为高电平

Daniel — Mon, 27 Jul 2026 02:33:47 GMT

您好

https://www.ti.com/lit/an/sprad12a/sprad12a.pdf

请您参考这个说明

RE: TMS320F28P650DK: F28P650DK6_176PTP芯片的CLB使用问题

Daniel — Mon, 27 Jul 2026 02:10:42 GMT

您好

以上是关于这个配置参考的，关于如何修正，会有相关工程师在您的新帖子中给出对应说明。

TMS320F28P650DK: F28P650DK6_176PTP芯片的CLB使用问题

Light — Fri, 24 Jul 2026 06:38:57 GMT

Part Number: TMS320F28P650DK

void main(void)
{
Device_init();
Device_initGPIO();

Interrupt_initModule();
Interrupt_initVectorTable();

Interrupt_register(INT_CLB1, &clb1ISR);
Interrupt_enable(INT_CLB1);

SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_CLB5);

Board_init();

SysCtl_disablePeripheral(SYSCTL_PERIPH_CLK_TBCLKSYNC); //<> Disable sync(Freeze clock to PWM as well)

PWM_Init();

GPIO_setPinConfig(myCLB_OUTPUTXBAR_EPWM7B_CLBOUTPUTXBAR_PIN_CONFIG);

SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_TBCLKSYNC); //<> Enable sync and clock to PWM

initTILE5(CLB5_BASE);

CLB_enableCLB(CLB5_BASE);

CLB_setOutputMask(CLB5_BASE, CLB_OUTPUT_00 | CLB_OUTPUT_02 | CLB_OUTPUT_12 | CLB_OUTPUT_13, true); //<> OUTLUT 使能
CLB_enableOutputMaskUpdates(CLB5_BASE);

//
// Enable Global Interrupt (INTM) and realtime interrupt (DBGM)
//
EINT;
ERTM;

// CLB_clearInterruptTag(myTILE1_BASE);

EPWM_setActionQualifierContSWForceAction(IGBT_7_EPWM_BASE, EPWM_AQ_OUTPUT_B, EPWM_AQ_SW_DISABLED); //<>
EPWM_setActionQualifierContSWForceAction(IGBT_7_EPWM_BASE, EPWM_AQ_OUTPUT_A, EPWM_AQ_SW_DISABLED); //<>

EPWM_setCounterCompareValue(EPWM7_BASE, EPWM_COUNTER_COMPARE_A, 750); //<> 测试使用
EPWM_setCounterCompareValue(EPWM7_BASE, EPWM_COUNTER_COMPARE_B, 750); //<> 测试使用

while(1)
{
asm(" NOP");
}
}

配置 GPIO13 通过xbar路由到CLB5的OUTLUT5输出口，输出EPWM7B的原始信号，实际测试时信号总是不正常，这是为什么？

RE: TMS320F28P650DK: F28P650DK6_176PTP芯片的CLB使用问题

Light — Mon, 27 Jul 2026 02:03:19 GMT

你好。以上的信息不能解决我遇到的问题，我现在面临的问题是F28P640DK7芯片中，EPWM7和8的信号只能给到CLB5和6中，但是实际测试中发现GPIO12到15通过CLB_OUTPUTXBAR方式路由到clb5和6中无法正常输出信号，只能在clb1到4中可以。我需要确认是什么问题导致的，是我配置不对还是芯片内部有问题？

TMS320F28P650DK: TMS320F28P650DK7芯片关于clb和xbar的使用问题 - C2000™︎ 微控制器论坛 - C2000 微控制器 - E2E™ 设计支持

RE: TMS320F2800137: Motor parameters

Eirwen — Mon, 27 Jul 2026 01:58:29 GMT

关于TMS320F28027移植到TMS320F2800137，您可以尝试参考下面链接中的资源：

TMS320F28027: transplanting it to TMS320F2800137 - C2000 microcontrollers forum - C2000™︎ microcontrollers - TI E2E support forums

TMS320F2800137: Motor parameters

zhou qicheng — Fri, 17 Jul 2026 02:40:54 GMT

Part Number: TMS320F2800137

universal_motorcontrol_lab_f280013x

Hello, I am using the main chip f2800137, and there is no mention in the general routine documentation about whether the resistance and inductance in the motor parameters distinguish between Y-type and delta-type configurations. However, after looking up the motor parameters for BLY172s in the routine, I found that this motor is of delta-type configuration, but the written motor parameters are the official line-to-line resistance and half of the inductance. This is different from the program for f28027. When I previously used the 027, the measured motor line-to-line resistance and inductance divided by 3 were written in, and it worked normally with load. However, dividing by 2 did not work. 1. Could you please confirm how to write the parameters for the delta-type motor of 137, so that it is consistent with the 027? 2. Secondly, why is there such a large error in the identification of the motor parameters for 137, sometimes 5uh and sometimes 1uh? Should I increase the chopping frequency

TMS320F28P650SK: Projiect compilation alarm issue

Yifei Qin — Fri, 24 Jul 2026 07:37:41 GMT

Part Number: TMS320F28P650SK

The following warning information appears when I use C2000Ware 5.04.00.00.

However, there is no such issue when using C2000Ware 5.01.00.00.

1、Then I compared the files and found that the function CAN_sendRemoteRequestMessage(uint32_t base, uint32_t objID) was changed in C2000Ware 5.04.00.00.

Did modifying this place fix some bug?

2、Similarly, the alarms generated by the PMBUS.C file are found in the newly added function.

PMBus_configModuleClockMode This function is also newly added.

How are these alarms generated, how should they be resolved, or can they be ignored?