c3 super mini adaption for version 2 #190
Replies: 13 comments 17 replies
-
|
On the esp32 c3 mini from wemos the LED is tied to PIN 7 so thats where the conflict comes from. If you board uses a different GPIO then the led can be used but that would require a specialized target to be added to support both boards. |
Beta Was this translation helpful? Give feedback.
-
|
what is the board defintion you are using in arduino ? |
Beta Was this translation helpful? Give feedback.
-
|
hi |
Beta Was this translation helpful? Give feedback.
-
|
Doesent really help, do you have a link to the manufacturer? |
Beta Was this translation helpful? Give feedback.
-
|
this is the link to the item I am using, there are a lot of these devices on aliexpress, have you never seen them before, they are very small and compact. |
Beta Was this translation helpful? Give feedback.
-
|
This board is not yet supported in the arduino for esp32. Its on the todo-list which means it will be included in arduino 3.x which gravitymon don't use yet. So we just have to wait and see when this board is supported on how to proceed. |
Beta Was this translation helpful? Give feedback.
-
|
This surprises me as it is just the basic esp32C3 chip on a small form factor board there is very little added to it, as far as i can make out the only real difference is that the rgb LED is replaced with a single blue led. i would expect the device to work exactly as the other board with the exception of the LED. my build so far is working fine with the exception of the LED. |
Beta Was this translation helpful? Give feedback.
-
|
Well, it there are changes then there needs to be a separate board definition file, if there is a similar board definition then most of the features will work. In your case everything expect the led since the pin for controlling that is different. It's possible to patch the framework if one creates a board definition. |
Beta Was this translation helpful? Give feedback.
-
|
that is what I thought, I shall see what I can do, I was just unsure if I would be conflicting with something else. |
Beta Was this translation helpful? Give feedback.
-
|
You can start with changing the LED_PIN in the arduino_pins.h for your board, should be in the framework_dir / variants / board_name / pins_arduino.h. I've just added a script in the dev branch that patches the definition for the s3 mini since that config is wrong and they only fixed that in 3.x |
Beta Was this translation helpful? Give feedback.
-
|
@mp-se: I've done a port to the Dev-KIT C V4 via your defines. Do you want to merge this port in your release? It's basically a Floaty, so no DS implemented. But maybe interesting for others or @dtashmore547 |
Beta Was this translation helpful? Give feedback.
-
|
The dev boards are not really useful for doing a build. I dont want to merge anything into the main project unless its possible to build a compete working device from it. |
Beta Was this translation helpful? Give feedback.
-
|
well, with the gyro, you get a working device. But understood, you don't want the board in main |
Beta Was this translation helpful? Give feedback.
-
|
Thats not what i wrote, ill be happy to add it if there is a tested and verified device that can be supported. If you have build instructions and can show a working hardware setup i can add it to main. |
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
I still have to get back to my c3 build, I was struggling to get the LED to work (just lack of knowledge) it is a blue LED and it is supposed to be on the 8 pin of the super mini module, i just need to work out how to get it defined correctly in your code. everything else is working so far but I miss the LED indication for when it is in configuration mode. I hope to get back to it soon and get my device complete with dedicated circuit board and onboard wireless charging circuit in a finalised condition, if i succeed i will contact you, so far it works with no LED indicator.
regards and thanks for your amazing work.
On 26 December 2024 23:37:18 GMT+02:00, Magnus ***@***.***> wrote:
Thats not what i wrote, ill be happy to add it if there is a tested and verified device that can be supported. If you have build instructions and can show a working hardware setup i can add it to main.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
what is the board definition you are using ? I can have a look at how its declaration. |
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
I found a board which was similar on the web but i couldn't get it to compile when i defined it.
the board only had esp32c3 super mini on it, was cheap on aliexpress, looked the ideal size to fit into the housings available, definitely fits better than the regular board into the rapt pill housings that i am using.
i am busy making my board available on pcbway, it's not perfect but works (switching from protel to kicad wasn't easy for me after 15 years working with protel until i retired) the component footprint for the super mini is .5mm too wide and i forgot to make the holes larger so the pins don't fit in, to compensate i stuck the device down with a 3m double sided pad and wired the connections which worked fine. if i can get it working 100 percent i can update the pcb. the operation is good so far but i still have to get the balancing done in the rapt pill housing, the wireless charging is working well, it is very useful with the rapt pill housing as that is hard to open and close with the double o-ring housing.
in the info i can find about it says the led of which there are two, 1 on the supply which i crippled as it would only be a battery drain, the other on pin 8 is a blue led and i feel it is the only thing holding me back. hope I haven't gone on too much i just feel it may be a useful addition to your stable.
regards
Dave
On 27 December 2024 09:58:58 GMT+02:00, Magnus ***@***.***> wrote:
what is the board definition you are using ? I can have a look at how its declaration.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
It looks like this board does not have the RBG led that the standard C3 has so that might be the issue. My framework assumes that a C3 board uses the RBG led. But this is something that can be fixed quite easily. This part is in my common espframework project in the led.cpp/hpp. just remove the defines for the C3 so it does not use the neopixelWrite(...) method and it should work. I can add an option to disable the RBG code in the framework. The easy way is to download the source and but that under lib/espfwk and then remove the dependecy from the platformio.ini file. That way you should be able to get past that step. |
Beta Was this translation helpful? Give feedback.
-
|
I just recalled that I had issues with the C3 mini board and the LED. On that board the LED was also the pin that was connected to the gyro so I had to disable the use of the LED on that board. You can check if thats the case for your board as well. |
Beta Was this translation helpful? Give feedback.
-
|
I have updated my espframework so it checks if the board has RGB led or not. You can also disable the led function if needed. Gravitymon is also updated (dev branch) to use the latest version and I have updated most of the dependant libraries to the latest versions. |
Beta Was this translation helpful? Give feedback.
-
|
that's very helpful thanks
DTAshmore
…On Sat, 28 Dec 2024, 17:24 Magnus, ***@***.***> wrote:
I have updated my espframework so it checks if the board has RGB led or
not. You can also disable the led function if needed. Gravitymon is also
updated to use the latest version and I have updated most of the dependant
libraries to the latest versions.
—
Reply to this email directly, view it on GitHub
<#190 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMZXKJ6U7WB4QJWK6GN3X32H27DBAVCNFSM6AAAAABNSEEJZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRYGU2DMMY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
finally got back to my C3 build, i can confirm that unlike the C3 D1 mini which has the RGB led on pin 7, my C3 super mini board has a single blue led on pin 8, i have tested the operation of this led and it is fine, if i enable the led function in the platform.ini file the gyro creases to work, i tried to define the led_builtin to pin 8 but this doesn't work, i am unsure how to proceed. everything else is working great on my board but i would still like to get the led working, i am not sure how to patch the esp framework.
regards
Dave
On 28 December 2024 17:22:39 GMT+02:00, Magnus ***@***.***> wrote:
I just recalled that I had issues with the C3 mini board and the LED. On that board the LED was also the pin that was connected to the gyro so I had to disable the use of the LED on that board. You can check if thats the case for your board as well.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
You cannot set the LED_PIN in your project this needs to be set in Arduino board configuration, typically the pins_arduino.h file for that board. You only set the board type in platformio.ini which then defines the pins. If you board is not part of the supported board lists you need to create those defintions yourself in a fork of the arduino framework. An simpler option is to use one of the board defintions and "patch" the pins_arduino.h before a build. I have done that for the s3 board since the defines for the RGB was faulty. See; script/patch_arduino.py for an example. |
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
that clarifies a lot for me, i found this page on Google which i shall try.
<https://sigmdel.ca/michel/ha/esp8266/super_mini_esp32c3_en.html>
looks promising
On 1 January 2025 13:53:19 GMT+02:00, Magnus ***@***.***> wrote:
You cannot set the LED_PIN in your project this needs to be set in Arduino board configuration, typically the pins_arduino.h file for that board. You only set the board type in platformio.ini which then defines the pins. If you board is not part of the supported board lists you need to create those defintions yourself in a fork of the arduino framework.
An simpler option is to use one of the board defintions and "patch" the pins_arduino.h before a build. I have done that for the s3 board since the defines for the RGB was faulty.
See; script/patch_arduino.py for an example.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
i have success with those instructions, downloaded the 2 files and placed as instructed, didn't work so copied the pins_arduino to the same directory as the esp32-hal-gpio.h and the esp32c3 board compiled, removed the -D ESPFWK_DISABLE_LED flag and the led is flashing.
thanks for your help, no idea how this can be incorporated into your code but i will help where i can.
1 possible problem i noticed it's that when i first logged onto the configuration page there was no gyro detected, i unplugged and plugged back into the usb and it came right, is this a possible problem?
Dave
On 1 January 2025 13:53:19 GMT+02:00, Magnus ***@***.***> wrote:
You cannot set the LED_PIN in your project this needs to be set in Arduino board configuration, typically the pins_arduino.h file for that board. You only set the board type in platformio.ini which then defines the pins. If you board is not part of the supported board lists you need to create those defintions yourself in a fork of the arduino framework.
An simpler option is to use one of the board defintions and "patch" the pins_arduino.h before a build. I have done that for the s3 board since the defines for the RGB was faulty.
See; script/patch_arduino.py for an example.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
Missing gyro is some bug in the i2c driver or hardware after flashing, require a reboot to work properly. |
Beta Was this translation helpful? Give feedback.
-
|
hi Magnus
i have been very happy with the results of my changes to get my espc3 super-mini working, should i pass on my changes to you or post them on the gravitymon forum post? so far i have a board on pcbway which is a little imperfect but completely useable, i intend to update it in time. it is possible to stick the board onto the standard ispindel board with an M3 double sided pad and fly wire it as it is such a small board. i can send the 2 files with instructions along with the small changes to the platform.ini file if you wish.
regards
Dave
On 1 January 2025 17:28:17 GMT+02:00, ***@***.*** wrote:
hi Magnus
i have success with those instructions, downloaded the 2 files and placed as instructed, didn't work so copied the pins_arduino to the same directory as the esp32-hal-gpio.h and the esp32c3 board compiled, removed the -D ESPFWK_DISABLE_LED flag and the led is flashing.
thanks for your help, no idea how this can be incorporated into your code but i will help where i can.
1 possible problem i noticed it's that when i first logged onto the configuration page there was no gyro detected, i unplugged and plugged back into the usb and it came right, is this a possible problem?
Dave
On 1 January 2025 13:53:19 GMT+02:00, Magnus ***@***.***> wrote:
>You cannot set the LED_PIN in your project this needs to be set in Arduino board configuration, typically the pins_arduino.h file for that board. You only set the board type in platformio.ini which then defines the pins. If you board is not part of the supported board lists you need to create those defintions yourself in a fork of the arduino framework.
>
>An simpler option is to use one of the board defintions and "patch" the pins_arduino.h before a build. I have done that for the s3 board since the defines for the RGB was faulty.
>
>See; script/patch_arduino.py for an example.
>
>--
>Reply to this email directly or view it on GitHub:
>#190 (reply in thread)
>You are receiving this because you were mentioned.
>
>Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
Please open a pull request with the changes in the code and documentation. Please publish your hardware releated documentation and pcb information on a separate site/github repository which can be linked from the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
ok Magnus
i will try, not done it before but always a first time, not too many changes as the files take care of most differences. hope the is no way i can mess up.
regards
Dave
On 7 January 2025 19:07:00 GMT+02:00, Magnus ***@***.***> wrote:
Please open a pull request with the changes in the code and documentation. Please publish your hardware releated documentation and pcb information on a separate site/github repository which can be linked from the documentation.
--
Reply to this email directly or view it on GitHub:
#190 (reply in thread)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
|
Beta Was this translation helpful? Give feedback.
-
|
I will validate the changes before I merge it anyway. I suggest you create a separate branch for the pull request since all changes you do there will be reflected in the pull request. This way you can do changes if there is a need and update the PR |
Beta Was this translation helpful? Give feedback.
-
I have updated my super mini boards to the current dev version and everything is working fine, I still have a desire to see the led in operation as it gives a useful indication of the state of the device.
I am lost as to why the led should interfere with the gyro as I have the gyro on gpio6 and gpio7 whereas the blue on-board LED is on gpio8. I would love to see the LED operating the same as the on-board LED of the esp8266 mini. is this possible? could I define the super mini as a separate device place this definition in all the places where the esp32c3 definition is used except the led.hpp and led.cpp and place the gpio8 as LED_INBUILT in the main.hpp folder or would that cause conflicts?
Beta Was this translation helpful? Give feedback.
All reactions