Regarding esp32s3 and ProffieOS

I saw in the ProffieOS logs that there’s experimental support for esp32s3. Has anyone tested it?

I think I’m probably the only one have tested it.
It’s been a while though.
I have a breadboard setup with an ESP32-S3, motion chip, amplifier, sd card and some neopixels for testing. However, none of it was very good performance-wise. The sound was glitchy, the neopixels were glitchy and the sd card was slow. So I gave up on it until things improve.

It’s entirely possible that things have improved. I have not tested it since then, and that was a while ago.

1 Like

If I plan to try using esp32s3 with ProffieOS, do you have any suggestions? For example, which module should I choose—do I need the esp32s3 N16R8, or is N8R2 sufficient? Also, which version of ProffieOS should I use? Are there any specific parts of the original ProffieOS code that need attention or modifications?(:з」∠)

1 Like

What do you mean by “use” here?
Do you mean try it out and experiment with it, maybe try to improve it so that it actually works?
Or do you mean “build a saber with an esp32s3 in it”?
Or something completely different?

I think the N8R2 would be sufficient. but I would still get N16R8 if possible, because it’s a new thing and it’s difficult to know what you’ll need. Maybe we’ll end up storing fonts in RAM to work around slow SD cards?

I would just use the latest ProffieOS. It should compile for Esp32S3 with the right config file. (Which might not be checked in…) ProffieOS has code for most things it needs already. However, as I said, it doesn’t perform very well. That means that one of two things needs to be done, either…

  1. build code in ProffieOS that uses the registers directly instead of the provided abstractions.
  2. fix the abstractions provided by ESP32 so that the perform better

It’s not clear which is better, and it’s possible that (2) has already been done.
The I2S and the WS2811 abstractions are the worst, so fixing those are the most important.

1 Like

I think I roughly understand. Thank you for your explanation. The reason I chose esp32s3 is that I’m in China, so the esp32S3 is relatively cheaper and easier to obtain. PCB fabrication is also simpler here. Additionally, platforms like JLCPCB offer free PCB manufacturing.

The reason behind this is that I previously made a lightsaber using an esp32, but my coding skills are average. The gesture sensing often triggers too easily or is sometimes too difficult to activate… So when I saw that ProffieOS experimentally supports esp32s3, I wanted to give it a try and make a version to see how it works. (Note: This was translated using AI, so the phrasing might seem a bit unusual.)

Please share what you build and such, I would be interested in seeing it.
Also, if you still want to build things using esp32, I may be able to help getting things to work, like I said, I still have my breadboard setup, I could dust that off, try and see if things have improved or not.

Thank you for your help. However, I currently only have one esp32S3 module on hand. I haven’t decided yet whether to design a PCB directly or first buy an esp32s3 development board for testing. Plus, I tend to procrastinate a bit, so I’m not sure when I’ll actually start working on it (:з」∠)