Skip to content

Conversation

@noqman
Copy link

@noqman noqman commented Dec 3, 2025

Hi, can you please help to add this board?
The product is still under development and will be launched soon.

Let me know if there are any issues with it.
Thank you!

@dhalbert
Copy link
Collaborator

dhalbert commented Dec 3, 2025

Hi, the build is overflowing on one or more languages.

You are freezing a lot of libraries. You could drop some of these:

  • adafruit_bus_device is already included as a C implementation. The frozen version will not be used.
  • adafruit_sdcard is not needed if sdcardio is enabled.
  • simpleio is not really needed. If you want a range() operation, see adafruit_simplemath.
  • You are including non-displayio display support with adafruit_framebuf and adafruit_ssd1306. Is it your intention to have both kinds of display support?

Look at the pico 2W build and see if there are any native (built-in) modules you might want to turn off to make room.

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reduce size

@noqman
Copy link
Author

noqman commented Dec 8, 2025

Hi!

Sorry, I forgot to mention earlier. This board will be used with a guidebook that our team is developing. We planning to freeze in all the required libraries so users don’t have to manually add anything into the lib folder. That’s why you see many libraries included here hahah. There are two more libraries I plan to add OPT4048 (which I already added) and PAJ7620.

  • I removed the adafruit_bus_device as per your comment
  • we use the simpleio Iibrary because we use it for buzzer code.

I tried to build the uf2 using linux and yeah like you said the size is too large:

Memory region Used Size Region Size %age Used
FLASH_FIRMWARE: 1377392 B 1020 KB 131.87%
RAM: 68720 B 512 KB 13.11%
SCRATCH_Y: 0 B 4 KB 0.00%
SCRATCH_X: 2 KB 4 KB 50.00%

Currently I try to remove some of the native (built-in) modules that aren’t used in our guidebook to help reduce the firmware size.

@dhalbert
Copy link
Collaborator

dhalbert commented Dec 8, 2025

CIRCUITPY_ULAB = 0 will remove ulab which is quite large, though also useful. You could turn off some unused display-bus and epaper support, etc. as well.

@noqman
Copy link
Author

noqman commented Dec 21, 2025

Hi!

Thanks again for the suggestion. We’ve disabled several unused modules and adjusted the firmware flash allocation (similar to Pico W / Pico 2 W). The firmware now takes up about 81% of the allocated space.

  1. From your experience, are there any issues we should expect when our firmware takes up most of the allocated flash space?

  2. We have also added one more newly created frozen library (PAJ7620). Would it be OK if we include this library in the CircuitPython community bundle? I’m asking because there is already an existing library for this sensor, but due to some disagreements with the current maintainer, we decided to develop and maintain our own version.

thanks

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, a question and a suggestion.

CIRCUITPY_MAX3421E = 0
CIRCUITPY_ULAB = 0
CIRCUITPY_ZLIB = 0
CIRCUITPY_SSL_MBEDTLS = 0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you still do https with this turned off? I'm surprised.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh.. thanks for pointing this out. I just tried running HTTPS-related code, and as expected it doesn’t work. Ill delete this line CIRCUITPY_SSL_MBEDTLS = 0

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me after the latest round of changes. If you're ready we can merge!

@noqman
Copy link
Author

noqman commented Dec 23, 2025

Yes! we are ready to proceed with merge

Before we do, I just wanted to follow up briefly on one earlier question to make sure we’re aligned:

We’ve added one newly created frozen library (PAJ7620). Would it be OK to include this library in the CircuitPython community bundle? I ask because there is already an existing library for this sensor, but due to some disagreements with the maintainer, we decided to develop and maintain our own version.

thanks!

@dhalbert
Copy link
Collaborator

dhalbert commented Dec 23, 2025

We’ve added one newly created frozen library (PAJ7620). Would it be OK to include this library in the CircuitPython community bundle? I ask because there is already an existing library for this sensor, but due to some disagreements with the maintainer, we decided to develop and maintain our own version.

This is ok, but I looked at deshipu/circuitpython-paj7620#1, and I think you could still work with the library author. His requests are minor, and his comments about vetting AI-generated code reflect appropriate caution.

If you do make a new version, you should make it have a different import name than the other library.

@noqman
Copy link
Author

noqman commented Dec 23, 2025

Ohh okay, noted on that. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants