 Hello everyone, and welcome to the Circuit Python Weekly for September 13th, 2021. This is the time of the week we get together to talk about all things Circuit Python. I'm Katny and I'm sponsored by Adafruit 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 them and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join at any time by going to adafru.it-slash-discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. This meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with a U.S. holiday. If the meeting time has changed, we'll notify you via Discord, and if you wish to be notified about changes to the meeting, we can add you to the Circuit Pythonistas Discord role. There's also a calendar available that we try to keep updated if you'd like to subscribe to that. This meeting is recorded. We record the audio from the Voice Channel and video of the Text Channel. If you'd rather not have your voice recorded, you're still welcome to participate. The video of 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 notes document to accompany the meeting and recording. If you wish to participate but can't make 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 notes document also contains timestamps to go along with the video, so you can use the document to view only the parts of the video that interest you most. This meeting tends to run 60 to 90 minutes, so this gives you the option to skip around. A link to the notes document is posted to the Circuit Python dev channel on the Adafürg Discord server every week, so check the pinned messages to find the latest document. This meeting is held in five parts. The first part is community news, which is a look at all things Circuit Python and Python on hardware in the community. It's a preview of our Python on microcontrollers newsletter. The second part is the state of Circuit Python libraries and Blinka. This is a statistical overview of the entire project and a chance to look at the project by the numbers separate from what we're all up to. The third part 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 minutes to talk about what you'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. And 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 or be something you've identified ahead of time is too long for status updates. And that covers how the meeting will go. So with that, we'll get started with community news. So first up, push the button, a handy Bluetooth button, a wonderful collaboration between maker Sovi Wong and BlitzCityDIY has produced the handheld push the button box. Inside is an Adafruit Feather NRF 52-840 express board programmed with Circuit Python to take the button input and send commands out via Bluetooth low energy. When the box is paired with a mobile phone playing songs, you have a complete solution for controlling your tunes without having to touch the phone. Sovi to sign the case and cover and BlitzCity 3D printed the case in yellow and Sovi milling one out of aluminum. Circuit Python code is available on GitHub. You can see Sovi's video on the case design and the BlitzCityDIY video on the electronics design. Next up, Halloween Hackfest. Join Hackaday, Digikey, and Adafruit for a Halloween themed contest. They want to see your crazy, creepy, ghostly, spooky, and awesome projects. If your costumes are favorite part of Halloween, 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 a light up jack-o-lantern with LEDs. Check out the Halloween show and tell with Hackaday Friday, October 29th at 1 p.m. to show off your awesome projects. And if you want to share them on social media, use the hashtag Halloween Hackfest. Hackaday and Digikey have partnered on this Halloween theme contest to offer three winners an online shopping spree to the Digikey warehouse. Next up, Python Language Reference Sheets. Aaron has crafted several reference sheets listing methods for handling data in Python. There are currently three reference sheets for Python, dictionary methods, list methods, and string methods. Now a few projects. Wrapping up the testing of a CO2 AQI particulate monitor uses the SCD-30 and PMSA003i sensors. The toughest part is figuring out how to take a decent photo of the LCD display. That is true. Controlling the Eligato Key Light Air using the ATMEGA0 ESP32-S2 and Circuit Python. There's a video available on YouTube for that. Send love letters with feathers programmed in Circuit Python and a beautiful transmutable swan case. And that says, you are seen and loved on it. And finally, converting an inexpensive white LED fixture to use colorful neopixels powered by an Adafruit QD Pi and Circuit Python. And that's by Les and there's a whole Twitter thread about that. So this has been a preview of the Circuit Python, I'm sorry, the Python on Hardware Weekly newsletter. It's 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 on hardware related news from around the web, including Circuit Python, Python, and MicroPython developments. To contribute your own project, you can edit next week's draft on GitHub and submit a pull request with the changes. You might also tag a tweet with hashtag Circuit Python on Twitter or email cpnews at adafruit.com. And that has been community news. Next up is the state of Circuit Python, the libraries and Blinko. This is a statistical overview of the project by the numbers. It's a chance to see how things are going and get a sense of the health of the project before we get into the nitty-gritty of what we're all doing with it. So I'll talk about the project overall and then we will split it off and talk about the core, the libraries, and Blinko separately. So overall we had 27 pull requests merged from 17 authors and there's a few names that I don't recognize. R.J.P. 5th, R. Dorsenoud, B. Jones 14, Pontus O, and Elliot G. So thank you to our new authors and thank you, of course, to all of our continued authors. And we had 12 reviewers. In terms of issues, we had 18 closed issues by 9 people and 10 opened by 10 people, so we are net down overall, which is good to see. And with that, I will turn it over to Scott to talk about the core. Hello. Okay, so for the core we had 18 pull requests merged from 12 different authors. So thank you to all of our authors. I won't point out the new folks that Katni just did, I think. And we had 7 reviewers for those 18 pull requests, so thank you to all of our reviewers. Warrior of Wire looks like a newer reviewer, so thank you to them. We have 5 open pull requests where the oldest is 9 days old, second oldest is 8, and then the other two are 1 and 0 days old. So that's great. We're getting through pull requests. Good job, everybody. Issues-wise, we had 8 closed issues by 5 people, 6 opened by 6 people, so we're net down 2, for a total of 409 open issues. Really, we made a lot of really good progress in the last few weeks, issues-wise. We triaged issues by assigning milestones. We had one issue that's not assigned to milestones that we'll have to take a look at, and we have 4 open issues on 7.0, which is going to be our next stable release. That's the thing that we're trying to focus on for the moment. So overall, we're really close to releasing 7.0. I want to talk about it in the weeds to get people's feelings on where we're at with that. And thanks to all the folks for the testing. Really, really appreciate it. Thanks, Scott. Next up, I will talk about the libraries. So this applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscores CircuitPython underscore, as well as a few other things, including our CircuitPython community bundle. So across all these repos, we had 8 pull requests merged by 7 different authors and 6 different reviewers. The oldest one that we merged was 105 days old, so it's good to see that we're still trying to kick through some of the older PRs, and that leaves us with 56 open pull requests. We had 8 issues closed by 5 people and 4 open by 4 people, so we are not down, leaving us with 345 open issues. If you're interested in contributing to CircuitPython on the Python side of things, check out circuitpython.org slash contributing. You'll find all this information and more, including a list of open pull requests and a list of open issues. You can search the issues by label. There are only 3 good first issues at the moment. We've not been great with curating that, and we need to step that up. But you can also search for bug or enhancement if you're looking for something a little more complicated. In terms of reviewing, if you check out all our open pull requests, take a look if you have the hardware, test it. If you don't, take a look for syntax, spelling that sort of thing. Leave a comment and let us know that you did, and once you're comfortable with that, we can look at adding you to the review team. In terms of library updates in the last 7 days, we have no new libraries, but a few updated libraries that I will not read off. Overall, we're still seeing a little bit of plugging away at older pull requests, which is excellent. I want to again put out the call to folks to help curate the issues to pull out and label good first issues for multiple reasons. One, obviously, it's great to have good first issues for folks who are new to things and want to get started with it, but also because with Hacktoberfest coming up, presumably, we automatically label all our good first issues as Hacktoberfest issues, and it would be good to have some stuff for folks to do because it seems like every year somebody picks most of those up. Oh, good. As Cass says, they did announce it. Yes, with Hacktoberfest coming up, we're going to see if we can curate some of those 345 issues. So if anybody's interested in helping out with that, please let me know. And I'm hoping that that'll be something that I can get to, obviously, in the next couple of weeks. And that's where we're at with the libraries. So with that, I'll turn it over to Melissa to talk about Blinka. Hello. So Blinka is our circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. This week we had one pull request merged by myself, and there were four open pull requests remaining. There were two closed issues by one person, and zero open by zero people leaving a net of 59 open issues. And according to Pi Wheels downloads, in the last month we had 9,502, and there are 76 supported boards. Thanks. So there hasn't been much activity lately, but I finally got a little time to get around to working on some of the issues. Great. That's where we're at. Excellent. Thank you, Melissa. Yeah. And that is the state of circuit Python, the libraries, and Blinka. Next up is Hug Reports. Hug Reports is an opportunity for us to highlight the great things that folks are doing in the community. It is held as around Robin where I will start and then go through the list alphabetically. I will read off notes for folks that are not here and will let folks who are here read off their own. So with that, I will get started. So Hug Report for Jeff simply because Hug Report for Crayola, for her work on getting the LED Animations Library working on the IS-31FL3741. This is a little breakout board we have with a huge amount of LEDs on it and it uses a particular control chip and the layout is super wonky to get that many LEDs in such a tiny space. And so it was a lot of work getting that working and I really appreciate that happening. And finally to my dad for roasting coffee for me. He roasted some coffee special for me before they went on a trip and I picked it up yesterday and it is absolutely delicious. So Hug Report there. All right. And next up I have some notes from Mark who says, a Hug Report to Doctor for discussion on Discord about a board idea and a group hug. And next up is Microdev. Ah, lurking. Okay. So Microdev has a group hug and a hug to Scott for the CI enhancement and starting work on the ESP32S3 port. Next up I have notes from Naradok who says, a Hug Report to Tan Newt, FOMI guy and unexpected maker for the weekly deep dive, live coding hardware streams. And next up is Scott. Hello. So first off, a hug report to Katie Bell for her work, continued work exploring the gap between block coding and text coding. There's a YouTube link there. It's a brand new presentation from Katie for the Picon Online 2021. So it's really great to see the progress that she's been making. Second, a hug report to Urish for the JavaScript RP2040 simulator and getting CircuitPython working on it. I think it's going to be a tool that we should think about for CI testing and how big memory imports and so far. I think that'd be really cool. And last up, a hug report to IGRR for joining the chat during my stream. They're from Espressif and got me the S3 dev kit and was answering questions in the chat as well. So thanks for joining Ivan during my stream when I was working on the S3. That's it for me. Thanks, Scott. Next up, I have notes from Charles who has a group hug. And next up is Dan. Okay. Scott, thanks for doing the port-specific pull request build. Scott made it so that if you change a file only in a certain port, it will only rebuild that port when you would do a pull request test build which saves a huge amount of time. We still do all the builds when the build is merged. And thanks, Katni, for doing that really complicated set of learn guide templates for the audio examples, which we will see pretty soon, I think. Okay. All right. Thanks, Dan. Next up is FOMI guy. All right. Thanks, Katni. This week, hugs for a user on GitHub, Dura Penza, who worked on some searching and filtering capabilities for circuitpython.org that I thought were really cool. NeuroDoc for some improvements inside CIRCUP and helping me work through some of the fixes that were needed due to the way that the CIRCUP Python org bundle is. And lastly, to ask Patrick W. for reviewing and leaving some feedback on cookie cutter PR that I'm working on. Thanks. Great. All right. Next, I have some notes from Jeff who's missing the meeting, who has a group hug, and to me for running the meeting today when Jeff was unexpectedly not available. And next up is Jerry. Hi. Excuse me. Where did my notes go? There. So thanks to Maker Melissa for identifying and fixing the BrainCraft backlight issue. Nice to have that working. And MicroDev for this quick fix to an issue that came up with the supervisor get previous traceback function. Thanks. All right. And finally, we will bump back to Melissa. Hi. I just wanted to give a hug to CrossVR for helping point me in the right direction for the Raspberry Pi display issue and a group hug to everyone else. That's it. All right. Excellent. Thank you. And that wraps up hug reports. Next up is status updates. Status updates is an opportunity for us to sync up on what everybody has been up to. Take a couple of minutes, talk about what you've done in the last week since last meeting and what you'll be doing in the next week until the next meeting. It's a great opportunity to provide quick tips and tricks on anybody's quick questions or possibly come up with topics for in the weeds if we run into longer discussions. This also helps around Robin in the same way. And so with that, I will get started. And then we will continue on through the list. So last week created the I2S circuit Python essentials template. Finding that the audio templates are more, as Dan mentioned, complicated than some of the others because there are very specific things to each chip. And so the templates have to be kind of complicated because I need sections where you can say, you know, this is specific to the SAMD51 or this is specific to RP2040. And the code examples are lengthy because they're set up for all possible boards that then the example is created for the specific guide that only has the board in it putting the guide for or the template into. So far it's been working out. I'm the only one who's dealing with them. I've been doing my best to make them so other people can use them. I hope that if that ends up being the case that I've added enough instruction and so on for it to make sense because obviously it makes sense to me, which is all that matters at the moment. So then I added that I2S template page to the MP3 playback on RP2040 guide using Pico as the example. And so that template is out in that guide and will eventually be added to other board guides. I added a note to the neokey ortho snap apart guide about calculating the maximum key matrix size for a given microcontroller using RP2040 as an example. Thank you to Todd Bot for that. He came up with specific for the RP2040 what the maximum key matrix size would be that you could handle and still have a pin left over for the neopixels. And I thought that was an interesting piece of information so I added it to the guide. I started the IS31FL3741 guide and I updated an incorrect wiring diagram earlier today. This week I'm going to finish the IS31FL3741 guide and work on any or all of the following guides proximity Trinky, PAM8302, the ANL rotary encoder or an alarm light transistor powering guide. And that's what I have going on. So next up is maker Melissa. Last week I finished fixing the Raspberry Pi driver to not turn it was not turning on the backlight on the ST7789 base displays. It turned out to be a pretty simple fix actually. I fixed the kernel pinning script to work on the more recent versions of the kernel because they added like a one colon to the version number which kind of messed things up. Except the file names themselves didn't use that one colon, only the version check did. Anyway, I fixed the 64 bit Raspberry Pi OS for Blinka install. It wasn't being detected correctly. I added the lib GPIO D pull send for 64 bit Raspberry Pi OS. I think that's still an open PR at the moment. And I looked into some issues regarding a potential spy bug but the results were inconclusive so far. This week I'm going to move over to finishing up the ENG guides and possibly start another guide. And that's it. Excellent, thanks Melissa. Next up I have some notes from Mark who says offer a couple weeks so feel free to ping me if there's something worth me looking at. And left my job of 20 years last week for a new job hoping I still have lots of circuit Python time. Next up are notes from Naradoc who says last week submitted a PR for third party bundles in circuit advanced a generic macros library running on macro pad keyboard and a generic keypad with new pixels with minimum configuration needed for each port and caught a cold meeting with vaccinated people has its downside. This week more macros library stuff go back to libraries that should be in the community bundle web sockets, whiskey server and add them and then really start on the Mac keyboards layout. And I'm going to do this in alphabetical order so I'm going to go to Scott next. Hello. So for me I got the CI changes in so that only boards related to a change are built. I'm pretty happy with it so far. Mainly I'm working on tweaking the BLE workflow to add modification times and moving slash renaming support. So I'm going to go ahead and moving slash renaming support should be the last bits to tweak on the workflow stuff for a while. PRs will get out this week for both hopefully I was like just poking the modification one right now. I started an ESP32S3 branch that first just updates to the latest IDF and I just was chatting with Ivan it sounds like they're going to branch 4.4 really soon so the timing should be really good we'll just update to 4.4 then and that's when we'll be able to get it in. I may refactor it this week maybe on my stream on Friday to enable non ESP32S2 builds so that would enable the S3 but potentially even like ESP and the C3 as well although they won't work because they don't have ESP but it should be similar to how SAMD51 and 21 works where there's just some top level macro that says whether it's SAMD51 or 21 that just substitutes everywhere so that's what I'm thinking I think I will probably plan on doing that on Friday should be cool the other thing I've been thinking about a long time that I might get to as well is doing the Raspberry Pi tiny USB support I'm really looking for a bit of a break from this BLE stuff but I'm going to have to keep poking the client side stuff as well so like I really don't want to stop doing BLE altogether until we've got people using it so yeah that's where I'm at kind of a mix of BLE and non-BLE to keep me going Sounds good thanks Scott Next up I have notes from Warrior of Wire This says renamed Task Code of CircuitPython async and looking for help adding to community bundle and circup I believe once it goes into the bundle circup finds it and I can help you add that to the community bundle no problem there and next up is Dan Okay scrolling up So last week after I finished fixing some I2S audio issues on RP2040 I was dissatisfied with the quality and I thought there was something wrong with the code but it was very erratic the problems that I was having and when I hooked up a Celia to look at the actual signals the problem went away which meant that it was some kind of weird grounding problem or something and I believe it was because I had two audio breakouts next to each other and they were wired in parallel and one was causing noise on the other so the software problem I had went away completely which was great I was able to close the issue though it took a while to figure that out so on there were a bunch of remaining 7.0 issues there were very few left now and we'll talk about them at the end as Scott mentioned I looked a little bit at supporting HID boot protocol devices which is keyboard and mouse when it's talking to the BIOS or something like that it's not quite as straightforward to do as I thought because there's a lot of negotiation that has to happen and I've been helping Dylan with some simple examples of your communication between boards we're trying to come up with a catchy example thanks Dan next up is FOMIGuy alright thanks Kenny last week I finished up some parts printing some parts and the final thing that I wanted to implement on the etch sketch which was making it have an accelerometer and shake and prompt you to clear it I made a PR to cookie cutter for some changes to support a third bundle the circuit python org bundle and I tested out the PR that was on circuit python org the website to add additional searching and filtering in the downloads pages where that's at this week I have a couple kind of stretch ideas in mind I don't know if I'll get to all of them for that sketch but I think it would be really neat to add a way to save your images so that you can retrieve them later a way to do maybe like spirograph images so we'll go in a circle and you turn the knobs and it changes some of the radius and different things about the circle and then I also want to do one that's like traditional colors with gray in the background and try to make it match the real etch sketch looks color wise and then the other thing I want to try to get back into this week is tiled game maps I have a module that I started a little while back and I have some specific ideas for puzzle games that I want to try to implement using that module so I got to work some more on the module to get it actually ready to go but that's what I got for this week thanks next up I have notes from Jeff says planning to work on 7.0 bugs if necessary otherwise improving parallel display will require sequential pins on the ESP32S2 and will be out the first part of the week for personal reasons and next up is Jerry I don't know if you just wanted me to read that off or I got a report I have no idea what I did this week totally fair alright and that it turns out is status updates so with that let's move on to in the weeds in the weeds is an opportunity for more long form discussions we have one topic so I will turn it over to Scott to introduce that hello so basically I wanted to ask folks how they feel about 7.0 there's a few issues open I think the main one that is concerning is the one the annotator was starting to look at the ESP S2 boot loop thing there's also an open pull request from TAC for updating tiny USB again which would be good but it has also brought a bit of instability with us as well so how do folks think about doing that or also should we just do 7.0 and then expect to do a 7.0.1 so I would lean towards doing 7.0 and planning on doing a 7.0.1 simply because folks are more likely to use a stable release than they are even in RC and getting it out there so folks can find those bugs rather than fix in 7.0.1, 7.0.2, whatever I think is crucial at this point because I think we're finding the last couple things and we're just banging our heads against them and I think we need more input that's my thought on it I agree with you and I think another thing we should take into consideration is that both Dan and Jeff and kind of myself, we haven't really bit off in the last week again so we're kind of prepped to jump on any issues that do come up if we did that so yeah, how do I go ahead? No, I was going to say that would be my suggestion is to just go for it and be prepared any other thoughts? What's in the, I didn't see that there was a tiny USB PR that was, is there something in there that It's for passing compliance tests? Okay, yeah, I think since we don't have specific issues Yeah, and microdev has the next code allocation fix as well Right, that needs actually the next code allocation thing has to be there's some touch up to do on that because there's some bills that overflowed, so we have to I've got, it was one of them the PCA 10-100 Yes, but the other ones were small SAMD 21 board I see So in order, we had a little exchange about that which you probably saw that I said, well we could, they're not very common boards and I thought we might get we might get, we could get rid of the one wire IO bridging thing on those boards or turn off rainbow IO those are the simplest things to do just on those two or three or four boards Yeah, for the Sandys Yeah So I have a big, I hit the PCA PCA 10-100 and the Bealeam file modification change I have as well Yeah and I added this knob to not pre-compute the queue string lengths and hashes in the flash and I think I'm going to I think we should turn that on for the PCA 10-100 because it's, the NRF has it has 128k RAM so I think we would benefit from switching that over So it uses more RAM, is that what you were saying? Right, right, so it's like it's one of the tables in the queue string stuff and instead of computing all the hashes and stuff and then storing them in flash, what we can do is we can compute them on startup and then we just have to store them in RAM but it gives us like 1800 more bytes on the PCA 10-100 so like for this board that very few people use and has 128k RAM like Well, would we use this switch anywhere else if we Well, I think the SAMD 21s have two little flash Yeah, they have two little flash to do that Or a two little RAM, sorry Right, two little RAM to do that So I was just wondering, let me just look and see what's turned on in the PCA 10-100 It's not a lot It's got a lot There's a lot, like we could turn off at exit or something Oh, is it on still? Yeah, it's on in PCA 10-100 Margaret F says it's off What are you looking at Dan to see whether it's on or off? I'm looking at the support matrix Oh, I'm looking at the mpconfig board make file Okay It says it's on in the support matrix So maybe that got, okay Alright Alright, so Alright, well we could turn it So we should accept your PR first And Or do the same thing Or do the same thing Because my PR is going to have other stuff in it Oh, I see It's just this flag, let me, I have it right here It's just out of this So yeah, I agree with micro dev that we should Wait to get this PR in Wait to get this traceback thing merged in But I think after that we could do 7.0 We could take Okay, yeah, well I mean we can't merge We need to that and we can't That PR doesn't build completely So we have to fix it before we merge it Yeah So I think maybe let's tentatively say Let's do 7.0 on Sunday night or Monday Next week Let's get in whatever we can in today And then we'll Or can in this week And then we'll do 7.0 on Monday So not do another RC I mean maybe what we want to do is push to get These last few things in this week and do an RC And then do 7.0 on Monday Right, because so I think of these things Of the remaining issues So I think we converge 5333 today with a few changes Yeah Although my credit is going to go to sleep soon Hopefully Okay Because there I think it's Right, but I could probably make those changes Yeah I could make all the bills work Even without your flag Yeah Right And And then there's And there's actually three issues here And the pull request and the 5332 And 5333 are the same And then an anecdote that says The boot loop issue is an issue I'm not really sure Maybe that's fixed by the USB thing Probably not Probably not Yeah There were also a few people were complaining that their File systems were getting erased Randomly On ESP32 S2 I don't know if to make it that And I think we could easily defer 5311 Because it already was broken So Yeah Defer that to 7xx Right Alright So then I only see 5333 Fixing 5332 and 5333 So we could I think we could do an RC2 Within the next day or two So And then Wait And do The other one At the beginning of next week Does that make sense? Or even sooner We could do it sooner We could have it for Wednesday I just don't want to do 7.0 Later in the week So Wednesday night is too soon I mean too late in the week I just want to make sure that we're around In case something drastic comes up Yeah You thought you would be away one day next week You know which day I don't know I was just going to offer to go To hang out with my niece Okay Because my parents usually babysit for them And they're out of town Okay I got it Text her It looks like the What do you think about the tiny USB thing? I don't see any I don't know of any outstanding issues That would fix So I don't know that we need to do that I think it just It could have potentially Caused a delay if it introduces new bugs Right Yeah So it's The build is broken because the PCA 10-100 is full And the STM32F411 is also full I assume Although that's Japanese not French Which is interesting Right But I think that Just getting rid of How do you Like if we turned off the Onewire I.O. transitional thing Those Small builds then That's probably enough That's probably enough, right? Yeah The Japanese build is 64 bytes different So Yeah So Erase randomly occasionally Right Anecdata does your Do you see this problem at all When you're not using tinyUF2? The boot loop problem Is it really related solely To using tinyUF2? Oh, okay Doesn't seem to matter I could try to replicate that This week I think it would be good I think, I mean, I think I don't know what to think about that I was wondering whether the fact that You and Jeff introduced only one extra byte Does that make any difference as opposed to an aligned Like a 16 byte aligned Gap or anything I don't think it I think you only need the one byte Okay Because it's all about when you're reading Off the end of the ATB Just reading one Like one pair of bits that says that It's done Like that the allocation is finished Okay So I think it, like it I thought it was only a problem It was perfectly aligned and read right into the FTP But yeah, I could I could try to reproduce it and see And see Well, maybe it's worth looking at that Because I think it'll come back to all of this I, yeah, I can see that Yeah So, Seth is saying Stalls and crashes on the S2 and the RP2040 boards Yeah, if you can reproduce it, please file an issue It's really hard for us to fix something that we can't I don't think they're in the chat, I would type that out Oh Okay, yeah, I can do that Okay So Get in the few things RC this week Stable next week, yes Yeah There are some other ways, like I have an idea I have some ideas about Maybe like, these These builds that don't fit, they're like by less than 100 bytes or something So it's possible that, like if I improve Something like the ARG validation code On a few routines, I could gain back that back So I'll look at that really briefly But the easiest thing is just to turn some stuff off I think the problem with doing Those like just get it under the amount Things is that it then Happens again Happens again and again Maybe the thing to actually look at is to do the different LiveGCC or whatever Yeah, I was thinking of that too, I was thinking of that Yeah, so maybe I can look at that first Because that's going to be like a thousand bytes Or something Yeah Alright, why don't I look at that and see if it's simple Yeah, so you want the file for me Yeah, or a pointer to the ARG package or something Yeah, I could do that I don't even know where to look I think it is pre-built, so I can find it for you And then we can just put that In S3 along with the Yeah, it does look like we do get a few more A few hundred bytes more with 11 as well Right, well I think that's That could even be 7.1 could be Well, I'd like to wait until Right, I mean I'd like to wait until Yeah, you can get it more Your arm down though it is Because that's much easier for everybody So Right And they get Yeah, yeah So I expect that to be around the end of the year December, January, yeah Yeah For 7.1, I will That's kind of when I'll do the IDF update I think as well Okay So that we can start doing S3 stuff And do you think that it makes sense So what do we expect? We would backport anything Like once we release 7.0 and branch it Then and branch 7x Or 7.1x or something 7.0x I don't necessarily think we'd actually branch I think the, you know, the reason to branch Is to be able to do something that we know Will destabilize it Well, I'm thinking of all the 8.0 The 8.0x changes that involve Making incompatible changes Right For those, so you're taking it for those Yeah, okay Yeah, we just defer those Okay Okay Like I think we'll come to the point where we do Want to do something for 8.0 and Or we want to Like at that point that we want to call Main 8.0 then we can But I wouldn't do that immediately I think We'll tag 7.0 and If we end up pulling something in For 7.1 that's more destabilizing We can go back and do the branch off the tag Okay Maintaining two branches is not very fun So I would say let's wait to Let's wait to branch Off 7.0 until we We want to be able to do something more drastic in In In Main Okay Okay, so I think the conclusion is We'll try to fix as many bugs this week as we can Along with a new RC Once the ones we know about already Are done And then regardless Or Probably regardless of what we find This week we'll do We'll plan on doing 7.0 on Monday next week Yeah Right, let's do some shim stopper Yeah Right Yeah and the BLE workflow stuff I'm not expecting to get in 7.0 So I'm expecting it to change a little bit Internally and that's fine Because it's got its own version number Right, that sounds good Yeah, so it's not critical For me to get this other BLE stuff That I'm working on In Alright and I'll look at the At the At the libgcc thing Yeah That'll solve a lot of problems, yeah Yeah, I'll take a look I'll figure out Where that is Okay Right Okay, sounds good Okay Excellent With that I'm going to go ahead and Wrap up This has been the CircuitPython Weekly for September 13th, 2021 Thank you to everyone who participated If you want to support Adafruit and CircuitPython And those of us that work on CircuitPython Consider purchasing from Adafruit At Adafruit.com This video The video of this meeting will be released on YouTube At youtube.com And the podcast will be available In major podcast services It will also be featured in the Python for Microcontrollers newsletter Visit adafruitdaily.com To subscribe The next meeting will be held On Monday, as usual As far as I know, at 2pm eastern 11am pacific This meeting is held on the Adafruit Discord Which you can join anytime by going to adafru.it To be notified about changes to the meeting In general you can ask to be added to the CircuitPython Easter's roll And we hope to see you all next week Thanks everyone!