<?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>MSP low-power microcontrollers</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/</link><description>Welcome to the MSP Low-Power Microcontrollers Section of the TI E2E Support Community, with support for MSP430™︎ and MSP432™︎ products. Ask questions, share knowledge, explore ideas, and help solve problems with fellow engineers.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification Request Regarding Safety Mechanism TIM6 – Timer Period Monitoring</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696878/mspm0g3218-q1-clarification-request-regarding-safety-mechanism-tim6-timer-period-monitoring/6545075</link><pubDate>Sat, 21 Nov 2026 03:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:71345f46-95e9-4658-98fa-5620746b022b</guid><dc:creator>Due Vo</dc:creator><description>Hello Abad, We can close this ticket now. Thank you very much. Best regards, Due Vo</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification Request Regarding Safety Mechanism TIM6 – Timer Period Monitoring</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696878/mspm0g3218-q1-clarification-request-regarding-safety-mechanism-tim6-timer-period-monitoring/6545073</link><pubDate>Sat, 21 Nov 2026 03:27:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d67f5754-2c64-4b57-a662-4fa132740c25</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, This is also confirmed. Meant to add it to my original response. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on WDT3: WWDT Software Test Execution Frequency</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696887/mspm0g3218-q1-clarification-on-wdt3-wwdt-software-test-execution-frequency/6545072</link><pubDate>Sat, 21 Nov 2026 03:21:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ff2609c6-7740-48ce-a26d-d51945745711</guid><dc:creator>Due Vo</dc:creator><description>Hello Abad, We can close this ticket now. Thank you very much. Best regards, Due Vo</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on WDT3: WWDT Software Test Execution Frequency</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696887/mspm0g3218-q1-clarification-on-wdt3-wwdt-software-test-execution-frequency/6545070</link><pubDate>Sat, 21 Nov 2026 03:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2fcf1817-b988-421d-9955-5748297ef1b6</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due Vo , WDT3 is for detecting latent fault and it is a startup test (at the beginning). At power-up, we initialize it (with smaller window) than do the test and during application we must re-initialize the watchdog for reset/nmi. It should be fine to check the self-test during start-up. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on REF2: VREF to ADC Reference Input Safety Mechanism</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696885/mspm0g3218-q1-clarification-on-ref2-vref-to-adc-reference-input-safety-mechanism/6545069</link><pubDate>Sat, 21 Nov 2026 03:16:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8046b8db-aef0-4926-b99d-c8f3316dacd2</guid><dc:creator>Due Vo</dc:creator><description>Hello Abad, We can close this ticket now. Thank you very much. Best regards, Due Vo</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification Request Regarding Safety Mechanism TIM6 – Timer Period Monitoring</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696878/mspm0g3218-q1-clarification-request-regarding-safety-mechanism-tim6-timer-period-monitoring/6545067</link><pubDate>Sat, 21 Nov 2026 03:14:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8ac91869-8396-4f34-ba92-87a0df179a94</guid><dc:creator>Due Vo</dc:creator><description>Hello Abad, Can you further check the below point? Furthermore, if this concept is appropriate, should Timer 1 and Timer 2 be configured to use independent clock sources to ensure sufficient diagnostic coverage and avoid common-cause failures? Thank you very much. Best regards, Due Vo</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on REF2: VREF to ADC Reference Input Safety Mechanism</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696885/mspm0g3218-q1-clarification-on-ref2-vref-to-adc-reference-input-safety-mechanism/6545066</link><pubDate>Sat, 21 Nov 2026 03:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:82e4ab40-4f89-4b8e-a539-fd551b679bec</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, My team confirmed that REF2 won’t apply since an external reference is being used. Also, it does not impact the ADC subsystem directly since the assumption from MSPM0 is that the external VREF works without issues. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification Request Regarding Safety Mechanism TIM6 – Timer Period Monitoring</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696878/mspm0g3218-q1-clarification-request-regarding-safety-mechanism-tim6-timer-period-monitoring/6545065</link><pubDate>Sat, 21 Nov 2026 03:09:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4a66ff00-5063-4ee7-a435-7fcd776e31b8</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, My team confirmed this is a valid approach for this application and the Safety Mechanism. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0L2228: LCD Current Consumption and Contrast: 4-MUX vs. 8-MUX</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1698615/mspm0l2228-lcd-current-consumption-and-contrast-4-mux-vs-8-mux/6544750</link><pubDate>Fri, 20 Nov 2026 17:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5ef9020f-3d5f-4357-a172-c9c71ebc536a</guid><dc:creator>Owen Li</dc:creator><description>Hi Ibuki, We do not have a spec for the LCD-related current consumption between 4 mux mode and 8 mux mode. Our architecture team does not believe there should be a significant change in current between the two LCD configurations. The LCD contrast will decrease, but we do not have any measured data for the 8-mux mode specifically. Here&amp;#39;s what we have documented that may help provide an idea of what to expect: Best, Owen</description></item><item><title>Forum Post: RE: MSPM33C321A-Q1: IAR with JLINK issue</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1693494/mspm33c321a-q1-iar-with-jlink-issue/6544725</link><pubDate>Fri, 20 Nov 2026 17:19:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c9a2549b-9c77-4b84-ac6a-bea48af36648</guid><dc:creator>JOJO ARTHUR</dc:creator><description>Hello Sophie, Do you have any updates on this case? Best Regards, Benedict Jojo</description></item><item><title>Forum Post: RE: MSP430-SDK: [MSP430F5529] How to increases the working frequency from 4 MHz crystal?</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1699295/msp430-sdk-msp430f5529-how-to-increases-the-working-frequency-from-4-mhz-crystal/6544655</link><pubDate>Fri, 20 Nov 2026 16:24:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:bd62136f-bc38-499d-a3df-ac307adc5b34</guid><dc:creator>Bruce McKenney</dc:creator><description>It appears you can use XT2 as the FLL reference input (SELREF=5) and use the (stabilized) DCO [I haven&amp;#39;t tried it with XT2, but the User Guide says it&amp;#39;s OK [Ref UG (SLAU208Q) Sec 5.2.5]]. You just need to choose appropriate divisor/multiplier values; you might start with FLLD=1 [/2] and FLLN=(12-1) [*12] for 4MHz/2*12-&amp;gt;24MHz. I think you also need DCORSEL=5. I don&amp;#39;t see an Example which exactly matches what you&amp;#39;re doing, but MSP430F55xx_UCS_04.c (FLL with XT1) and MSP430F55xx_UCS_10.c (high-speed operation with DCO) should get you started.</description></item><item><title>Forum Post: RE: MSPM33C321A-Q1: Create Zephyr DTS (Device Tree) automatically</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1699062/mspm33c321a-q1-create-zephyr-dts-device-tree-automatically/6544352</link><pubDate>Fri, 20 Nov 2026 09:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:68ff1d43-e452-4ece-b27a-10fdb73851ff</guid><dc:creator>Xiaodong LI</dc:creator><description>Hi Til I will check with team and reply to you later Thanks</description></item><item><title>Forum Post: MSP430-SDK: [MSP430F5529] How to increases the working frequency from 4 MHz crystal?</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1699295/msp430-sdk-msp430f5529-how-to-increases-the-working-frequency-from-4-mhz-crystal</link><pubDate>Fri, 20 Nov 2026 03:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b9dbf644-5a8a-49ed-a71c-d000df48932e</guid><dc:creator>Ted Wu</dc:creator><description>Part Number: MSP430-SDK Other Parts Discussed in Thread: MSP430F5529 Hi friend, We have two projects, both using the MSP430F5529 single-chip microcontroller. One project needs to implement SPI master and USB CDC functionality, while the other needs to implement SPI slave functionality. We are using a 4MHz crystal oscillator. How can we increase the operating frequency of these two projects to 24MHz? If we replace the crystal oscillator with an 8MHz one, how can we increase the operating frequency of these two projects to 24MHz? Best regards, Ted Wu</description><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/MSP430_2D00_SDK">MSP430-SDK</category><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/MSP430F5529">MSP430F5529</category></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on REF2: VREF to ADC Reference Input Safety Mechanism</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696885/mspm0g3218-q1-clarification-on-ref2-vref-to-adc-reference-input-safety-mechanism/6544012</link><pubDate>Fri, 20 Nov 2026 02:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f441d9a8-a017-4540-8027-4d7744be5fbe</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, I&amp;#39;m still waiting for the feedback. I sent a reminder email to my team. As mentioned in other threads, I&amp;#39;ll be out until the 3rd, so further communications should be rely to your assigned FAE. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification on WDT3: WWDT Software Test Execution Frequency</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696887/mspm0g3218-q1-clarification-on-wdt3-wwdt-software-test-execution-frequency/6544013</link><pubDate>Fri, 20 Nov 2026 02:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:14f82f6e-1ce3-47ef-9e08-006aba54449c</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, I&amp;#39;m still waiting for the feedback. I sent a reminder email to my team. As mentioned in other threads, I&amp;#39;ll be out until the 3rd, so further communications should be rely to your assigned FAE. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3218-Q1: Clarification Request Regarding Safety Mechanism TIM6 – Timer Period Monitoring</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1696878/mspm0g3218-q1-clarification-request-regarding-safety-mechanism-tim6-timer-period-monitoring/6544011</link><pubDate>Fri, 20 Nov 2026 02:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:49cca9ac-7110-48f6-8a8f-0c82b7b758de</guid><dc:creator>Diego Abad Sajamin</dc:creator><description>Hi Due, I&amp;#39;m still waiting for the feedback. I sent a reminder email to my team. As mentioned in other threads, I&amp;#39;ll be out until the 3rd, so further communications should be rely to your assigned FAE. Best Regards, Diego Abad</description></item><item><title>Forum Post: RE: MSPM0G3518-Q1: Internal temperature sensor with external reference of 3.3V connected</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1698989/mspm0g3518-q1-internal-temperature-sensor-with-external-reference-of-3-3v-connected/6543416</link><pubDate>Thu, 19 Nov 2026 14:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8a02d59f-9597-4b34-b7fb-b0da09079777</guid><dc:creator>Purva Patil</dc:creator><description>Hi Pengfei, Thank you for the response. In the example mentioned in adc12_internal_temp_sensor_mathacl , the values for TRIM_C, TSc, DL_SYSCTL_getTempCalibrationConstant() which is stored in the memory uses internal reference of 1.4V . Could you please share the scale up values for these parameters for external 3.3V reference? We had referred MSPM0G3519: MSPM0G3519 : Internal temperature measurement issue - Arm-based microcontrollers forum -… , it showed coefficients for internal 1.4V instead of 3.3V VDDA. We have the boards with us which has external reference of 3.3V, it is difficult for us to make modifications on hardware level, could you please help with this? Regards, Purva Patil</description></item><item><title>Forum Post: RE: MSPM0G3518-Q1: Internal temperature sensor with external reference of 3.3V connected</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1698989/mspm0g3518-q1-internal-temperature-sensor-with-external-reference-of-3-3v-connected/6543382</link><pubDate>Thu, 19 Nov 2026 13:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:37ed9300-d898-491c-9555-d05a05dac456</guid><dc:creator>Pengfei Xie</dc:creator><description>Hi Purva, You are not able to use internal reference and external reference at the same time. When VREF is in external mode, it will get voltage input from VREF+ pin. When VREF is in internal mode, it will output voltage to VREF+. So if you use internal 1.4V VREF, and connect 3.3V on VREF+ pin, it will cause issue as you see large current in your test. There is no problem to use temperature sensor with external reference, you just need to configure the VREF module as external reference mode as you did for other ADC channels. But there is no trim data for 3.3V reference as the spec in datasheet is tested in 1.4V. But you could refer to SDK example adc12_internal_temp_sensor_mathacl for temperature calculation under 3.3V reference (the example use VDD as reference but the voltage is 3.3V)</description></item><item><title>Forum Post: MSPM33C321A-Q1: Create Zephyr DTS (Device Tree) automatically</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1699062/mspm33c321a-q1-create-zephyr-dts-device-tree-automatically</link><pubDate>Thu, 19 Nov 2026 09:26:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:285f3c4f-11ef-4532-8733-d3202a55ce4c</guid><dc:creator>Til Schoengarth</dc:creator><description>Part Number: MSPM33C321A-Q1 Other Parts Discussed in Thread: SYSCONFIG Hi team, is it possible to create the .dts file in zephyr, i.e. the Device tree config with a TI GUI? Similar to how SysConfig is configuring the device for FreeRTOS applications? If not is there a plan in the future to have a GUI tool for this? And is the .dts in the TI Zephyr Release manually or automatically created? Thanks! Til</description><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/Infotainment%2b_2600_amp_3B00_%2bCluster">Infotainment &amp;amp; Cluster</category><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/MSPM33C321A_2D00_Q1">MSPM33C321A-Q1</category><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/SYSCONFIG">SYSCONFIG</category></item><item><title>Forum Post: MSPM0G3518-Q1: Internal temperature sensor with external reference of 3.3V connected</title><link>https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1698989/mspm0g3518-q1-internal-temperature-sensor-with-external-reference-of-3-3v-connected</link><pubDate>Thu, 19 Nov 2026 05:57:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5015bc19-9cf2-4ad5-8d4e-5cd6c9923cb7</guid><dc:creator>Purva Patil</dc:creator><description>Part Number: MSPM0G3518-Q1 Hello TI team, We are facing issue with temperature sensor reading. I have connected external reference as well since we need it for other analog readings, when we try to enable internal reference of 1.4V for internal temperature sensing, the current drawn by the board increases from 4mA to 20mA. The raw adc count we get is 780, even if internal /external ref is selected Can we read the temperature using external reference? If we connect external 3.3V ref, does it cause any issue?Is there a way to turn off the internal Vref with any settings? Within the ref manual section 23.2.2, “Only one type of reference (internal or external) can be selected at a Time”, but how do we use internal reference without current being ramped up? Can we get the TRIM and TSC temperature coefficients equivalent to 3.3V reference so that temperature sensor could be measured with external 3.3V reference voltage? Datasheet has coefficients only for 1.4V internal reference. Could you please help on this issue? Regards, Purva</description><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/Industrial%2bAutomation">Industrial Automation</category><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/MSPM0G3518_2D00_Q1">MSPM0G3518-Q1</category><category domain="https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/tags/MSPM0G3519">MSPM0G3519</category></item></channel></rss>