Replies: 2 comments
-
|
That is great finding, Amazing.
Thank you
Chris
…On Sat, Apr 5, 2025 at 5:06 PM robonxt ***@***.***> wrote:
Observations on bpad testing
- Boards:
- bpad_v1_board (prototype 1: 4 haptics, speaker, compass?)
- IDEs:
- legacy: 1.8.19
- current: 2.3.5
- Cores:
- ArduinoESP32: 2.0.13, 2.0.17, 3.0.7, 3.2.0
- bpad: 0.1.2
- Libraries: (to be updated)
- lovyanGFX: 1.1.5, 1.1.9, 1.1.16, 1.2.0
- lvgl: 8.3.0-dev, ???
Boards
I originally have the bpad_v1_board for testing. Since many features in
software (especially the bpad Core) has been designed for newer revisions,
I am doing many workarounds to get it to work properly.
IDEs
Got it working on legacy 1.8.19, no changes needed.
I was previously running into issues with the compiler on the current
2.3.5 IDE not allowing older ESP32 Core 2.0.13 to be uploaded. I've fixed
that by uninstalling and reinstalling it completely.
Cores ArduinoESP32
I am forced to use ArduinoESP32 2.X Core due to something (maybe
lovyanGFX?) not being updated to completely use the new i2s/i2c system.
Code compiles correctly, however bpad_v1_board will bootloop with the
following truncated error:
entry 0x403c88b8
E (120) i2c: CONFLICT! driver_ng is not allowed to be used with this old driver
abort() was called at PC 0x4201f05b on core 0
Another change to newer cores is that ledcAttachPin() and ledcSetup() has
been merged into one.
Old ArduinoESP32 v2.X Core code:
ledcSetup(BACKLIGHT_PWM_CHANNEL, BACKLIGHT_PWM_FREQUENCY, BACKLIGHT_PWM_RESOLUTION);
ledcAttachPin(PIN_LCD_BL, BACKLIGHT_PWM_CHANNEL);
New ArduinoESP32 v3.X Core code:
ledcAttach(PIN_LCD_BL, BACKLIGHT_PWM_FREQUENCY, BACKLIGHT_PWM_RESOLUTION);
NOTE: libraries still need to be working with new core version in order
for code to compile and upload successfully
However, if sticking to v2.X, then it is safe to upgrade completely to
v2.0.17 from the Arduino Boards Manager.
bpad
Since the bpad Core was designed for the newer hardware revisions with
16MB flash + 2 partitions, bpad_v1_board does NOT work with it. TO BE
UPDATED when new board revision is tested.
Libraries lovyanGFX
lovyanGFX v1.1.16 seems to be the final working one for the ArduinoESP32
2.X Core. 1.2.0 is only for ArduinoESP32 3.X Core, however it does not work
properly on bpad_v1_board. Can be safely upgraded to v1.1.16 from the
Arduino Libraries Manager.
lvgl
lvgl could be optimized a bit more, since it takes the longest to compile.
Perhaps some unused UI features can be disabled? I have not tested newer
version as lvgl version may be dependant on lovyanGFX? TO BE UPDATED
—
Reply to this email directly, view it on GitHub
<#2>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELIOPX6SCVMHWPGHKP726T2YBVZVAVCNFSM6AAAAAB2RBGOHKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGE3TANJSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I made a quick repo for the proto1 board's core: https://github.com/robonxt/bpad_proto1_core |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Observations on bpad testing
Boards:
bpad_proto1_board
I have the bpad_proto1_board for testing. Since many features in software (especially the bpad Core) has been designed for newer revisions, I am doing many workarounds to get it to work properly.
Known board info:
Options for uploading:
OPTIONAL to fix flashing error:
- Erase All Flash Before Sketch Upload = EnabledIDEs:
legacy
Got it working on legacy v1.8.19, no changes needed.
current
I was previously running into issues with the compiler on the current v2.3.5 IDE not allowing older ESP32 Core v2.0.13 to be uploaded. I've fixed that by uninstalling and reinstalling it completely.
Cores:
ArduinoESP32
I am forced to use ArduinoESP32 v2.X Core due to something (maybe lovyanGFX?) not being updated to completely use the new i2s/i2c system. Code compiles correctly, however bpad_proto1_board will bootloop with the following truncated error:
Another change to newer cores is that
ledcAttachPin()andledcSetup()has been merged into one.Old ArduinoESP32 v2.X Core code:
New ArduinoESP32 v3.X Core code:
However, if sticking to v2.X, then it is safe to upgrade completely to v2.0.17 from the Arduino Boards Manager.
bpad
Since the bpad Core was designed for the newer hardware revisions with 16MB flash + 2 partitions, bpad_proto1_board does NOT work with it. TO BE UPDATED when new board revision is tested.
bpad_proto1_core
This core was vibe coded by me to make it easy to have all the defaults working fine on the known ESP32 v2.0.17 core. Created so I can have a custom ESP32 core without messing up my existing cores.
Libraries:
lovyanGFX
lovyanGFX v1.1.16 seems to be the final working one for the ArduinoESP32 2.X Core. v1.2.0 is only for ArduinoESP32 v3.X Core, however it does not work properly on bpad_proto1_board . Can be safely upgraded to v1.1.16 from the Arduino Libraries Manager.
lvgl
lvgl could be optimized a bit more, since it takes the longest to compile. Perhaps some unused UI features can be disabled? I have not tested newer version as lvgl version may be dependant on lovyanGFX?
bpad_proto1_lvgl
This is a experiment I'm trying to "lighten" the last working version (that was given to me through the private repo) so I can have two versions of the lvgl library installed without conflicting with my existing libraries and code. TO BE UPDATED
Beta Was this translation helpful? Give feedback.
All reactions