atomic14 / esp32-laser-show

MIT License
64 stars 18 forks source link

idf version? #2

Open jschoch opened 3 years ago

jschoch commented 3 years ago

having issues with 4.x can you confirm the idf version you are using?

cgreening commented 3 years ago

Let me check to see what happens with the latest version in platformio

cgreening commented 3 years ago

This is the output from platform io when I kick off the build:

Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32doit-devkit-v1.html
PLATFORM: Espressif 32 (3.3.2) > DOIT ESP32 DEVKIT V1
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES: 
 - framework-espidf 3.40300.0 (4.3.0) 
 - tool-cmake 3.16.4 
 - tool-esptoolpy 1.30100.210531 (3.1.0) 
 - tool-ninja 1.9.0 
 - toolchain-esp32ulp 1.22851.191205 (2.28.51) 
 - toolchain-xtensa32 2.80400.210211 (8.4.0)
jschoch commented 3 years ago

thanks!

cgreening commented 2 years ago

I should have checked - is it issues with building or running?

jschoch commented 2 years ago

there seems to be issues with zlib and reading the files, lots of loadprohibeted and abort() errors. Not sure if it is my partitioning, i don't think I changed anything but it was an issue. I tried just the single vader and xwing files but I also had issues.

I could get the spi working by making my own draw2() function and just feeding x/y so that part worked great.

also, I wonder how hot your galvo drivers get. I'm not sure if I am running at the right speed, they are getting pretty hot.