From paulmacdnc at att.net Fri Feb 7 13:04:07 2025 From: paulmacdnc at att.net (The MacDougals) Date: Fri, 7 Feb 2025 14:04:07 -0500 Subject: [TriEmbed] Monthly meeting 2/10 at 7:00pm at The Forge Initiative References: <0a8601db7993$117909a0$346b1ce0$.ref@att.net> Message-ID: <0a8601db7993$117909a0$346b1ce0$@att.net> We will have our normal monthly meeting on Monday 2/10/25 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 630 Davis Drive, Suite 205 Morrisville, NC We do not plan to use jitsi for those who cannot make it in person. ---> Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete at soper.us Fri Feb 21 08:25:30 2025 From: pete at soper.us (Pete Soper) Date: Fri, 21 Feb 2025 09:25:30 -0500 (EST) Subject: [TriEmbed] Glucose monitor in a future Apple watch Message-ID: There was discussion of glucose monitors at the January mtg and this Apple blurb caught my eye. https://www.patentlyapple.com/2025/02/a-federal-judge-has-invalidated-an-omni-medsci-patent-which-could-open-the-door-for-a-blood-glucose-solution-for-apple-watch.html Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From pete at soper.us Sat Feb 22 08:03:27 2025 From: pete at soper.us (Pete Soper) Date: Sat, 22 Feb 2025 09:03:27 -0500 (EST) Subject: [TriEmbed] Digikey tariff collection fyi Message-ID: <936314e5-13f5-4235-bbe4-9fccf6d44ad1@soper.us> (Yes, of course Mouser and the rest must impose the same tariffs)? https://www.digikey.com/en/resources/tariff-resources Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From christophersvec at yahoo.com Sun Feb 23 21:11:43 2025 From: christophersvec at yahoo.com (Christopher Svec) Date: Mon, 24 Feb 2025 03:11:43 +0000 (UTC) Subject: [TriEmbed] Free dev boards References: <1216928462.3114760.1740366703269.ref@mail.yahoo.com> Message-ID: <1216928462.3114760.1740366703269@mail.yahoo.com> Hi, I've got 20-30 dev boards I'd like to find a new home for. They're a bunch of STM32's, MSP430/432's, and an old Rasp Pi or 2. Most are new or barely used. Anyone know someone / somewhere who could use them? Thanks! -svec -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.j.lord at ieee.org Sun Feb 23 21:31:50 2025 From: c.j.lord at ieee.org (Charles J. Lord, PE) Date: Sun, 23 Feb 2025 22:31:50 -0500 Subject: [TriEmbed] Free dev boards In-Reply-To: <1216928462.3114760.1740366703269@mail.yahoo.com> References: <1216928462.3114760.1740366703269.ref@mail.yahoo.com> <1216928462.3114760.1740366703269@mail.yahoo.com> Message-ID: I could definitely use them for IEEE STEM activities Charles Charles J. Lord, PE President, Blue Ridge Advanced Design and Automation Past Chair, IEEE-USA Consultants Committee Life Member Chair, IEEE Western NC Section Chair, IEEE NC Council Co-Chair, IEEE SoutheastCon 2025 c.j.lord at ieee.org On Sun, Feb 23, 2025, 10:12 PM Christopher Svec via TriEmbed < triembed at triembed.org> wrote: > Hi, > > I've got 20-30 dev boards I'd like to find a new home for. They're a bunch > of STM32's, MSP430/432's, and an old Rasp Pi or 2. Most are new or barely > used. > > Anyone know someone / somewhere who could use them? > > Thanks! > > -svec > _______________________________________________ > 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 scottghall1 at gmail.com Sun Feb 23 22:29:52 2025 From: scottghall1 at gmail.com (Scott Hall) Date: Sun, 23 Feb 2025 23:29:52 -0500 Subject: [TriEmbed] Free dev boards In-Reply-To: <1216928462.3114760.1740366703269@mail.yahoo.com> References: <1216928462.3114760.1740366703269.ref@mail.yahoo.com> <1216928462.3114760.1740366703269@mail.yahoo.com> Message-ID: Anything Charles doesn't take I'll take off your hands for the kids in the north-Wake beginning electronics group I've been doing lately (currently associated with the Boy Scouts and Girl Scouts electronics merit badges). On Sun, Feb 23, 2025 at 10:11?PM Christopher Svec via TriEmbed < triembed at triembed.org> wrote: > Hi, > > I've got 20-30 dev boards I'd like to find a new home for. They're a bunch > of STM32's, MSP430/432's, and an old Rasp Pi or 2. Most are new or barely > used. > > Anyone know someone / somewhere who could use them? > > Thanks! > > -svec > _______________________________________________ > 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/ > > -- Scott G. Hall Raleigh, NC, USA scottghall1 at gmail.com *Although kindness is rarely a job, no matter what you do it's always an option.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampas at gmail.com Thu Feb 27 08:50:04 2025 From: trampas at gmail.com (Trampas Stern) Date: Thu, 27 Feb 2025 09:50:04 -0500 Subject: [TriEmbed] USB RNDIS enumeration help needed Message-ID: I am trying to do USB RNDIS enumeration and having issues. I have googled and read everything I can find and keep running into issues. I get the enumeration working and it will work for days on my PC, then at some point it will not work. I switch hubs, ports and it might work again for days, then stop. I have been using Saleae logic analyzer as well as USB protocol analyzer (Total Phase Beagle device) and have been unable to figure out the issues. My initial thoughts were that Microsoft was doing some predictive analysis on device timing. That is, I noticed that if the USB request from the host came in too quickly it would cause issues. I figured that based on the packet NAKs that Microsoft might dynamically change request timing to compensate for slower devices. I figure this would maximize the bus bandwidth utilization by not sending packets that most likely would be NAK'd. I am not sure if this is true or not, but sounded reasonable? I since changed my device to be all interrupt driven for fastest response. This addressed some issues, but not all of my problems. Now I seem to have hit another issue. The host sends an RNDIS Initialize message, after which I setup device's USB peripheral to send the RESPONSE_AVAILABLE message, however the host never seems to poll for the RESPONSE_AVAILABLE and then timeout on the RNDIS Initialize message. I have previously seen this behavior and found that if I delayed setting up the RESPONSE_AVAILABLE message it would sometimes work. Specifically, I would send the REPONSE_AVAILABLE using main loop verses right away in the interrupt handler and it would work most of the time. This did not make any sense as that as I understand it the host has to poll for the RESPONSE_AVAILABLE so the timing of configuring peripheral to send message should not matter, since it is all host driven system. As I understand it the host does an interrupt polling messages to the RNDIS command end point to request the RESPONSE_AVAILABLE. I am not seeing and polling message from host (Windows) on the RNDIS interrupt end point. I do see EP0 polling, but not ones on the RNDIS command endpoint. I was wondering if anyone had experience with USB and possibly could offer some advice, education, or help. I do have all kinds of data captures and logs etc.. Thanks! Trampas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampas at gmail.com Thu Feb 27 13:44:50 2025 From: trampas at gmail.com (Trampas Stern) Date: Thu, 27 Feb 2025 14:44:50 -0500 Subject: [TriEmbed] USB RNDIS enumeration help needed In-Reply-To: References: Message-ID: I figured out that my driver was not sending a zero length packet after receiving the RNDIS Initialize message. This fixed the problem above, and now I am on to debugging the next issue. Thanks Trampas On Thu, Feb 27, 2025 at 9:50?AM Trampas Stern wrote: > I am trying to do USB RNDIS enumeration and having issues. I have googled > and read everything I can find and keep running into issues. I get the > enumeration working and it will work for days on my PC, then at some point > it will not work. I switch hubs, ports and it might work again for days, > then stop. > > I have been using Saleae logic analyzer as well as USB protocol analyzer > (Total Phase Beagle device) and have been unable to figure out the issues. > > > My initial thoughts were that Microsoft was doing some > predictive analysis on device timing. That is, I noticed that if the USB > request from the host came in too quickly it would cause issues. I > figured that based on the packet NAKs that Microsoft might dynamically > change request timing to compensate for slower devices. I figure this > would maximize the bus bandwidth utilization by not sending packets that > most likely would be NAK'd. I am not sure if this is true or not, but > sounded reasonable? I since changed my device to be all interrupt driven > for fastest response. This addressed some issues, but not all of my > problems. > > Now I seem to have hit another issue. The host sends an RNDIS Initialize > message, after which I setup device's USB peripheral to send the > RESPONSE_AVAILABLE message, however the host never seems to poll for the > RESPONSE_AVAILABLE and then timeout on the RNDIS Initialize message. > > I have previously seen this behavior and found that if I delayed setting > up the RESPONSE_AVAILABLE message it would sometimes work. Specifically, I > would send the REPONSE_AVAILABLE using main loop verses right away in the > interrupt handler and it would work most of the time. This did not make > any sense as that as I understand it the host has to poll for the > RESPONSE_AVAILABLE so the timing of configuring peripheral to send message > should not matter, since it is all host driven system. As I understand it > the host does an interrupt polling messages to the RNDIS command end point > to request the RESPONSE_AVAILABLE. I am not seeing and polling message > from host (Windows) on the RNDIS interrupt end point. I do see EP0 > polling, but not ones on the RNDIS command endpoint. > > I was wondering if anyone had experience with USB and possibly could > offer some advice, education, or help. I do have all kinds of data > captures and logs etc.. > > Thanks! > Trampas > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrglenasmith at gmail.com Thu Feb 27 17:32:16 2025 From: mrglenasmith at gmail.com (Glen Smith) Date: Thu, 27 Feb 2025 18:32:16 -0500 Subject: [TriEmbed] USB RNDIS enumeration help needed In-Reply-To: References: Message-ID: Did you write the driver or is this another one of those times where you spend a fair bit of time pulling your hair out checking your own work only to discover it was someone else that caused the problem? On Thu, Feb 27, 2025, 2:45 PM Trampas Stern via TriEmbed < triembed at triembed.org> wrote: > I figured out that my driver was not sending a zero length packet after > receiving the RNDIS Initialize message. This fixed the problem above, and > now I am on to debugging the next issue. > > Thanks > Trampas > > On Thu, Feb 27, 2025 at 9:50?AM Trampas Stern wrote: > >> I am trying to do USB RNDIS enumeration and having issues. I have >> googled and read everything I can find and keep running into issues. I >> get the enumeration working and it will work for days on my PC, then at >> some point it will not work. I switch hubs, ports and it might work again >> for days, then stop. >> >> I have been using Saleae logic analyzer as well as USB protocol analyzer >> (Total Phase Beagle device) and have been unable to figure out the issues. >> >> >> My initial thoughts were that Microsoft was doing some >> predictive analysis on device timing. That is, I noticed that if the USB >> request from the host came in too quickly it would cause issues. I >> figured that based on the packet NAKs that Microsoft might dynamically >> change request timing to compensate for slower devices. I figure this >> would maximize the bus bandwidth utilization by not sending packets that >> most likely would be NAK'd. I am not sure if this is true or not, but >> sounded reasonable? I since changed my device to be all interrupt driven >> for fastest response. This addressed some issues, but not all of my >> problems. >> >> Now I seem to have hit another issue. The host sends an RNDIS Initialize >> message, after which I setup device's USB peripheral to send the >> RESPONSE_AVAILABLE message, however the host never seems to poll for the >> RESPONSE_AVAILABLE and then timeout on the RNDIS Initialize message. >> >> I have previously seen this behavior and found that if I delayed setting >> up the RESPONSE_AVAILABLE message it would sometimes work. Specifically, I >> would send the REPONSE_AVAILABLE using main loop verses right away in the >> interrupt handler and it would work most of the time. This did not make >> any sense as that as I understand it the host has to poll for the >> RESPONSE_AVAILABLE so the timing of configuring peripheral to send message >> should not matter, since it is all host driven system. As I understand it >> the host does an interrupt polling messages to the RNDIS command end point >> to request the RESPONSE_AVAILABLE. I am not seeing and polling message >> from host (Windows) on the RNDIS interrupt end point. I do see EP0 >> polling, but not ones on the RNDIS command endpoint. >> >> I was wondering if anyone had experience with USB and possibly could >> offer some advice, education, or help. I do have all kinds of data >> captures and logs etc.. >> >> Thanks! >> Trampas >> >> _______________________________________________ > 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 trampas at gmail.com Fri Feb 28 12:46:38 2025 From: trampas at gmail.com (Trampas Stern) Date: Fri, 28 Feb 2025 13:46:38 -0500 Subject: [TriEmbed] USB RNDIS enumeration help needed In-Reply-To: References: Message-ID: I started with a driver example I found online, then started extending and debugging. I am finding that much of my problems are mainly timing issues. The example code for the USB is all blocking code, as such when using multiple composite devices, each device is blocking the other from getting processor and USB resources. It is the kind of problem that is made for an RTOS or async/await language.... Trampas On Thu, Feb 27, 2025 at 6:32?PM Glen Smith wrote: > Did you write the driver or is this another one of those times where you > spend a fair bit of time pulling your hair out checking your own work only > to discover it was someone else that caused the problem? > > On Thu, Feb 27, 2025, 2:45 PM Trampas Stern via TriEmbed < > triembed at triembed.org> wrote: > >> I figured out that my driver was not sending a zero length packet after >> receiving the RNDIS Initialize message. This fixed the problem above, and >> now I am on to debugging the next issue. >> >> Thanks >> Trampas >> >> On Thu, Feb 27, 2025 at 9:50?AM Trampas Stern wrote: >> >>> I am trying to do USB RNDIS enumeration and having issues. I have >>> googled and read everything I can find and keep running into issues. I >>> get the enumeration working and it will work for days on my PC, then at >>> some point it will not work. I switch hubs, ports and it might work again >>> for days, then stop. >>> >>> I have been using Saleae logic analyzer as well as USB protocol analyzer >>> (Total Phase Beagle device) and have been unable to figure out the issues. >>> >>> >>> My initial thoughts were that Microsoft was doing some >>> predictive analysis on device timing. That is, I noticed that if the USB >>> request from the host came in too quickly it would cause issues. I >>> figured that based on the packet NAKs that Microsoft might dynamically >>> change request timing to compensate for slower devices. I figure this >>> would maximize the bus bandwidth utilization by not sending packets that >>> most likely would be NAK'd. I am not sure if this is true or not, but >>> sounded reasonable? I since changed my device to be all interrupt driven >>> for fastest response. This addressed some issues, but not all of my >>> problems. >>> >>> Now I seem to have hit another issue. The host sends an RNDIS >>> Initialize message, after which I setup device's USB peripheral to send the >>> RESPONSE_AVAILABLE message, however the host never seems to poll for the >>> RESPONSE_AVAILABLE and then timeout on the RNDIS Initialize message. >>> >>> I have previously seen this behavior and found that if I delayed setting >>> up the RESPONSE_AVAILABLE message it would sometimes work. Specifically, I >>> would send the REPONSE_AVAILABLE using main loop verses right away in the >>> interrupt handler and it would work most of the time. This did not make >>> any sense as that as I understand it the host has to poll for the >>> RESPONSE_AVAILABLE so the timing of configuring peripheral to send message >>> should not matter, since it is all host driven system. As I understand it >>> the host does an interrupt polling messages to the RNDIS command end point >>> to request the RESPONSE_AVAILABLE. I am not seeing and polling message >>> from host (Windows) on the RNDIS interrupt end point. I do see EP0 >>> polling, but not ones on the RNDIS command endpoint. >>> >>> I was wondering if anyone had experience with USB and possibly could >>> offer some advice, education, or help. I do have all kinds of data >>> captures and logs etc.. >>> >>> Thanks! >>> Trampas >>> >>> _______________________________________________ >> 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: