<?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>API solutions</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6539120</link><pubDate>Mon, 16 Nov 2026 00:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d3f5896b-c002-4c23-b56e-e070ff7db2f0</guid><dc:creator>Wendy</dc:creator><description>Hello， We would like to know whether there is a solution to the issue we mentioned.</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6536998</link><pubDate>Thu, 12 Nov 2026 02:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:323fb1fc-236b-492f-9289-b48d0a9f717a</guid><dc:creator>Nick Saulnier</dc:creator><description>Hello Wendy, Apologies for the delayed response here. I won&amp;#39;t have time to respond today. Please ping the thread again so I have another reminder tomorrow. Regards, Nick</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6533288</link><pubDate>Sat, 07 Nov 2026 01:25:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c95e95dd-2165-4aeb-8477-313a600fbc3f</guid><dc:creator>Wendy</dc:creator><description>Hello， We would like to know whether there is a solution to the issue we mentioned. We look forward to your reply. Thank you very much.</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6527726</link><pubDate>Mon, 02 Nov 2026 16:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9dbe2f5f-21b6-41b9-9e67-e63f238ac964</guid><dc:creator>Ryan Kitto</dc:creator><description>Hi Juan, There are two ways you should be able to accept it. One way is just by hovering my name on this thread, and pressing the three dots. That should let you accept it: The other is by clicking on my name, and pressing the &amp;quot;+Connect&amp;quot; button: After pressing accept, you should be given a &amp;quot;Send a Private Message&amp;quot; button in those same spots. Thanks, Ryan</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6527669</link><pubDate>Mon, 02 Nov 2026 15:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:869c9795-0eaa-4b40-b583-c90f0c350a2f</guid><dc:creator>Juan Abreu</dc:creator><description>Ryan Kitto please let me know how to view/accept the E2E friend request</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6526728</link><pubDate>Fri, 30 Oct 2026 20:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:e83a26fd-afa0-4e59-a432-8f6f137a9ba9</guid><dc:creator>Juan Abreu</dc:creator><description>Sorry but not sure where/how to approve the friend request :( I did not see it show up in a notification or on my dashboard.</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6526471</link><pubDate>Fri, 30 Oct 2026 16:34:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2369b7b8-e7aa-4b63-b005-839458e76048</guid><dc:creator>Ryan Kitto</dc:creator><description>Hi Juan, Please accept my E2E friend request and send me a PM, I will send you the tool and guide we have available. Thanks, Ryan</description></item><item><title>Forum Post: RE: TPSM33625FEVM: TI-API: Inventory Subscription Push callback blocked by TI Web Filter (403)</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1686420/tpsm33625fevm-ti-api-inventory-subscription-push-callback-blocked-by-ti-web-filter-403/6526082</link><pubDate>Fri, 30 Oct 2026 10:21:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:da3d8cca-2203-4666-aded-cfc435df023c</guid><dc:creator>Sateesh Goudappanavar</dc:creator><description>Hi, Assuming this is addressed and resolved, I&amp;#39;ll be closing this E2E thread. Please feel free to reach out to us in case of further queries. Thank you Best regards, Sateesh A G</description></item><item><title>Forum Post: RE: AM2434: AM2434: Follow-up on October 2026 Industrial Communications SDK Release and PROFINET Configuration Support</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690212/am2434-am2434-follow-up-on-october-2026-industrial-communications-sdk-release-and-profinet-configuration-support/6526080</link><pubDate>Fri, 30 Oct 2026 10:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8bacda2b-9837-4ad0-a2cc-ffb95ebbeb79</guid><dc:creator>Kamil Alkhouri</dc:creator><description>Hello Uie-Tae Lee, The next standard release will be around April 2027. The selection of which parameters to be dynamically configurable is not made yet. Based on your question I will note down that some customers are interested in the 1-port device to give this parameter a higher priority. Thanks. Kind regards, Kamil</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6525511</link><pubDate>Thu, 29 Oct 2026 21:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8a19ae07-826b-42c9-8320-b38e94e1f2ee</guid><dc:creator>Juan Abreu</dc:creator><description>I appreciate you getting back to me. We would be modifying already deployed product. So, swapping parts or changing trace/part connections is not an option. The datasheet says that there is a process for the OTP modification, but I am assuming that process needs to be privately shared (i.e. not via forum discussion).</description></item><item><title>Forum Post: RE: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only/6525446</link><pubDate>Thu, 29 Oct 2026 20:01:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1cac7d44-9391-44fc-bf2f-121e52bee1f2</guid><dc:creator>Ryan Kitto</dc:creator><description>Hi Juan, Are you trying to modify an existing design? Or are you just looking to disable the USB3 lines when the hub is placed? The USB3 and USB2 lines work on separate internal PHYs, so if you wanted to, you can disable the USB3 lines by simply not connecting them to the USB connector. Alternatively, you can also switch to one of our USB2 hubs, which comes with no USB3 functionality, such as the TUSB4041I. Thanks, Ryan</description></item><item><title>Forum Post: TUSB8043A: Restrict TUSB8043A to USB 2.0 only</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693901/tusb8043a-restrict-tusb8043a-to-usb-2-0-only</link><pubDate>Thu, 29 Oct 2026 16:55:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8721287a-ab10-4740-aaf2-bbc3b2b83351</guid><dc:creator>Juan Abreu</dc:creator><description>Part Number: TUSB8043A Other Parts Discussed in Thread: TUSB4041I We are using TUSB8043A and need to restrict it to USB 2.0 only. Can you send us the process to perform the OTP change called out in section 8.3.4 of the datasheet.</description><category domain="https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/tags/TUSB4041I">TUSB4041I</category><category domain="https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/tags/TUSB8043A">TUSB8043A</category></item><item><title>Forum Post: RE: AM2434: Regarding the EtherCAT SubDevice, the processing time for each process is longer than expected. (Continued)</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693298/am2434-regarding-the-ethercat-subdevice-the-processing-time-for-each-process-is-longer-than-expected-continued/6523787</link><pubDate>Wed, 28 Oct 2026 15:05:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ced84dda-2784-4c61-b810-fb6b0d373a72</guid><dc:creator>Harsha Begihally Shanmukhaswamy</dc:creator><description>Hi, We will analyze the wireshark logs and provide you the feedback. Kind Regards,</description></item><item><title>Forum Post: AM2434: Regarding the EtherCAT SubDevice, the processing time for each process is longer than expected. (Continued)</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1693298/am2434-regarding-the-ethercat-subdevice-the-processing-time-for-each-process-is-longer-than-expected-continued</link><pubDate>Wed, 28 Oct 2026 08:09:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:56ebacbc-42e6-414d-ae6e-7415c724ee2a</guid><dc:creator>Ryoma Akiyama</dc:creator><description>Part Number: AM2434 Hello, Developer Team. #1678274 Since the previous thread was locked, I am posting the continuation here. (Please note that I am posting this as a &amp;quot;New Question&amp;quot; because the &amp;quot;Related Questions&amp;quot; section did not appear.) We conducted tests using cycle times of 250&amp;#181;s, 500&amp;#181;s, and 1ms. The results confirm that the object values ​​are updated correctly at 500&amp;#181;s and 1ms. (The failure previously observed at 1ms was due to an incorrect DC cycle time setting.) I have attached the Wireshark logs from the tests conducted at 250&amp;#181;s, 500&amp;#181;s, and 1ms. Wireshark.zip For these tests, a 4-byte data value—located at offset 0x63 in each frame (the 10th byte of the input/output process data)—is incremented during the application processing of both the main and sub-devices. Please review the attached information. Kind regards,</description><category domain="https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/tags/Industrial%2bAutomation">Industrial Automation</category><category domain="https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/tags/AM2434">AM2434</category></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6521775</link><pubDate>Tue, 27 Oct 2026 01:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0885ffd4-b09a-4a6b-8372-d6e20a7f23f1</guid><dc:creator>Wendy</dc:creator><description>Hello， Yes, we use the R5F to obtain GPS time and then write it to the RTC clock. To ensure time synchronization accuracy, we need to implement writing to the RTC clock via the I2C interface on the R5F. However, the linux core needs to obtain the RTC clock at initial power-up as the system clock, so we have this requirement.</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6521504</link><pubDate>Mon, 26 Oct 2026 19:07:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:58c8fdc4-2908-443f-9b45-8e9f0929ffbc</guid><dc:creator>Nick Saulnier</dc:creator><description>Hello Wendy, Just to make sure I understand your design: Is the R5F receiving the &amp;quot;true&amp;quot; time from GPS, rather than from the external RTC clock? If yes, would your design then occasionally update the RTC clock&amp;#39;s time based on the &amp;quot;true&amp;quot; time from the GPS? Regards, Nick</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6520421</link><pubDate>Mon, 26 Oct 2026 00:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b75a3fed-e529-4d9e-b7f0-2a45c04acb8c</guid><dc:creator>Wendy</dc:creator><description>Hello, Actually, we want some log messages generated during initial system startup to reflect the RTC time. After that, the Linux core should essentially no longer have anything to do with this RTC. The R5F is actually connected to GPS and is used to parse GPS and write the time-synchronization time. During runtime, Linux does not use NTP or similar mechanisms to modify the time; the external RTC clock is the only time source.</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6520368</link><pubDate>Sun, 25 Oct 2026 13:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6c5ca64b-1693-418b-b98a-c170165bee19</guid><dc:creator>Nick Saulnier</dc:creator><description>Hello Wendy, Thank you for the ping. This is the kind of problem which could be approached several different ways. Let&amp;#39;s talk some more to decide whether any of the possible approaches would make sense in your system. Summarizing the desired design 1) Source time from external RTC connected over I2C 2) both Linux and R5F cores should share the same timebase Followup questions 1) Will the system time be updated from any outside sources during runtime? (for example, if Linux started getting time from a time master over Ethernet like with NTP, it looks like kernel config CONFIG_RTC_SYSTOHC allows Linux to write this NTP-synced time back to the RTC every few minutes) Or is the unmodified external RTC clock the only source of time? 2) What are you trying to accomplish with the shared timebase between Linux and R5F? (for example, collecting data samples with R5F, where Linux needs to know the time that the data sample was collected at within XXX usec?) 3) What &amp;quot;accuracy&amp;quot; do you need? (what is the maximum time difference allowable between the RTC clock source, the Linux system time, and the R5F time?) Initial thoughts It is technically possible to start with I2C ownership in Linux, then Linux releases the I2C by unbinding the I2C driver, and R5F could poll the TISCI status of the I2C to see when it is released. But the Linux OS is not designed to lose control of an RTC connected over I2C during runtime. It might be easier to let Linux continue owning the RTC connected over I2C, and write a small kernel driver or userspace application to pass the RTC value to R5F (off the top of my head, not sure if this is easy to do in userspace, or if kernel driver would be better): Send an RPMsg from Linux to R5F, and grab the Linux system time &amp;amp; GTC counter value at the moment before writing the RPMsg. Then the R5F core reads its own clock (r5f_now) and the GTC counter value again (gtc_now) at the moment that it receives the RPMsg. Then r5f_updated = linux_system_time + (gtc_now − gtc_linux) &amp;#215; tick_period And you can adjust the R5F&amp;#39;s counter by r5f_updated - r5f_now. If you really value both cores being as close to the RTC value as possible, you might even be able to adjust the Linux code that reads the RTC value from I2C so that it captures the GTC counter value right when the RTC value is read, and send that to the R5F instead. Then you remove the variable of the Linux system time from the mix. Not sure how much clock drift to expect in a design like this. Regards, Nick</description></item><item><title>Forum Post: RE: LMG3526R030: Synchronous Boost implementation</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1691165/lmg3526r030-synchronous-boost-implementation/6519518</link><pubDate>Fri, 23 Oct 2026 09:12:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c598451d-2783-48b7-81ff-75bfa56e912b</guid><dc:creator>Michele Santucci</dc:creator><description>Yes I&amp;#39;m using LMG3525R030Q because the board on which I&amp;#39;m working is a modified PMP22650E2(001) board. Anyway I didn&amp;#39;t found int into the product list when creating the case so I took the more similar PN... I didnt found much docs about it and I think that it never reached the production stage. The main issue I&amp;#39;m having with this component is the lack of a body diode, the emulation works but with a pretty high voltage drop. This lead to some issue into BOOST bootstrap sequence coding. I solved it by simply driving high-side GaN statically on and low-side statically off until the bootstrap capacitor reach almost VIN and then I start PWM controller driving both leg mosfet with complementary duty cycles (deadband and so on). This work but since I&amp;#39;m not an expert and not really sure this&amp;#39;s a 100% fault proof behaviour. I&amp;#39;m looking for specific firmware rather than schematics the board I&amp;#39;m working is already been built and it has a pretty standard schematics. The target output voltage is about 90V but right now I need to work with a low voltage setup (12-24V). BTW There&amp;#39;s a pin-to-pin compatibile component with a more efficient body-diode emulation feature?</description></item><item><title>Forum Post: RE: AM6422: AM6422 IIC RTC linux RTOS</title><link>https://e2e.ti.com/support/enterprise-automation-integration-group/enterprise-automation-integration/f/api-solutions-forum/1690568/am6422-am6422-iic-rtc-linux-rtos/6519209</link><pubDate>Fri, 23 Oct 2026 03:09:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:90baa992-f1d3-4075-8f52-7a3ef6e4f00d</guid><dc:creator>Wendy</dc:creator><description>Hello， Is there a solution to the question I raised above?</description></item></channel></rss>