 Hello, everyone. This is the Circuit Python Weekly Meeting for March 20, 2023. It's the time of week where we get together to talk about all things Circuit Python. I'm Jebler, also known as Jeff Epler, and Adafruit sponsors me to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support Adafruit and Circuit Python and folks like me, consider your purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join us anytime by going to adafruit.com. There's pretty much 24-7 activity, but we hold this meeting in the Circuit Python DevTex Channel and the Circuit Python Voice Channel, typically on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with the U.S. holiday. In the notes document, there is a link to the calendar that you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you'd like to receive these notifications or if you'd like to participate in the meeting, ask us to add you to the Circuit Python Discord role. I just mentioned the notes document. If you are participating live, you'll find that under the PIN messages tab. Otherwise, you'll find a link in the doobly-do with timestamps so that you can skip around to the parts that interest you the most. The meeting tends to run 45 to 60 minutes, and after the meeting, we will pin the next week's meeting notes to the Circuit Python DevTex Channel on the Adafruit Discord. You can find that document anytime during the week so that you can add your notes, your hug reports, and your status updates for us to read during the meeting. This meeting is held in five parts. Next up is community news. Look at all things Python, Circuit Python, and Python on hardware in the community, and it's a preview of our Python and Microcontrollers newsletter made by the Inevitable AN. The second part is the state of Circuit Python, the libraries, and Blanca. It is a quantitative overview of the whole project and a chance to look at the project by the numbers separate from our status updates. Next, and the first participatory section is hug reports. An opportunity to highlight the good folks things are doing, taking the time to recognize awesome folks in and around the community. And that's fun. I just got signed out of the document that I was in. Bear with me here as I get back in. All right, that's fun. All right, so where were we? Hug reports. Taking the time to recognize the awesome folks in our community. The next up after that is status updates. Status updates is an opportunity to report on what we've been up to. Take a couple of minutes and talk about what you've been doing since the last meeting and what you'll be up to over the next week or so. And if you have anything else from your life that's appropriate to share, please do. We like to get to know each other a little better than just talking about the work. And then the fifth and optional part is in the weeds, the opportunity for a more long form discussion. This discussion can come out of status updates or be something you've identified ahead of time as too long for status updates. And that's how the meeting will go. And with that, I will step over to community news. First up, MicroPython support for the Raspberry Pi Pico W has started. Oh, okay. For the Pico W, Bluetooth has supported. So Phil Howard at Pimeroni is working to complete a GitHub pull request for Bluetooth support in MicroPython. It's labeled as experimental at the moment. The notes say Bluetooth works. You'll want Adafruit's Blue Fruit Connect and the MicroPython BLE Simple Peripheral.Pi and BLA Advertising.Pi if you want to experimentally kick the tires. And thanks Tim for getting some of the links. There is a Twitter and a GitHub as well as a blog discussing the progress. As item number two, CircuitPython 8.0.4 has been released. It is a bug fix revision of CircuitPython and the newest stable release. And we've got a link to the blog and the GitHub release notes. We encourage everybody who is using CircuitPython to upgrade to this latest bug fix version. Another MicroPython item, MicroPython switches to a new package manager known as MIP. MIP stands for MIP installs packages. And it's similar in context and concept to Python's PIP tool, but it does not use the Pi PI index. Rather, it uses MicroPython lib. It will automatically fetch compiled NPY files when downloading from MicroPython lib. And there is a link to the documentation in MicroPython. Next up, we have podcasts. CircuitPython needs to... Charlie Nganda was interviewed on embedded.fm. They spoke with her about making things glow, dealing with imposter syndrome, and using origami. The projects talked about are documented on her website. You can find her on Instagram and Mastodon. Adafruit came up a lot in this episode. And those are just a few items from the CircuitPython Weekly newsletter. This and more is available in our Weekly Python for MicroControllers newsletter, which goes out via email on Tuesday mornings. To subscribe, visit AdafruitDaily.com. And a big thanks to Ann for putting the newsletter together. If you have any Python on project hards... If you have any Python on hardware projects to share, whether that is CircuitPython, MicroPython, or Python running on Raspberry Pi or a single board computer, please consider contributing that to the newsletter. You can open a pull request on GitHub, tag at AnnEngineer on Twitter with the hashtag CircuitPython, or email cpnewsatadafruit.com with a link. And that is community news. Next, we are going to talk about the state of CircuitPython, the libraries, and Blanka. So, this is a quantitative overview of the whole project. It's mostly stats plucked from GitHub and a few other places. It gives us a chance to look at the health of the project separate from our status updates. We'll talk about the project overall, then separately discuss the core libraries and Blanka. And Scott, Katni, and Melissa, if there's any reason that I can't pass it over to you at the appropriate time, please let me know. Alright, so overall, on the past seven days, we saw 27 pull requests merged from 19 authors. And regrettably, I didn't go through this list to mention people who I don't see as regular contributors, so I'll just read a couple of off. We've got Brent Y.I. Paint Your Dragon is a native fruit person, but doesn't work on CircuitPython a whole lot, so thank you. Cryer, Cree Steve, Steve Foundry. There's a lot of less familiar names here. D. Karchner, B.W. Shockley, Furbrain, so thanks to those folks who are less frequent contributors and thanks to the folks who are regular contributors as well. And next stat, we had eight reviewers across everything, so big thanks, especially to those who are not kind of the core people. So thank you, Micradev, and thank you to Jose Posada, as well as more internal people like Tim, myself, Scott, Dan, Melissa, and Tektrick. Issues-wise, we saw 26 issues closed by 14 people and 17 open by 16 people, so it's nice to see a downward trend for a week, and it's nice to see the number of people who are participating in issues, so thank you to all of those folks. And now I will turn it over to Scott to talk about the core. Hello. Okay, for the core, we had 13 pull requests merged from 10 different authors, so thank you to all of those authors. We had five reviewers, and thanks again to reviewers. We're always looking for more reviewers, because the more reviewers we have, ooh, good morning. The more reviewers we have, the more authors we can support. We have 35 open pull requests, which is quite a lot, but many, many of those are drafts, so if you have boards in particular that have open draft PRs, please take a look at those. And the number of these are pretty early, so that's good too. Issues-wise, we had 17 closed issues by 8 people and 13 opened by 12 people, so a good number of people involved in getting through issues, which is awesome. We have a total of 639 open issues. We use milestones to gauge priority for Adafruit-funded folks. So we have zero open issues on 8.0.x, which is our kind of highest priority thing. And then the next stable release will be 8.1, and there's 11 open issues on 8.1. We have 25 for 9.0, and 9.0 will probably, development will probably start after 8.1 is marked stable. We have seven issues not assigned to milestones, so we'll have to take a look at those and prioritize those, triage and prioritize those as well. And that's the numbers for the core. Thank you, Scott. Next up is the libraries. And Katnie, may I say welcome back? Thank you. So this is about all of the CirclePython libraries, including the CirclePython community bundle, the Adafruit-circuit-python libraries, which is everything that starts with Adafruit underscore-circuit-python underscore, and a few extras such as our cookie cutter. We had 12 pull requests merged across all of those libraries. With eight authors and four reviewers, leaving us with 42 open pull requests. We had seven closed issues by five people, and four opened by four people, leaving us with 602 open issues. 74 of those are labeled good first issue. If you're interested in contributing to CirclePython and the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more, including a list of open pull requests and all of the issues listed out as well by library. If you're interested in contributing code or documentation, check out the open issues page. If you're new to everything, good first issue is a great place to start. If we have a guide on contributing to CirclePython using Git and GitHub, and we're always available on Discord to help. If you're interested in reviewing, check out the open pull requests. Take a look at the code. If you have the hardware, please test it. If you do not, check the code, if it's solid, leave a comment and let us know you did that. Once you're comfortable with that, we can talk about leveling you up to the review team. In terms of library PyPI weekly download stats, there were 167,769 PyPI downloads, over 309 libraries, and the top 10 can be found in the notes. In terms of library updates, in the last seven days, we had one, two, three, four, five new libraries. And a number of updated libraries. One thing I do want to call out is that Cedar Grove Studios submitted CircuitPython underscore 85293. That is the 100th community library to be submitted to the community bundle. So congratulations Cgrover, thank you so much, and congratulations to everybody who's submitted to the bundle to get us to this number. We always had high hopes for the community bundle and obviously without community support and us supporting the community, it wouldn't live up to what we hoped it would, but it has definitely become that and it is continuing to be that. So thank you to everyone who has submitted a community library. And that's what we have for the libraries. All right, thank you, Katni. And to round out this section, Melissa will give us the updates on Blinka. Hello. So Blinka is our CircuitPython compatibility layer for MicroPython and SiriPy and other single board computers. And this week we had two pull requests merged by two authors and one reviewer. There are currently four open pull requests amongst all the repositories and there were two closed issues by one person and zero opened, leaving a net of 94 open issues. We had 16,449 PyPI downloads in the last week and 10,489 PyWheels downloads in the last month and we are at 101 boards. So it's all looking good. Thank you, Melissa. The next section is Hug Reports. Hug Reports is a chance to highlight folks in the CircuitPython community and beyond for doing awesome things. Let's start then go down the list in the document order to give everyone a chance to participate. If you're text only or missing the meeting, I'll read your notes when I get to them in the list. So I have a hug report to Tim, foamy guy, it was nice to see you in person and thank you for picking up the tab. We had a lovely brunch together, got to catch up on mostly non CircuitPython stuff. That was fun. Next up, Dan, thank you for taking over that pull request to enable creating FAT32 file systems again. I had made a change between 7.3 and 8 to disable the creation of larger FAT file systems across all of the boards to save flash storage. And a user ran into this as a problem because they wanted to format a larger SD card with CircuitPython. And I made a quick pull request to re-enable that, but it didn't quite fit on all of the boards and Dan took that over, so thank you. And final hug to Katnick. Welcome back. The community missed you and I missed you. And next I'll read notes from Seagrover and after that hand it over to Dan. Seagrover writes, a hug to BlitzCityDIY, Liz, for the beautiful, plucky, and sweet-sounding MIDI Liar robot. A second hug to Jose David for the quick turnaround of a community bundle submission. And finally, a hug to the 27-plus contributors to the CircuitPython bus device library. Having some interference and performance issues using two spy devices from the same manufacturer, bus device was able to sort it out and accommodate the disparate lock and timing constraints. This is an utterly amazing tool that just works. And next up is Dan. Okay, thanks to you, Jeff, for knowing why formatting larger SD cards did not work. So you remembered what you've done saving me work and trying to pursue that. That was great. And thanks to Scott for pursuing performance and kind of turning it into a science rather than a ad hoc thing. Okay. Thanks, Dan. Next I have notes from David Glode and then I'll hand it over to, I guess I'll be reading more, notes from a couple of people. All right. So first, David writes, a hug to DJ Devin3, the first and only international shipping of a TR cowbell. To NaraDoc for adding board.display support on the Lolan S2 Pico. And to TTMobi for adding Lilligo T embed support. And to Mayor Melissa for updating that on CircuitPython.org. And as DJ Devin3 doesn't seem to be here, I'll read his notes as well. Devin has a hug to Tectric for volunteering to review my Steam API example PR for the Adafruit Request Library. A hug to all the community members that turned out for last week's show and tell with a special hug to Steve X for his first show and tell. He showed a really nice southern list, multi solenoid and relay project. And finally a hug to SCUR for advice on a PCB design project. All right. FOMI guy, you are up. And then I'll read notes from Jose David. All right. Thanks, Jeff. First up, I'll report for you. It was great to get a chance to hang out and catch up over a meal. I definitely appreciate it and had a great time. Thanks to Isaac Ben, Neerdoc, and Anecdata as well, Scott, all of whom helped me in various different ways to be able to get the disk info web workflow API working. I could not have got there without hope from all of these folks. And a hug report for Jose David, who's responded to a couple of different issues across GitHub and has been submitting lots of different improvements across lots of different libraries as well. Thanks. All right. Thank you. By the way, FOMI guy lives just a couple of hours away. So like this is the second time I've hung out with him. But, you know, it takes a bit of an excuse to drive three hours. Anyway, Jose David writes a hug to Neerdoc for being helpful and to test the simple dial library in the Lilligo watch to make a clock. I only wear a watch while exercising, but I've ordered a Lilligo watch to use with circuit python. Thanks to Neerdoc for adding the support for it. Next, a hug to Cgrover for including the 805293 digital potentiometer driver in the community bundle. A hug for FurBrain. Also for including two new community libraries, AsyncButton and it says here DistoxLibrary. I'm not sure what library that is. Also a hug for DJDiven3 for helping me with hardware ideas and being an excellent sounding board for new projects. Next, a hug for Tectric for solving an old issue in the community library zip packaging system. Zip files in the release artifacts were only including the examples files when the library was a package. And thanks also to Casa Eno for reporting it. And finally, a hug to Fummy Guy for testing and finding the problem with the Blinka hard example in Bitmap font. And that brings us to Hug Reports from Katni. So first up, to reiterate, a hug report for Cgrover for submitting the 100th library to the community bundle. I have a hug report for Keith the EE for a wonderful circuit Python LED hat workshop and build along on the Python Discord. It's been over a year in the coming and it was absolutely wonderful and worth it. And I hope that there are more to come in the future. And finally, a group hug to the whole community for keeping everything running smoothly while I was out for three weeks. And I was absolutely disconnected from work for a vacation and knowing this community is amazing was a part of why I was willing to do that. So thank you very much. Thanks, Katni. Next we have maker Melissa. I want to give a hug to Dan for helping out with circuitpython.org and also to David Claude for contributing to circuitpython.org. I want to give a hug to Matthew J.S. and Al I'm sure butchered that for fixing the Rock 4 and Orange 5 4 boards in Blinka. And Katni, welcome back. I want to give a hug to everyone who has tried the new installer and provided feedback and a group hug to everyone else. Thank you, Melissa. I will read notes from a couple of folks and then let Scott wrap up this section. But first, Mark writes a hug to Tenut for some quick answers about how he was doing performance testing to give me a path to follow as well as some PR review suggestions. Then I have a note from Paul Cutler, a hug for Dishaput and Nerdok for helping me with code for my reverse TFT remote control project this weekend. And now take it away, Scott. Thanks, Jeff. First, a hug to Foamy Guy for the Disk Info API PR. Totally did not expect it. But I saw it go by in the chat and I'm very excited, so thanks for picking that up. I have a report to Werewolf from I Am Hex. It's a kind of reverse engineering Hex viewer tool that I definitely recommend. The coolest part about it is that you can have bookmarks. So if you're trying to understand a binary file, you can either generate a bookmarks file that has JSON in it and load it and visualize it in I Am Hex or you can just annotate it by drawing on it and then export it, which is cool as well. They helped me understand what the format was on their Discord, so that was super helpful. A hug report to Flavio T on GitHub for the PySigRock PRs. They had dropped into the SigRock IRC channel asking about a plugin based version of SigRock and I was like, oh, I know this, so I managed to contact them and they were super excited and did some PR, so I'm going to look at those this week. And then lastly Gordon from Raspberry Pi just dropped me an email to let me know that they're now automating their USB PID listings. Those of you have probably seen that there's been some PRs blocked by people saying they got a PID from Raspberry Pi but it wasn't listed publicly, so Gordon's updated his workflow so that they get updated more quickly, which is super helpful and wanted to do a hug report for that. And that's it for me. Alright, thanks Scott, thank you everybody. Next up is status updates. It's the time to tell folks what we're up to individually. I'll start and then we'll go through the list on you. Please take a couple of minutes to talk about what you've been doing since the last meeting and what you'll be doing until the next meeting. It's also an opportunity to provide quick tips and tricks but if this discussion becomes long it's best to move it in the weeds and just another general reminder you can add your topics to in the weeds at any time until we get there. And I will go first. I've been working for a couple of weeks on IMX, specifically using the i2s out peripheral and finally I got this morning the bit clock and the LR clock pins toggling. There's no actual audio data coming out yet. Hopefully once the audio data comes out it will be close to done. I'm guessing it's a pin-muxing problem because that and clocking have been the two problems that I've had but I don't know yet. And there's also a peripheral called the medium quality audio it's a way that the chip internally can take one of the i2s out peripheral data and turn it into a PWM audio stream on a particular pair of pins. So they would really share most of the implementation. That is what I will be working on next after i2s out is wrapped up. Yeah, so that's what is up with me. It feels like a short list but there's just been a lot of learning self-teaching about how the IMX works all along with this. And next because Ketny needs to leave early why don't you go ahead with your status update? Thank you. It's looking like we might be done by the time I have to go but still I didn't want to take a chance. Alright, that's fine. Yeah. Last week I returned from being out for a bit and worked on Thursday and Friday which was basically just filled with miscellaneous tasks of which I have many so it was good to kind of get through some of that backlog. This week I will be writing up the guide for the Feather RP20 or RP2040 DVI board. It's pretty much identical on some level to the RP2040 however there are 8 pins used for a DVI output on the board. So I'll be doing up a guide for that. The next one up is the Feather RP2040 RFM boards. Plural, there are 4 I believe but they all use the exact same pinouts so I'll be doing the board definition for those and the pretty pins to get ahead of that and then depending on how long those take I'll be doing the lining grow light and time lapse projects between Feather things. Other stuff, I pause the time lapse I think that particular plant is slowly dying if it was going to bloom it would have already. This means I can set it up in a better location in a better way when I choose another plant to photograph. Also use a raspberry pie that's more available currently using a pie 0 to W and pick another less dying plant to time lapse. I built a grow light setup using air plants right before leaving 4 weeks ago. I researched it and apparently dot stars have the right frequencies for plant growth the plants are thriving so evidently it's working they require a lot of light to be happy. Incidentally I had the brightness set at 20% from testing which I completely forgot about so I bumped it up to 70 yesterday and apparently overdid it. Came in this morning to dim LEDs, a powered off microcontroller and electrical burning smell. The board was fine dropped brightness to 50 plugged it all back in, same results swapped out the power supply and everything is happy again that power supply is now in the trash. There will be a guide for this project but I'll be using far less LEDs I already knew this was overkill but apparently it's serious overkill for the linear space that I'm lighting I apparently need 60 LEDs and there are currently 384 I used the high density dot star strips when medium density or even low density would likely work so for the actual guide I'll be using a much lower density strip which also is much easier to solder and will probably be able to be at full brightness without destroying another power supply that's what I've got. Live and learn. Pretty much. And before we move on I'll just circle back I was talking about the DistoX library and Fomy Guy says it mimics the DistoX protocol for communicating with paperless cave surveying tools and apparently it works over Bluetooth. So if you're in that world you probably know what it is and if you're not in that world you probably don't need it but anyhow, next I have notes from C Grover who is text only. C Grover writes the final evolution of the string length calculator algorithm for the string car feather wing project was completed and successfully tested on the bench. This is a senseless version that uses the initial string in collision of the first lap to learn string length and predict the return trip regardless of DC motor speed and battery decay. It looks like the weather may prevent an infield test between trees along the river very soon. After reaching a few false summits the AD 5293 digital potentiometer driver was completed and submitted to the community bundle. This is a 10-bit linear potentiometer that accommodates true AC signals by using the dual power supplies needed by op amps. This is the final piece of the technical puzzle for the Precision VCO module project. Osh Park produced the extra perfect custom breakout PCB and next with appropriate musical fanfare is the Precision VCO Euro Rack module. And next up we have news from Dan. Okay, so last Tuesday I released circuit python 804 Right now I don't have any urgent fixes in the pipeline for an 805 so maybe it will stay that way. We'll see. I fixed a bunch of miscellaneous build and release problems. I fixed an HID library issue that somebody found in which the LED the keyboard LED state was not being remembered properly so that PR is still actually waiting to be reviewed. Maybe I'll have the original course to review it or if somebody else wants to review it, that'd be great. I also noticed that there are a bunch of outstanding issues for the HID library and another thing I noticed is that our examples for HID code don't check to see whether the USB is connected or not that didn't exist when the HID library was written so it's probably worth updating the examples for the HID library and at least some of the examples in the Learn Guide so I'll probably take a look at that on and off. There were a lot of things to review and there were a lot of bugs to test, potential bugs to test to see if they were really bugs or not. Some of them are and some of them aren't so I feel like I'm fighting a lot of fires at the moment but they're small fires and when I get off of that I'll try to go back to working on more 8xx issues and especially things like USB host for IMX or other things for IMX. Okay, that's it. Thank you Dan and now that you mentioned it I know that one of my projects on Learn was affected by this not checking USB connected and I guess I'll go ahead and fix that now. Anyway next I've got notes from a couple of people and up after that will be Foamy Guy. So David Glowde writes that he's been testing the board.display support for the Lolan S2Pico by Naradoc closing the issue, updating circuitpython.org as well as quick testing of the Lilligo T embed by TTMobi. Next, DJ Devin writes submitted a PR for a 3D design of the Adafruit 7 inch TFT touchscreen to the Adafruit CAD parts repo should make it easier for anyone wanting to print 3D enclosure using the bare 7 inch display. The 5 inch display is still missing from CAD parts however anyone can now scale down the 7 inch to 5 inch since they're almost identical except for display size. Next up, my Laura mail boom box is now a 2x40 watt system for 100 watts peak. For a 4 inch speaker system that's pretty impressive. Switched to a 100 watt pile amplifier with built in Bluetooth classic. It'll help cut down on the spaghetti monster inside the mail box. And finally designed a mountable 15 Neopixel strip on a PCB that I'm calling Bleeding Rainbow. Adafruit's Neopixel strip would have worked nicely but I wanted to learn how to design a Neopixel strip myself for the next version of the TR cowbell. Alright, Tim, you are up next. Alright, thanks Jeff. The last like a couple of weeks or so I've been fighting against my computer a little bit with some issues that I was thinking were hardware issues and I swapped out some RAM and have updated lots of things and have seen some improvements but I've also seen some weirdness that is cropping up during circuit python builds. But I'm kind of going fingers crossed and hoping that we can at least be done with it freezing up which I haven't seen since the last couple of rounds of things I've updated. So improvement but still something going on in there that I'm trying to get worked out. In circuit python land I tested out some of the speed differences between the boundary fill function which there's an open PR to add some handling of background tasks and interrupts to that so put in an example and some results on that PR with the differences in times for those two variations. Last week I worked on a change in the scrolling label library or it's actually just in the display text library but it's the scrolling label specifically had a slightly different API with regards to the name of the property that you can use to set its text which was due to me not knowing a different way to do it when I wrote it initially but I have since learned that and went back and fixed that based on some feedback on an issue there. I implemented the disc info in point for Web workflow learned a lot about FATFS which I think is the library we use for handling that stuff as well as just the core generally in the process. For this week I have a couple of different PRs lined up most of them are around Web stuff in particular Ethernet I got to get out my feather wing and my other router and get stuff set back up on my desk to test with that this week so that's what I've got going on, thanks. I'll read some notes from Jose David and then after that is maker Melissa so Jose David has been working on pull request reviews as well as an issue for the EMC 2101 which I believe is a library and I don't know what the device does. Alright Melissa you are up next. So last week I finished the changes to the circuit python installer so it can be used in other places besides circuit python.org I made a small follow up PR on circuit python.org that fixes some bugs with the installer and updates one of the boards. I worked more on a secret chat GPD project which I'm hoping to share and show until this week. I updated the Web serial ESP tool code to remove some deprecated stuff. This week I'm going to work on designing a 3D printable part for the secret project and then finish that all up and I'll likely start writing a guide for it and then I'll work on fixing some other GitHub stuff after that that's where I'm at. Alright I think I've heard the rumor about what the project is and if what I heard is right it will be worth tuning in to show until to see this project when it is ready. Sounds fun. Anyway and last reminder if you have any in the weeds topics add them now. But now I will read notes from Mark a.k.a. Gambler who is hopefully finishing up a port request to ensure memory release for on disk GIF and display audio bitmap that are quicker and easier to pick up by the garbage collector. And now Scott you get to round out this section of status updates. Alright so you know the preview of this but I spent a lot of time last week trying to figure out how some mystery build of Circa Python was seemingly twice as fast and I ended up getting to the point where I could generate builds that were the same and one of the things that I had to change was the way that I was measuring the time which is not which was not right. So by changing how I measured time I changed what the results were even though it wasn't actually faster which is a huge face palm and I knew that I had done that and it's frustrating for sure. I learned a lot of neat reverse engineering sorts of tools and processes to figure that out lots of squinting it to hex dumps which I did get pretty much technical results which is kind of cool. But the moral of the story is that you should always have a reference reference measurement clock measurement to make sure that your onboard clock is in the right ballpark so I'm working on adding that right now and then I will publish the I think that it's already as a draft PR but I had to fix the teensy four which I just did and so I'll polish that up and hopefully get that out today. Once that PR is out I think I haven't run the numbers because the script is not working but I think it is like a 3x speedup so it should be awesome. Once the PR is out I'm going to do some e-paper tests I've got a prototype of the e-paper feather and Lamar also asked me to do a check on the RP2040 deep sleep power consumption so I'll be taking a quick look at that while I'm doing e-paper stuff. After that I'm going to get back to the IMX and try to get all of the EVKs going because unlike the SAMD 51 or 21 we're actually starting at the bottom of the chip family line which is quite exciting because we're going to have faster and more RAM chips that we can move to or make products for afterwards so I want to make sure that we're ready for that and I should say that the EVKs are the manufacturers dev kits, evaluation kits from NXP for the IMX so I've got a collection of those I've been so excited for these for so long so I'm excited to get to that and support the full family maybe including the 1176 which has a it's clocked at a gigahertz which is kind of obscene thank you Scott kind of excited about it honestly yeah, sounds like so we have no in the weeds topics this week so I will do the little outro this has been the circuit python weekly for March 30th 2023 thanks to everyone who participated if you want to support Adafruit and circuit python and those of us that work on circuit python consider purchasing your parts from the Adafruit shop at adafruit.com video of this meeting is released on youtube at youtube.com slash adafruit and the podcast is also available on major podcast services it is also featured in the python for microcontrollers newsletter visit adafruitdaily.com to subscribe the next meeting will be held at the usual time of 2pm eastern 11am pacific on monday march 27th just a reminder we are already observing daylight saving time or summer time here in the united states I think various other countries are switching over now or soon so just double check what that offset is to your local time this meeting is held on the adafruit discord which you can join by going to adafruit.it slash discord to be notified about this meeting and any changes to the time or day you can ask to be added to the circuit python east's role on discord it's free it gives you just a few notifications a week and we'd love to add people and bring you into our community a little closer anyway that's all we hope to see you next week thank you everybody