-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Board files for LOLIN S3 MINI #8010
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhalbert I do not have the board.
I just try to review stuff I am comfortable with.
The optimisation flag is what concerns me most with this definition.
If you want me to stop reviewing stuff, just tell me.
# | ||
# SPI RAM config | ||
# | ||
# CONFIG_SPIRAM_MODE_QUAD=y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should have been more specific, sorry.
It's CONFIG_SPIRAM_TYPE_AUTO
that is unwanted.
You want CONFIG_SPIRAM_MODE_QUAD
or CONFIG_SPIRAM_MODE_OCT
enabled.
You can just try out if oct works if you are too lazy to check the schematic.
If oct doesn't boot, quad.
@bill88t No problem, keep reviewing. THe optimization change may be needed to make it fit. |
Isn't it the policy to just disable unused modules in favor of keeping optimisation as is? It's a 4mb S3 board. That should be added in the |
Normally we would turn ESPCAMERA off. We don't necessarily preserve optimization in favor of turning of general-purposes functionality. O2 is a lot bigger than Os. That is certainly true on various SAMD boards, for instance. We use Os to have all the useful modules. |
If |
Thanks! Removed. I had thought the optimization flag was brought over from the existing Lolin S3 board files, but it was me who accidentally pasted it from somewhere else. Sorry about the confusion. |
Although may not be relevant I would remove all the extraneous pin definitions for those not broken out on the board. I would include a definition for the onboard WS2812 which I believe is on IO47. I can't be more specific on my phone lol |
I don't understand the merge conflicts either. Strange. But I am new to this whole process, so maybe I did something accidentally. circuitpython/ports/espressif/boards/lolin_s3_mini/pins.c Lines 101 to 103 in 5c49978
re: extraneous pins. I checked pins.c and don't see any pins defined that are not also exposed on the board. |
I think the easiest way to fix this would be to make a new branch, copy the new files into it, and make a new PR. We can close this one assuming the new one works. |
Quite true. I was looking at it on my phone. I can blame my old eyes, better than blaming myself. Thanks again. |
Ok. I will create a new branch and PR. Thanks for all your help! |
|
@tkroo you don't need to delete your fork. Just deleting the branch would be ifne. |
Oh well, I've already deleted it. I think what caused the merge conflict was that I had merged my branch into my fork's main. Anyway, I'll create a new fork, branch, and PR. |
Yes, try to keep your |
new PR: #8023 |
My first time creating a new board definition, hopefully everything is ok.