# Pico Inky Pack - some thoughts

**URL:** <https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955>\
**Category:** Discussion\
**Created:** [December 12, 2022, 6:02pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955 "2022-12-12T18:02:10Z")\
**Posts on this page:** 9\
**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:** [December 12, 2022, 6:02pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/1 "2022-12-12T18:02:10Z")

</div>

The “Pico Inky Pack” is a small 2.9" monochrome e-paper that you  
can plug into your Pico/Pico-W. Technically it is the same as  
the display used in the Badger2040. So it is natural to do a  
comparison between the Inky-Pack (+Pico) and the Badger2040.

Cons:

- thicker package (z-dimension)
- only three buttons
- no Stemma/Qt connector
- no power-management
- no mounting holes
- no standard-driver for CircuitPython
- price

Pros:

- slimmer (y-dimension)
- access to all pins (but read on)
- no power-management (yes!)
- “builtin” wifi with the Pico-W

Looking at the cons, the missing Stemma/Qt connector and mounting holes  
hurt the most. But at least there is enough space to glue on some threads  
in the corners.

Since the Badger2040 supports CircuitPython, it only took some time  
to port the initialization-code for the display from the board-definition  
file (board.c) to pure Python. I will publish the driver soon.

As you might have noticed “no power-management” is listed as con and  
as pro. The power-management of the Badger2040 is very efficient, but  
has the drawback that it needs manual intervention to start the device  
again. It is not possible without hacks to start on a timer-event, and  
external events aren’t supported either.

The Inky-Pack has no power-management and therefore you can use every  
available option together with your Pico. Adafruit for example has a  
nice timer-enable button, connected to the enable-pin of the Pico will  
turn on the mcu in predefined intervals.

One of the big drawbacks of the Badger2040 is the missing access to important  
GPIOs. No general purpose GPIOs are available (unless you can do without  
UART), and you have no ADC-pins. Here is where the Inky-Pack shines.

But the Inky-Pack has one big design flaw: it uses GP26/A0 for the busy  
pin of the Inky-Pack instead of GP22. GP26 is not only an ADC pin, but  
it is also used for I2C, more specifically, the only I2C next to 3V3.  
So using GP26 instead of GP22 the Inky-Pack blocks the simplest  
option to plug in I2C-components without having wires all over the Pico.  
Maybe there is a reason not to use GP22, but I don’t understand it. It is a pure  
IO-pin without special functions and it sits right next to the other pins routed  
to the display.

@Hel: maybe you can pass this on to your engineers for a better V2-version  
of the Inky-Pack.

So when should you choose the Inky-Pack compared to Badger2040? One reason  
is that you want to use the builtin wifi of the Pico-W. But adding an  
ESP-01S to a Badger2040 is simple and Badger2040+ESP-01S is still cheaper  
than Inky-Pack+Pico-W.

A second reason is you want a device that wakes up in intervals or from  
external events. The Badger2040 needs hardware-hacks to support this.

And finally, the Inky-Pack gives you access to more pins.

---

<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:** [December 13, 2022, 9:21am UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/2 "2022-12-13T09:21:59Z")

</div>

Thanks for the thorough feedback! I’ve passed it on.

---

<div class="post-metadata">

**Author:** ![m1cr0py7h0n](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/m1cr0py7h0n/32/11507_2.png) [@m1cr0py7h0n](https://forums.pimoroni.com/u/m1cr0py7h0n)\
**Post date:** [March 4, 2025, 2:00pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/3 "2025-03-04T14:00:59Z")

</div>

> [@bablokb](#):
>
> But the Inky-Pack has one big design flaw: it uses GP26/A0 for the busy  
> pin of the Inky-Pack instead of GP22. **GP26 is not only an ADC pin, but it is also used for I2C** , more specifically, the only I2C next to 3V3.  
> So using GP26 instead of GP22 the Inky-Pack blocks the simplest  
> option to plug in I2C-components without having wires all over the Pico.

@hel has this been solved and will you come up with a new PICO inky pack version (exchanging PIN 22 in favour of PIN 26)?  
I am waiting for the epaper display for weeks and one possible reason could be that you are working on a redesign… please let us know…  
I so, I then would be waiting for the next revision on PICO inky pack…

---

<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 4, 2025, 2:07pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/4 "2025-03-04T14:07:34Z")

</div>

We won’t be making any more Inky Packs with this screen as I believe it’s has now been discontinued by the manufacturer.

---

<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 4, 2025, 2:41pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/5 "2025-03-04T14:41:25Z")

</div>

Will there be a replacement? AFAIK, the display is also used in the Badgers.

---

<div class="post-metadata">

**Author:** ![m1cr0py7h0n](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/m1cr0py7h0n/32/11507_2.png) [@m1cr0py7h0n](https://forums.pimoroni.com/u/m1cr0py7h0n)\
**Post date:** [March 4, 2025, 2:42pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/6 "2025-03-04T14:42:19Z")

</div>

> [@hel](#):
>
> discontinued by the manufacturer

Wow…that’s a significant info…  
Are there any other options for a epaper display, which support fast screen update modes? I really liked the fast screen updates in b/w mode, so simple animations were actually possible with just a very minimal flicker of the screen within 1 second…

What then happens to the Badger upgrade?  
Sounds that there would be no Badger2350 in the pipeline…or are you working on a comparable solution?

---

<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 4, 2025, 2:58pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/7 "2025-03-04T14:58:53Z")

</div>

Yep, we’re currently working on Badger v2, with RP2350 and a different eInk screen :)

(and if that screen works out well, I’d imagine we could do a Pico Pack with it too).

---

<div class="post-metadata">

**Author:** ![m1cr0py7h0n](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/m1cr0py7h0n/32/11507_2.png) [@m1cr0py7h0n](https://forums.pimoroni.com/u/m1cr0py7h0n)\
**Post date:** [March 4, 2025, 3:22pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/8 "2025-03-04T15:22:02Z")

</div>

> [@hel](#):
>
> Yep, we’re currently working on Badger v2, with _RP2350_ and a different eInk screen

…would you please be so kind as to share some timelines by when we could expect the new Badger2350 for order?

---

<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 4, 2025, 3:51pm UTC](https://forums.pimoroni.com/t/pico-inky-pack-some-thoughts/20955/9 "2025-03-04T15:51:39Z")

</div>

I don’t think we have any timescales to share yet, sorry.
