# CircuitPython for Badger2040W

**URL:** <https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592>\
**Category:** Support\
**Created:** [March 2, 2023, 9:29am UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592 "2023-03-02T09:29:14Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bablokb](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@bablokb](https://forums.pimoroni.com/u/bablokb)\
**Post date:** [March 2, 2023, 9:29am UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/1 "2023-03-02T09:29:14Z")

</div>

Hi pirates,

I have created the CircuitPython board-definition files for the Badger2040W and also a CP driver for the PCF85063A. Any objections that I create a pull request for upstream CircuitPython?

---

<div class="post-metadata">

**Author:** ![hel](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/hel/32/6075_2.png) [@hel](https://forums.pimoroni.com/u/hel)\
**Post date:** [March 2, 2023, 4:07pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/2 "2023-03-02T16:07:48Z")

</div>

Sounds awesome - can we have a look at your proposed changes?

---

<div class="post-metadata">

**Author:** ![bablokb](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@bablokb](https://forums.pimoroni.com/u/bablokb)\
**Post date:** [March 2, 2023, 5:58pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/3 "2023-03-02T17:58:16Z")

</div>

yes: [GitHub - bablokb/circuitpython: CircuitPython - a Python implementation for teaching coding with microcontrollers](https://github.com/bablokb/circuitpython/) and then select branch badger\_2040\_w.

---

<div class="post-metadata">

**Author:** ![bablokb](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@bablokb](https://forums.pimoroni.com/u/bablokb)\
**Post date:** [March 10, 2023, 2:39pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/4 "2023-03-10T14:39:25Z")

</div>

@hel any news here? Having this in upstream would be really great, since there are regular CircuitPython relases and once it is in upstream, newer versions are built automatically.

---

<div class="post-metadata">

**Author:** ![hel](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/hel/32/6075_2.png) [@hel](https://forums.pimoroni.com/u/hel)\
**Post date:** [March 10, 2023, 2:59pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/5 "2023-03-10T14:59:14Z")

</div>

I’ve passed this on to our software team but it’s been a busy couple of weeks - I’ve applied a nudge :)

---

<div class="post-metadata">

**Author:** ![bablokb](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@bablokb](https://forums.pimoroni.com/u/bablokb)\
**Post date:** [March 10, 2023, 3:07pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/6 "2023-03-10T15:07:20Z")

</div>

Thanks. Would it be possible to get in contact with the software team directly? Because there are some boards that are still lacking CircuitPython support and I would love to see this happen (and I am willing to contribute):

- Tufty2040: I see no reason not to upstream the existing code, since all problems so far have nothing to do with CircuitPython
- Plasma2040W: should be very easy to do. Currently, the product page links to a CP version for the normal Pico, which is not suitable
- InkyFrame: my next task, since CP now supports the display. Buttons need an extra driver, but that should be feasible.

---

<div class="post-metadata">

**Author:** ![hel](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/hel/32/6075_2.png) [@hel](https://forums.pimoroni.com/u/hel)\
**Post date:** [March 10, 2023, 3:53pm UTC](https://forums.pimoroni.com/t/circuitpython-for-badger2040w/21592/7 "2023-03-10T15:53:21Z")

</div>

Sounds good - I’ve dropped you a DM :)
