09/08/2020 at 16:08 •
I recently got a new PCB revision and the footprint appears to be correct, as I can now flash the ESP32
However when the firmware runs, I get the following messages repeated through the USB serial terminal (meaning the chip keeps resetting as far as I understand):
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff0030,len:4 load:0x0034ffff,len:455360511 ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff0030,len:4 load:0x0034ffff,len:455360511 ets Jun 8 2016 00:22:57
I'm not sure if this a software or hardware issue at the moment. Any pointers would be most appreciated!
I seem to be able to write and read from the flash ok from what I can tell.
06/30/2020 at 12:50 •
Whilst I am working on re-designing the PCB, to use the correct esp32-d0wd footprint, I am also going to investigate making use of TensorFlow via Python, to recognise different acoustic events in a house.
To do this I will record various sounds in a house using a microphone and a laptop, I will then attempt to classify these events using TensorFlow. I was planning on looking into using a convolutional neural network to achieve this.
Some of the acoustic events I will attempt to detect, include:
- Door opening
- Tap running
- Light / mains switch being turned on/off
- Smoke alarm
- Gas hobs on oven being turned on
- Phone ringing
- Microwave oven / standard oven beep
- Kettle finished boiling
- Fridge turning on
- Toaster popping
I am also curious if an end user could train the system to detect new events by allowing the classifier to be updated.
I've just started evaluating the classifier from https://github.com/drscotthawley/panotti/ using sound files for smoke alarms etc. from - https://freesound.org/browse/ . It makes use of TensorFlow for creating the model.
06/24/2020 at 23:28 •
Unfortunately there was a rather big flaw in the current version of the PCB, making the ESP32 non-functional. I had used a footprint for the ESP32-d0wd chip which is incorrect.
I am currently working on redesigning the PCB with a correct footprint.
With the current PCB revision, the USB chip however does appear functional as it is detected by my computer.
The PCB with the footprint flaw is shown below, it was designed using KiCad 5.