From pete at soper.us Mon Feb 2 07:50:44 2026 From: pete at soper.us (Pete Soper) Date: Mon, 2 Feb 2026 08:50:44 -0500 Subject: [TriEmbed] Important Update on Mbed Message-ID: <4bb87d2a-35ee-4bc8-a31f-7907225eadb2@soper.us> Arm is withdrawing support in July. https://os.mbed.com/blog/entry/Important-Update-on-Mbed/ Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampas at gmail.com Mon Feb 2 08:21:56 2026 From: trampas at gmail.com (Trampas Stern) Date: Mon, 2 Feb 2026 09:21:56 -0500 Subject: [TriEmbed] Important Update on Mbed In-Reply-To: <4bb87d2a-35ee-4bc8-a31f-7907225eadb2@soper.us> References: <4bb87d2a-35ee-4bc8-a31f-7907225eadb2@soper.us> Message-ID: If you guys have not tried AI for development I suggest you do. In the last 6-7 months it has greatly improved to the point I have done entire projects without writing a line of code. What this means is that Mbed, arduino, and other such "easy build" systems will be replaced with AI. For example, I hated Zephyr RTOS because of the device tree mess, which in my opinion was a big design and implementation mistake. However with AI it is no longer a barrier. Basically I tell AI to start me a zephyr project, give it a text file with the pin assignments and a few minutes later I have hardware up and running. AI does everything from installing Zephyr, configuring device trees, building, flashing, etc. Basically AI 3 months ago was at the level of a college intern, today it is at the level of a college graduate with a couple years experience. It still makes mistakes, and goes off down rabbit holes. However, with some supervision and clear instructions and enabling it to see its own errors it can get the job done. Also another great thing is that it knows git. I no longer have to look up git commands, I just tell AI what to do. I personally thought about learning Rust awhile back, but quickly realized it was a waste of time. With AI the programming language is no longer an issue. That is AI can check C code for memory safety and do everything Rust provided, even translate C to Rust. As such AI removes the "coding" part of development and forces us to focus more on requirements and test cases. I have been thinking about using AI to reverse engineer some 8051 assembly on car computers. However it is almost a moot point... Trampas On Mon, Feb 2, 2026 at 8:51 AM Pete Soper via TriEmbed < triembed at triembed.org> wrote: > Arm is withdrawing support in July. > > https://os.mbed.com/blog/entry/Important-Update-on-Mbed/ > > Pete > _______________________________________________ > Triangle, NC Embedded Interest Group mailing list > > To post message: TriEmbed at triembed.org > List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org > TriEmbed web site: https://TriEmbed.org > To unsubscribe, click link and send a blank message: mailto: > unsubscribe-TriEmbed at bitser.net?subject=unsubscribe > Searchable email archive available at > https://www.mail-archive.com/triembed at triembed.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvaughters04 at yahoo.com Mon Feb 2 10:06:29 2026 From: jvaughters04 at yahoo.com (John Vaughters) Date: Mon, 2 Feb 2026 16:06:29 +0000 (UTC) Subject: [TriEmbed] Important Update on Mbed In-Reply-To: References: <4bb87d2a-35ee-4bc8-a31f-7907225eadb2@soper.us> Message-ID: <1149395087.2099706.1770048389619@mail.yahoo.com> I totally agree, but will say that I have been using AI for over a year now and it saves me tons of time. I've been feeding it software specs to see how it responds. I have had mixed results, but I will say that the programming language barrier is much smaller, Meaning I can program in whatever I need, and then massage it after that. It actually helps you learn the language. I still prefer to program in languages I have better knowledge, but it is a huge help. Sometimes I don't even know the code that is written, just what it does. Code someone else wrote for instance. I load it into AI and then ask it to change certain things about it. Then I just test it. Often times it works with minor effort. Most of what I do is utilities or interfaces, so not overly complex software. I have used it for ESP32 projects as well and it is great for picking the best pins and it saves me time reviewing pinouts as I just ask AI these questions. It is also good for reviewing hardware specs. As always with AI, if it is important, you definitely need to double check the answers. But many times I just roll with it if the cost of a mistake is low cost. For sure it can bring you down some rabbit holes and you need to learn how to respond to it, or work with it to get better results, but the net gain is fantastic, if your goal is to get things done and fast. It's a game changer. People worry about it taking jobs, but I believe it will increase productivity and also increase output. It has for me at least. John Vaughters On Monday, February 2, 2026 at 09:22:36 AM EST, Trampas Stern via TriEmbed wrote: If you guys have not tried AI for development I suggest you do. In the last 6-7 months it has greatly improved to the point I have done entire projects without writing a line of code. What this means is that Mbed, arduino, and other such "easy build" systems will be replaced with AI. For example, I hated Zephyr RTOS because of the device tree mess, which in my opinion was a big design and implementation mistake. However with AI it is no longer a barrier. Basically I tell AI to start me a zephyr project, give it a text file with the pin assignments and a few minutes later I have hardware up and running. AI does everything from installing Zephyr, configuring device trees, building, flashing, etc. Basically AI 3 months ago was at the level of a college intern, today it is at the level of a college graduate with a couple years experience. It still makes mistakes, and goes off down rabbit holes. However, with some supervision and clear instructions and enabling it to see its own errors it can get the job done. Also another great thing is that it knows git. I no longer have to look up git commands, I just tell AI what to do. I personally thought about learning Rust awhile back, but quickly realized it was a waste of time. With AI the programming language is no longer an issue. That is AI can check C code for memory safety and do everything Rust provided, even translate C to Rust. As such AI removes the "coding" part of development and forces us to focus more on requirements and test cases. I have been thinking about using AI to reverse engineer some 8051 assembly on car computers. However it is almost a moot point... Trampas On Mon, Feb 2, 2026 at 8:51 AM Pete Soper via TriEmbed wrote: > > Arm is withdrawing support in July. > > https://os.mbed.com/blog/entry/Important-Update-on-Mbed/ > > Pete > > _______________________________________________ > Triangle, NC Embedded Interest Group mailing list > > To post message: TriEmbed at triembed.org > List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org > TriEmbed web site: https://TriEmbed.org > To unsubscribe, click link and send a blank message: mailto:unsubscribe-TriEmbed at bitser.net?subject=unsubscribe > Searchable email archive available at https://www.mail-archive.com/triembed at triembed.org/ > > _______________________________________________ Triangle, NC Embedded Interest Group mailing list To post message: TriEmbed at triembed.org List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org TriEmbed web site: https://TriEmbed.org To unsubscribe, click link and send a blank message: mailto:unsubscribe-TriEmbed at bitser.net?subject=unsubscribe Searchable email archive available at https://www.mail-archive.com/triembed at triembed.org/ From pete at soper.us Wed Feb 4 10:05:38 2026 From: pete at soper.us (Pete Soper) Date: Wed, 4 Feb 2026 11:05:38 -0500 Subject: [TriEmbed] Onerous 3D printer law pending in NY Message-ID: <174db3c5-969b-48fd-9683-c7bee3df6ceb@soper.us> (Not passed yet; It's part of the state's budget legislation.) https://blog.adafruit.com/2026/02/03/new-york-wants-to-ctrlaltdelete-your-3d-printer/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From petesoper at gmail.com Wed Feb 4 10:18:38 2026 From: petesoper at gmail.com (Pete Soper) Date: Wed, 4 Feb 2026 11:18:38 -0500 Subject: [TriEmbed] Onerous 3D printer law pending in NY In-Reply-To: <174db3c5-969b-48fd-9683-c7bee3df6ceb@soper.us> References: <174db3c5-969b-48fd-9683-c7bee3df6ceb@soper.us> Message-ID: <8d552760-9cc3-4d4a-b03b-f7fa1af56871@gmail.com> Should have mentioned that Adafruit is focused on 3D printers but the legislation includes CNC mills and other devices. Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From paulmacd at acm.org Fri Feb 6 21:29:19 2026 From: paulmacd at acm.org (The MacDougals) Date: Fri, 6 Feb 2026 22:29:19 -0500 Subject: [TriEmbed] Monthly meeting 2/9 at 7:00pm in person at The Forge Message-ID: <002001dc97e1$f2a2bee0$d7e83ca0$@acm.org> We will have our normal monthly meeting on Monday 2/9/26 at 7:00 pm Agenda: - Welcome - Announcements - P.O.T.M. - Show and Tell The plan for this month is to meet in person at: The Forge Initiative 1012 Investment Blvd, Suite 103 Apex, NC 27502 As well as being at the Forge the meeting will also be online at the usual Jitsi URL:    https://meet.jit.si The meeting will be recorded. ---> Paul From petesoper at gmail.com Fri Feb 6 22:02:10 2026 From: petesoper at gmail.com (Pete Soper) Date: Fri, 6 Feb 2026 23:02:10 -0500 Subject: [TriEmbed] Monthly meeting 2/9 at 7:00pm in person at The Forge In-Reply-To: <002001dc97e1$f2a2bee0$d7e83ca0$@acm.org> References: <002001dc97e1$f2a2bee0$d7e83ca0$@acm.org> Message-ID: <3c0f6429-e262-43ec-b1d9-b9c67a3cee4a@gmail.com> https://meet.jit.si/TriEmbed -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottghall1 at gmail.com Mon Feb 9 15:29:37 2026 From: scottghall1 at gmail.com (Scott Hall) Date: Mon, 9 Feb 2026 16:29:37 -0500 Subject: [TriEmbed] When player pianos and tesla coils meet ... In-Reply-To: References: Message-ID: "1 MILLION VOLT piano sounds UNREAL" https://youtu.be/Q8WXvDLofL8?si=6Z2N9tVJzuo0ju7j *More Tesla Coil / Plasma Speaker music:* “Music Tesla coil Mario” https://youtube.com/shorts/9_NoVwdvP4I?si=11bjhyDv864A1v_n “AC/DC – Thunderstruck, but with Tesla Coils” https://youtu.be/gqs8bRMhBgA?si=wyCJ_qAA7Y1fKE59 *More automated pianos and homemade organs:* “Entry of the Gladiators on my homemade music machine” https://youtu.be/D49pxyuEEsI?si=r76GuNz70W6BYUSe “Bugler’s Holiday on my homemade organ” https://youtu.be/BoD7uKeVnkc?si=Irr2cpUO1gt43XbT “Livin La Vida Loca on a mechanical organ” https://youtu.be/woTmxtvIUmo?si=Xtm7rAavesL_SQea “Testing my 32-note midi organ” https://youtu.be/pEQVVBxxDj4?si=V3BbA0MQbdXG5zV7 “Homemade pipe organ demo” https://youtu.be/py7NwL2h_6U?si=gdpUxXk79kUQvpVt *Bonus feature:* “25 Most Amazing Tesla Coil Experiements” https://youtube.com/shorts/9_NoVwdvP4I?si=11bjhyDv864A1v_n -- Scott G. Hall Raleigh, NC, USA scottghall1 at gmail.com *”**Failure is the opportunity to begin again more intelligently.” -- Henry Ford* -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncgadgetry at gmail.com Tue Feb 10 09:51:16 2026 From: ncgadgetry at gmail.com (Rodney Radford) Date: Tue, 10 Feb 2026 10:51:16 -0500 Subject: [TriEmbed] Fwd: Texas Instruments to acquire Silicon Labs In-Reply-To: <1386396275.136903487.1770736918641@abmktmail-batch1c.marketo.org> References: <1386396275.136903487.1770736918641@abmktmail-batch1c.marketo.org> Message-ID: ---------- Forwarded message --------- From: Brandon Tolany Date: Tue, Feb 10, 2026, 10:28 AM Subject: Texas Instruments to acquire Silicon Labs To: [image: Silicon Labs] Dear Rodney, We are excited to share that Silicon Labs has announced a planned acquisition by Texas Instruments (TI), a global leader in semiconductor technology. This combination brings together Silicon Labs’ leadership in embedded wireless connectivity with TI’s manufacturing scale, global reach, and operational excellence. Together, we expect to accelerate innovation, enhance supply reliability, and expand the level of support we can provide to customers worldwide. Importantly, Texas Instruments is acquiring Silicon Labs to build on what we do best. Our product roadmap, customer commitments, and day-to-day operations remain unchanged. Until the transaction closes—expected in the first half of 2027, subject to customary approvals—it is business as usual, and your current contacts and agreements remain the same. We wanted you to hear this directly from us as a trusted customer. If you have any questions, your Silicon Labs representative is happy to discuss what this means for you. Thank you for your continued partnership. We are excited about the opportunities ahead. Sincerely, *Brandon Tolany* *Sr. Vice President Sales & Marketing* *Additional Information and Where to Find It * In connection with the proposed transaction, Silicon Laboratories Inc. (“Silicon Labs) plans to file a proxy statement with the Securities and Exchange Commission (the “SEC”) with respect to a special meeting of stockholders for purposes of obtaining stockholder approval of the proposed transaction. This communication is not a substitute for the proxy statement or any other document that Silicon Labs may file with the SEC. The definitive proxy statement (when available) will be sent or given to the stockholders of Silicon Labs and will contain important information about the proposed transaction and related matters. STOCKHOLDERS OF SILICON LABS ARE URGED TO READ THE PROXY STATEMENT (INCLUDING ANY AMENDMENTS OR SUPPLEMENTS THERETO AND ANY DOCUMENTS INCORPORATED BY REFERENCE THEREIN) AND OTHER RELEVANT DOCUMENTS IN CONNECTION WITH THE PROPOSED TRANSACTION THAT SILICON LABS WILL FILE WITH THE SEC WHEN THEY BECOME AVAILABLE BECAUSE THEY WILL CONTAIN IMPORTANT INFORMATION ABOUT THE PROPOSED TRANSACTION AND THE PARTIES TO THE PROPOSED TRANSACTION. Stockholders and investors will be able to obtain free copies of the proxy statement and other relevant materials (when available) and other documents filed by Silicon Labs at the SEC’s website at www.sec.gov. Copies of the proxy statement (when available) and the filings that will be incorporated by reference therein may also be obtained, without charge, by contacting Silicon Labs’ Investor Relations at investor.relations at silabs.com or (512) 416-8500. *Participants in the Solicitation * Silicon Labs, Texas Instruments Incorporated (“Texas Instruments”) and their respective directors and executive officers may be deemed, under SEC rules, to be participants in the solicitation of proxies in respect of the proposed transaction. Information regarding Silicon Labs’ directors and executive officers is available in (a) Silicon Labs’ Annual Report on Form 10-K for the fiscal year ended December 28, 2024, including under the headings “Item 10. Directors, Executive Officers and Corporate Governance,” “Item 11. Executive Compensation,” “Item 12. Security Ownership of Certain Beneficial Owners and Management and Related Stockholder Matters” and “Item 13. Certain Relationships, Related Transactions, and Director Independence,” which was filed with the SEC on February 4, 2025, and can be found at www.sec.gov; (b) Silicon Labs’ definitive proxy statement for its 2025 annual meeting of stockholders, which was filed with the SEC on March 12, 2025, under the headings “Proposal One: Election of Directors,” “Ownership of Securities,” “Executive Officers,” and “Compensation Discussion and Analysis,” and can be found at www.sec.gov; and (c) subsequently filed Current Reports on Form 8-K and Quarterly Reports on Form 10-Q. To the extent holdings of Silicon Labs’ securities by its directors or executive officers have changed since the amounts set forth in Silicon Labs’ proxy statement for its 2025 annual meeting of stockholders, such changes have been or will be reflected on Forms 3, 4 and 5, filed with the SEC (which can be found at www.sec.gov). Copies of the documents filed with the SEC by Silicon Labs will be available free of charge through the website maintained by the SEC and at Silicon Labs’ website at https://investor.silabs.com/. Information regarding Texas Instruments’ directors and executive officers is available in (a) Texas Instruments’ Annual Report on Form 10-K for the fiscal year ended December 31, 2024, including under the headings “ITEM 10. Directors, executive officers and corporate governance,” “ITEM 11. Executive compensation,” “ITEM 12. Security ownership of certain beneficial owners and management and related stockholder matters” and “ITEM 13. Certain relationships and related transactions, and director independence,” which was filed with the SEC on February 14, 2025, and can be found at www.sec.gov; (b) Texas Instruments’ definitive proxy statement for its 2025 annual meeting of stockholders, which was filed with the SEC on March 5, 2025, under the headings “Election of directors,” “Executive compensation,” and “Security ownership of directors and management,” and can be found at www.sec.gov; and (c) subsequently filed Current Reports on Form 8-K and Quarterly Reports on Form 10-Q. To the extent holdings of Texas Instruments’ securities by its directors or executive officers have changed since the amounts set forth in Texas Instruments’ proxy statement for its 2025 annual meeting of stockholders, such changes have been or will be reflected on Forms 3, 4 and 5, filed with the SEC (which can be found at www.sec.gov). Copies of the documents filed with the SEC by Texas Instruments will be available free of charge through the website maintained by the SEC at www.sec.gov and at Texas Instruments’ website at https://investor.ti.com/. Other information regarding the participants in the solicitation and a description of their direct and indirect interests, by security holdings or otherwise, will be set forth in Silicon Labs’ definitive proxy statement and other relevant materials to be filed with the SEC regarding the proposed transaction when such materials become available. Investors and stockholders should read the proxy statement carefully when it becomes available before making any voting or investment decisions. Copies of these documents may be obtained, free of charge, from the sources indicated above. *No Offer or Solicitation * This communication is for informational purposes only and does not constitute an offer to sell or the solicitation of an offer to buy any securities or a solicitation of any vote or approval, nor shall there be any sale of securities in any jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such jurisdiction. No offer of securities shall be made except by means of a prospectus meeting the requirements of Section 10 of the Securities Act of 1933, as amended, and otherwise in accordance with applicable law. *Cautionary Statement Regarding Forward-Looking Statements * This communication contains “forward-looking statements” within the meaning of of Section 27A of the Securities Act of 1933, as amended, Rule 175 promulgated thereunder, Section 21E of the Securities Exchange Act of 1934, as amended, and Rule 3b-6 promulgated thereunder. Such statements include statements concerning anticipated future events and expectations that are not historical facts. Any statements about Texas Instruments’ or Silicon Labs’ plans, objectives, expectations, strategies, beliefs, or future performance or events constitute forward-looking statements. Forward-looking statements are typically identified by words such as “believe,” “expect,” “anticipate,” “intend,” “target,” “estimate,” “continue,” “positions,” “plan,” “predict,” “project,” “forecast,” “guidance,” “goal,” “objective,” “prospects,” “possible” or “potential,” by future conditional verbs such as “assume,” “will,” “would,” “should,” “could” or “may,” or by variations of such words or by similar expressions or the negative thereof. Such forward-looking statements include but are not limited to statements about the benefits of the proposed transaction, including future financial and operating results, Texas Instruments’ or Silicon Labs’ plans, objectives, expectations and intentions, the expected timing of completion of the proposed transaction and other statements that are not historical facts. Actual results may vary materially from those expressed or implied by forward-looking statements based on a number of factors, including, without limitation: (a) risks related to the consummation of the proposed transaction, including the risks that (i) the proposed transaction may not be consummated within the anticipated time period, or at all, (ii) the parties may fail to obtain Silicon Labs stockholder approval of the merger agreement, (iii) the parties may fail to secure the termination or expiration of any waiting period applicable under the Hart-Scott-Rodino Antitrust Improvements Act of 1976, as amended, or obtain other required governmental and regulatory approvals, and (iv) other conditions to the consummation of the proposed transaction under the merger agreement may not be satisfied; (b) the effects that any termination of the merger agreement may have on Silicon Labs or Texas Instruments and their respective businesses, including the risk that Silicon Labs’ or Texas Instruments’ stock price may decline significantly if the proposed transaction is not completed; (c) the effects that the announcement or pendency of the proposed transaction may have on Silicon Labs or Texas Instruments and their respective businesses, including the risks that as a result (i) Silicon Labs’ or Texas Instruments’ business, operating results or stock price may suffer, (ii) Silicon Labs’ or Texas Instruments’ current plans and operations may be disrupted, (iii) Silicon Labs’ or Texas Instruments’ ability to retain or recruit key employees may be adversely affected, (iv) Silicon Labs’ or Texas Instruments’ business relationships (including, customers and suppliers) may be adversely affected, or (v) Silicon Labs’ or Texas Instruments’ management’s or employees’ attention may be diverted from other important matters; (d) the effect of limitations that the merger agreement places on Silicon Labs’ ability to operate its business, return capital to stockholders or engage in alternative transactions; (e) the nature, cost and outcome of pending and future litigation and other legal proceedings, including any such proceedings related to the proposed transaction and instituted against Silicon Labs and others; (f) the risk that the proposed transaction and related transactions may involve unexpected costs, liabilities or delays; (g) other economic, business, competitive, legal, regulatory, and/or tax factors, including the impact of the current global memory chip shortage; and (h) other factors described in the reports of (i) Silicon Labs filed with the SEC, including but not limited to the risks described in Silicon Labs’ Annual Report on Form 10-K for its fiscal year ended December 28, 2024, which was filed with the SEC on February 4, 2025, and Silicon Labs’ Quarterly Reports on Form 10-Q, and that are otherwise described or updated from time to time in Silicon Labs’ other filings with the SEC and (ii) Texas Instruments filed with the SEC, including but not limited to the risks described in Texas Instruments’ Annual Report on Form 10-K for its fiscal year ended December 31, 2024, which was filed with the SEC on February 14, 2025, and Texas Instruments’ Quarterly Reports on Form 10-Q, and that are otherwise described or updated from time to time in other filings with the SEC. All forward-looking statements attributable to Silicon Labs or Texas Instruments, or persons acting on Silicon Labs’ or Texas Instruments’ behalf, are expressly qualified in their entirety by this cautionary statement. Further, each of Silicon Labs and Texas Instruments disclaims any obligation to update the information in this communication or to announce publicly the results of any revisions to any of the forward-looking statements to reflect future events or developments, except as otherwise required by law. Readers are cautioned not to place undue reliance on these forward-looking statements that speak only as of the date hereof. You are receiving this email because you provided your contact information to Silicon Labs. To change your communication preferences, please log in and update email preferences. If you no longer wish to receive emails from Silicon Labs, you can unsubscribe . Review our online Privacy Policy . Silicon Labs, 400 W. Cesar Chavez St., Austin, TX 78701 View in Browser -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottghall1 at gmail.com Fri Feb 20 12:18:29 2026 From: scottghall1 at gmail.com (Scott Hall) Date: Fri, 20 Feb 2026 13:18:29 -0500 Subject: [TriEmbed] Restoring old musical instruments, or building your own Message-ID: Thought you might enjoy these -- the first uses pneumatic logic instead of electronic O-roll Orchestrion plays the "Atlanta Rag": https://youtu.be/qy3__GAiBus?si=Y1aliwVvQGmIt6ud O Roll Test Orchestrion Plays "Beer Barrel Polka": https://youtu.be/955mEk_q8hM?si=Kk5JSPYiFTzfHtm- Hupfeld Sinfonie Jazz Orchester plays 'Sunny Havana': https://youtu.be/s-ESCeEGC-E?si=HunMPU-8cvtqpAjI Bugler's Holiday on my homemade organ: https://youtu.be/BoD7uKeVnkc?si=t83SCFCUWXM4tvrv -- Scott G. Hall Raleigh, NC, USA scottghall1 at gmail.com *”**Failure is the opportunity to begin again more intelligently.” -- Henry Ford* -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.nobile at gmail.com Sun Feb 22 14:02:38 2026 From: carl.nobile at gmail.com (Carl Nobile) Date: Sun, 22 Feb 2026 15:02:38 -0500 Subject: [TriEmbed] The February meeting at The Forge has been published. Message-ID: Hi all, I've just published the February meeting on YouTube. https://youtu.be/m-2IFbHZclw I also updated the TriEmbed website: https://triembed.org/triembed-presentation-archive/ ~Carl -------------------------------------------------------------- Carl J. Nobile (Software Engineer/API Design) carl.nobile at gmail.com -------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From myemail1234 at duck.com Sun Feb 22 19:57:04 2026 From: myemail1234 at duck.com (myemail1234 at duck.com) Date: Sun, 22 Feb 2026 20:57:04 -0500 Subject: [TriEmbed] The February meeting at The Forge has been published. References: <0D8EF7B2-C5C0-4C2A-9643-9E46C0BCFFF7.1@smtp-inbound1.duck.com> Message-ID: ::claps:: On Sun, Feb 22, 2026 at 3:03 PM Carl Nobile via TriEmbed < triembed_at_triembed.org_myemail1234 at duck.com> wrote: > Hi all, I've just published the February meeting on YouTube. > https://youtu.be/m-2IFbHZclw I also updated the TriEmbed website: > https://triembed.org/triembed-presentation-archive/ ~Carl --------------- > *DuckDuckGo* did not detect any trackers. More > > Report Spam > > Hi all, > > I've just published the February meeting on YouTube. > > https://youtu.be/m-2IFbHZclw > > I also updated the TriEmbed website: > https://triembed.org/triembed-presentation-archive/ > > ~Carl > > -------------------------------------------------------------- > Carl J. Nobile (Software Engineer/API Design) > carl.nobile at gmail.com > -------------------------------------------------------------- > _______________________________________________ > Triangle, NC Embedded Interest Group mailing list > > To post message: TriEmbed at triembed.org > List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org > TriEmbed web site: https://TriEmbed.org > To unsubscribe, click link and send a blank message: mailto: > unsubscribe-TriEmbed at bitser.net?subject=unsubscribe > Searchable email archive available at > https://www.mail-archive.com/triembed at triembed.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: