<?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: AM263P4: Re-Post of "DO-178C certification concerns regarding R5F ROM and HSM ROM"</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1687176/am263p4-re-post-of-do-178c-certification-concerns-regarding-r5f-rom-and-hsm-rom/6539123</link><pubDate>Mon, 16 Nov 2026 00:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3349897f-b174-44cc-aac5-e666d6f79ca6</guid><dc:creator>Shaunak Deshpande</dc:creator><description>Hi Liam, Apologies for this taking so long. Let me reach out to the concerned team again regarding the NDA. Regards, Shaunak</description></item><item><title>Forum Post: RE: AM263P4-Q1: Clarification on OSPI Controller IDLE Bit Timeout and Flash Reset Pulse Duration</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697012/am263p4-q1-clarification-on-ospi-controller-idle-bit-timeout-and-flash-reset-pulse-duration/6539107</link><pubDate>Sun, 15 Nov 2026 18:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1ea814ce-4946-407a-8ed2-6c4aa6df1433</guid><dc:creator>Aswin Sankar</dc:creator><description>Hi, [quote userid=&amp;quot;637661&amp;quot; url=&amp;quot;~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697012/am263p4-q1-clarification-on-ospi-controller-idle-bit-timeout-and-flash-reset-pulse-duration&amp;quot;] 1. OSPI Controller IDLE Bit – Maximum Wait Time [/quote] No specific timeout value is mentioned in the TRM/RA for this bit, however the SDK is using a timeout of 500us. You could also use that as a timeout value. RA only mentions that, this bit will have some inherent delay. [quote userid=&amp;quot;637661&amp;quot; url=&amp;quot;~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697012/am263p4-q1-clarification-on-ospi-controller-idle-bit-timeout-and-flash-reset-pulse-duration&amp;quot;] 2. Flash Device Reset – Reset Pulse Duration [/quote] This is a property of the flash. For example, in IS25LX256 Flash you can refer to reset recovery specification in the Flash datasheet.</description></item><item><title>Forum Post: AM2432: AM2432 Burst Read Issue (using UDMA)</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697754/am2432-am2432-burst-read-issue-using-udma</link><pubDate>Sun, 15 Nov 2026 18:26:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:cc737b62-489c-4cd8-89b0-0eabf88db5e5</guid><dc:creator>Juheon Woo</dc:creator><description>Part Number: AM2432 Hi TI experts, I am trying to use burst mode (via UDMA) to read data from an FPGA (configured as NOR flash device), but the data I read in the end on the MCU side seems to be corrupted. The waveform capture shows the data I am supposed to be reading, and the debug statements show the actual data that I am reading on the MCU. It looks like possibly the timing that the MCU is capturing the read data might be off, but I am not sure what configurations I need to fix in this case as I have already tried different GPMC timing configurations for the read cycle. I have also attached the GPMC_CONFIG register settings and the DMA packet setup I have currently as a context. Thank you so much for the help.</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/AM2432">AM2432</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/Test%2b_2600_amp_3B00_%2bMeasurement">Test &amp;amp; Measurement</category></item><item><title>Forum Post: RE: AM2634-Q1: CAN Tx Failure on Frame A in MCAL</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697502/am2634-q1-can-tx-failure-on-frame-a-in-mcal/6539089</link><pubDate>Sun, 15 Nov 2026 04:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6ac1f4f9-bacb-4640-9372-e273f726a8d0</guid><dc:creator>Jenney Ni</dc:creator><description>Hi Pranav, What issues can this trigger? Could it cause blocking? Regards, Jenney</description></item><item><title>Forum Post: RE: AM2634-Q1: CAN Tx Failure on Frame A in MCAL</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697502/am2634-q1-can-tx-failure-on-frame-a-in-mcal/6539064</link><pubDate>Sat, 14 Nov 2026 11:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:127470d0-750b-4324-a150-d46d1e7e6fa2</guid><dc:creator>Pranav Siddappa</dc:creator><description>Hi Jenny, #3: Ideally these functions should not be left empty. These functions are used to make a piece of code &amp;quot;atomic&amp;quot;. Atomic means that when a piece of code is running, nothing else should make any other changes, this includes interrupts. So in the Schms functions we usually disable interrupts so nothing can preempt this piece of code. You can take a look at the CAN example for a sample implementation of the schm function. The actual implementation varies based on the AUTOSAR vendor and the application. Having these are empty will basically lead to race conditions for editing variables or parameter which are crucial for driver&amp;#39;s correct functionality. So different parts of the driver can overwrite a variable or param during use which might cause an issues Regards, Pranav Siddappa</description></item><item><title>Forum Post: RE: AM2634-Q1: CAN Tx Failure on Frame A in MCAL</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697502/am2634-q1-can-tx-failure-on-frame-a-in-mcal/6539063</link><pubDate>Sat, 14 Nov 2026 11:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7dc65bfe-9733-49a7-ae2a-1820d4b1991d</guid><dc:creator>Jenney Ni</dc:creator><description>Hi Pranav, for #1 question: Customer cannot reproduce this issue on bench now. Only found it in the aftermarket&amp;#39;s vehicles which cannot debug. So they cannot confirm it. for #2 question: The only difference of A and B is freeHwObjectCount. I will check the object name of Frame B later. for #3 question: Customer don&amp;#39;t have the implementation of SchM_Enter_Can_CAN_EXCLUSIVE_AREA_0() and SchM_Exit_Can_CAN_EXCLUSIVE_AREA_0() in the upper layer of the AUTOSAR stack. they want to know where there is risk? Regards, Jenney</description></item><item><title>Forum Post: RE: AM13E23019: AM13E23019 debug breakpoint failure</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1696134/am13e23019-am13e23019-debug-breakpoint-failure/6538990</link><pubDate>Fri, 13 Nov 2026 23:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:30a71511-c550-45a1-bf08-c84afc07c378</guid><dc:creator>Delaney Woodward</dc:creator><description>Hi Simon, I will reply back again early next week. Best Regards, Delaney</description></item><item><title>Forum Post: RE: MSPM0G3519-Q1: Undefined behavior with ARM-CGT-CLANG 5.1.0.LTS using option "-mmathacl"</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697647/mspm0g3519-q1-undefined-behavior-with-arm-cgt-clang-5-1-0-lts-using-option--mmathacl/6538929</link><pubDate>Fri, 13 Nov 2026 21:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b117d0ec-49ec-4d82-9c10-06d25523aa5c</guid><dc:creator>James Nagurne</dc:creator><description>Thank you for the descriptive report. I was able to reproduce this without a test case and have filed https://sir.ext.ti.com/jira/browse/EXT_EP-13786 to track the defect. As a workaround, you can keep -mmathacl for this release. This will impact performance negatively.</description></item><item><title>Forum Post: RE: AM2634-Q1: AM2634-Q1: Sysconfig 1.28.0+4712 generates broken code for MCSPI LLD and HLD drivers.</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697448/am2634-q1-am2634-q1-sysconfig-1-28-0-4712-generates-broken-code-for-mcspi-lld-and-hld-drivers/6538899</link><pubDate>Fri, 13 Nov 2026 20:45:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f710a09e-5ba0-4f61-aa01-6cb42c407b2b</guid><dc:creator>Eugene K</dc:creator><description>I disagree that current SDK examples are representative of the features of the IP. They are very simple and not highlighting the real use of the SDK drivers. I would like to see error handling examples, timeouts, heterogenous configurations etc. As for our use case we have multiple &amp;quot;smart&amp;quot; devices connected to different MCSPI instances. Some of the devices share the same MCSPI instance. Some require very fast response (SPI message sent within microseconds) to external stimuli, and some do not. All of the devices use multi-word protocol of different message sizes even on the same MCSPI instance and thus MCSPI HW IP with auto CS control is not applicable (as noted in TRM and here MCU-PLUS-SDK-AM263X: MCSPI CS issue/workaround for Multi-channel mode (SDK version 9.02) - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums ). Regards, Eugene</description></item><item><title>Forum Post: RE: MSPM0L1306: circumstances under which Uniflash can unlock a JTAG locked M0</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1695854/mspm0l1306-circumstances-under-which-uniflash-can-unlock-a-jtag-locked-m0/6538888</link><pubDate>Fri, 13 Nov 2026 20:14:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0eac34ba-aeaa-45f8-82b8-bf472f9154ab</guid><dc:creator>Chris</dc:creator><description>Zoey, Thanks. I can see these commands. I&amp;#39;m unable to find the input for the password, however. Where can I find this?</description></item><item><title>Forum Post: RE: AM2634-Q1: AM2634-Q1: AM263x SDK LLD MCSPI does not use timeout in miltiple APIs</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697409/am2634-q1-am2634-q1-am263x-sdk-lld-mcspi-does-not-use-timeout-in-miltiple-apis/6538858</link><pubDate>Fri, 13 Nov 2026 19:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:765dad91-347c-4a13-9d80-6aa29d659789</guid><dc:creator>Pranav Siddappa</dc:creator><description>Hi Eugene, I agree this has turned out to be an inconvenience. The bugs reported by you do indicate the need for a clean up. Please allow me some to track the status of the issues reported. I will report back to you with a response on this from the dev team. Regards, Pranav Siddappa</description></item><item><title>Forum Post: RE: AM2634-Q1: AM2634-Q1: Sysconfig 1.28.0+4712 generates broken code for MCSPI LLD and HLD drivers.</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697448/am2634-q1-am2634-q1-sysconfig-1-28-0-4712-generates-broken-code-for-mcspi-lld-and-hld-drivers/6538851</link><pubDate>Fri, 13 Nov 2026 19:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a7e6490c-c34a-4444-b079-2838ab212681</guid><dc:creator>Pranav Siddappa</dc:creator><description>Hi Eugene, The bug reported in: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1692756/am2632-q1-am263x-sdk-26-00-00-sysconfig-1-28-0-4712-generates-incorrect-code-for-multi-channel-mcspi-configuration , has been fixed internally. I am checking for when a release can be prepared. Since the issue in this thread is also a bug, i will keep you informed on the status of this as well. [quote userid=&amp;quot;636987&amp;quot; url=&amp;quot;~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697448/am2634-q1-am2634-q1-sysconfig-1-28-0-4712-generates-broken-code-for-mcspi-lld-and-hld-drivers/6538748&amp;quot;]Should SDK examples be more representative of the use cases like this one?[/quote] -&amp;gt; The SDK examples are only to be used as reference which cover the basic features of the IP. I will check internally if its feasible to add more examples. Despite this there may be a chance that some scenarios will be missed, which seems to be case now as well. Can i get more idea on what you are trying to use MCSPI for in your project? If i get a better idea of the requirement, i might be able to a preliminary check of the APIs and the driver flow. Regards, Pranav Siddappa</description></item><item><title>Forum Post: RE: AM13E23019: AM13E23019 debug breakpoint failure</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1696134/am13e23019-am13e23019-debug-breakpoint-failure/6538847</link><pubDate>Fri, 13 Nov 2026 19:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1dcfe411-b7a9-45e1-81a7-daf7267021f8</guid><dc:creator>Simon Bj&amp;#246;rklund</dc:creator><description>Hello Delaney The checked optimisation flag was -g, so optimisation for debugging. I tried also by turning off optimisation with -0 flag but no change in the behaviour. The default baudrate in the example for UART comm port communication is 9 200 000 which is very high, so thinking that it might occasionally saturate the shared USB line I lowered it, but no effect. I can see that the code is properly running that segment because by share luck I can stop it there by manually halting the repeatedly. So not sure what is going on. BR</description></item><item><title>Forum Post: RE: TIDA-010955: TIDA-010955 Arc Fault truncating value</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697451/tida-010955-tida-010955-arc-fault-truncating-value/6538835</link><pubDate>Fri, 13 Nov 2026 18:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b07153e9-e25f-4e3a-8a6f-eadd9adb90cb</guid><dc:creator>Elena Ilic</dc:creator><description>For more clarification on my first question: In run_feature_extraction: //load the data into RAM first to reduce the reading time from Flash memory tvmgen_default_bias_data_0 = tvmgen_default_bias_data[0]; tvmgen_default_scale_data_0 = tvmgen_default_scale_data[0]; tvmgen_default_shift_data_0 = tvmgen_default_shift_data[0]; tvmgen_default_bias_data_0 is an int while tvmgen_default_bias_data[] is an array of floats. Then in model_input_conversion: float temp_add_bias; // biasing, scaling and shifting to convert floating model input to fixed point model input temp_add_bias = model_input_float + tvmgen_default_bias_data_0; int32_t scale = (int32_t)floorf(temp_add_bias * tvmgen_default_scale_data_0); The value is added to a float and stored to a float, and the eventual final answer is cast to int anyways, so I&amp;#39;m a bit confused on what is the purpose of immediately casting tvmgen_default_bias_data[0] to an int rather than keeping as a float?</description></item><item><title>Forum Post: RE: AM2634-Q1: AM2634-Q1: Sysconfig 1.28.0+4712 generates broken code for MCSPI LLD and HLD drivers.</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697448/am2634-q1-am2634-q1-sysconfig-1-28-0-4712-generates-broken-code-for-mcspi-lld-and-hld-drivers/6538748</link><pubDate>Fri, 13 Nov 2026 16:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:82e0a1e0-02a1-475f-83ca-b6e62c166e19</guid><dc:creator>Eugene K</dc:creator><description>Pranav Siddappa When could we expect all MCSPI issues fixed? There seems to be quite a few of them. The initial multi-channel bug is two years old. Should SDK examples be more representative of the use cases like this one? Regards, Eugene</description></item><item><title>Forum Post: RE: AM2634-Q1: AM2634-Q1: AM263x SDK LLD MCSPI does not use timeout in miltiple APIs</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697409/am2634-q1-am2634-q1-am263x-sdk-lld-mcspi-does-not-use-timeout-in-miltiple-apis/6538745</link><pubDate>Fri, 13 Nov 2026 16:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6c07a833-1041-431a-8d13-838f76b6c9c8</guid><dc:creator>Eugene K</dc:creator><description>I agree that timeout should be in the application domain. However, I do not understand the logistic of having the timeout parameter and mostly checking its validity if it is not used. That seems to be confusing and forces user to provide irrelevant data to an API. Some API cleanup is warranted not just documentation. I would also expect that SDK examples be more representative of this use case. That will remove ambiguity and will provide additional testing for the driver. Regards, Eugene</description></item><item><title>Forum Post: RE: AM6442: CPTS maximum PPM correction</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1696468/am6442-cpts-maximum-ppm-correction/6538699</link><pubDate>Fri, 13 Nov 2026 16:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5ea3a9fc-8742-4afb-bdf1-34723f9cf2f6</guid><dc:creator>Nick Saulnier</dc:creator><description>Hello MH, On the question of differences between CPTS instances and limitations on nudge/PPM, we&amp;#39;ll need to get input from people familiar with the actual hardware IP. For the clock sync usecase: * Is the clock master external and providing PPS to give the clock? * which clocks are the ones with a &amp;quot;high error&amp;quot;? * which cores, etc are consuming the clock master&amp;#39;s inputs? * What is the acceptable drift or error between the clock master and the cores, etc which are consuming the clock? Depending on who is consuming the clock corrections within the AM64x, and how accurate you need all your clocks to be, you may need to take advantage of hardware features like the time sync router: [FAQ] AM64x: What is the Time Sync Router for? How do I use it? Regards, Nick</description></item><item><title>Forum Post: RE: TMS570LS1224: TMS570LS1224 – UART baud rate ~15x slower (possible PLL / clock configuration issue)</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1683969/tms570ls1224-tms570ls1224-uart-baud-rate-15x-slower-possible-pll-clock-configuration-issue/6538655</link><pubDate>Fri, 13 Nov 2026 15:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:af30fc91-1f47-4561-bfc1-85600dfea067</guid><dc:creator>Timis  Claudiu</dc:creator><description>https://meet1754116704602-2591.webex.com/meet1754116704602-2591/j.php?MTID=m24c15c3bc2c9bf327f1188afc94c575e</description></item><item><title>Forum Post: RE: TMS570LS1224: TMS570LS1224 – UART baud rate ~15x slower (possible PLL / clock configuration issue)</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1683969/tms570ls1224-tms570ls1224-uart-baud-rate-15x-slower-possible-pll-clock-configuration-issue/6538652</link><pubDate>Fri, 13 Nov 2026 15:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b24026a3-6fb5-4d31-866e-7d4d1c46f119</guid><dc:creator>jagadish gundavarapu</dc:creator><description>Please share new meeting link.</description></item><item><title>Forum Post: MSPM0G3519-Q1: Undefined behavior with ARM-CGT-CLANG 5.1.0.LTS using option "-mmathacl"</title><link>https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1697647/mspm0g3519-q1-undefined-behavior-with-arm-cgt-clang-5-1-0-lts-using-option--mmathacl</link><pubDate>Fri, 13 Nov 2026 15:18:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:13ca2887-d882-40f9-b46a-0226ef85b5a1</guid><dc:creator>Simon Tomschik</dc:creator><description>Part Number: MSPM0G3519-Q1 Other Parts Discussed in Thread: MSPM0G3519 We are encountering sporadic freezes of FreeRTOS when using the ARM-CGT-CLANG 5.1.0.LTS for the Texas Instruments MSPM0G3519 with the option &amp;quot;-mmathacl&amp;quot;. The CPU is hanging endlessly within the SysTick handler (the FreeRTOS option &amp;quot;configUSE_TICKLESS_IDLE&amp;quot; is set to 1). After some debugging we found that interrupts are enabled within &amp;quot;vPortSVCHandler_C&amp;quot; even though this function has explicitely disabled the interrupts before. The root cause for the re-enabled interrupts is the function __aeabi_uidivmod_hw/__aeabi_idivmod_hw shipped together with the ARM-CGT-CLANG 5.1.0.LTS compiler implementing the mathacl division. This function needs to disable the interrupts to access the math accelerator, but this function unconditionally re-enables the interrupts even if the interrupts have been disabled on calling the function. The statement &amp;quot;ulCompletedSysTickDecrements / ulTimerCountsForOneTick&amp;quot; in &amp;quot;vPortSVCHandler_C &amp;quot; will call the function __aeabi_uidivmod_hw/__aeabi_idivmod_hw causing the interrupts to be re-enabled at a location where the interrupts are expected to be disabled. The software is running stable when removing the option &amp;quot;-mmathacl&amp;quot;.</description><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/MSPM0G3519_2D00_Q1">MSPM0G3519-Q1</category><category domain="https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/tags/MSPM0G3519">MSPM0G3519</category></item></channel></rss>