 Hello everyone, this is the CircuitPython Weekly for August 30th, 2021. This is the time of the week where we get together to talk about all things CircuitPython. My name is Scott, and I work on CircuitPython for Adafruit, and I just realized my headphone cord was zipped into my hoodie. CircuitPython is a version of Python designed to run on tiny computers called microcontrollers. CircuitPython development is primarily sponsored by Adafruit, so if you want to support them and CircuitPython, consider purchasing hardware from Adafruit.com. This meeting is hosted on Adafruit Discord server. You can join any time by going to the URL adafru.it slash Discord. We hold the meeting in the hashtag CircuitPythonDevTextChannel and the CircuitPythonVoiceChannel. This meeting typically happens on Mondays at 2pm Eastern, 11am Pacific, except when it coincides with a US holiday. If the meeting time is changed, we'll notify you via Discord. If you wish to be notified about changes to the meeting, we can add you to the at CircuitPythonNisa's Discord role. There's also a calendar available that we try to keep updated if you'd like to subscribe to that. Speaking of which, next week will be on Tuesday and not on Monday, because Monday is a US holiday, so next week applies to this. We'll be meeting on Tuesday, not Monday, I'll say it again. This meeting is recorded. We record the audio from the VoiceChannel and the video of the TextChannel. If you'd rather not have your voice recorded, you're still welcome to participate by adding to the NotesDoc. The video this meeting will be posted to YouTube and the audio is released as a podcast. If you find this podcast is not available on your favorite podcast service, please let us know. There is a NotesDoc to accompany the meeting and recording. If you wish to participate but can't make it to the meeting, you can leave hug reports and status updates for us in the document, and we'll read them off during the meeting. The NotesDoc also contains timestamps to go along with the video, so you use the doc to view only, so you can use the doc to view only the parts of the video that interest you most. The meeting tends to run 60 to 90 minutes, so this gives you the option to skip around. A link to the NotesDoc is posted in the CircuitPython DevChannel on the Adafruit Discord every week. Check the pinned messages to find the latest NotesDoc. This meeting is held in five parts. The first part is community news. This is a look at all things CircuitPython and Python on hardware in the community. It is a preview of our Python on microcontrollers newsletter. The second part is the state of CircuitPython libraries in Blinka. This is a statistical overview of the entire project. It's a chance to look at the project by the numbers separate from what we've all been up to. The third is hug reports. Hug reports is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. The fourth part is status updates. Status updates is an opportunity to sync up on what we've been up to. Take a couple of minutes and talk about what we've been doing in the last week since the last meeting and what you'll be up to over the next week until the next meeting. The fifth part is in the weeds. In the weeds is an opportunity for more long form discussions. These discussions can come out of status updates to be something you've identified ahead of time as too long for status updates. And that covers how the meeting will go. With that, I will get started with community news. And I will take a time code before I do that. So this is community news. The first item we have on community night, community news, hello Monday morning, is building with circuit Python podcast. The real Python podcast presents building with circuit Python and constraints of Python for microcontrollers with the lead developer of circuit Python with Scott Shockroft at Adafruit. That's myself. You can check it out at realpython.com slash podcasts slash rpp slash 75. And the pitch or the description of this goes, can you make a version of Python that fits within the memory constraints of a microcontroller and have it still feel like Python? That is the intention behind circuit Python. This week on the show, we have Scott Shockroft, who is the project lead for circuit Python. We talk about all things circuit Python while working with the language on several projects. I've developed many of my own questions to ask Scott. Scott answers my questions about bootloaders, packages, the bundle and Bluetooth low energy BLE. He also talks about the struggle of fitting the language and board specific libraries within tiny memory constraints. We just discussed projects and boards for beginners and many resources to learn from, learn more. All right, next up in community news, Linux turns 30. On August 25th, Linux, the ubiquitous operating system turns 30 years old. Dated from a post graduate student, Linus Torvalds posted on the comp.os.minix news group. And there's a link to the Adafruit blog about it. It says, Linux turns 30. This is from ZDNet. Linux turns 30. Linus Torvalds on his just a hobby operating system and interview with Linus Torvalds. All right, next up. Arduino embraces Python. Power of Python for Arduino, Nano, RP2040 Connect and the Nano 33 BLE. It's a link to the Arduino blog, and there's a link to the Adafruit coverage as well. Quote, Python support for three of the hottest Arduino boards out there is now yours through our partnership with Open MV and the Nano RP2040 Connect, Nano 33 BLE and the Nano 33 BLE Sense can now be programmed with a popular micropyton language. Next up, Halloween hack fest. Join Hackaday DigiKey and Adafruit for a Halloween themed contest. They want to see your crazy, creepy, ghostly, spooky and awesome projects. If costumes are your favorite part of Halloween, then why not dress up your outfit with some hacked upgrades? You could even design a ghoulish prop to add to your home's Halloween decor or light up a jack-o'-lantern with LEDs. Whether it's technical, artistic or just plain terrifying, Hackaday wants to see your projects. Check out the Halloween show and tell with Hackaday Friday, October 29th at 1 PM Pacific to show off your awesome projects entered in the contest. Don't forget to also share your projects on social media and use the hashtag Halloween hack fest. Hackaday and DigiKey have partnered on this Halloween themed contest to offer three winners an online shopping spree to the DigiKey warehouse. With links there to Hackaday and Hackaday IO. Next up, 10 beginning Circuit Python education courses. Professor John Gallagher has released 10 new Circuit Python school videos for his fall course. They are tutorials for beginners. The first videos use the Adafruit Circuit Playground, Bluefruit Slash Express. He states the videos are free to share with educators and newbies. Check out the first video on YouTube, which describes the series, and you'll see the whole playlist. And thank you to Fome Guy for putting the links in the Discord chat. Okay, we've were through the news. This all comes as a preview for the newsletter. The Circuit Python Weekly newsletter is a Circuit Python community run newsletter emailed every Tuesday. The complete archives are available at adafruitdaily.com slash category slash Circuit Python. It highlights the latest Python and hard to relate related news from around the web, including Circuit Python, Python and MicroPython developments. To contribute your own news or project, edit next week's draft on GitHub. Go to the github.com slash adafruit slash Circuit Python dash weekly dash newsletter and check the drafts folder there. You can submit and pull requests with the changes, or you may also tweet tag a tweet with hashtag Circuit Python on Twitter or email cpnews at adafruit.com. And that's it for community news. Next up, we have state of Circuit Python libraries in Blinka. This is a statistical overview of the health of the project, and it's broken down by the major components of Circuit Python overall. So overall, I can't type this morning, apparently. I don't know. There it is. Couldn't find my colon. OK. Overall, we had 54 pull requests merged from 19 different authors. So thank you to everybody who contributed. I think all of these names I do recognize previously. Maybe Wormbit is new, so thank you to Wormbit. And thanks to all of our authors. We had 12 reviewers, so thank you to all of our reviewers. You help us support all of these authors, so we really appreciate it. Issues-wise, we had 42 closed issues by 11 people. 21 opened by 16 people, so we're down 21, which is awesome. So those are the stats for overall. For the core, we had 41 pull requests merged from 16 different authors. So thank you, again, to all of our authors and reviewers. We had eight reviewers for those 16 authors. So thank you to all of our reviewers on the core. I think eight reviewers is actually a bit more than we normally have. So that's awesome. We have eight open pull requests as of these stats. The two oldest are 37 and 23 days old, so not too bad. Everything besides that is three days or less. So we're cruising through stuff, which is awesome. We've been making a lot of progress, and I'll talk about that just in just a bit. Issues-wise, for the core, we had 29 closed issues by six people, 14 opened by nine people. So we're net down 15 still, which is awesome. We have 415 open issues. We have six active milestones. The main ones are the main things to note here is that we have five issues not assigned to milestones. So those need to be triaged, and we have four open issues under 7.0.0, which is the ones that we want to close before we do a release candidate. Speaking of which, overall, we're very close to release candidate. We'll do it this week, barring any catastrophic bugs that I cannot fix. So expect to see that. We really want to push to get 7.0 out the door, because 6.3 is aging. There's lots of good fixes in 7.0. So with that, let's kick it over to Katnney for the library update. I didn't even realize you'd gotten through the core. I was writing out my library update. Sorry. I'm cruising. I'm cruising here. You are. So we had, this applies to all the Adafruit Circuit Python libraries. That's everything that starts with Adafruit Underscore Circuit Python Underscore, as well as a few extras such as our cookie cutter and the community bundle. So all this information applies to all of those repositories. There were 13 pull requests merged by eight authors and eight reviewers. That's leaving 54 open pull requests. We had 12 issues closed by seven people and five open by five people. So that left us with 340 open issues. In terms of library updates in the last seven days, we had one new library, the ST7565, and a number of updated libraries that I will not read off. If you're interested in contributing to Circuit Python on the Python side of things, go to circuitpython.org slash contributing. You'll find all of this information and more open pull requests, open issues, and library infrastructure issues. Take a look at the open issues list, see if anything strikes you fancy. Leave a comment if you're going to work on it. In terms of reviewing, reviewing is a great way to participate. It's super helpful to us because as Scott stated earlier, the more reviewers we have, the more authors we can support. To start reviewing, take a look at the open PRs. And if you have the hardware, test it. If you don't, feel free to check it for syntax or simply check the code and leave a comment. If you have any questions, feel free to ask them. And if it looks good to you, let us know. That is super helpful. And it's a great way to get started with reviewing. And once you're comfortable with that, we can look at adding you to our review team. So overall, we're continuing to see new libraries and updates to the libraries being added every week. Something that occurred to me because of the Halloween Hackfest section of the community news was with Hacktoberfest being imminent, I would like to put a call out to folks who are interested in helping us go through the library issues list and labeling good first issues as such as we head into October. When our good friend Adobot automatically adds the Hacktoberfest tag to good first issue labeled issues. As stated earlier, as of this meeting, there are 340 issues to go through. Three are currently labeled as good first issue, but if I remember correctly, they're not really well labeled, so we should consider updating those as well. Further, for those that are familiar with the libraries, it would be greatly appreciated if we could identify issues that haven't been filed that fit the good first issue labeled, docs updates, etc. While this is ostensibly being done under the blanket of Hacktoberfest, it's something I've been trying to do for a long time, so it's worth doing regardless of the reason. Having good first issue labeled issues lowers the barrier for folks who are new to all of this and want to contribute. And right now, we have been woefully lacking in keeping that particular label well applied. So if anybody's interested in helping out with this, it would be super appreciated. I can walk you through what it is that we're looking for in terms of a good first issue and have you go through, because the issues are all on circuitpython.org slash contributing. So it's all aggregated in one place. So yeah, anyway, that's what I've got for library updates. Awesome. Thank you, Hattie. All right. Next up, let's check in with Melissa about Blinka. Hello. So for Blinka, we had not much activity this last week. We had zero pull requests merge. There are currently three open pull requests among all the different repositories. Oh, I forgot to say Blinka is our circuitpython compatibility layer for MicroPython Raspberry Pi and other single board computers. And to continue, we had one closed issue by one person and two open by two people leaving a net of 62 open issues. There were 9,598 pie wheels downloads in last month and we are now up to 76 boards. And that's it. Dave is asking, how did it get the name Blinka? I have no idea, to be honest. It was like that before I started working on it. Yeah, it originated when it was first created to be a layer on top of MicroPython. And I think when Lomar contracted Nick to do that work, she called it Blinka. Okay, I don't know if the snake or the Blinka package came about being named first. I think the snake was named to Blinka before the package. Ah, okay. I'm not entirely sure why we copied the name, but that's the way it goes. Yeah. Alright, that's the history of Blinka. Okay, so thank you, Melissa. And thanks, Dave, for the question. Next up, we have Hug Reports. Hug Reports is a chance for us to say thank you to folks in our community for all of the awesome work they've been doing. I'll go through the folks in the note stock here and we'll, if you say no microtext only I'll read it off for you. Otherwise, I'll expect you to unmute. So I'll go first. So for me, two Hug Reports. One to Jeff Epler for code debugging with me last week. We spent like three intense hours debugging on Thursday and figured out the MAG tag crash. And Hug Reports to David Glad for filing that issue. It's quite the doozy. And then thank you to Ivan IDRR for letting us stag him to talk about the hanging read. We found an address on the ESP32S2 where when we read the address, the microcontroller stops. And then it has to be reset. So thanks to those folks. And let me scroll up. Next up, we have from Ann, Group Hug. And next up is FoamyGuy. Alright, thanks, Scott. First hug is to you and Jeff for collaborating to figure out that bug on the MAG tag. That definitely seemed like quite the doozy. And it was definitely interesting as well to see the explanation of it on deep dive also. Next up to the GitHub user, Aris Bone, for creating a test script that tries out various sizes of the gauge widget. And it tries to find which ones, if any, suffer from a bug that's relating to the way that it gets filled in. And then lastly, I just have a group hug for everybody. Thanks. Thanks, FoamyGuy. Alright, next up is Jerry. Hi. Yeah, thanks to Brent and I'm not sure who else is involved in all the development work on the Whippersnapper project. It's been fun to play with. Yeah, I think Lauren is the other person. L-O-R-E-N is also working on that a lot too. Thanks. Alright, next up is Katnie. Alright, so my first hug report is to Jeff for a lovely chat next week ahead of him being out for a bit. To Dave P for helping me with cleaning up an image in Photoshop. That was last week I put, it was a shot in the dark and I had a cleaned up image back before the end of the meeting. That was excellent. So FoamyGuy for adding divider lines to grid layout in the display IO layout library. I will be testing that this week. To Naradoc for helping me improve my audio PIN script and therefore once I update the rest of them all of my PIN finding scripts to better exclude unexposed PIN names. And to Keith the EE for joining the Circuit Python Helpers role on Discord and for working towards joining the Circuit Python library and review team. Awesome. Thank you, Katnie. Next up we have text from Keith the EE who says a hug report to Katnie for helping me figure out the Circuit Python Helpers role as well as the other helpers for answering my questions. Hug report to Jeff and Scott for figuring out the ESP32-S2 bug, the fix works on my Metro ESP32-S2 and everyone for being awesome and helping me with random questions. Next up is Maker Melissa. Hello, I just had a group hug for everyone and that's it. Awesome. Thanks, Melissa. And last up we have notes from Naradoc who says hug report to ask Patrick W for digging into and merging circuit PRs. Hug report to Dee Griswold on GitHub for circuit PRs and everyone fixing bugs as 7.0 is approaching. And that's it for hug reports. Next up is status updates. And I should have said that this is done as around Robin but we're practiced to have had it. This is a chance for us to spend a minute or two talking about what we were working on in the previous week and what we plan on working on in the coming week. And as I did in hug reports, I will start and then we'll go through the list. So I spent most of last week bug hunting including the mag tag watchdog timer crash. Also tweaked the BLE API to recursively delete and not reload immediately after right. So that's checked in. This week I'll be bug hunting if anything came up over the weekend. The release candidate and then release the release candidate this week hopefully. I've got a look at the BLE UART example slash code that break with the Nordic UART service and circuit Python. My plan is to actually change the circuit Python workflow to not present as an Nordic UART service. That'll be helpful because then we'll be able to have other characteristics for reading like the board name and the version number, for example. So that'll give us more flexibility in the long run. Antonio is back from vacation starting tomorrow. So I'm going to check in with them and work on the app side of things in particular glider. And if I get through all that, I next on my list is I really want to play around with Raspberry Pi tiny USB support as a prerequisite for supporting circuit Python bare metal on the Raspberry Pis. So that we can get display IO on TVs. So those are what I am looking at doing this week. Next up we have notes from Ann. Ann says besides the Python on microcontrollers newsletter, I'm using the new Adafruit macro pad to make a a random digit generator keypad similar to the Hirsch scramble pad high security system. I demonstrated the project on show and tell and I should have a guide finished by Wednesday. Next up is foamy guy. Alright, last week I updated the learn guide code for all the ones using pulse out or all the ones that we can update so far to use the new API. I made a repo in circuit Python org for the gauge widget. And while I was working on some examples, I noticed an issue with that so started debugging it. I finished up a PR that I started a few weeks back adding a new feature to the grid layout that lets you make divider lines between all of the content cells very easily. So that's cool. And then this week I am going to keep going trying to figure out the grid issue, see if we can find a way to fill it that does not have the same problem. And then the other thing I want to work on this week is an update in cookie cutter to add a third option for the bundles right now. There's just two options for the bundles and then based on some other inputs it kind of defaults to a different bundle. So we'll make that choice more clear so that all three of them are there. And that's what I got. Thanks. Thanks foamy guy. Alright, next up is Jerry. Hi, thanks. Let's see. So I've been playing around a lot last week with these with the only 2640 camera still on the ESP 32 s to sell the board. And they made an example copy Jeff's example over and converted it from to do the webcam it's been working but there's always been this little glitch. Where sometimes it throws an extra bite in so I made a really crude work around that's been great. And it actually is very stable now because they just if the extra bit is there it's thrown away, but it's not a long term fix still trying to dig through the the actual code and see if we understand where that bites coming from but not yet. And then also spent a fair amount of time playing with brain craft hat. You know, where you know, who have them. Every time the kernel updates on Raspberry Pi, there's a chance they break the F, F BCP module. And so it had been pinned back to a pretty old kernel from last year. And so played around some of the new ones and found that you can upgrade to a newer kernel. That's the latest one that works. I'm still trying to understand why that is, but at least some progress. And then there was a forum post where somebody ran to this funny issue where they were using an RFM nine X feather wing on an RF 52 840 board and work great under USB power, but wouldn't wouldn't wouldn't find the RFM nine X board under battery power. And they traced it down and found out it's because of the SPI M device that the thing defaults to on the first SPI device. For some reason that one won't run under battery power. But if you create a dummy SPI device first, and then connect up so it picks the second one, it works fine. So really puzzled by that and I'll look into it more. I don't know if it's something you want to discuss in the weeds or if it belongs here or not or at this point, we can discuss in the weeds. That's fine. Okay, so I don't really have any ideas, but I'll describe it a little more than right. Thanks, Jerry. Next up is cat knee. All right, so last week, I published the CD for X guide and tested the CD 41 thoroughly on circuit python and raspberry pi. I don't normally test this thoroughly but somebody reported in the forums. Not long before I started this guide that the CD 30 was failing on their raspberry pi. It was long since determined there's something else going on there. But I also tested the CD 30 on raspberry pi and finally stopped after 60 hours of it running smoothly. They reported it was typically failing within an hour, eight hours at the longest. So my concern was that I had published the CD 30 guide with raspberry pi instructions. And if those were incorrect, I needed to update that they're not incorrect. It turns out it's fine. There's something else going on. So FYI, if you're looking for, you know, CO2 sensors, both the CD 30 and the CD 40 and 41 are excellent choices for Arduino circuit python and raspberry pi. I put the MP3 playback on RP 2040 guide in moderation. Much noise was made in the process. The circuit python essentials MP3 template was completed as part of this guide. I wrote a script to return a list of audio capable pins now with improved pin exclusion and tested the IS 31 FL 3741 LED matrix breakout. Happy rainbows abound. Also, they seriously need to shorten that part number. So this week for you, Scott, I'll provide any reviews needed for getting 7.0 into RC and stable. Test the grid layout PR from foamy guy with the project that sparked the feature request in the first place. It's my little GitHub phrases macro pad. I needed dividing lines. And so ideally, that'll work well for that. I need to get video for the MP3 guide. That's the final piece of publishing that guide is to get video of the MP3, what the MP3 sounds like when it plays so that folks know. Following that, I'll be doing the INA 219 stem and QT rev guide update. That version of that board came out a long time ago, but managed to miss us updating the guide. This is not the case anymore, but actually I need to write the guide for the IS 31 FL 3741. And then once the MP3 guide is published, put together a quick guide for the PAM 8302 breakout, which is a speaker amplifier. And the reason we're waiting on the MP3 guide is that the Pico example in the MP3 guide is going to get mirrored into that as the example. So I'm not duplicating work as well. I need to find out what might be required to port the OBS timestamp code from Linux to Mac OS and Windows to decide whether it's worth doing as a project. Because I don't think it's I don't feel like it's worth writing a guide if we only have it working on one operating system. It shouldn't be too bad, but it's a little outside my wheelhouse, so I will be asking for help there. And then somebody requested a fristing object for one of our parts. And so I need to do that eventually. This past weekend, I avoided working on something I should have been doing. Secret project, I'll explain it when I can, which led me to begin organizing parts. That's how badly I was trying to avoid doing what I was supposed to be doing. I stopped after a bit because it's work and I should be doing it during work, but it was still nice to get started. I've decided on if I touch it, it gets organized approach to it in general, which if that's all I do will take almost literally forever to get everything organized. But at the rate I've been going, which is none, this approach will at least be a start. It's also leading to slowly filling up my desk because if I don't have time to put it somewhere labeled it stays on my desk, I swear I'll get to it soon. That said, I'm curious, for those of you who do organize your microcontrollers and components, how do you organize them? And not so much what kind of containers you use as much as how do you categorize them? If you have any kind of systems, let me know because I'm still trying to figure out exactly how I want to organize everything. And that's my update. Awesome. Thank you, Katney. I feel your pain organizing stuff. For sure. Next up is maker Melissa. Hello. First of all, in response to Katney, I actually organized my boards by the form factor. But anyway, last week I worked on a new circuit Python code editor interface. And this week I'm working on wrapping that up. And then I can take a look at the Raspberry Pi kernel pending at some point. And after that I'll start a new TFT product guide. And that's it for me. Awesome. Thank you, Melissa. And last up is Neradoc. No mic. Okay. So, notes from Neradoc. Last week, PR to have the board ID available in code and in bootout.txt. Progress made on generating keyboard layouts for Adafruit HID from platform layouts. Windows using keyboard layout.info. Make your layout with neradoc.me slash layouts and test it. I discovered last week's at network Chuck video on bad USBs, which explains why at least five people came asking for layouts for the Pico ducky this week. And this week PR to circuit to use the board ID, the link to the board's downloads page to update circuit Python. Add some of the generated layouts to the layout repo. For now I prefer adding them as they are requested to have a minimum of testing for each. Look into a way to somewhat automate the tests to layouts and looking for a good source of Mac layout data and implement the generator. That's it from Neradoc. Alright, and that is also the last of status updates. So, we'll go to our final section in the weeds, which is a chance for us to have any longer form discussion about any topics. And we have one topic this week from Jerry, which we previewed a bit earlier. So, take it away Jerry and give us more info. Yeah, so, so this, what the user found was that it, you know, when you plug into this RFM 9x feather wing on the NR52840 and he tried to use battery power, it would just not, it would not find the device, the SPI interface that when you power up the, or try to initialize the RFM 9x, it does a little sanity check which goes to read a region of version register and it would fail. But it would work fine under USB. In fact, he found it would if he powered the battery, if he bypassed the battery, put the battery voltage into the USB, it also worked. So, it's just, it's not a power issue. It doesn't look like. Well, I don't know. So, then what he found was that if you look at the code in the RFM 9x and in the SPI, I'm sorry, in the core for the NR52840, it has these SPIM devices and for the NR52840, there's a SPIM3 is enabled and it's the first one chosen. And the difference between it and the other two is that it defaults to a maximum bond rate of 32 megabits. But we're only using the initialization for the RFM is only at five megabits per second, so it's not clear why that would matter. And something different, but that one fails. So, he tried and found what works is if you create a dummy SPI instance, just pick some pins and generate an SPI instance and ignore it and then generate the one on the other one you want using the main, the board SPI devices, pins, it all works fine because it bypasses that SPIM3 even goes to one of the other ones. So, that's about all I know. It doesn't make a lot of sense to me. And I know there were some issues with this SPIM3 that Dan worked on a long time ago. So, there may be something lurking in there. So, just trying to get some clues as to, you know, how to troubleshoot it and what to look at. So, what board is this? This is the NRF 52840 Feather Express. And if you put the battery power in through the USB, it works? I believe that he tried that and it's putting only like 4.2 volts and I think that was just a test to see if it was something to do with the regulator coming through the charger. It doesn't seem to be the problem. Well, it's not clear, it might be. I looked at the schematics on it and I can't, the only, there is one resistor size that's different on the 52840 from the Feather Express, I mean from the M4, and I'm trying to remember it was on the Enable line. The pole up or pole down on the Enable is a little different. It's not clear to me why that would matter. Again, in fact it works if you switch SPIMs. It all works. Makes me think it's not a power issue. Yeah, I would be curious to see if you could replicate it on a separate board. Yeah, well it doesn't happen for sure on the M4 or on an ESP32. I've been using those with batteries for a long time. Yeah, I guess I mean a different NRF board. I should be specific. Yeah, he tried it on both the Express and on the Sense and they both failed the same way. Yeah, they're super similar though, like maybe even like on one of Nordics boards would be interesting. That's a good idea, that's a good thing to try. I tried using a breakout board instead of the Feather Wing and that made no difference, they both paid the same. Yeah, I mean I know SPIM3 has had specific issues. Right. I would be curious to see a salient trace of the SPIMus. Okay, that's a few things to do. Alright, some ideas to play with and it's just a puzzle but luckily there's a clean workaround that is good for now. And I haven't tried any other SPI devices either. That's the other thing I guess to try. Because, and again I'm just amazed it hasn't come up before but I guess that people try to run it on the battery. Right. So it's, I know I've used the NRF 52840s with radios a lot but I've never run it on the battery before. Have you tried slower than the 5 megahertz clock rate as well? I have not. I think the original poster did try to change it with no impact but a bunch of things. So just wanted to bring everyone's attention, it's kind of a funky bug. Yeah, it definitely smells funky. I don't think it's a high priority for me. No, absolutely not. There is an issue out there for it. But yeah, I definitely put it on a long milestone. But yeah, it is interesting. Yeah. And in fact, I think I did want to do a project with that because the RFM 9x is the Laura radio, right? Right. Yeah. I haven't tried that. I also should try it with an RFM69 to see if it behaves the same way. I suspect it will. But these are all things to try out. Yeah, it'd be interesting. I briefly wanted to do, and I think Dylan, she was looking at this combination of things recently too. Okay. Maybe it was something else. It was something else. It was a Laura something that she was doing. I should try it with a xenon, a particle board. Yeah. Yeah, that would be easy to test and that would give you an idea. I've used them with the radios before, but never. Yeah. See, they'll have different power circuitry. The Feather NRF and the Feather NRF sense are like, we'll more design the express and then just remove the SWD and plot in the sensors for the sense. They're going to be very similar. Right. Okay. That's a good thing to try. Cool. I'll be curious to hear what the conclusion of that is. But I'm glad there's a workaround as well. Yeah. All right. I'm going to wrap up. Thanks, Jerry. Yep. All right. So this has been the Circuit Python Weekly. I'm scrolling down for August 30th, 2021. Thanks to everyone who participated. If you want to support Adafruit and Circuit Python and those of us that work on Circuit Python for Adafruit, consider purchasing from the Adafruit shop at Adafruit.com. The video of this meeting will be released on YouTube at YouTube.com slash Adafruit. And the podcast will be available on major podcast services. It will also be featured in the Python for Microcontrollers newsletter tomorrow. Visit AdafruitDaily.com to subscribe. The next meeting is not on Monday. Next week, it is on Tuesday, which makes it September 7th, 2021. So again, next week's meeting is a day later. It is at the same time, 2 p.m. Eastern, 11 a.m. Pacific. So it is 24 hours later than normal. This meeting is held on the Adafruit Discord server, which you can join by going to adafru.id slash discord. To be notified about the meeting and any changes to the time or day, you can ask to be added to the at Circuit Pythonistas role on Discord. And with that, we hope to see you all next week on Tuesday. Thank you all. Thanks, everyone. Thanks.