Home of the Squeezebox™ & Transporter® network music players.
Page 170 of 174 FirstFirst ... 70120160168169170171172 ... LastLast
Results 1,691 to 1,700 of 1734
  1. #1691
    How did you connect the ESP32 to the DAC?
    https://github.com/sle118/squeezelite-esp32#spdif

    I approximated the circuit with what I had.

  2. #1692
    Senior Member
    Join Date
    Jul 2017
    Posts
    164
    Quote Originally Posted by Syco54645 View Post
    I tried multiple ways, including the raspiaudio.github.io site.
    This also happens when you use the ESP32 Download Tool?

  3. #1693
    Junior Member
    Join Date
    Sep 2022
    Posts
    21
    Quote Originally Posted by mboxler View Post
    This also happens when you use the ESP32 Download Tool?
    So don't edit your posts on mobile. It immediately deleted them.

    Anyway I get the same thing using the flash tool. Esptool (the python package) does the same thing as well. Best I can tell from Google is the module is bad from a shoddy soldering job. I have a replacement coming so will see if that one works better. I also ordered 3 if the modules in the first post but those are coming from China.
    Last edited by Syco54645; 2022-10-02 at 16:15.

  4. #1694
    Junior Member
    Join Date
    Sep 2022
    Posts
    21
    Well more or less the same thing with the replacement. Partition 1 is invalid. I guess I will wait for the ones from Aliexpress, probably better anyway. They are a smaller form factor.
    Last edited by Syco54645; 2022-10-03 at 16:16.

  5. #1695
    Junior Member
    Join Date
    Mar 2019
    Posts
    14
    Quote Originally Posted by Syco54645 View Post
    Well I decided to try to set this up on my esp32 wrover and am having issues. I tried multiple ways, including the raspiaudio.github.io site. It seems that when I flash this device with the squeezelite-esp32 it is causing boot issues. I pulled the log from the raspiaudio site (serial terminal works as well) and see the partitions are somehow messed up. I dropped the log on pastebin. https://pastebin.com/G808Xw9A

    Below is the error that I am seeing but I am not really sure how to proceed, I am searching the web atm but thought someone here may know. Thank you.

    edit: this is the module that i purchased. https://smile.amazon.com/MELIFE-ESP3...s%2C195&sr=8-5

    Code:
    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:0x3fff0018,len:4
    load:0x3fff001c,len:6948
    load:0x40078000,len:13772
    load:0x40080400,len:4532
    entry 0x400806a0
    I (63) boot: Chip Revision: 1
    I (33) boot: ESP-IDF v4.0.2-206-g5630b17e1 2nd stage bootloader
    I (33) boot: compile time 07:30:49
    I (36) boot: Enabling RNG early entropy source...
    I (39) qio_mode: Enabling default flash chip QIO
    E (44) qio_mode: Failed to set QIE bit, not enabling QIO mode
    I (50) boot: SPI Speed      : 80MHz
    I (55) boot: SPI Mode       : DIO
    I (59) boot: SPI Flash Size : 4MB
    E (63) flash_parts: partition 0 invalid magic number 0x102a
    E (69) boot: Failed to verify partition table
    E (74) boot: load partition table error!
    ets Jun  8 2016 00:22:57
    I have a module that looks very similar to this, although the vendor was different. Although the picture shows a WROVER-E chip, mine was a plain WROVER. The WROVER brings out the pins that internally connect to the flash, and those are connected all the way to the bottom few pins on either side of the USB connector. I found that having *anything* connected to those pins (just plugged into a breadboard in my case) was enough to cause errors accessing the flash, often meaning that squeezelite firmware wouldn't boot.

    Could that be your issue? Note that the WROVER-E doesn't expose the flash connections outside the chip, so if you do have a WROVER-E it can't be your issue.

  6. #1696
    Junior Member
    Join Date
    Sep 2022
    Posts
    21
    Quote Originally Posted by edw5 View Post
    I have a module that looks very similar to this, although the vendor was different. Although the picture shows a WROVER-E chip, mine was a plain WROVER. The WROVER brings out the pins that internally connect to the flash, and those are connected all the way to the bottom few pins on either side of the USB connector. I found that having *anything* connected to those pins (just plugged into a breadboard in my case) was enough to cause errors accessing the flash, often meaning that squeezelite firmware wouldn't boot.

    Could that be your issue? Note that the WROVER-E doesn't expose the flash connections outside the chip, so if you do have a WROVER-E it can't be your issue.
    Thanks for the suggestion but I did not have the module plugged into anything. My modules have not even shipped yet from Aliexpress so it is going to be a while. Not really seeing any on amazon to get quickly.

  7. #1697
    Member cOOLio's Avatar
    Join Date
    Sep 2022
    Location
    Germany
    Posts
    36
    Quote Originally Posted by Syco54645 View Post
    Well I decided to try to set this up on my esp32 wrover and am having issues. I tried multiple ways, including the raspiaudio.github.io site. It seems that when I flash this device with the squeezelite-esp32 it is causing boot issues. I pulled the log from the raspiaudio site (serial terminal works as well) and see the partitions are somehow messed up. I dropped the log on pastebin. https://pastebin.com/G808Xw9A

    Below is the error that I am seeing but I am not really sure how to proceed, I am searching the web atm but thought someone here may know. Thank you.

    edit: this is the module that i purchased. https://smile.amazon.com/MELIFE-ESP3...s%2C195&sr=8-5

    Code:
    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:0x3fff0018,len:4
    load:0x3fff001c,len:6948
    load:0x40078000,len:13772
    load:0x40080400,len:4532
    entry 0x400806a0
    I (63) boot: Chip Revision: 1
    I (33) boot: ESP-IDF v4.0.2-206-g5630b17e1 2nd stage bootloader
    I (33) boot: compile time 07:30:49
    I (36) boot: Enabling RNG early entropy source...
    I (39) qio_mode: Enabling default flash chip QIO
    E (44) qio_mode: Failed to set QIE bit, not enabling QIO mode
    I (50) boot: SPI Speed      : 80MHz
    I (55) boot: SPI Mode       : DIO
    I (59) boot: SPI Flash Size : 4MB
    E (63) flash_parts: partition 0 invalid magic number 0x102a
    E (69) boot: Failed to verify partition table
    E (74) boot: load partition table error!
    ets Jun  8 2016 00:22:57
    I have exactly the same/ or similar dev kit with Espressiff WROVER E chip. Added right now more error logs to the ticket. Maybe this will help the DEVs to find the issue with the latest WROVER E chip not booting up
    https://github.com/sle118/squeezelite-esp32/issues/182
    Last edited by cOOLio; 2022-10-07 at 04:57.
    SmarthomeServer:ioBroker(HABPanel>vis)+LMS8.2@Raspi4-4GB-256GB-SSD|NAS4TB@Fritzbox7590+2*AVM1750E(Mesh)
    Control:3*FireHD10@HABPanel
    AV:PhilipsAmbilight+HUE@ATV(ChC&SpC)|NividiaShield(Ch C&SpC)|FireTV4kMax(SpC)@2*Sony
    Teufel7.2@DenonAVR(HEOS)|5*pCP@Raspi3(BeringerUCA2 02|2*PiFiDAC2.0|USBAudio)
    SqueezeliteESP32@3*ESP32-A1S+MUSE-PROTO+3*MAKT32+MAKT32CL+ESP32-ADF+1*ESP-Muse-Mn-Cast


    https://SqueezeESP32.blogspot.com

  8. #1698
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    546
    Quote Originally Posted by cOOLio View Post
    I have exactly the same/ or similar dev kit with Espressiff WROVER E chip. Added right now more error logs to the ticket. Maybe this will help the DEVs to find the issue with the latest WROVER E chip not booting up
    https://github.com/sle118/squeezelite-esp32/issues/182
    This board is using version D0WD-V3 of the chip, and it seems to be affected by an issue with flash memory.
    https://github.com/espressif/esp-idf/issues/7994

    Let's continue this discussion on github issue 182
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  9. #1699
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    546

    Web installer

    Over the past couple of weeks, I concentrated on revamping the build system, paving the way to a full integration with the esp-web-tools which allows flashing a complete set of binaires from the web browser.

    The current state of the installer is rough, but it's up to date with the latest builds and fresh easy to use.

    https://sle118.github.io/squeezelite-esp32-installer/
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  10. #1700
    Junior Member
    Join Date
    Mar 2019
    Posts
    14
    Quote Originally Posted by sle118 View Post
    This board is using version D0WD-V3 of the chip, and it seems to be affected by an issue with flash memory.
    https://github.com/espressif/esp-idf/issues/7994

    Let's continue this discussion on github issue 182
    Coolio's board may be using a WROVER-E, but from the 2016 bootloader date in his logs I think the original poster has a WROVER, just like I have. I don't have anything with a WROVER-E, but the logs in the Espressif issue suggest that has a bootloader dated 2019. My problem was definitely noise on the pins that interface to the flash, and removing the noise (I broke the pins off with pliers) made the problem go away.

    FWIW, I only had problems with squeezelite, I think because it runs the chip at 240MHz. All the Espressif samples I tried run at 160MHz, and they were all okay.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •