fruchti/colorchord
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
colorchord/embedded8266
History
bbkiwi 2539f021dc Fix ws2812_i2s.c to include ccconfig.h and explicitly invert literals to prevent warning
2019-05-29 17:05:43 +12:00
..
esp82xx@a08b47184b stab at the esp8266 port 2018-11-30 07:01:36 -05:00
hardware move readme 2016-08-13 14:14:27 -04:00
user Fix ws2812_i2s.c to include ccconfig.h and explicitly invert literals to prevent warning 2019-05-29 17:05:43 +12:00
web update experimental branch 2018-11-18 15:27:29 -05:00
ccconfig.h A squashed, should only change a few lines and no mucking about with submodules 2019-05-23 14:07:47 +12:00
image.elf-0x00000.bin stab at the esp8266 port 2018-11-30 07:01:36 -05:00
LICENSE Modularize esp8266 components 2016-08-19 00:13:41 +02:00
Makefile update rev 2016-08-26 23:50:57 -04:00
README.md Update README.md 2019-02-06 23:08:41 -08:00
user.cfg stab at the esp8266 port 2018-11-30 07:01:36 -05:00

README.md

#ESP8266 ColorChord

WARNING THIS IS UNDER CONSTRUCTION

(based off of ESP8266 I2S WS2812 Driver)

This project is based off of the I2S interface for the mp3 player found here: https://github.com/espressif/esp8266_mp3_decoder/

If you want more information about the build environment, etc. You should check out the regular WS2812 driver, found here: https://github.com/cnlohr/esp8266ws2812i2s

WARNING: This subproject is very jankey! It's about stable, but I don't think it's quite there yet.

Hardware Connection

Unfortunately the I2S Out (WS2812 in) pin is the same as RX1 (pin 25), which means if you are programming via the UART, it'll need to be unplugged any time you're testing. The positive side of this is that it is a pin that is exposed on most ESP8266 breakout boards.

The audio data is taken from TOUT, but must be kept between 0 and 1V.

An option that has been thurroughly tested is for use with the 2019 MAGFest Swadge. https://github.com/cnlohr/swadge2019

Audio portion: Audio portion of schematic

Notes

./makeconf.inc has a few variables that Make uses for building and flashing the firmware. Most notably the location of the toolchain for the esp8266/85 on your system. You should edit them according to your preferences or better add export ESP_ROOT='/path/to/the/esp-open-sdk' to your bashrc.

If you have problems with burning the firmware or transfering page data over network (make netburn or make netweb), you should try uncommenting

OPTS += -DVERIFY_FLASH_WRITE

in makeconf.inc. This way the esp checks if the flash is written correctly. Especially with some ESP-01 modules there has been a problem with the flash not being written correctly.