the C6 has a vastly different version of NINA-FW, so if you see differences, then upgrading/downgrading NINA-FW on the Airlift Featherwing would narrow down what is different
#circuitpython-dev
tulip sleet
manic glacierBOT
slender iron
👋 Hi folks, I'm back working while the baby is napping (~2 hours a day). Feel free to ping me here, on issues or PRs and I'll get back to you when I can.
lone axle
the C6 has a vastly different version of NINA-FW, so if you see differences, the...
I think it may be a more general issue with version 3 of nina-fw. I have tested a feather RP2350 + Airlift featherwing now and found that I see the same issues there as on the Fruit Jam with the C6. I've also now downgraded the Airlift featherwing to version 2 nina-fw and am getting consistently successful requests.
I do think the slowness mentioned in my original message was unrelated. That turned out to be display related. The terminal showing caused it to slow down considerably and was further exacerbated by debug=True, and additional prints that I had added. If I stop showing the terminal before running request it iterates at a much faster pace.
Strangely the slowness induced by the display actually seems to have been helping the network issue though. With terminal hidden and faster iteration now the request frequently fails with Timed out waiting for SPI char. Chunk size no longer seems to matter all sizes frequently fail with the same exception.
I'm going to test a little more and try with a different port to see if it's rp2350 specific and then I'll make an issue with my findings on nina-fw.
I noticed under the releases of nina-fw repo there is are debug builds of the bin files. Would those potentially output any more useful info? and if so does it just come out of serial or need something external hooked up?
tulip sleet
I noticed under the releases of nina-fw repo there is are debug builds of the bi...
I dont' remember, but yes, it probably comes out of TXD0.
But there are multiple debug logging options. I had to turn on mbedtls or lwip separately to debug something or other. Try a couple of different webservers, and if you can, also try an http vs https server, to see if there's some slowdown due to encryption.
manic glacierBOT
manic glacierBOT
tidal kiln
is there anyway to suppress the I2C pull up check in CP?
tulip sleet
is there anyway to suppress the I2C pull up check in CP?
only by changing a compilation option
tidal kiln
does bitbangio do the check also? 🤔
tulip sleet
no, doesn't look like it
tidal kiln
Adafruit CircuitPython 9.2.8 on 2025-05-28; Adafruit QT Py RP2040 with rp2040
>>> import board
>>> import bitbangio
>>> i2c = bitbangio.I2C(board.SCL, board.SDA)
>>>
indeed
thanks!
unkempt mist
I think it may be a more general issue with version 3 of nina-fw. I have tested ...
FWIW, Today I updated an Airlift ESP32 breakout board with the 3.0.0 firmware and after that I was unable to make any successful http requests. I downgraded back to 1.7.7 and things were fine again. Plan to try 2.0.0 once I get back home.
manic glacierBOT
lone sandalBOT
sick pier
lone axle
<@&356864093652516868> the (currently) Bi-Weekly meeting will occur today here on discord and the normally scheduled time of 11am US Pacific / 2pm US Eastern. About 2 hours from now. Fill in your notes and status updates to the shared document any time: https://docs.google.com/document/d/1tNfH3S0mIj57cCBzMRyaPH49nARgvj3ZDp2TbR1Nd4o/edit?tab=t.0 We look forward to hearing from all attendees.
@sick pier That is enough random gif / emotes. This is not really on topic in this channel and pushes other messages further back in history even though it's not as directly problematic as some types of spam.
tulip sleet
@lone axle could you read my input for the meeting? I heard nearly all of the previous meeting but my earbuds went out. Tnx
lone axle
Yep, will do.
thorny jay
Thank you @lone axle
wraith crow
Great Job @lone axle and Thanks!!!
lone axle
Thank you, Have a great week everyone 👋
lone axle
Here is the notes document for the next CircuitPython Weekly Meeting. It is on Monday 7/28/25 at the normal time of 11am Pacific / 2pm US Eastern here on Discord. Add your hug reports and status updates to the document before the meeting. If you are unable to attend but would still like to contribute, feel free to add your notes and we’ll read them off during the meeting. Hope to see you there! <@&356864093652516868> https://docs.google.com/document/d/1ncUmb1lkvktAE-wOGZbF_OMUQQu0iEHk9b1R_t55Rmg/edit?usp=sharing
tulip sleet
@lone axle If you have time to approve https://github.com/adafruit/circuitpython/pull/10468, I would be grateful. Scott already approved it, but there was a minor merge conflict in one board file that I fixed, so it needs a re-review. Then I can proceed with making the changes to update which TinyUF2 to use everywhere.
tulip sleet
@lone axle tyvm!
lone axle
Yep, you're welcome
lone axle
Maybe for external displays we should encourage people to initialize them in boot.py and set them onto supervisor.runtime.display That would do a few things that I think are positive:
- more closely mimic the core behavior with init display once on boot up then keep it around without releasing
- lead to more portable
code.pysince display initialization with pins / different types of displays etc.. all live outside ofcode.py - make the project code run faster since it won't be releasing and re-initialzing the display every time it runs.
orchid basinBOT
tulip sleet
https://blog.adafruit.com/2025/07/15/circuitpython-10-0-0-beta-0-released/
Highlights of this release
- Increase the firmware partition size for ESP32-S2 boards with 4MB flash, allowing more features to be included. This change was made for 4MB flash ESP32-S3 boards in previous releases. Starting with this release, you must now update the TinyUF2 bootloader on all 4MB flash ESP32-S2 and ESP32-S3 boards. See the release notes for details.
- Fix Espressif
pulseio.PulseInregression.
The "OPEN INSTALLER" button on the CircuitPython.org board pages is now updated to install the new bootloader
slender iron
Maybe for external displays we should encourage people to initialize them in boo...
The one big downside is that errors aren't sent directly over usb. couldn't we check the state of s.r.d before releasing displays to achieve the same thing?
lone axle
The one big downside is that errors aren't sent directly over usb. couldn't we c...
checking before releasing would prevent the re-initialization, but not help make the project code portable since it will still have the display initialization inside of there.
I did not consider the errors not going out though and that is unfortunate for this because it would make troubleshooting issues with the init more confusing since people will need to know to look in boot_out, assuming they would go to there.
I guess there really is no need to use boot.py as I think more about it. Instead of encourage setting up the display in there projects could set it up in a seperate file display.py or whatever and then in code.py check for the display and if it's None then call the function from display.py to initialize it.
manic glacierBOT
manic glacierBOT
manic glacierBOT
manic glacierBOT
manic glacierBOT
manic glacierBOT
manic glacierBOT
green mural
I'm new at this. A month or so ago I got a library for an AS7343 light sensor accepted to the community bundle. Now I need to fix and issue, but I'm not sure how to do that and stay connected to the community bundle. I read that I should make the changes to my personal repo for the library and then change the version tag and magically it will go into the community bundle, but I'm not finding much that actually makes sense for this process.
jaunty juniper
I'm new at this. A month or so ago I got a library for an AS7343 light sensor ac...
the bundle picks up the latest release (tag) on github, so you make your changes, commit, push, and in GitHub you go to releases and make one with a tag that's a valid version number (a.b.c), and tonight the bundle release script will pick it up
green mural
@jaunty juniper Thanks. I'll try this in a few days when I get the issue fixed.
lone sandalBOT
tulip sleet
<@&356864093652516868> Meeting in just over an hour at US ET 2pm. Add your notes to https://docs.google.com/document/d/1ncUmb1lkvktAE-wOGZbF_OMUQQu0iEHk9b1R_t55Rmg/edit?usp=sharing
candid sun
@tulip sleet i thought the meeting was next week (28th)?
lone axle
Same, that is what I mentioned at the end of last week meeting and set up the doc for.
tulip sleet
<@&356864093652516868> SORRY - it's next week. I was looking at the wrong week.
thorny jay
You might not regret the cardputer acquisition, it is really tiny but feel like a full computer (without mouse).
The kind of portable programming device we were having with pocket calculator (HP / TI / Sharp).
I don't think it is really usable as you need small fingers, and the screen is super small, but there are a lot of interesting details.
You can make it thin by removing the extended battery, you can attach that to lego technics.
I need to make better use of that gem, that currently stay protected in the provided box.
devout jolt
You might not regret the cardputer acquisition, it is really tiny but feel like ...
Agreed that it’s so small as to be almost unusable. But as a test platform for WiFi, screen, I2S audio, & sd card, it’s pretty good. I have it in my set of remotely-accessible CirPy boards for that reason
pastel valley
the most useful thing i did with it so far (which is the project i was working on with bitmap fonts) was for it to work as a replacement for the app to run a bluetooth label printer
the other thing i did with it was microdrummo https://www.reddit.com/r/M5Stack/comments/1lfw5gl/microdrummo_a_drum_machine_sequencer_for_cardputer/
lone axle
That is cool! nice job fitting that into such a small display.
thorny jay
Agreed that it’s so small as to be almost unusable. But as a test platform for W...
You'll have to tell me more about "set of remotely-accessible CirPy board"... do you have some sort of online machine with CircuitPython gizmo USB connected to it, and you ssh or else to that machine?
Now, I was thinking the cardputer was coming with a nice protective box... but maybe not, if it is not the case, then the case I use is a Pimoroni plastic box. https://shop.pimoroni.com/products/pirate-brand-plastic-loot-box?variant=21803682693203
My cardputer was moving a bit in there, so I added a tissue and then it was tight in. I am not sure if I used the Small or Large version. Large: 145x90x40mm vs Small: 90x66x30mm.
The reason I don't know is that it is so small that I could not locate my cardputer at home for the moment. That is the problem of beeing too small.
thorny jay
You'll have to tell me more about "set of remotely-accessible CirPy board"... do...
Small it is, I just checked:
Small Pimoroni box: 90x66x30mm
Cardputer: 84.0 x 54.0 x 19.7 mm
So with just a little bit of padding, it is well protected and not moving into the box. Almost a perfect fit.
thorny jay
Small it is, I just checked:
Small Pimoroni box: 90x66x30mm
Cardputer: 84.0 x 54...
Just noticed the v1.0 of the cardputer is EOL, and the v1.1 has a small difference in the StampS3 it use some power management. Let's assume the same version of CircuitPython works on both v1.0 and v1.1 and that Dan will have the new version.
I might get a v1.1 in addition to my v1.0 (that is hard to find right now), just to check.
devout jolt
You'll have to tell me more about "set of remotely-accessible CirPy board"... do...
It's just exactly like you describe: a Raspberry Pi with a powered 7-port USB hub and various CircuitPython devices (currently: Lolin S2 mini, QTPy m0, Trinkey of some sort, cardputer, Pico, M4 pyportal)
I ssh into the Pi, use "discotool" to find the serial port & mount point of each device, use "microcontroller.on_next_reboot(microcontroller.RunMode.{UF2,BOOTLOADER})" to try out new CirPy builds or UF2 bootloaders. The USB hub also is controllable via uhubctl so I can powercycle a specific hub port if needed
manic glacierBOT
manic glacierBOT
manic glacierBOT
tulip sleet
@lone axle did you turn on the "no reset" in the web serial tool?
i haven't checked the pins
you could just load the passthrough and then try esptool.py from the shell, like just chip_id
lone axle
it is on. I didn't explicitly flip the switch though, it loads for me in this position
tulip sleet
that looks right. maybe limor wrote a passthrough already?
lone axle
esptool.py does the same thing on the neopixel and outputs this:
esptool v5.0.1
Serial port /dev/ttyACM0:
Connecting......................................
A fatal error occurred: Failed to connect to Espressif device: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
my best guess is that either Serial1 or SPI are incorrect, but I'm not sure how to tell exactly. Serial1 seems to match as defined here: https://github.com/earlephilhower/arduino-pico/blob/cdf25b45b8b5926b8cfbd1544608484069abf3e1/variants/adafruit_fruitjam/pins_arduino.h#L46-L47, SPI is more ambiguous because there are both SPI1 and SPI0 defined here: https://github.com/earlephilhower/arduino-pico/blob/cdf25b45b8b5926b8cfbd1544608484069abf3e1/variants/adafruit_fruitjam/pins_arduino.h#L52-L62. Looking at the pin diagram I believe SPI1 is correct, but it's unclear to me which just SPI is, I tried using SPI1 and SPI2 in the code as well though and neither of this behaved any different.
manic glacierBOT
quartz folio
Hello devs. I'm looking for @gilded cradle to see if she would like to discuss some PRs for code.circuitpython.org and maybe working together on some future changes: https://github.com/circuitpython/web-editor/pulls
manic glacierBOT
manic glacierBOT
manic glacierBOT
tulip sleet
@lone axle do you want to merge the nina-fw now (you gave a thumbs up), or else figure out how to test C6 and merge after that?
(can answer in the PR)
crimson ferry
dan, just out of curiosity, Nina now supports ESP32 and C6… Is there any reason it wouldn’t work with S2 or S3?
tulip sleet
dan, just out of curiosity, Nina now supports ESP32 and C6… Is there any reason ...
it certainly could, but we haven't tried building it for those. There might be some minor tweaks necessary. The motivation for the ESP32 and C6 is that they are really cheap and therefore reasonable as co-processors.
@lone axle there are Python versions of passthroughs. I don't know if you tried https://github.com/adafruit/Adafruit_CircuitPython_miniesptool. Also see https://github.com/adafruit/nina-fw/issues/68
lone axle
<@382939733107408897> there are Python versions of passthroughs. I don't know if...
Thank you, I'll check those out. Only tried arduino.
lone axle
<@382939733107408897> there are Python versions of passthroughs. I don't know if...
Only tested briefly but no luck with miniesptool. I am thinking at least part of my problem is I'm not getting the C6 into boot loader mode properly. The arduino passthrough and this miniesptool code seems to be using GPIO0 for that https://github.com/adafruit/Adafruit_CircuitPython_miniesptool/blob/fdd7cce7eddd45e29930759984ccc58e63849d40/examples/miniesptool_simpletest.py#L18. But I am unsure how to set that based on the fruit jam pinout. It seems like maybe GPIO0 doesn't get it's own pin on the RP2350, and perhaps it's IO9 instead of 0, but maybe that is okay for this module.
The schematic shows it connected sort of to the IRQ pin and I have tried using that in place of GPIO0 but it doesn't seem to work.
I'm not 100% fluent in schematic icons, maybe this is indicating that ESP_BOOT is broken out to a pad or pinhole. I briefly tried jumping a single pinhole on the board that is near-ish to the ESP to GND while running the arduino pass through code but it didn't help, and I decided not to push my luck randomly jumping what is to me an unknown pin much more.
tulip sleet
are you using rev C or rev D or earlier?
there was some shuffling of this, but I think it was early on
lone axle
I believe it's rev C
yep, just found the label, definitely rev C.
It does have some of the I2S pins used by the TLV dac swapped around on this revision as compared to some later ones, I've swapped them in the code on my device to work around that.
tulip sleet
are you using board.ESP_IRQ?
lone axle
I beleive so, I updated the simpletest code with these:
tx = board.ESP_TX
rx = board.ESP_RX
resetpin = board.ESP_RESET
gpio0pin = board.ESP_IRQ
a confusing thing is that IO9 has nothing to do with the pin numbers on the RP2350. The RP2350 has its GPIO23 connected to ESP_BOOT
does ESP_TX go to the RX pin on the C6?
need to make sure whose point of view it is
lone axle
I believe so. Sorry I cropped out the other side. This is the full C6 module in the Fruit Jam schematic:
from here: https://learn.adafruit.com/admin/guides/4298/editor/30676 if you can access
tulip sleet
rev D:
{ MP_ROM_QSTR(MP_QSTR_ESP_CS), MP_ROM_PTR(&pin_GPIO46) },
// was GPIO0 on ESP32. Used for IRQ and mode switching.
{ MP_ROM_QSTR(MP_QSTR_ESP_IRQ), MP_ROM_PTR(&pin_GPIO23) },
// BUSY is also known as READY, and is RTS for BLE mode.
{ MP_ROM_QSTR(MP_QSTR_ESP_BUSY), MP_ROM_PTR(&pin_GPIO3) },
{ MP_ROM_QSTR(MP_QSTR_ESP_RESET), MP_ROM_PTR(&pin_GPIO22) },
// TX and RX are from the point of view of the RP2350.
{ MP_ROM_QSTR(MP_QSTR_ESP_TX), MP_ROM_PTR(&pin_GPIO8) },
{ MP_ROM_QSTR(MP_QSTR_ESP_RX), MP_ROM_PTR(&pin_GPIO9) },
Rev C onl y has { MP_ROM_QSTR(MP_QSTR_ESP_CS), MP_ROM_PTR(&pin_GPIO46) },
ok, never mind..., thought there might be pin changes there
I did get this working on a Fruit Jam mockup with RP2350B Metro and a C6 breakout.
lone axle
I have a full ESP32-C6 Feather that I got out, but am unsure if it could be used to test. Willing to try if it can.
tulip sleet
import board
import digitalio
import time
esp32_reset = digitalio.DigitalInOut(board.D12)
esp32_gpio0 = digitalio.DigitalInOut(board.D10)
esp32_gpio0.switch_to_output(False)
esp32_reset.switch_to_output(False)
time.sleep(0.1)
esp32_reset.value = True
time.sleep(0.1)
esp32_reset.deinit()
esp32_gpio0.deinit()
this is when I was using the breakout
oh, wait, not a breakout, what was I doing, maybe the C6 Feather
honestly, I don't remember. Most of my testing was with the ESP32 breakout. The Feather has IO9 broken out, so you could make a test jig with that
tulip sleet
<@&356864093652516868> Monday meeting is in a little over two hours at 2PM US Eastern time. Add your notes here: https://docs.google.com/document/d/1ncUmb1lkvktAE-wOGZbF_OMUQQu0iEHk9b1R_t55Rmg/edit?usp=sharing. We're doing bi-weekly meetings in July and August, so there will be two weeks of news in this meeting.
turbid radish
Searching for a 3.5 to 7" LCD display that has a HDMI interface that can do 640x480 (hopefully at 72Hz) for Fruit Jam. Lits of 800x400 but I specifically want 640x480 mode
This is the only one not in China https://www.ebay.com/itm/205222850146
turbid radish
turbid radish
cpnews@adafruit.com for tips
I always welcome tips for articles & projects
Subscribe to the newsletter https://www.adafruitdaily.com/
candid sun
thorny jay
Thank you @tulip sleet
turbid radish
Thanks @tulip sleet !
lone axle
Thanks for hosting Dan. have a great week everyone 👋
tulip sleet
<@&356864093652516868>
Here is the notes document for the next CircuitPython Weekly Meeting, in two weeks, on August 11, 2025. We are doing bi-weekly meetings during July and August. It is at the normal time of 11am Pacific / 2pm US Eastern here on Discord. Add your hug reports and status updates to the document before the meeting. If you are unable to attend but would still like to contribute, feel free to add your notes and we’ll read them off during the meeting. Hope to see you there! <@&356864093652516868>
https://docs.google.com/document/d/11KpdjrQUXbQ_-uasV4gLlZIPz3q-nfP7A2c9isIOVvg/edit?usp=sharing
tiny peak
https://github.com/dhalbert/cookiecutter-playground-bundle
re: meeting in the weeds discussion on the mysterious cookiecutter-playground-bundle repo that @tulip sleet didn't remember the details about... way back when (perhaps mid/late June, 2024?), there was a CircuitPython meeting where a couple folks (perhaps Dan & Jeff?) discussed how it would be useful to have a cookiecutter for building Playground guide project bundles. So, I wrote one. I still use an evolved version of that bundle builder for all my guides. But, for my purposes, it's more convenient to just copy the bundle_builder.py stuff and the associated .github folder with the action spec yaml file rather than using cookiecutter. So, I asked Dan if Adafruit would be interested in maintaining the cookiecutter I wrote, he suggested I could transfer it to him as an intermediate step (as I'm not a member of the Adafruit org), and so I did that.
The current contents of the cookiecutter-playground-bundle repo are out of date (code refers to 8.x and is unaware of 10.x, etc.). If anyone wanted to spruce that up a bit, a good starting point would be to compare the cookiecutter-playground-bundle Makefile, bundle_builder.py, and bundle_manifest.cfg files to the ones in any of my recent Plaground guide repos, for example, perhaps samblenny/fruit-jam-portable-midi-synth.
tulip sleet
The current contents of the cookiecutter-playground-bundle repo are out of date ...
Thanks, I took the transfer and then failed to do anything about it 😦
tiny peak
Thanks, I took the transfer and then failed to do anything about it 😦
no worries. life moves fast. there's much to do.
in the mean time, we've had some great improvements to 9.x and 10.x
dev hours well spent
manic glacierBOT
manic glacierBOT
devout jolt
Is there a reason why the CircuitPython Learn Guide sections for boards with SD cards use adafruit_sdcard rather than the built in sdcardio? e.g. this one for the Metro RP2350: https://learn.adafruit.com/adafruit-metro-rp2350/sd-card
stuck elbow
Is there a reason why the CircuitPython Learn Guide sections for boards with SD ...
sdcardio is relatively new
tulip sleet
we have a to-do for this somewhere. I think the issue is that it's a shared page and we have to consider how to mention both, or separate boards without sdcardio
devout jolt
we have a to-do for this somewhere. I think the issue is that it's a shared page...
ah shared page would explain it, thanks
devout jolt
sdcardio is relatively new
can't wait for sdioio on RP2, but that would require cleverer folks than me
tulip sleet
it is actually a "templated page", which allows us to tweak certain parts for the specific guide
it would be easy enough to copy this template and change the example to use sdcardio. It has to get put on someone's to-do list 🙂
i put it on my to-do list, but someone else might do it
devout jolt
it would be easy enough to copy this template and change the example to use sdca...
It's not high-priority to me. I was looking for a "default example" of SD card use as I'm trying to track down what is maybe a CIRCUITPY filesystem or flash corruption bug while using SD cards with I2S audio. I have working code just wanted to make sure I was close to expected use cases
tulip sleet
there is this mini-example: https://docs.circuitpython.org/en/latest/shared-bindings/sdcardio/index.html
devout jolt
there is this mini-example: <https://docs.circuitpython.org/en/latest/shared-bin...
yep. my code looks something like this: https://github.com/todbot/circuitpython-tricks/blob/main/larger-tricks/i2s_sdcard_pico.py
tulip sleet
once it's mounted, nothing different to see
I looked at the learn guides containing "sdcardIo" but there are not a lot of fancy audio projects
maybe they mostly still use adafruit_sdcard
tulip sleet
@devout jolt
Is there a method to unconfigure the PIO-USB usb host stuff?
I'm not familiar enough with it to know, sorry.
the automounting is about making boards like Fruit Jam work more easily out of the box. See new stuff in https://docs.circuitpython.org/en/latest/docs/workflows.html about Mass Storage, CPSAVES, and automounting
thorny jay
Hello @dahn did you get your Cardputer, what version did you take? I have now two differents, the v1.0 and the v1.1.
Both run 9.2.8 without problem.
There is a behaviour difference for the v1.1.
The trick is that the neopixel(?) is only powered when the screen is powered. So at boot time, the first few blink at bootstap are not visible. Not sure how to turn off the screen, but the theory is that v1.1 can sleep and consume much less than the v1.0. The other difference relate to Wifi antena that give better reception on v1.1 (not tested but hardware only).
I have a video of both startup, if needed I can upload and share.
So the same CircuitPython firmware is good enough for both version of the Cardputer.
thorny jay
Hello @dahn did you get your Cardputer, what version did you take? I have now tw...
In the coming weeks, the Cardputer ADV is expected. The big difference expected is that the keyboard will not be a matrix of 4x14 (consuming that 4+14 GPIO) but there will be an I2C interface to read the keyboard. And the saved GPIO will be exposed.
So while it might be possible to boot with the same firmware, but without the keyboard.
Right now I have no clue how CP can support and I2C keyboard "natively". I am sure someone with more skills will be able to propose a way to support it.
tulip sleet
Hello @dahn did you get your Cardputer, what version did you take? I have now tw...
I got V1.1, from Digi-Key.
slender iron
<@352910176736772096>
> Is there a method to unconfigure the PIO-USB usb host s...
No, tinyusb doesn't have deinit
tulip sleet
@devout jolt ^^
lone axle
@tiny peak if you're interested in simplifying the build process and configuration for your project bundler, it's possible to use circup programmatically from other code, and it can target a mock device on the local filesystem instead of a real device. It will automatically download the bundle and get libraries out of it to include in the bundle zip. The Fruit Jam OS builder uses this technique here: https://github.com/adafruit/Fruit-Jam-OS/blob/main/build.py#L115-L122 It would save you from needing to list out the libraries in the config file since it can use the --auto flag, it'll also automatically grab dependencies of libraries it includes.
tiny peak
<@1220648290941669377> if you're interested in simplifying the build process and...
Thanks for the suggestion... I realize my approach is a bit outside the norm. If somebody wants to overhaul that stuff to work in a more typical way, go for it! I come from more of a security minded background where minimizing auto-magical stuff helps me sleep better. I worry about stuff like software supply chain attacks on pypi packages, minimizing the amount of random code that gets run on my dev box without my specific request for it to happen, and overall just minimizing opportunities for bit-rot. For my purposes, it works great to use the bundle_manifest.cfg file with a hardcoded bundle zipfile URL and hardcoded library names to be extracted from that file by my bundle_builder.py script. It's basically a low-effort equivalent of package managers that let you do lock-file style dependency version pinning with version numbers, SHA hashes, or whatever. I like it because it lets me get very reproducible results while pulling in a minimum of external code that might break or misbehave for reasons outside my control at some future time.
I realize most people don't care about that stuff though. If people want to use a different approach that works in a more familiar way with more automatic magic stuff, that's good too.
lone axle
I see upsides both ways :). Not having it pull in new versions of libraries that may be incompatible is nice about the more manual approach for instance
I just used the latest version of your bundler successfully on my first project with it 🎉 So thanks for sharing this tool!
tiny peak
yeah, one of my main priorities for the bundle builder was making it easy to have a relatively simple and stable thing for guides that would also be easy to update if needed. I just kinda slapped together the minimum thing that met that goal.
lone axle
And I'd say I generally worry about similar things. But I've also written lots of, and read through all of circup so I feel more comfortable with it.
tiny peak
yeah, for an Adafruit maintained thing, using circup would probably make a lot of sense
one note on usage is that when I write a guide, I usually update the board I'm using to the newest CircuitPython release and grab the latest library bundle URL to match it. My procedure for using it definitely depends on the Playground guide mentioning the specific CircuitPython version I was using
I don't really have a good solution for helping people update the bundle if that's needed to match an upgraded CircuitPython version
I'm probably gonna run into that if I end up updating all my Fruit Jam guides once I get a production rev D+ board and 10.0.0 gets released
to update things for 10.0.0, probably I'll just manually go through my repos and guides, bump the library bundle url, test and commit that, cut a new release, then edit the guide urls for the download project bundle buttons.
crimson ferry
Is there a way in CircuitPython to programmatically get the SERCOM number on M4 for a given pin (other than a lookup table)?
stuck elbow
Is there a way in CircuitPython to programmatically get the SERCOM number on M4 ...
it uses a lookup table internally
crimson ferry
SAMD51 boards have primary and secondary SERCOMs for some pins... will CircuitPython automatically use: primary only? whichever is still available?
(is there a way to force secondary, or mix primary and secondary by a device needing that?)
tulip sleet
SAMD51 boards have primary and secondary SERCOMs for some pins... will CircuitPy...
When a sercom is needed, CircuitPython just searches for a free one. It doesn't classify them as "primary" or "secondary". I would say there may be multiple available per set of pins, but there is no priority order.
crimson ferry
thanks, I had a bug but fixing that confirmed... I can have a device use mixed primaries and secondaries of a given SERCOM 🙂
tulip sleet
So sometimes allocating things in a different order will pick SERCOM's in a different order. example where it matters: https://learn.adafruit.com/adafruit-trinket-m0-circuitpython-arduino?view=all#trinket-m0-create-uart-before-i2c-2986086
crimson ferry
ah, that makes sense. my issue is I'm using a Feather M4 (b/c FeatherWings) and using almost all the pins, but have 6 SERCOM devices so it's tight
tulip sleet
and you know about enumerating them all, like this? https://learn.adafruit.com/adafruit-trinket-m0-circuitpython-arduino?view=all#wheres-my-uart-2985036. I have similar scripts for the other SERCOM uses.
crimson ferry
yeah, I just modified one to get the pins for SPITarget 🙂
tulip sleet
Limor had to spend time playing musical SERCOM's to get the best pin choices on various SAMD boards.
crimson ferry
I can see that would be quite a challenge to optimize
now to see if I can juggle further and get my second UART back
I always thought the CS pin didn't have to be on a SERCOM on SAMD (the SPI pin finder I had doesn't use it), but for SPITarget I can't switch the CS pin willy-nilly (like, to A0 which isn't on any SERCOM)
tulip sleet
for the purposes of SPITarget, CS is handled by the hw so it knows data is coming in (my assumption). For sending data out, your program knows when it. There is hw support for hw-controlled CS: CTRLB.MSSEN
but we don't use it
crimson ferry
ah, ok that also makes sense, thanks
lone axle
Builds of Fruit Jam OS are published as zip file assets on the Github release https://github.com/adafruit/Fruit-Jam-OS/releases, much like individual libraries, and the bundle. Would we want to / is it possible to have a special link or button on https://circuitpython.org/board/adafruit_fruit_jam/ that downloads the latest Fruit Jam OS zip?
and/or sort of related, but perhaps a question for the learn devs, is it possible to have a button or link in a learn guide that automatically links to a file on the latest release of a repo without having to specify the specific release tag in the URL?
fiery pecan
Builds of Fruit Jam OS are published as zip file assets on the Github release ht...
The answer to your second question is documented here: https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases#linking-to-the-latest-release
lone axle
The answer to your second question is documented here: https://docs.github.com/e...
Nice! thank you for that pointer. That makes it very convenient. I knew the release page could be accessed that way, but not the assets.
tulip sleet
@slender iron I am all set to do a beta.1 release immediately (release notes done) so we can have a named release for MagTag. Anything else you want in it?
slender iron
nope!
orchid basinBOT
slender iron
FYI Fruit Jams are in stock: https://www.adafruit.com/product/6200
orchid basinBOT
tulip sleet
CircuitPython 10.0.0-beta.2 released!
https://blog.adafruit.com/2025/07/30/circuitpython-10-0-0-beta-2-released/
Highlights of this release
- Support quad-color e-paper displays.
- Support MagTag 2025 Edition display.
- Use full Mozilla SSL root certificate list for all -network-capable boards.
ionic elk
I have an update to my rclcpy module that has a lot of divergence between the common-hal and shared-bindings. Common hal has a new registry file that contains a type registry helper, and shared-bindings has a whole new folder for message classes that don't have any common-hal requirements. Should I be putting some of this stuff in shared module, or tweaking circuitpy_defns.mk in some special way?
as far as I can tell circuitpy_defns.mk expects exact file parity between common-hal and shared-bindings, which I guess I can fake with a bunch of empty files but it seems a bit silly
tulip sleet
I have an update to my `rclcpy` module that has a lot of divergence between the ...
shared-bindings is meant for the Python-to-C API implementation. There should be little or no actual implementation of stuff in shared-bindings. Occasionally there is, but it would be better factored out to shared-module. There are examples of major modules split between port-specific common-hal and shared-module stuff: _bleio, for instance.
ionic elk
There's no implementation in the files, it's just making Python class types
To be more specific, I have a new submodule to rclcpy called std_msgs that contains Int32.c, Bool.c, etc, representing ROS message types as micropython classes
Well, barely any implementation. All they do is assign variables to the internal object.
tulip sleet
This sounds like the same case: shared-bindings/microcontroller/ResetReason.* is just an enum using py/enum.h. There aren't any shared-module/ResetReason.* or common-hal/ResetReason.* files. So you could look to see how ResetReason.c is handled in the make files
ionic elk
Ok, I'll check that out, thanks dan!
crimson ferry
has anyone seen espressif (S3 specifically) boards locking up, as in CIRCUITPY still accessible, but serial freezes and the board blinks red (one is alpha.7, the others are beta.0) ...no exceptions, no safemode detected
tulip sleet
has anyone seen espressif (S3 specifically) boards locking up, as in CIRCUITPY s...
i have not seen this. Was networking in use?
crimson ferry
some were mainly I2C or SPI , others used wifi.monitor ...I'll upgrade, then see if I can narrow it down
tulip sleet
i could imagine a busy-wait loop in I2C that never gets what it wants. e.g. the fix for this: https://github.com/adafruit/circuitpython/issues/8093
but could be a lot of other things
tiny peak
has anyone seen espressif (S3 specifically) boards locking up, as in CIRCUITPY s...
I've seen some of those symptoms happen before (CIRCUITPY drive still mounted in macOS but serial console is unresponsive). This has definitely happened to me on RP2350 boards when using USB host with devices that send a lot of data (high speed gamepad, MIDI controllers with MPE, etc). I can't remember if I've also seen this on ESP32-S3 in combination with using a MAX3421E USB host FeatherWing, but it's definitely possible. I know I saw some pretty weird glitches with USB host on ESP32-S3 last year, but this year I've been doing RP2350, so my memory is a bit hazy on details.
another thing... sometimes I get a kinda similar issue when attempting to sync code to the CIRCUITPY drive while the board is running code that's doing a lot of USB host IO. In that case, my rsync process will hang, the serial console will hang, and the macOS finder will become slow (perhaps with spinning beachball cursor). The CIRCUITPY drive still looks like it's mounted, but it doesn't actually work. In that case, the board will sometimes reset it self eventually, but it can take a while. Usually I just manually reset when that happens.
I think that case has to do with macOS recently introducing some weird behaviors when writing to FAT filesystems
my impression is that there are probably some places in the CircuitPython core where the TinyUSB USB device implementation can get starved for CPU by other IO handling code in the core.
...or at least there seems to be some kind of race condition, interrupt handler priority fight, stack corruption, use after free, or something.
like, a time or two I've seen garbage strings get returned if I try to use the adafruit usb host library to check device manufacturer and product strings.
since you mention ESP32-S3 specifically, and most the other ESP boards (excepting S2) don't have USB device support, I wonder if maybe there's some kind of race condition / interrupt fight thing going on between TinyUSB and wifi.
crimson ferry
I've also seen something similar to the first thing you mentioned... copying to/from CIRCUITPY while (certain?) code is running may cause trouble for macOS Finder, sometimes it recovers, sometimes I get impatient
orchid basinBOT
main furnace
Adafruit CircuitPython 10.0.0-beta.2 on 2025-07-30; Adafruit LED Glasses Driver nRF52840 with nRF52840
manic glacierBOT
manic glacierBOT
tidal kiln
see convo in #help-with-circuitpython for context, but can someone confirm these TX/RX pin defines are wrong (bug)?
https://github.com/adafruit/circuitpython/blob/234ebf4fb1bbfc19412bc7a2bc7528d4ae62f37b/ports/espressif/boards/adafruit_feather_esp32s3_reverse_tft/mpconfigboard.h#L26-L27
tulip sleet
see convo in <#537365702651150357> for context, but can someone confirm these TX...
replied there
ionic elk
Does Circuitpython diverge from micropython on the creation of class constant types? I'm noticing that the recommendation of usermod:
const mp_obj_type_t vector_type = {
{ &mp_type_type },
.name = MP_QSTR_vector,
.print = vector_print,
.make_new = vector_make_new,
};
does not work
I get error: 'mp_obj_type_t' {aka 'const struct _mp_obj_type_t'} has no member named 'print'
MP_DEFINE_CONST_OBJ_TYPE appears to be the widely used replacement but I can't find proper documentation for it anywhere, it's got a lot of macro shenanigans going on behind the scenes so I don't like that I'm cargo coding with it
MP_TYPE_FLAG_HAS_SPECIAL_ACCESSORS is also very common and undocumented, don't really know what it does
stuck elbow
`MP_TYPE_FLAG_HAS_SPECIAL_ACCESSORS` is also very common and undocumented, don't...
it enables properties
stuck elbow
I'm trying to build 10.0.0-beta.2 and I'm getting:
In file included from esp-idf/components/esp-tls/esp_tls.h:11,
from ./common-hal/socketpool/Socket.h:13,
from ../../shared-bindings/socketpool/Socket.h:9,
from ../../shared-bindings/socketpool/SocketPool.h:13,
from common-hal/socketpool/SocketPool.c:7:
esp-idf/components/esp-tls/esp_tls_errors.h:12:10: fatal error: mbedtls/error.h: No such file or directory
12 | #include "mbedtls/error.h"
| ^~~~~~~~~~~~~~~~~
and a whole lot of other missing files, is there an additional step now?
stuck elbow
same for beta.1 and master
random junco
Is it related to Dan's comment from earlier on his failing build? https://github.com/adafruit/circuitpython/pull/10537#issuecomment-3145439221
manic glacierBOT
ionic elk
@tulip sleet ^ feature complete PR of the new ROS2 message system up if I could entice you to look at my stab at a class registry. Still needs a bit of cleanup I'll tackle this weekend.
manic glacierBOT
manic glacierBOT
manic glacierBOT
manic glacierBOT
fleet hollow
@lone axle Thanks for the recent color palette PR merge in Fruit-Jam-OS! I was looking deeper into the code and just now noticed the implementation of a launcher.conf.json file to turn mouse support on and store favorite apps. Instead of environment variables for the color palette, should they instead be moved over there? And are there any plans for documentation of the implementation of that file in the future?
lone axle
<@382939733107408897> Thanks for the recent color palette PR merge in Fruit-Jam-...
Ah, yeah that is a good call. The color configs should go into that one instead of settings.toml. There are plans to document that (and the rest of Fruit Jam OS). The main product guide has my focus first, but Fruit Jam OS guide is on my list to work on.
manic glacierBOT
manic glacierBOT
ionic elk
@tulip sleet As I work on refactoring out some of the old usermod stuff I was using, should I remove or refactor the _print functions I made based on the old usermod class docs? Are they superseded by any circuitpython automated stuff? They don't seem super common in shared-bindings
stuff like
static void bool_print(const mp_print_t *print, mp_obj_t self_in, mp_print_kind_t kind) {
(void)kind;
rclcpy_std_msgs_bool_obj_t *self = MP_OBJ_TO_PTR(self_in);
mp_print_str(print, "Bool(data=");
tulip sleet
<@329766224093249548> As I work on refactoring out some of the old usermod stuff...
If they are useful, fine to leave them in. We don't really have something automated that prints internal values, except namedtuple, etc. Example of a current more informative print routine is keypad_event_print() in keypad/Event.c
ag -Q '_print(' |more will show more.
tiny peak
Question for people who work on the CircuitPython core and built-in frozen modules: What's your preferred IDE or editor to use? I'm getting semi serious about starting a quest to troubleshoot various USB host glitches that have been bugging me. I'm thinking it would be easier if I had more editor support for navigating between related code compared to what I usually use (BBEdit or vim).
I'm specifically curious about editing tools that help with type checking, static analysis, and navigating between definitions of and references to variables, functions, classes, etc.
Bonus points for tools that might help to identify common C problems like failure to guard against null pointers, possible buffer overflows, use after free, and so on.
manic glacierBOT
tulip sleet
Question for people who work on the CircuitPython core and built-in frozen modul...
I use emacs and TAGS files, and use ag to do global code searches. Maybe not exactly what you were expecting/hoping to hear. I think Scott uses Sublime, at least some of the time.
tiny peak
oh... interesting. I tend to be pretty primitive about it and use stuff that works over ssh. Have actually used emacs some in the past, but hadn't heard of TAGS files or ag, so I'll put those on the list of stuff to read about. Thanks!
tulip sleet
Jeff Epler has used some code-analysis tools to catch various code erros
there is also TAGS support in vim
read about etags
besides ag, there is also rg, pretty similar
ag is aka silversearch
tulip sleet
ag and rg are extremely fast, much faster than grep -r
tiny peak
okay, cool I'll read about those
tulip sleet
halbert@cod:~/repos/circuitpython$ time ag foobar >/dev/null
real 0m2.276s
user 0m3.764s
sys 0m5.750s
thanks
slender iron
I'm using zed now to get LLM powered autocomplete. I don't do much code navigation with it though. The main thing you should get for USB host debugging is a USB sniffer. That way you can see all of the packets from an agnostic source.
I got a https://www.adafruit.com/product/6005 but trust the https://www.adafruit.com/product/708 (or 480) more.
tulip sleet
I have successfully made traces with the Cynthion
The Beagle only puts out a proprietary format and .csv. Scott wrote a converter from the .csv dump to .pcapng. The Packetry software for the Cynthion generates .pcap directly
full plume
Question for people who work on the CircuitPython core and built-in frozen modul...
I've been primarily using VS Code. If you get it set up properly, it can be very helpful for both C/C++ and Python/CircuitPython code.
full plume
Since my primary dev system is currently a Windows system, I'm running CircuitPython builds under WSL. That works fine - VSCode even has a specific mode for "WSL based" workspaces.
The one squishy bit I haven't gotten fully working yet is running the firmware reliably / easily in debug over USB.
I've done a bit and I think it's plausible (maybe someone already has it working?) but I haven't seriously needed it yet.
tiny peak
I've been primarily using VS Code. If you get it set up properly, it can be _ve...
That sounds interesting. I hear it also supports ripgrep, cscope and other stuff. I'll add that to my list of stuff to read up on. Thanks!
tiny peak
I'm using zed now to get LLM powered autocomplete. I don't do much code navigati...
yeah... I noticed the Beagles are gone. Been thinking about a Cynthion. Thanks!
full plume
That sounds interesting. I hear it also supports ripgrep, cscope and other stuff...
I hadn't heard of ripgrep or cscope. Honestly though, unless you're already used to them you probably wont' need them if you're using VSCode. Getting VSCoder "set up properly" is partly about using the right extensions, but mostly about configuring your workspace so it knows where to find and how to "process" your source. For example, include paths and relavent conditional compilation macros for C/C++, and interpreter version / venv / library path for python. Once that's set up properly, you can simply CTRL-RightClick on just about anything and it will take you right to the declaration/definition.
tiny peak
that sounds cool. I'm particularly curious about static analysis stuff because some of the bugs I've seen while using the USB host API smell like some of the stereotypical memory corruption bugs that commonly happen in C.
...random garbage or all zeros in places that should have a string or an int, and so on.
full plume
VSCode also has recursive directory regex search/replace built in (i.e. while there is a ripgrep extension available, it already supports very similar functionality). IIRC the regex syntax is mostly compatible with python's re expression format. The only quirk that comes up frequently is you need to use $1 and $1 for the replace expression instead of 'using \1 and \2 like python'
full plume
that sounds cool. I'm particularly curious about static analysis stuff because s...
Haven't stressed the memory related static analysis bits for C code much so I can't say how comprehensive it will be. Almost all my serious embedded code has been in C++ for a long time, and I'm quite careful with memory - almost everything is reference counted and/or RAII wrapped. Doesn't mean I never have memory corruption issues, but when they occasionally come up it's almost always because of order-of-initialization problems with "global" / singleton variables or access from multiple threads without proper concurrency management (or bugs in other libraries my projects depend on)
slender iron
yeah... I noticed the Beagles are gone. Been thinking about a Cynthion. Thanks!
They still make beagles. Adafruit just doesn't stock them anymore
tulip sleet
tulip sleet
Of interest: https://github.com/espressif/esp-idf/issues/17052
manic glacierBOT
manic glacierBOT
slender iron
@tulip sleet I'm going to switch epd to a struct so I can add partial commands
slender iron
@tulip sleet I'm just about to get on my laptop
slender iron
@tulip sleet can chat now
manic glacierBOT
tiny peak
@tulip sleet For bumping a submodule commit version (e.g. TinyUSB), are any CircuitPython-specific magic incantations needed with make or scripts or something, or does it just work the normal way?
tulip sleet
just cd into the submodule, do a git pull or git fetch, and checkout the commit you want. then cd back up and commit the change
If you think that's the "normal" way
tiny peak
awesome. thanks. I know some of the submodule stuff is a bit unusual.
tulip sleet
we use --filter=blob:none, but that's just to save time and space, and doesn't affect the commits
tiny peak
when you mentioned testing the new TinyUSB version, were you expecting that would be done internally at Adafruit?
I can poke at it on my Fruit Jam and such, but that's far from comprehensive compared to all the boards that use TinyUSB
zinc walrus
I'm planning on migrating from Windows to Debian soon, and in preparation I've been implementing new workflows in a Debian WSL install. Since so many distros are based on Debian, I reasoned that I should probably start there too.
The Building CircuitPython learn guide recommends an Ubuntu environment, but several of the devs here use Arch and others. I'm aware of some differences (flatpaks, etc), but are there any pitfalls preventing me from using Debian as my base? I'm not quite smart enough to build CircPy yet, but I'm steadily learning how so that I can experiment with the Zephyr port.
@slender iron built me a Zephyr test binary a few months ago for an nRF5340 Audio DK, but no matter what I tried I couldn't flash it. The Audio DK is amazing hardware, but Zephyr/NCS is so tedious when rapid prototyping that I'm desperate for a higher-level language, and CircuitPython would be an absolute dream. @tiny peak's playground writeups have also been inspiring and informative.
Are there any devs here who might provide wisdom and insight on my journey? I have plenty of CLI experience (I grew up on Unix and CP/M), but this is a very deep rabbit hole, and I could use some guidance.
tulip sleet
I'm planning on migrating from Windows to Debian soon, and in preparation I've b...
We recommend Ubuntu because it's very common, packages are kept up to date, there is a robust PPA system, etc. Recommending a particular distribution makes it easier to duplicate an issue or provide support.
But the differences between distributions are pretty small, and most packages are available everywhere. I don't think you'd have much if any trouble using Arch instead of Ubuntu, or Debian instead. So pick the one that's appealing.
zinc walrus
Thanks, @tulip sleet. I always appreciate your input.
tulip sleet
You're welcome!
tiny peak
I'm planning on migrating from Windows to Debian soon, and in preparation I've b...
I've used Debian for CircuitPython and Zephyr, and it's mostly fine. You'll occassionally run into stuff with udev rules and group membership where you don't have the permissions you need to access a hardware device. Once in a while something might come up where you have the wrong version of some library, or if you try to use a system python package instead of the latest thing from PyPi. I've found instructions for Ubuntu mostly work. The differences between Debian and Ubuntu are pretty small. Take what I say with a grain of salt though because I've been doing Linux stuff for over 20 years, so I probably don't even notice some of the stuff that I do to work around any glitches in instructions.
zinc walrus
I've used Debian for CircuitPython and Zephyr, and it's mostly fine. You'll occa...
Yes, I've already bumped up against udev permissions, and I'm aware of system Python versus venv Python. It's good to hear others have had success, even if it requires further study. Thanks for the response, @tiny peak, and for sharing your helpful writeups.
tulip sleet
uninstall modemmanager if it is installed. It can grab serial ports
zinc walrus
uninstall modemmanager if it is installed. It can grab serial ports
already done. thanks for the tip.
tiny peak
@zinc walrus One thing to keep in mind about Debian is that the Bookworm to Trixie major version update is about to happen (Trixie release is tomorrow I think?)
zinc walrus
<@834445433060589579> One thing to keep in mind about Debian is that the Bookwor...
The minor version upgrades for the past few months have thus far been painless. Should I expect any problems with the major version upgrade?
tiny peak
Dunno... I expect that there will be version bumps on lots of tools and libraries. Might affect CircuitPython build tools, compiler toolchains, etc. in a meaningful way, or it might not. Hard to say.
If you start on Bookworm, stuff will probably work fine, but you'll be missing out on lots of version updates on other stuff which you might enjoy having access to.
zinc walrus
If you start on Bookworm, stuff will probably work fine, but you'll be missing o...
Thanks for the warning. I usually wait a bit for the dust to settle before blindly upgrading. I'll watch the forums for potential problems.
zinc walrus
If you start on Bookworm, stuff will probably work fine, but you'll be missing o...
Just out of curiosity, what desktop environment do you use?
tiny peak
Just out of curiosity, what desktop environment do you use?
xfce with an aggressive set of sudo apt remove ... to get rid of default plugins and widgets that annoy me (supplemented with some sudo apt install ... to ensure important auto-installed packages don't get zapped)
I always make sure to uninstall avahid, cups, libreoffice, and tools that do automatic disk access (indexers, thumbnailers, etc). General idea is to reduce the number of open ports and stuff that messes with files on mounted drives.
tulip sleet
I use cinnamon, and keep a rather short bottom panel so I maximize screen space
tiny peak
Figuring out how to configure your editor(s) to avoid pooping temporary files all over the place can be really helpful for CircuitPython. I prefer to edit on my hard drive and then rsync files to CIRCUITPY (followed by a sync to flush the cache quickly)
tulip sleet
one problem I haven't solved, and don't know where to lay the blame, is that the inter-application clipboard doesn't seem to get filled properly unless I copy something twice. E.g. copying a URL from the browser to discord requires ctrl-c ctrl-c ctrl-v
I use middle button click to send the current selection somewhere else a lot.
zinc walrus
Very interesting information, @tiny peak and @tulip sleet. I'm still command-line only since I'm using WSL, but as I plan my move to a bare metal install, I'm beginning to consider desktops. Thanks so much for the recommendations and details.
tiny peak
something to keep in mind if you want a softer start... ssh works great for a lot of stuff
I usually use a Mac for my daily driver productivity apps that I don't want to have to burn time tinkering with. Then, I've got a few linux boxes and an Ethernet LAN on my desk, so I can ssh or VNC out to Debian. Or, for stuff that needs GPU acceleration (e.g. Blender), I can just switch my monitor over to a different input source.
That way, if you have a dev environment install go really sideways, it doesn't take out your whole setup
tulip sleet
i use nomachine (free version) to remote-desktop to mac and windows from Linux
zinc walrus
Yes, VS Code on Windows essentially uses SSH to "remote" access the WSL virtual machine, so I'm already comfortable with the concept, but I only have one PC to deal with at the moment.
tiny peak
FWIW, picking up some old cheap stuff off ebay has really improved my dev setup. Dell P series monitors are great. Old intel mac minis are great (but go for the higher spec ones).
tulip sleet
I buy from https://www.dellrefurbished.com/, but make sure you have a coupon (30-50% off) or buy a "Hot Deal". I have bought maybe a dozen desktops and laptops from there, all were fine. They are off-lease, and come with proper Windows licenses (unlike some other refurbs I've encountered).
tiny peak
+1 for off-lease Dell stuff
zinc walrus
Well, I'm not exactly swimming in developer money, but I scrounge what I can.
tiny peak
great thing about linux is it will run on some seriously garbage computers (going by modern specs)
tulip sleet
the mix on dellrefurbished has really leaned toward laptops these days; they are seriously cheap and plentiful.
full plume
I'm planning on migrating from Windows to Debian soon, and in preparation I've b...
FWIW, my primary desktop environment is Windows 11 but I regularly use the "default" (Ubuntu) WSL2 to build CircuitPython images. Most of the Linux PCs I've set up over the past few years have been Ubuntu - I haven't done much with Debian lately (other than using OctoPi for my print farm). If you're not able to get CircuitPython to build under Debian WSL2, maybe there's a Debian vs Ubuntu difference although that feels like a stretch. Keeping USB happy under WSL is a pain, but that shouldn't affect builds...???
How far have you gotten / what are your roadblocks building CircuitPython?
One specific recommendation for using the WSL is to stay in the "local WSL file system" for your builds (i.e. something like ~/git/circuitpython instead of /mnt/c/Users/jbrel/git/circuitpython). I initially tried that latter, using WSL to build in the directories I had already checked out on a normal Windows drive. It was ridiculously slow and temperamental. After cloning the circuitpython repo directly into the local WSL file system, builds in the new repo ran an order of magnitude faster.
full plume
just learned something about Discord : I like embedding (hopefully helpful) relevant links in Discord messages. It's easy using [description](link) Markdown syntax, for example : [Markdown](https://en.wikipedia.org/wiki/Markdown). But that typically appends an embedded window showing the linked page when displaying the message, which sometimes feels like unnecessary clutter, Turns out that wrapping a link in angle brackets (<http://...>) disables that but keeps the link itself in the message text. So the above link to Markdown was written [Markdown](<https://en.wikipedia.org/wiki/Markdown>), so there shouldn't be any extra window displayed after this...
digital maple
Hi! 👋 I’m working on adding support for a new board to CircuitPython, and I’m about to draft a PR. I’m a bit unsure about which branch I should use as the base, should I be branching off main/master, or is there another branch I should target for new board additions? Thanks in advance!
stuck elbow
Hi! 👋 I’m working on adding support for a new board to CircuitPython, and I’m a...
I always added my boards to main
digital maple
Got it, thanks! I’ll branch off main then.
main furnace
AirLift can't do web workflow. Change my mind.
candid sun
<@&356864093652516868> We'll have our weekly meeting in about 90 minutes from now in this text channel and in the circuitpython voice channel. Please take the time to add your notes in advance to the document: https://docs.google.com/document/d/11KpdjrQUXbQ_-uasV4gLlZIPz3q-nfP7A2c9isIOVvg/edit?tab=t.0 -- I look forward to everyone's updates!
main furnace
Open Installer is great but it seems to always install the English firmware.
devout jolt
Is there a description somewhere of how code.circuitpython.org's not-CIRCUITPY "USB mode" works and is it the same as Thonny's method?
slender iron
Is there a description somewhere of how code.circuitpython.org's not-CIRCUITPY "...
I think it is similar to mpremote. Basically entering the raw repl to change things.
slender iron
Open Installer is great but it seems to always install the English firmware.
Please file an issue!
devout jolt
I think it is similar to mpremote. Basically entering the raw repl to change thi...
That was my assumption too. I was hoping for more details as it works really well for ESP32 and I wanted to talk about it on our podcast 😀
