<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>C2000™︎ microcontrollers</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/</link><description>&lt;p style="display:none;"&gt;blank&lt;/p&gt;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: TMS320F280039C: Continuous NMI Reset Loop caused by memcpy() reading corrupted Flash sector on every boot</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362246</link><pubDate>Thu, 28 May 2026 09:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4f59eb96-6474-410b-ada8-be4ff3ca3ec0</guid><dc:creator>Tanmay parekh</dc:creator><description>e2e.ti.com/.../1526.Code.txt</description></item><item><title>Forum Post: TMS320F28P650DK: Request for confirmation of Silicon revision for the TMDSCNCD28P65X control card</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650221/tms320f28p650dk-request-for-confirmation-of-silicon-revision-for-the-tmdscncd28p65x-control-card</link><pubDate>Thu, 28 May 2026 09:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d48f9295-04a0-4a10-aa7e-dbc82ba5e420</guid><dc:creator>Aditya Iyer</dc:creator><description>Part Number: TMS320F28P650DK Other Parts Discussed in Thread: TMDSCNCD28P65X , , TMDSHSECDOCK Dear Team, We are planning to procure the TMDSCNCD28P65X controlCARD evaluation module for the MCU TMS320F28P650DK along with the docking station TMDSHSECDOCK . Before proceeding with the purchase, we would like to confirm the silicon revision that will be supplied with the control card. Specifically, we would like to ensure that the silicon version does not contain the ADC-related errata mentioned in the documentation. Please find below the details for reference: IC Part Number: TMS320F28P650DK TMS320F28P650DK data sheet, product information and support | TI.com Control Card Part Number: TMDSCNCD28P65X TMDSCNCD28P65X Evaluation board | TI.com 3) ADC Errata Reference: TMS320F28P65x Real-Time MCUs Silicon Errata (Rev. D) 4) Silicon Revision Information Reference: Could you please confirm: Whether the control card will be shipped with Revision A silicon in which this ADC errata is resolved/not present. The current silicon revision with which the control card will be shipped. Your confirmation will help us proceed further with procurement. Best regards, Aditya Iyer</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F28P650DK">TMS320F28P650DK</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMDSHSECDOCK">TMDSHSECDOCK</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMDSCNCD28P65X">TMDSCNCD28P65X</category></item><item><title>Forum Post: RE: TMS320F280039C: Continuous NMI Reset Loop caused by memcpy() reading corrupted Flash sector on every boot</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362243</link><pubDate>Thu, 28 May 2026 09:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:94ea24d6-84e8-4fa3-8efa-26b7346e80e3</guid><dc:creator>Tanmay parekh</dc:creator><description>Hi Aswin, [quote userid=&amp;quot;542961&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362216&amp;quot;]On of the option to create flash corruption is using a power interrupt simulation, reset the MCU mid write to leave a sector in corrupted state[/quote] At what function in the below code should i do power interrupt simulation ? Also does power interrupt simulation mean to turn off Power or something else ? Also I do have access to only API&amp;#39;s of flash library and not the enitre function [quote userid=&amp;quot;542961&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362216&amp;quot;]I would suggest for a full flash erase before every new program load(not a sector erase)[/quote] So my application is running from Bank 0 and I am using Bank 2 (0xAF000) to store some data during runtime at particular trigger point, so need to erase sector only..</description></item><item><title>Forum Post: RE: F29H85X-SOM-EVM: Issue while importing CSD example available in TIFS_F29_V26 sdk</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1648572/f29h85x-som-evm-issue-while-importing-csd-example-available-in-tifs_f29_v26-sdk/6362232</link><pubDate>Thu, 28 May 2026 09:31:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0bc34f08-09c3-455e-a944-033c3001e4e6</guid><dc:creator>Anand Kulkarni</dc:creator><description>Hi Shashank, Pl. follow below step: Open CCS 20.5.0 and navigate to &amp;#39;File-&amp;gt;Preferences-&amp;gt;Code Composer Studio Settings-&amp;gt;Products&amp;#39; and then click on the Refresh icon and make sure &amp;#39;F29H85X-SDK 26.0.0&amp;#39; is discovered. regards, Anand</description></item><item><title>Forum Post: RE: TMS320F280039C: Continuous NMI Reset Loop caused by memcpy() reading corrupted Flash sector on every boot</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362216</link><pubDate>Thu, 28 May 2026 09:16:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:27fd0331-a8e3-45cf-bd3b-5e8fac8bfb13</guid><dc:creator>Aswin P</dc:creator><description>[quote userid=&amp;quot;653559&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot&amp;quot;]Please help in ways of recreating flash corruption[/quote] On of the option to create flash corruption is using a power interrupt simulation, reset the MCU mid write to leave a sector in corrupted state. Please ensure of the below checks are correct - Verify the flash wait state are correct as per the datasheet. What i understand is that, the auto ECC write during the mcal_flash_program_autoecc_sector() created corrupted ECC code. Full erase (not just sector erase) clears residual bit patterns that caused the corruption. I would suggest for a full flash erase before every new program load(not a sector erase) Thanks Aswin</description></item><item><title>Forum Post: RE: TMS320F280039C: Continuous NMI Reset Loop caused by memcpy() reading corrupted Flash sector on every boot</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649838/tms320f280039c-continuous-nmi-reset-loop-caused-by-memcpy-reading-corrupted-flash-sector-on-every-boot/6362200</link><pubDate>Thu, 28 May 2026 09:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:911556a9-b1c0-48a7-9e80-c309c808df33</guid><dc:creator>Aswin P</dc:creator><description>Hi Tanmay, Let me go through the issue, i will get back shortly. Thanks Aswin</description></item><item><title>Forum Post: RE: F29H85X-SOM-EVM: Issue while importing CSD example available in TIFS_F29_V26 sdk</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1648572/f29h85x-som-evm-issue-while-importing-csd-example-available-in-tifs_f29_v26-sdk/6362188</link><pubDate>Thu, 28 May 2026 08:59:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:db234b49-f486-4c5f-a56e-087276bb128c</guid><dc:creator>Aswin P</dc:creator><description>Hi Shashank, Apologies for the delayed response, let me loop SDK experts on this query. Thanks Aswin</description></item><item><title>Forum Post: RE: TMS320F28386D: example use FPU</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649904/tms320f28386d-example-use-fpu/6362161</link><pubDate>Thu, 28 May 2026 08:41:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:64ce228f-c62a-474e-8c83-0f7028129753</guid><dc:creator>Andres Linder</dc:creator><description>Thanks for the reply, I fell into a TRAP while executing the first ASM command. I couldn&amp;#39;t find examples in &amp;quot;{c2000ware sdk}libraries\dsp\FPU for the ARM core. So first, could you confirm that the TMS320F28386D controller has a ARM core with an FPU?</description></item><item><title>Forum Post: RE: F29H859TU-Q1: Is SECCFG can be downloaded using hex file?</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649962/f29h859tu-q1-is-seccfg-can-be-downloaded-using-hex-file/6362093</link><pubDate>Thu, 28 May 2026 07:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7a74019a-263a-442c-a338-2c2da4f52580</guid><dc:creator>Aswin Sankar</dc:creator><description>Hi Shuqing, [quote userid=&amp;quot;610907&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649962/f29h859tu-q1-is-seccfg-can-be-downloaded-using-hex-file&amp;quot;]if customer in bankmode1, it can&amp;#39;t be downloaded(success in bankmode0), the error is showed in below[/quote] In this case, what is the bankmode of the device. The device seems to be in bank mode 1. In this case are you loading the ssu out file related to bank mode 1 itself. Can you load the defualt bankmode 1 ssumode1 file located at f29h85x-sdk_26_00_00\source\defseccfgbin and check once? I was able to obtain the same error message as in your case by loading bankmode0 ssu .out file in bank mode 1. Was the Bank Mode configuration in Sysconfig changed to MODE 1? [quote userid=&amp;quot;610907&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649962/f29h859tu-q1-is-seccfg-can-be-downloaded-using-hex-file&amp;quot;]if device work in bankmode0, how to reprogram the flash data and seccfg data without program the default seccfg file to device? In the actually firmware update, it isn&amp;#39;t possible to program the default seccfg file everytime it needs ota[/quote] Can you please tell me in what scenario this issue is being observed. My understanding is that in bank mode 0, no other configs other than the default config is working. [quote userid=&amp;quot;610907&amp;quot; url=&amp;quot;~/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649962/f29h859tu-q1-is-seccfg-can-be-downloaded-using-hex-file&amp;quot;]if device work in bankmode1, how to program the hex file( include the seccfg) to device through bootloader?[/quote] In F29H85X SDK, there is an example which demonstrates writing of seccfg into flash from code. f29h85x-sdk_26_00_00\examples\driverlib\single_core\flash\flash_mode0_seccfg_program. Customer can follow this example to program seccfg. Hex file can be dumped into a c array and used.</description></item><item><title>Forum Post: TMS320F28377D-EP: Clock Tree</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650137/tms320f28377d-ep-clock-tree</link><pubDate>Thu, 28 May 2026 06:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f23d6707-e7e8-4875-8efa-666f3dc499c7</guid><dc:creator>Kasai Shigeo</dc:creator><description>Part Number: TMS320F28377D-EP Other Parts Discussed in Thread: SYSCONFIG Hi, I am new to sysconfig on CCS. I am getting the following two warnings in the configuration. I have a question about it. How do I add the &amp;#39;Device Support&amp;#39; module and where is the &amp;#39;Device Support&amp;#39; module? WARNINGS CPU1:Clock Tree Add the &amp;#39;Device Support&amp;#39; module in order to use Clock Tree tool and generate device support files.This suggestion can be ignored if not using Clock Tree tool. CPU2:Clock Tree Add the &amp;#39;Device Support&amp;#39; module in order to use Clock Tree tool and generate device support files.This suggestion can be ignored if not using Clock Tree tool. Any advice or suggestions would be greatly appreciated. Thank you.</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/SYSCONFIG">SYSCONFIG</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F28377D_2D00_EP">TMS320F28377D-EP</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/Aerospace%2b_2600_amp_3B00_%2bDefense">Aerospace &amp;amp; Defense</category></item><item><title>Forum Post: RE: TMS320F28386S: lwIP UDP memory leak</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649816/tms320f28386s-lwip-udp-memory-leak/6361983</link><pubDate>Thu, 28 May 2026 06:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f0083bda-ebbb-4c4c-a072-a9201345cccc</guid><dc:creator>Gouri Siva M</dc:creator><description>Hi, It is actually not a simple patch. You might need to refer the latest version of C2000ware. There are changes all over application, interface layer and driver.</description></item><item><title>Forum Post: RE: TMS320F28386S: lwIP UDP memory leak</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649816/tms320f28386s-lwip-udp-memory-leak/6361967</link><pubDate>Thu, 28 May 2026 06:21:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a84481dc-d26d-439c-bcef-273e7f808e89</guid><dc:creator>Nir Givon</dc:creator><description>Hi, thanks. please advice on the best way for me to fix my issue. this project is 4 years old. i would like to fix rather than rewrite the hole project. Can i only replace a spesific file or library? do i need to upgrade everything? what would be the least amount of change that will solve this issue? Thanks</description></item><item><title>Forum Post: RE: TMS320F28386S: lwIP UDP memory leak</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649816/tms320f28386s-lwip-udp-memory-leak/6361959</link><pubDate>Thu, 28 May 2026 06:16:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0a632c02-fa80-4baf-8912-648f308a891e</guid><dc:creator>Gouri Siva M</dc:creator><description>Hi, Memory leaks have been removed in the latest C2000ware release.</description></item><item><title>Forum Post: RE: F29H859TU-Q1: Impact of a peripheral register access with a lower size than the size of the register</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1647660/f29h859tu-q1-impact-of-a-peripheral-register-access-with-a-lower-size-than-the-size-of-the-register/6361956</link><pubDate>Thu, 28 May 2026 06:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1c14a11f-080c-4302-a234-a74b45c5347f</guid><dc:creator>Francois Charlot</dc:creator><description>Hi Vivek, Thank you. It does not look to me that the TRM explicitly mentions that some peripheral registers may be byte- or halfword-accessed. Looking at the driverlib code, I see many HWREGB accesses being made to the least significant byte of some registers because the 3 most significant bytes of these registers are RESERVED. So, what should one assume? That byte- and halfword-accesses are allowed to all peripheral registers? That&amp;#39;s what I would assume. If that&amp;#39;s not the case, what is the rule since the TRM does not seem to explicitly show this information? For question #2 above, I would assume that no read-modify-write operation be performed when writing through an HWREG8 or HWREG16 macro. Please confirm. However, I am wondering what happens when reading with HWREG8 the LSB of a 32-bit register that contains R/W1C or R/W0C bit fields in the 3 MSBs. Would the read-set to 0 or 1 operation be only performed on the LSB as one would expect? Best regards, Fran&amp;#231;ois.</description></item><item><title>Forum Post: TMS320F28384D: Failed OPT process at address 0x78010 , can 't access by JTAG</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650100/tms320f28384d-failed-opt-process-at-address-0x78010-can-t-access-by-jtag</link><pubDate>Thu, 28 May 2026 05:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:08effb49-44cf-4201-a1d2-2d2a52e4d5a6</guid><dc:creator>Eyal Saban1</dc:creator><description>Part Number: TMS320F28384D Hello TI Support, We are working with the TMS320F28384D device from the C2000 family and are trying to enable JTAG lock using DCSM OTP programming. We programmed the OTP area starting at address 0x780000 (Zone1 OTP configuration) according to the following configuration: .sect &amp;quot;dcsm_otp_z1_linkpointer&amp;quot; .retain .long 0x00003FE0 .long 0x00003FE0 .long 0x00003FE0 .long 0xFFFF0000 ; Z1OTP_JLM_ENABLE .long 0x5AFF4854 ; Z1OTP_GPREG1 .long 0x5AFFFF1F ; Z1OTP_GPREG2 .long 0x03030303 ; Z1OTP_GPREG3 .long 0xFFFFFFFF ; Z1OTP_GPREG4 .long 0xFB7FFFFF ; PSWDLOCK .long 0x7FFFFFFF ; CRCLOCK .long 0x5FAABBBB ; Z1OTP_JTAGPSWDH0 .long 0x4E30DDDD ; Z1OTP_JTAGPSWDH1 .long 0x00000000 ; Z1OTP_CMACKEY0 .long 0x00000000 ; Z1OTP_CMACKEY1 .long 0x00000000 ; Z1OTP_CMACKEY2 .long 0x00000000 ; Z1OTP_CMACKEY3 The OTP programming process failed at address 0x780010 with FMSTAT = 0x30. Address 0x780010 corresponds to the PSWDLOCK field, which itself appears valid. However, after further investigation, we suspect the failure was actually caused by the JTAG password high fields (JTAGPSWDH0 / JTAGPSWDH1). It appears that these OTP locations were already factory programmed by TI with the following values: JTAGPSWDH0 = 0x4BFFFFFF JTAGPSWDH1 = 0x3FFFFFFF In our assembly file, we mistakenly attempted to program: JTAGPSWDH0 = 0x5FAABBBB JTAGPSWDH1 = 0x4E30DDDD Our understanding is that OTP programming can only change bits from 1 to 0, and therefore the operation failed because some bits would require changing from 0 back to 1. We understand the programming mistake. Our main question now is whether the DSP can still be used and how we can reconnect/debug the device. We attempted multiple password combinations, including: Default JTAG passwords H0/H1 values L0/L1 passwords from the Zone Select Block pointed by Z1-LINKPTR However, all JTAG unlock attempts failed. This is confusing because: JTAGPSWDH0/H1 are located at 0x780014 / 0x780016 L0/L1 passwords are located in the Zone Select Block referenced by Z1-LINKPTR The programming failure occurred earlier at 0x780010 We would appreciate clarification on the following: Can the device still be recovered and used? What password values should CCS use in this situation? Does a failed OTP programming sequence partially program the JTAG password fields? Is there any way to determine the actual programmed OTP contents after FMSTAT=0x30 failure? Could the device now be permanently locked even though the failure occurred before the JTAG password locations? Is there any recommended recovery/debug procedure for this scenario? Any guidance would be greatly appreciated. Best regards, Eyal</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F28384D">TMS320F28384D</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/Industrial%2bAutomation">Industrial Automation</category></item><item><title>Forum Post: RE: F29H850TU: password-based JTAG protection</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1645406/f29h850tu-password-based-jtag-protection/6361903</link><pubDate>Thu, 28 May 2026 05:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:31b2f82e-ab86-4147-8e61-50dc84a163a5</guid><dc:creator>Eyal Saban1</dc:creator><description>Hi Marlyn , We don&amp;#39;t need AUTOSAR in our project and we are not utilizing the HSM , great that you are relasing a reference for a simple JTAG lock using Best Regards, Eyal.</description></item><item><title>Forum Post: C2000WARE: TMS320F280049C controller is not supporting MPU, but how we can protect memory regions</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650092/c2000ware-tms320f280049c-controller-is-not-supporting-mpu-but-how-we-can-protect-memory-regions</link><pubDate>Thu, 28 May 2026 05:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a1888aaf-b2ad-4d7d-b235-3de822a5391a</guid><dc:creator>Vinod V</dc:creator><description>Part Number: C2000WARE Other Parts Discussed in Thread: TMS320F280049C TMS320F280049C controller is not supporting MPU like cortexM, but how we can protect memory regions by calling memory exception or trap when memory of one region try to overwrite or corrupt another or adjacent memory.</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/C2000Ware">C2000Ware</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F280049C">TMS320F280049C</category></item><item><title>Forum Post: RE: TMS320F28386D: example use FPU</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1649904/tms320f28386d-example-use-fpu/6361834</link><pubDate>Thu, 28 May 2026 04:07:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:e9e5f9d2-f143-4af6-bdd7-bb727038d97f</guid><dc:creator>Kunal Wasnik</dc:creator><description>Hi , Can you please clarify by &amp;quot;software is no longer running&amp;quot;. Also can you try switching to latest ccs if you are not. You can find fpu example in &amp;quot;{c2000ware sdk}libraries\dsp\FPU Regards Kunal.</description></item><item><title>Forum Post: TIEVM-VIENNARECT: Request: TIEVM‑VIENNARECT / TIDM‑1000 Vienna source for F2837x (DigitalPower SDK) — files missing in my SDK</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650067/tievm-viennarect-request-tievm-viennarect-tidm-1000-vienna-source-for-f2837x-digitalpower-sdk-files-missing-in-my-sdk</link><pubDate>Thu, 28 May 2026 03:24:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:92acbfd9-fd37-46ad-8f95-07d7879646b8</guid><dc:creator>Mitsuyasu INO</dc:creator><description>Part Number: TIEVM-VIENNARECT Hello TI team and community, I am working with the TIEVM‑VIENNARECT hardware and the C2000 DigitalPower SDK. I would like to request assistance or a copy of the Vienna rectifier (TIDM‑1000) firmware/project configured for the F2837x family, or guidance on where to find the complete set of source files in the SDK. Summary: - EVM: TIEVM‑VIENNARECT - MCU / controlCARD: TMDSCNCD28379D (TMS320F28379D) - SDK: C2000Ware DigitalPower SDK (please see version below) - Problem: After downloading the SDK, the Vienna/PFC project appears incomplete in my installation — several source files and/or project configurations seem to be missing or not included in the CCS project. I need the complete project or instructions to assemble the F2837x-targeted project. What I have checked: - Searched under solutions/tidm_1000/ for pfc3phvienna, device, common, and libraries/dpl folders. - Opened the CCS project under solutions/tidm_1000/f2838x/project but the project does not include all .c/.h files (pfc3phvienna_*.c, pfc3phvienna_settings.h, DPL blocks, device init files). - Attempted to add missing folders manually but unsure which exact files are required for a proper F2837x build and which project settings (linker command file, include paths, device-specific defines) must be changed. Request: 1. Could TI provide the complete TIDM‑1000 / TIEVM‑VIENNARECT project files configured for F2837x (or instructions to convert the provided f2838x project to F2837x)? 2. If direct file sharing is not possible, could you list the exact files/folders and CCS project settings (device, linker cmd, include paths, preprocessor defines) required to build for TMDSCNCD28379D? 3. Any known caveats when porting from f2838x examples to F2837x (pin mapping, ADC/ePWM differences, DPL compatibility)? Attachments I can provide on request: - SDK folder listing under solutions/tidm_1000 (text file) - CCS build log showing missing symbols/errors - Screenshots of the project tree in CCS Please let me know what additional information you need. Thank you for your help. Best regards, Honda R&amp;amp;D Co.,Ltd Mitsuyasu Ino</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/Hybrid">Hybrid</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/C2000Ware">C2000Ware</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/electric%2b_2600_amp_3B00_%2bpowertrain%2bsystems">electric &amp;amp; powertrain systems</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F28379D">TMS320F28379D</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TIEVM_2D00_VIENNARECT">TIEVM-VIENNARECT</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMDSCNCD28379D">TMDSCNCD28379D</category></item><item><title>Forum Post: TMS320F28P550SG: F28P55 driverlib Bug : ADC_setInterruptSource() failed with code generated by sysconfig</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1650064/tms320f28p550sg-f28p55-driverlib-bug-adc_setinterruptsource-failed-with-code-generated-by-sysconfig</link><pubDate>Thu, 28 May 2026 03:22:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:aa21ed09-b803-4964-84f8-f9b74fdf8abb</guid><dc:creator>Min-Kuang Lin</dc:creator><description>Part Number: TMS320F28P550SG Other Parts Discussed in Thread: SYSCONFIG , C2000WARE i&amp;#39;m using CCS20.4.1, C2000Ware.6.0.1, offline SysConfig 1.27.1+4634, and set ADC_INT_TRIGGER_OSINT4 as ADC A interrupt 4 source. The error is shown at initial stage that &amp;quot;ASSERT(intTrigger &amp;lt; 35U);&amp;quot; can i just modify the magic number 35 to 36 in driverlib/adc.h ?</description><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/TMS320F28P550SG">TMS320F28P550SG</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/C2000Ware">C2000Ware</category><category domain="https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/tags/SYSCONFIG">SYSCONFIG</category></item></channel></rss>