<?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>Arm-based microcontrollers</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/</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: AM62P-Q1: AM62P-LP: Cold Boot Optimisation</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1646323/am62p-q1-am62p-lp-cold-boot-optimisation/6361454</link><pubDate>Wed, 27 May 2026 22:03:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4b08406d-2c64-4f5e-9ba1-f976bca63332</guid><dc:creator>Thomas Carr</dc:creator><description>Hi Suren, I&amp;#39;ll give that a go! A debug call would be great and tomorrow afternoon works! Thanks Tom</description></item><item><title>Forum Post: RE: MSPM0L1117: Does MSPM0L1117 Support Mutli-Word Programming?</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649964/mspm0l1117-does-mspm0l1117-support-mutli-word-programming/6361430</link><pubDate>Wed, 27 May 2026 21:43:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:26470f05-7b3b-4304-a0b4-d52586bd1212</guid><dc:creator>Owen Li</dc:creator><description>Hi Chris, I am looking into this with my team and I will get back to you as soon as I have an answer for you. Best, Owen</description></item><item><title>Forum Post: RE: LP-AM263P: Error code 1170 - DAP connection error - error connecting to the Target (ARM based MCU)</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1647862/lp-am263p-error-code-1170---dap-connection-error---error-connecting-to-the-target-arm-based-mcu/6361400</link><pubDate>Wed, 27 May 2026 21:16:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:35e613fb-1ec5-49f2-bc0e-7fef2f7cbbde</guid><dc:creator>Yamuna  Sundar</dc:creator><description>Hello Fleenor, Thank you very much for your detailed guidance on the troubleshooting steps. Creating a new target configuration file helped solve the issue and I am not seeing the error code 1170 when I debug the code.</description></item><item><title>Forum Post: RE: MSPM0G3507-Q1: BSL flash through UART on CCS</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649579/mspm0g3507-q1-bsl-flash-through-uart-on-ccs/6361391</link><pubDate>Wed, 27 May 2026 21:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:cd7c719b-5664-488b-8982-ea41b31170f2</guid><dc:creator>Crane Shao</dc:creator><description>Hello, Ok got it. Just curious what kind of monitor would work. Isn&amp;#39;t BSL Core in the MCU the kind of monitor? Thanks! Crane</description></item><item><title>Forum Post: RE: AM62L: OPTEE is not loaded with SDK11.2</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649829/am62l-optee-is-not-loaded-with-sdk11-2/6361370</link><pubDate>Wed, 27 May 2026 20:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9dc494b0-034c-4bfc-bfb4-599d13ce913c</guid><dc:creator>Hong Guan64</dc:creator><description>Hi Tony, I&amp;#39;m attaching two logs with AM62L Linux SDK 11.2.8.2 on AM62L EVM - am62l_11.2.8.2_optee_dbg.log: TRNG - am62l_11.2.8.2_optee_dbg_prng.log: PRNG Best, -Hong e2e.ti.com/.../am62l_5F00_11.2.8.2_5F00_optee_5F00_dbg.log e2e.ti.com/.../am62l_5F00_11.2.8.2_5F00_optee_5F00_dbg_5F00_prng.log</description></item><item><title>Forum Post: RE: AM2612: AM2612 SPI read parallel question</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649891/am2612-am2612-spi-read-parallel-question/6361367</link><pubDate>Wed, 27 May 2026 20:48:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b1298fe2-7181-4531-8e13-fe65dd09926d</guid><dc:creator>Fleenor</dc:creator><description>Hi Kita, Thank you for the detailed description of your customer&amp;#39;s application requirements. Yes, the AM2612 SDK can support simultaneous SPI communication on two hardware modules with polling-based completion checking. Here&amp;#39;s how to approach this: Parallel SPI Implementation Approach: Configure both SPI modules independently - Set up SPI0 and SPI1 (or your chosen modules) with identical timing parameters to handle 3 chip selects each (2 hardware CS + 1 software CS). Initiate transfers simultaneously - Use the SDK&amp;#39;s non-blocking transfer APIs to start communication on both SPI modules back-to-back without waiting for completion: MCSPI_transfer(spi0Handle, &amp;amp;spi0Transaction); MCSPI_transfer(spi1Handle, &amp;amp;spi1Transaction); Poll for completion - Check the transfer status registers for both modules in a tight loop: while(!MCSPI_isTransferComplete(spi0Handle) || !MCSPI_isTransferComplete(spi1Handle)); Repeat for remaining chip selects - Execute this pattern three times (once per chip select group) to complete all 6 channel reads. Expected Timing: Single 6-byte transfer: ~5 &amp;#181;s bus time + ~2 &amp;#181;s overhead = 7 &amp;#181;s Parallel 2-channel read: ~7 &amp;#181;s per iteration &amp;#215; 3 iterations = ~21 &amp;#181;s total This should meet your 30 &amp;#181;s requirement with margin Recommendations: Ensure both SPI modules are clocked from the same source for synchronization Use DMA if available to further reduce CPU overhead, though polling should be sufficient Verify CS timing meets your magnetic encoder specifications Please let me know which SDK version you&amp;#39;re using and if you need additional assistance implementing parallel SPI configuration and polling mechanism. Best Regards, Zackary Fleenor</description></item><item><title>Forum Post: RE: AM62P-Q1: AM62P-LP: Cold Boot Optimisation</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1646323/am62p-q1-am62p-lp-cold-boot-optimisation/6361348</link><pubDate>Wed, 27 May 2026 20:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:538ddf9a-827e-4557-a4a3-8449110d74f4</guid><dc:creator>Suren Porwar</dc:creator><description>Hi Thomas, The wic image should work on LCD1 as well, SK-LCD2 resolution is 1920x720 instead of 1920x1200 (SK-LCD1), the display should still be able to render graphics on it. Please give a try with the wic image, that I attached in my previous reply? We can get on a debug call, tomorrow if you are available in the afternoon. Best Regards Suren</description></item><item><title>Forum Post: RE: AM2612-Q1: AM2612 UART automatic RTS in MCAL</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649414/am2612-q1-am2612-uart-automatic-rts-in-mcal/6361345</link><pubDate>Wed, 27 May 2026 20:34:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ac49465a-34ed-4737-a5dc-eed9bcee987a</guid><dc:creator>Fleenor</dc:creator><description>Hi Kita, Thank you for your question regarding RS-485 automatic RTS control on the AM2612-Q1. Hardware Capability Confirmed The AM2612 UART hardware does support RS-485 mode with automatic direction control. According to the AM261x Technical Reference Manual (SPRUJB6B), the RS-485 external transceiver direction control is implemented through the UART_MDR3 register. RS-485 Configuration To enable RS-485 mode with automatic RTS direction control, configure the following register bits: UART_MDR3 DIR_EN - Set to 0x1 to enable RS-485 External Transceiver Direction UART_MDR3 DIR_POL - Sets the polarity for the RTS/DIR signal: 0 = TX: RTS=0, RX: RTS=1 1 = TX: RTS=1, RX: RTS=0 The hardware automatically monitors the TX FIFO and TX shift register to control the direction signal. When both are empty, the transceiver is set to RX mode. There is a guard band delay counter of 3 bit clock cycles after the TX shift register empties to allow time for the stop bit to transition through the transceiver before switching to receive mode. MCAL Configuration Since there may not be a direct RS-485 GUI option in the current MCAL version, you will need to configure RS-485 mode through direct register access. This can be done in a post-initialization callback or user configuration hook after the standard UART initialization: /* Enable RS-485 mode with automatic direction control */ UARTx-&amp;gt;MDR3 |= (1U MDR3 |= (1U &amp;lt;&amp;lt; 3U); /* DIR_POL - Set polarity (adjust based on your transceiver) */ Additional Verification Steps Confirm that the RTS/DIR pin is correctly assigned in your PINMUX/SysConfig settings Verify your MCAL version - newer releases may include explicit RS-485 configuration options Review section 13.1.4.4.8.2 &amp;quot;RS-485 Mode&amp;quot; in the AM261x TRM (SPRUJB6B) for complete details Check the MCU+ SDK for any RS-485 reference examples Reference Documentation AM261x Technical Reference Manual (SPRUJB6B), Section 13.1.4.4.8.2 UART_MDR3 Register details at offset 0x80h Please let me know if you need clarification on the register configuration or have additional questions about the implementation. Best Regards, Zackary Fleenor</description></item><item><title>Forum Post: RE: AM62P-Q1: AM62P-LP: Cold Boot Optimisation</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1646323/am62p-q1-am62p-lp-cold-boot-optimisation/6361332</link><pubDate>Wed, 27 May 2026 20:25:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:718a7686-fa11-4692-a941-d7fd92c28b31</guid><dc:creator>Thomas Carr</dc:creator><description>Hi Suren, For the YOCTO image error, yes, I included the error and the fix I needed to do from the instructions provided, this is with a fresh workspace and only the suggested changes being made, this is just showing that at least some things are missing from the instructions. My notes were originally written in MD so if the formatting is a bit hard to read please paste the contents into an MD editor. I&amp;#39;ll have another look through the SDK, the doc you pointed me to took me here: https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/11_01_05_03/exports/docs/linux/How_to_Guides/Target/How_to_boot_quickly.html#secondary-boot-loader-sbl I then followed onto here: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/latest/exports/docs/api_guide_am62px/TOOLS_BOOT.html#LINUX_APPIMAGE_GEN_TOOL And I followed the Falcon boot instructions from there. I am missing something, so please if you can give me detailed instructions of how to do this that would be immensely helpful. Also, I have an SK-LCD1 display, any chance you could complete a build with that dbc override so I can replicate on my hardware? Thanks Tom</description></item><item><title>Forum Post: RE: AM6421: MCU Plus SDK cross compatibility</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649540/am6421-mcu-plus-sdk-cross-compatibility/6361302</link><pubDate>Wed, 27 May 2026 20:05:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:08a7b2b5-ff05-4dfa-8e26-4447bf592714</guid><dc:creator>Joe Paolino</dc:creator><description>Hi Meet, As I re-read through the SysFW releases, we can definitely use the SA2UL timeout for DMA in Release 11, and the updated efuse timing parameters in 11.2. So with that I guess I could re-phrase the request for an 11.2 bootloader/SysFw and 10.1 Application. Are there any compatibility issues that would prevent that combo? Thank you, Joe</description></item><item><title>Forum Post: RE: MSPM0G3507-Q1: BSL flash through UART on CCS</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649579/mspm0g3507-q1-bsl-flash-through-uart-on-ccs/6361277</link><pubDate>Wed, 27 May 2026 19:41:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0871bbcc-aa5a-40b6-9c54-2e33e7791ab2</guid><dc:creator>Ki</dc:creator><description>Hello, [quote userid=&amp;quot;527652&amp;quot; url=&amp;quot;~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649579/mspm0g3507-q1-bsl-flash-through-uart-on-ccs&amp;quot;]Does the below config in CCS work to flash the MCU on LanuchPad through UART?[/quote] However the primary use of the &amp;quot;UARTConnection&amp;quot; is to enable GUI Composer access to target memory via UART. It requires a monitor running on the target and not really meant for use beyond that use case. Thanks ki</description></item><item><title>Forum Post: TIDM-BIDIR-400-12: TIDM-BIDIR-400-12 schematic source request: PADS ASCII / Altium / OrCAD format</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649994/tidm-bidir-400-12-tidm-bidir-400-12-schematic-source-request-pads-ascii-altium-orcad-format</link><pubDate>Wed, 27 May 2026 19:23:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:27a5ce67-44fd-4a80-96f7-fd6224dcae09</guid><dc:creator>Sourabh Bodige</dc:creator><description>Part Number: TIDM-BIDIR-400-12 Other Parts Discussed in Thread: CONTROLSUITE , C2000WARE Hi TI team, We are using the TIDM-BIDIR-400-12 reference design as a starting reference for an in-house medical UPS bidirectional DC-DC converter design. Our target application is approximately 400 W, with 12 V / 24 V battery support and a 390–400 V HV DC bus. The design files we currently have from C2000Ware / controlSUITE include: SCH_{TXN010}_BiDirDCDC_rD.zip Inside that archive: SCH_BiDirDCDC_07_09_14_HN.sch A .asc file that appears to be a PADS PowerPCB ASCII netlist BOM in Excel Gerbers TI design guide / schematic PDFs, including tidrhs9 and tidrht0 The .sch file appears to be a PADS Logic binary schematic file from around 2014. Our hardware engineering team uses Altium Designer, but this binary .sch file does not import cleanly into Altium. The .asc file appears to be a netlist rather than a schematic ASCII export, so it also does not work as an editable schematic import source. Request: Is it possible to obtain the TIDM-BIDIR-400-12 schematic in any of the following alternative formats? PADS Logic ASCII schematic export Example: .txt file exported from PADS Logic using File → Export → ASCII Altium Designer project files Example: .PrjPcb / .SchDoc OrCAD Capture schematic Example: .dsn Even just the PADS Logic ASCII schematic export would be very helpful, since Altium can typically import that format more reliably than the binary PADS schematic file. We are not looking to redistribute the files. This is for internal engineering reference only, to review the TI power-board schematic and accurately map the controller and power-stage connections for our own board design. Could you please confirm the correct CAD tool/version used for the original schematic and whether TI can provide one of the alternative schematic formats above? Thanks,</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/ControlSUITE">ControlSUITE</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/C2000Ware">C2000Ware</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/TIDM_2D00_BIDIR_2D00_400_2D00_12">TIDM-BIDIR-400-12</category></item><item><title>Forum Post: RE: AM62P-Q1: AM62P-LP: Cold Boot Optimisation</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1646323/am62p-q1-am62p-lp-cold-boot-optimisation/6361253</link><pubDate>Wed, 27 May 2026 19:15:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8cf84ccf-1ddb-4d84-9f5e-8a5b9d8d37e2</guid><dc:creator>Suren Porwar</dc:creator><description>Hi Thomas, From the attached log, I do see there are errors when compiling the yocto image and also you haven&amp;#39;t followed the instructions provided in the MCU+SDK to disable the logs(As I still see the System Init... and other logs being shown). Attaching a wic image that I had created with all the above mentioned changes and tested with SK-LCD2 Display connected to my AM62P board. e2e.ti.com/.../coreimage_2D00_11.1_2D00_lcd2.wic_2800_1_2900_.xz There is a demo folder in the boot partition which has the MCU+SDK images that i created and flash those on the NOR. u-boot-commands.txt file should have all the commands to run as well. Hope this helps Best Regards Suren</description></item><item><title>Forum Post: AM2612: AM2612 PROFINET DEVICE DEMO</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649984/am2612-am2612-profinet-device-demo</link><pubDate>Wed, 27 May 2026 18:25:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0e3da904-6fb1-4a00-b603-3e6f36fe3fd3</guid><dc:creator>ENIS SARAC</dc:creator><description>Part Number: AM2612 We are trying to run profinet_device_demo provided. we are using ccs 20.5.1.12 and LP-A261 but program exit form _system_pre_init any help will be appreciated. in adition what is the differnec between ind_comms_sdk eval and prod versions best regards Enis</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/AM2612">AM2612</category></item><item><title>Forum Post: RE: TM4C1231C3PM: The MCU is not detected in Uniflash and shows: “Error 1170@0x00 – Target not connected”</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1648869/tm4c1231c3pm-the-mcu-is-not-detected-in-uniflash-and-shows-error-1170-0x00-target-not-connected/6361164</link><pubDate>Wed, 27 May 2026 18:15:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:016a975d-c0ef-4f0e-ab15-f4e76d8bc3c3</guid><dc:creator>Eric Rentschler</dc:creator><description>Hi Deepan, Can you try to use the LM Flash Programmer tool to erase the flash and get the mcu back to a factory state? Tool is located here . Thanks, -Eric Rentschler</description></item><item><title>Forum Post: RE: TM4C129DNCPDT: Subject: Timer0A interrupt not firing in TivaWare (TM4C) – Timer running but ISR not executingTimer ISR interrupt is not occuring</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1648632/tm4c129dncpdt-subject-timer0a-interrupt-not-firing-in-tivaware-tm4c-timer-running-but-isr-not-executingtimer-isr-interrupt-is-not-occuring/6361161</link><pubDate>Wed, 27 May 2026 18:12:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:cd22452c-f720-4aea-9dda-951f226a84d5</guid><dc:creator>Eric Rentschler</dc:creator><description>Hi Sarath, In the timers.c example in the SDK, the interrupts are configured in a different order, IntMasterEnable first, IntEnable second, and TimerIntEnable last. Can you try this order and let me know if the issue still persists? Thanks, -Eric Rentschler</description></item><item><title>Forum Post: MSPM0L1117: Does MSPM0L1117 Support Mutli-Word Programming?</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649964/mspm0l1117-does-mspm0l1117-support-mutli-word-programming</link><pubDate>Wed, 27 May 2026 17:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:db4c8a20-c17f-4e90-9aeb-faa12dbe8a99</guid><dc:creator>Chris W</dc:creator><description>Part Number: MSPM0L1117 I see enum DL_FLASHCTL_COMMAND_SIZE below in the flash driver but I do not see any write routies for sizes greater than one word (64-bit). If I try to write data to FLASHCTL.CMDDATA2 (0x400ce138) it will not take but no error is asserted. I assume this means multi-word programming is not supported however, I can not explicitly find this statement in any documentation (datasheet or reference manual). /*! @enum DL_FLASHCTL_COMMAND_SIZE */ typedef enum { /*! Flash Command size is one word */ DL_FLASHCTL_COMMAND_SIZE_ONE_WORD = FLASHCTL_CMDTYPE_SIZE_ONEWORD, /*! Flash Command size is two words */ DL_FLASHCTL_COMMAND_SIZE_TWO_WORDS = FLASHCTL_CMDTYPE_SIZE_TWOWORD, /*! Flash Command size is four words */ DL_FLASHCTL_COMMAND_SIZE_FOUR_WORDS = FLASHCTL_CMDTYPE_SIZE_FOURWORD, /*! Flash Command size is eight words */ DL_FLASHCTL_COMMAND_SIZE_EIGHT_WORDS = FLASHCTL_CMDTYPE_SIZE_EIGHTWORD, /*! Flash Command size is a sector */ DL_FLASHCTL_COMMAND_SIZE_SECTOR = FLASHCTL_CMDTYPE_SIZE_SECTOR, /*! Flash Command size is a bank */ DL_FLASHCTL_COMMAND_SIZE_BANK = FLASHCTL_CMDTYPE_SIZE_BANK } DL_FLASHCTL_COMMAND_SIZE;</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/MSPM0L1117">MSPM0L1117</category></item><item><title>Forum Post: RE: SW-EK-LM4F120XL: can not download SW-EK-TM4C1294XL-2.2.0.295.exe/SW-TM4C-2.2.0.295.exe</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649223/sw-ek-lm4f120xl-can-not-download-sw-ek-tm4c1294xl-2-2-0-295-exe-sw-tm4c-2-2-0-295-exe/6361000</link><pubDate>Wed, 27 May 2026 16:24:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d8add2e7-c25e-455a-9349-83abdf48aea3</guid><dc:creator>Erik Vaughn</dc:creator><description>Could you try this link: https://www.ti.com/tool/download/SW-TM4C For the TM4C1294 I believe it should be the above not the stellaris device.</description></item><item><title>Forum Post: AM6442: AM6442 with TPS65224-Q1 PMIC Query on ADC section</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649944/am6442-am6442-with-tps65224-q1-pmic-query-on-adc-section</link><pubDate>Wed, 27 May 2026 15:42:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0b736c2b-d803-408c-9cc0-990e6e4e6666</guid><dc:creator>Mythili Balakrishnan</dc:creator><description>Part Number: AM6442 Other Parts Discussed in Thread: TPS65224-Q1 Hi, We are working on a custom platform based on AM64x processor, where we are using the TPS65224-Q1 PMIC. In our design, GPIO4 of the TPS65224-Q1 is configured as an input to the PMIC’s internal 12-bit ADC block. Through an external multiplexer, we plan to provide the following voltages to the ADC input pin: 1. 0.75 V 2. 0.85 V 3. 1.1 V 4. 1.8 V 5. 3.3 V Could you please guide us on how to test and validate the ADC capture functionality in the AM64x Linux SDK 11.02 environment. Any guidance or reference documentation would be helpful.</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/TPS65224_2D00_Q1">TPS65224-Q1</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/Robotics">Robotics</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/AM6442">AM6442</category></item><item><title>Forum Post: RE: MSPM0C1104: Factory Reset does not work</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1649389/mspm0c1104-factory-reset-does-not-work/6360931</link><pubDate>Wed, 27 May 2026 15:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:803fdaa0-2632-4758-b6b9-ac98c479f62e</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi RH, This message normally means that your SWD connections are good (since you can connect to other cores) but the device is locked/bricked. Can you try the following and see if it unlocks the device: 1. Disconnect the LaunchPad from power 2. Open a Uniflash session for the device (Check both device and debugger, or select the launchpad image) 3. Press and hold the NRST button (S3). 4. Connect the LaunchPad to power while continuing to hold the NRST button 5. Click on the &amp;quot;Setting &amp;amp; Utilities&amp;quot; tab and click on/Issue a manual Factory Reset DSSM command 6. Release the NRST button when the console prompts you to press the NRST button Best Regards, Diego Abad</description></item></channel></rss>