#Can you point me in some direction , as
1 messages ยท Page 1 of 1 (latest)
hi, i'll put it in a thread to save clogging main channel. which board was it that you got ?
I got the ESP32 N8R2 board which suppose to have 2 MB PSRAM.
Now I am not sure, if the seller sent me a worng board. Because I have the number P2N8 on it. I asked the seller but unfortunelty he/she is not replying. So searched the internet and found some more folks with the same number.
do you have a picture or link to the board?
Yes I do.
this is the link I brought it from : https://probots.co.in/esp32-s3-devkitc-1-development-board-wireless-module-wifi-bluetooth.html
and this is the image of the board
https://ibb.co/89B1JFW
try getting logs over serial using the port marked USB
Do you mean using web.esphome.io ?
yyes that should be fine, once the logs page is open. click 'reset device'
ok.. let me try that.
Build:Mar 27 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x400454d5
SPIWP:0xee
mode:QIO, clock div:1
load:0x3fce3808,len:0x1658
ets_loader.c 78
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x10 (RTCWDT_RTC_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:QIO, clock div:1
load:0x3fce3808,len:0x1658
ets_loader.c 78
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x400454d5
SPIWP:0xee
mode:QIO, clock div:1
load:0x3fce3808,len:0x1658
ets_loader.c 78
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
I keep getting this log in a loop.
try changing this to qio
platformio_options:
board_build.flash_mode: dio
I think I found something I dint add to my config.
i dint add exactly this before compiling my last build.
Apparently I pasted this config but dint compile it.
let me try that first.
ok ๐
๐ฅณ
finally after nearly 4 hours its connected.
nightmare!
Indeed ๐.. but finally I moved forward.
I still have to test the wake word .. but can check it tomorrow after doing all the connections.
does it show PSRAM enabled in the purple part of the logs when setting up components?
Just get more information.
What was the platformio_options so important for it.
Let me check that..
On getting the logs , this is what I got
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x1658
load:0x403c9700,len:0xbc0
load:0x403cc700,len:0x2f3c
entry 0x403c9950
I (24) boot: ESP-IDF 4.4.6 2nd stage bootloader
I (25) boot: compile time 20:32:34
I (25) boot: Multicore bootloader
I (27) boot: chip revision: v0.1
I (30) boot.esp32s3: Boot SPI Speed : 80MHz
I (35) boot.esp32s3: SPI Mode : DIO
I (40) boot.esp32s3: SPI Flash Size : 4MB
I (45) boot: Enabling RNG early entropy source...
I (50) boot: Partition Table:
I (54) boot: ## Label Usage Type ST Offset Length
I (61) boot: 0 otadata OTA data 01 00 00009000 00002000
I (68) boot: 1 phy_init RF data 01 01 0000b000 00001000
I (76) boot: 2 app0 OTA app 00 10 00010000 001c0000
I (83) boot: 3 app1 OTA app 00 11 001d0000 001c0000
I (91) boot: 4 nvs WiFi data 01 02 00390000 0006d000
I (98) boot: End of partition table
I (103) esp_image: segment 0: paddr=00010020 vaddr=3c0d0020 size=4aabch (305852) map
I (166) esp_image: segment 1: paddr=0005aae4 vaddr=3fc97160 size=03cfch ( 15612) load
I (169) esp_image: segment 2: paddr=0005e7e8 vaddr=40374000 size=01830h ( 6192) load
I (173) esp_image: segment 3: paddr=00060020 vaddr=42000020 size=c2e54h (798292) map
I (323) esp_image: segment 4: paddr=00122e7c vaddr=40375830 size=11930h ( 71984) load
I (347) boot: Loaded app from partition at offset 0x10000
I (347) boot: Disabling RNG early entropy source...
I (347) cpu_start: Multicore app
I (351) spiram: Found 16MBit SPI RAM device
I (356) spiram: SPI RAM mode: sram 80m
I (360) spiram: PSRAM initialized, cache is in normal (1-core) mode.
I (367) cpu_start: Pro cpu up.
I (371) cpu_start: Starting app cpu, entry point is 0x403764c4
Ohh you mean like this?
I have frankenstien setup right now.. ๐ As I am at my home town.
My HA server is in Germany, but I am accessing it remotely to do all my compilation.
So can't use that over wifi feature.
But I added the server config, but I dont see any logs there.
I mean the webserver config to my yaml code, but I think I loose most of the initial logs before I can access it.
try changing logger to
logger:
hardware_uart: 0
that may give you the esphome logs but you need to connect to usb port not com port
ok.. let me try this.
the labelling on the board is a little back to front from what you would expect
its give me an error for this.
I changed it to
logger:
hardware_uart: UART0
also a side note, in order to get the addressable led to work, if it isnt . then there are 2 tiny pads on the board next to the led that need to be bridged. also the same for 5v output from 5v pin, there is also a pair of pads that have to be bridged if you want 5v output from the pins when connected to usb
The led is working fine..
sorry yes, my bad trying to remember off the top of my head lol
I was able to turn it on and off using the web server page.
So now I am waiting for this to compile.
cool thats good then, i know on other boards of the same design that its needed
yes the compile with micro wake word is quite a long one
Also did you face any problems with flashing the binary using ESPHome from a mac m1 or m2 machine?
I initially could not get it flash the binary. I then searched about why it was not flashing and some mentioned ESP32 S3 have some problems while being flashed from M series mac .
I haven't come across that problem, and haven't got a mac myself so i don't know about that one.
these are the pads if you want 5v out for anything
ohh good to know.
Does this mean when I use the MAX98357A for the audio amplifier, which needs 5v.. I need to connect these pads? or is to provide 5v while using it using the USB port?
yes if you want to connect the max to the 5v pin then you need to join those 2 pads together. otherwise the 5v pin will only operate as an input
Ohh. I was not aware about this too.
Thanks for giving me a heads up.
you're welcome, it caught me out for a while
You defintely saved me some hours of debugging ๐
I got the logs from esphome,
[C][logger:447]: Logger:
[C][logger:448]: Level: DEBUG
[C][logger:449]: Log Baud Rate: 115200
[C][logger:451]: Hardware UART: USB_SERIAL_JTAG
[C][esp32_rmt_led_strip:175]: ESP32 RMT LED Strip:
[C][esp32_rmt_led_strip:176]: Pin: 48
[C][esp32_rmt_led_strip:177]: Channel: 0
[C][esp32_rmt_led_strip:202]: RGB Order: GRB
[C][esp32_rmt_led_strip:203]: Max refresh rate: 0
[C][esp32_rmt_led_strip:204]: Number of LEDs: 1
[C][light:103]: Light 'on board light'
[C][light:105]: Default Transition Length: 1.0s
[C][light:106]: Gamma Correct: 2.80
[C][template.switch:068]: Template Switch 'mute'
[C][template.switch:091]: Restore Mode: always OFF
[C][template.switch:057]: Optimistic: YES
[C][psram:020]: PSRAM:
[C][psram:021]: Available: YES
[C][psram:024]: Size: 2047 KB
[C][restart.button:017]: Restart Button 'Restart'
[C][captive_portal:088]: Captive Portal:
[C][web_server:168]: Web Server:
[C][web_server:169]: Address: esp32-s3-wake-word.local:80
[C][mdns:115]: mDNS:
[C][mdns:116]: Hostname: esp32-s3-wake-word
[C][ota:096]: Over-The-Air Updates:
[C][ota:097]: Address: esp32-s3-wake-word.local:3232
[C][ota:100]: Using Password.
[C][ota:103]: OTA version: 2.
[W][ota:107]: Last Boot was an unhandled reset, will proceed to safe mode in 6 restarts
[C][api:139]: API Server:
[C][api:140]: Address: esp32-s3-wake-word.local:6053
[C][api:142]: Using noise encryption: YES
[C][micro_wake_word:057]: microWakeWord:
[C][micro_wake_word:058]: Wake Word: hey jarvis
[C][micro_wake_word:059]: Probability cutoff: 0.500
[C][micro_wake_word:060]: Sliding window size: 10
brilliant and theres the 2mb PSRAM so all is good ๐
Yes.. Thanks a lot for this.
no problem , happy to help
I still have to check after connecting the microphone and the max if all is working fine.
but will call it a night anc check tomorrow.
But thanks a lot for all the help.
My 4 hours dint go to waste. ๐.
Good outcome atleast.
absolutley ... good luck with the rest of the build. feel free to ping me if you need any info ๐
Sure, Will share my updates on this thread. So other can also use it to create theirs devices.
See you untill next time ๐
Hey @woeful chasm ,
Today I was trying to connect the INMP441 microphone.
This is the last configuration I compiled and added to the ESP32S3 .
https://pastebin.com/GwE6GN34
I also configured a pipeline with whisper and piper. ( no wake word config)
Then connected the ESP32S3 in homeassistant and set the pipeline in it.
I tried testing it, but the micro wake word is not getting picked up by the microphone.
What would be the problem do you think?
I am not getting any logs on the console.
I tried using mute and unmute and these are the logs I got.
Hi , do you have the lr pin on the mic connected to gnd?
yeah , that all looks good and the config. in order for micro wake word to function it doesn't even rely on the pipeline so it should just work. i would check wiring again and test for continuity between the esp and the mic, also check voltage at mic is 3.3v
when you say the wakeword it should register in the ESPHome logs for the device
ok.. let me try.
I had added web_server config to it.. do you think it could cause any problems?
it can cause issues , for troubleshooting i would remove it
what version of ESPHome are you running ?
yes I know there have been some enhancments made in 2024.3.0 but I haven't got around to testing anything on the release yet... i've been stuck on a different project for a couple of weeks. so am falling behind ๐
๐.. Can understand that.
So I tried removing the web_server config.
then also updated esphome to 2024.3 and then in the documentation example.
I saw this .
on_wake_word_detected:
then:
- voice_assistant.start:
wake_word: !lambda return wake_word;
I added that also.. But no luck. ๐
it must be related to the microphone itself i feel.
i'll quickly solder some wires and test it with your config ...see what happens for me
ok. no hurry..
ok done and compiling
๐ค
forgot cant compile from command line with micro ww ... so started again from dash ๐
ohh ok ๐
i could have been a less than 5 minute build lol ... no records broken today
๐ It take a bit of time.. but as long as it works.
ok thats not working for me either, i will have a play now and keep you updated ๐
ok was my error, had wires wrong way ... yes it works..
ohh nice.
so config is deffo ok
i used a slightly different version of s3 n16r8 but still a standard dev ... just because it was the 1 infront of me ... but i can swap it over ๐
and first pin on the right markeed as gnd for ground.
ahh no no..
dont have to take the trouble of doing that.
it works so I have figure out what wrong with my connection or with the microphone.
I think somehting is wrong on my side.
I remeber 2 days back when you had asked me to add the logger for hardware_UART .. I was able to see the purple color log specifying the PSRAM .
Today I dont see the logs anymore.
not even on wireless?
Yes.. not even wireless.
I still have the logger config..
connected to the laptop using USB port and not COM port
thats strange, is it the same if you disconnect everything ? so it's just the bare board
does it give you the initial bootloader whne viweing them over usb ?
swapped to this board and works too
this is the log I get in green
I (174) esp_image: segment 1: paddr=00065b34 vaddr=3fc972ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x420ca7c2
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x1658
load:0x403c9700,len:0xbd4
load:0x403cc700,len:0x3034
entry 0x403c9954
I (24) boot: ESP-IDF 4.4.6 2nd stage bootloader
I (24) boot: compile time 11:06:01
I (25) boot: Multicore bootloader
I (26) boot: chip revision: v0.1
I (30) boot.esp32s3: Boot SPI Speed : 80MHz
I (35) boot.esp32s3: SPI Mode : DIO
I (40) boot.esp32s3: SPI Flash Size : 4MB
I (45) boot: Enabling RNG early entropy source...
I (50) boot: Partition Table:
I (54) boot: ## Label Usage Type ST Offset Length
I (61) boot: 0 otadata OTA data 01 00 00009000 00002000
I (68) boot: 1 phy_init RF data 01 01 0000b000 00001000
I (76) boot: 2 app0 OTA app 00 10 00010000 001c0000
I (83) boot: 3 app1 OTA app 00 11 001d0000 001c0000
I (91) boot: 4 nvs WiFi data 01 02 00390000 0006d000
I (98) boot: End of partition table
I (102) esp_image: segment 0: paddr=00010020 vaddr=3c0d0020 size=55b0ch (350988) map
I (174) esp_image: segment 1: paddr=00065b34 vaddr=3fc97290 size=03d84h ( 15748) load
I (177) esp_image: segment 2: paddr=000698c0 vaddr=40374000 size=06758h ( 26456) load
I (185) esp_image: segment 3: paddr=00070020 vaddr=42000020 size=cc868h (837736) map
I (338) esp_image: segment 4: paddr=0013c890 vaddr=4037a758 size=0cb30h ( 52016) load
I (358) boot: Loaded app from partition at offset 0x10000
I (358) boot: Disabling RNG early entropy source...
I (369) cpu_start: Multicore app
I (369) spiram: Found 16MBit SPI RAM device
I (370) spiram: SPI RAM mode: sram 80m
I (371) spiram: PSRAM initialized, cache is in normal (1-core) mode.
I (582) spiram: SPI SRAM memory test OK
I (591) cpu_start: Pro cpu start user code
I (591) cpu_start: cpu freq: 240000000
I (591) cpu_start: Application information:
I (594) cpu_start: Project name: esp32-s3-wake-word
I (600) cpu_start: App version: 2024.3.0
I (605) cpu_start: Compile time: Mar 21 2024 11:01:53
I (611) cpu_start: ELF file SHA256: c67729182a260af4...
I (617) cpu_start: ESP-IDF: 4.4.6
I (621) cpu_start: Min chip rev: v0.0
I (626) cpu_start: Max chip rev: v0.99
I (631) cpu_start: Chip rev: v0.1
I (636) heap_init: Initializing. RAM available for dynamic allocation:
I (643) heap_init: At 3FC9FE98 len 00049878 (294 KiB): D/IRAM
I (649) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DIRAM
I (656) heap_init: At 600FE000 len 00002000 (8 KiB): RTCRAM
I (662) spiram: Adding pool of 2048K of external SPI memory to heap allocator
I (671) spi_flash: detected chip: generic
I (675) spi_flash: flash io: dio
W (679) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (693) sleep: Configure to isolate all GPIO pins in sleep state
I (699) sleep: Enable automatic switching of GPIO sleep configuration
I (706) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
ok just noticed although it is working that PSRAM isn't enabling as it is set to quad in the config, these boards need octal. whether that will make a difference. you will need to re-flash over serial
also just tested and try getting the logs using com as i think the hardware_uart will enable that port for logs, i just tried and i now get full logs on com labelled port ๐คฆโโ๏ธ
ok . let me try that.
I am now using this site https://esp.huhn.me/ to erase the flash once.
and try again.
ohh so I dont need to change from COM to USB port.
Right now I am trying to reflash the initial config that I shared with you.
then Ill try with octal mode for PSRAM.
The initial purple log is back.
Not yet change the config to use octal .. still on quad.
let me connect the microphone now.
I connected the microphone.. No luck yet.
I see a warning saying "wake word is already running".
let me now try with octal mode.
that warning is fine i get that ๐ did you re-power after connecting the mic?
Yes. I turned it off.. then connected the mic and then commected the power back again..
Hey,
Sorry I had to go out for some work.
I am back now.. I'll try with octal now.
Also just a thing that struct me, octal means 8, and quad means 4, so was this config with 80Mhz wrong?
speed: 80MHz
Would it have been 40Mhz .. Just something I thought while I was out.
i believe that quad & octal are the type of spi connection that the ram chip has to the ESP chip , and the 80mhz is the actual speed of the ram i may be wrong but that is my understanding
This time with the change to "octal" gave me this error
E (370) opi psram: PSRAM ID read error: 0x00000000, PSRAM chip not found or not supported, or wrong PSRAM line mode
E (374) spiram: SPI RAM enabled but initialization failed. Bailing out.
And this in the purple logs
[C][psram:020]: PSRAM:
[C][psram:021]: Available: NO
and with quad did it show as available?
ah yes, sorry my bad again , this is a 2mb PSRAM isn't it ... doh!
Yes it did show up with quad.
No Issues.
Since this config worked with your ESP32 S3 board, then its related to the microphone.
yes, certainly something related to the mic, it's unusual for them to be faulty
Yes. its 2 mb.. so its should be quad .. according to this https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html#ordering-information
Yes.. Usually they are not.
Hey @woeful chasm ,
Some good news.
It works!! ๐
The problem was with the microphone itself. I bought a new one and also found that my jumper cables were too long. (20cm)
I cut it short and used a new microphone and its working all fine.
๐ great news, hope the video does well
Yes ๐ ..Thanks a lot for all the help @woeful chasm .
Hey @woeful chasm ,
I published my video a while ago . Here is the link to it. https://youtu.be/rT_q0g8dtmY
and also a blog post containing all the information: https://smarthomecircle.com/How-to-setup-on-device-wake-word-for-voice-assistant-home-assistant
Hope it helps others too. ๐
hi there, yes... I have watched ๐ and helped a few people that were inspired by your video ... so you're getting some views for sure! good work buddy! .. i will have to take a look at the blog. thanks for the update and the shout out ๐
Actually thanks to you for helping me to get it working. ๐