CircuitPython for Tufty

Currently there is no support for CircuitPython for Tufty. I can find a CP-fork with Tufty support, but this fork is now 800+ commits behind main.

I followed the open issue on that, but there has not been any progress for a long time. Do you think it is possible to create a pull-request for mainline CP? This would mean that the CP uf2 is built automatically and allows more people to play with it and maybe this will help with fixing the open issues.

BTW: Adafruit also has some board in the main-tree which are by no means stable or feature complete.

I’m thinking you’re going to have to ask this request of Adafruit. I don’t think Pimoroni has much control over what happens Circuit Python wise.
Just curious what you want to do, Circuit Python wise on your Tufty? I have one and have had a lot of fun with it. Micro Python here though.

No. Board specific code in CP is maintained by the manufactures. The fork I am referring to is from Pimoroni.

CP has many, many libs which you can just install using “circup”. As simple as with pip. With MP, I have to hunt all over the internet to find libs, and many of them don’t “just work”. And even if they work, they have to be manually installed and maintained.

An example: I would use a cheap ESP-01S as a wifi coprocessor for the tufty. With CP, this is a matter of a addding a few lines of code. circup would then detect the missing libs and update everything. Same with sensors and so on.

MP does have a number of advantages compared to CP, but I decide on a per project basis what to use. And often I do prototyping using CP and then switch to C++.

We had some issues getting the Tufty screen working properly in CircuitPython that we’ve been unable to resolve so far :( The details are in this issue if you want a look: Issues with bringing up the new Pimoroni Tufty LCD board · Issue #6505 · adafruit/circuitpython · GitHub

Yes, I have read this issue. But it does not help anybody if you keep your current work in a fork which is now almost 900 commits behind mainline. As far as I can see we are talking about five tufty-specific files, so it should be no problem pushing these to mainline. It would give hackers a chance to play with it and maybe solve the problem. But nobody wants to work on a fork that is so old…

Chris has updated the fork to be inline with mainline, so it should be easier to build now. He’s reluctant to raise it as a PR though until the issue is resolved.

Thanks! I will give it a try and report back

1 Like