OK, I have been tinkering again. I quite like this board - it is designed to take 12V DC, and drive 10 separate outputs at 12V DC. Intended for the alarm system, but works for lots of other use cases (e.g. nice big 12V LED lamps in my DEFCON light box).

My latest tinkering, apart from ESP32-S3, is to put a WS2812 by each output plug to allow output status to be shown clearly.

I might order some when back from my holiday.

#PCB #ESP32

Fun latest board...

#ESP32 #PCB

Well, that is one of my simpler programming leads 🙂

#ESP32 #PCB

Agon Light, o faixa preta dos 8 bits.

https://retropolis.com.br/2023/08/20/agon-light-o-faixa-preta-dos-8-bits/

#MundoRetro #AgonLight #BASIC #BBCMicro #carto #ESP32 #eZ80 #microSD #MSX #resenha #SBC #usb #VGA #z80

Matter is driving me nuts - even the simplest example seems almost impossible to cut down *NOT* to be driving the physical device, i.e. just the matter side. I already have code for the LEDs which uses a way later and better led_strip drive but cannot use as it clashes with esp-matter having built in use of led_driver somehow. Why would the matter side all have code for talking to the physical devices. Why?

Arggg!

#ESP32

Arrrrrg!

OK I can build the default example light for matter.

So starting from there and adding bits of my own code a bit at a time.

I am using a much later led_strip module. But it clashes. So I removed its led_strip 1.0.0 and all calls to it.

But it still insists on using esp-matter/device_hal/led_driver/ws2812/led_driver.c and moans about a load of stuff.

But I cannot find what tells it to even link in ws2812 or why tsp-matter has that anyway rather than it being in the module.

#ESP32

Arg, example light matter code working, but cannot get the CMake stuff for my own app to build, and one complicated issue after another driving me mad.

I'll get there... But Matter is a pain.

#ESP32

And this is working - this time it was 1.2mm PCB x 2, so 2.4mm, and that fits very well in a USB socket. #ESP32

Neater, no buttons, and only 30x30mm board. Much more readable GPIO numbers. #ESP32

This could be a good sign...
#ESP32

Got these in today - I ordered before I realised the GPIO0(BOOT) and RST(EN) buttons are not actually needed. #ESP32

The new #ESP32 S3 based LED modules work, and the DMA for the RMT means no glitches.

This is annoying - using ESP IDF, changing target from ESP32 to ESP32S3 is zapping my sdkconfig for some reason, and not even pulling in things from sdkconfig.defaults in the process. Little things like CONFIG_FREERTOS_HZ revert to 100 not the 1000 I usually have set, etc. Causing havoc.

This could be a challenge to fix!

Extra fun, only on one of my projects??!!

#ESP #ESP32

Oooh, I like my new test board, especially as the USB JTAG/Serial is working as expected now - reset and flashing just work. Way better. #ESP32 #PCB

JLCPCB finally have the 3D model for the S3. #PCB #ESP32

This fun.

It looks like ESP32-S3 has USB JTAG, on by default, yay.

It even has OpenOCD pre-installed as a tool.

Just sparse on the actual instructions to use it.

What I am trying to do is flash via JTAG (via USB), which I am hoping I can do without having to bugger with GPIO0 first!

#ESP32 #ESP32S3 #JTAG #USB #OPENOCD

So I am a couple of days in to "The S3 ESP32 is the next thing" without having one to play with. Order some boards. Tinkered with foot print a bit. Made some other designs to use it. Read up on usable GPIOs. By the time I have actual boards next week I'll have re-done most of my PCB designs. I really hope I am not disappointed. #ESP32 #PCB

This may be more useful to start with. #PCB #ESP32

OK, let's see if I can make one of these work... #PCB #ESP32

"Olimex ESP32-S3-DevKit-LiPo is a new open-source hardware ESP32-S3 board with 8MB flash, 8MB PSRAM, as well as LiPo battery and JTAG support that can run Linux 6.3, or the more traditional Arduino or MicroPython firmware."

12 Euros ESP32-S3-DevKit-LiPo board runs Linux 6.3 - CNX Software
https://www.cnx-software.com/2023/07/29/esp32-s3-devkit-lipo-board-linux-6-3/

#ESP32