Avesom work @Rop .
Still waiting for NTC/RTC time issue... ;-)

@0x1abin The prebuilt firmware doesn't work for me either. I get this:

I (362) heap_init: Initializing. RAM available for dynamic allocation:
I (369) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (375) heap_init: At 3FFB9E48 len 000261B8 (152 KiB): DRAM
I (381) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (387) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (394) heap_init: At 400907AC len 0000F854 (62 KiB): IRAM
I (400) cpu_start: Pro cpu start user code
I (194) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
E (306) camera_demo: Camera probe failed with error 0x20001

Faulty device?

Hi all,

Thank you for your comments and advise.

My M5Stack work fine too after update library by 0x1abin's advise.

The solution is much easyer:

dacWrite (25,0);

@suremicro 在 Custom Prototype Board 中说：

Yes, if you head over to https://easyeda.com/zazarltd the design is there which you can use to get your own boards made. I used JLCPCB.

Haven't used JLCPCB, I've used Seeedstudio Fusion service https://www.seeedstudio.com/fusion_pcb.html a few times. They are especially good if you need several of the same board as they send 10 copies

another user reported maybe same problem in espressif github.

https://github.com/espressif/arduino-esp32/issues/1726

@loboris I understand it. Thank you for your reply.

I have been looking a bit closer at this and trying to make sense of it with and I think there is a simple design error but it should still work.

this is the WROVER kit control logic ..

and this is the M5CAMs

so it looks like VT2 is reversed but it should still work regardless, it might be affecting the timing perhaps ?

Using platformio with no mods and the WROVER kit board selected a close look at the reset timing shows that the EN line is always taken high (by about 500nS) after GPIO0 is also taken high, hence it never enters boot mode. I think I can get around it by hacking the esptool.py .. but its late now, 4am, so it can wait till tomorrow.

a failed program attempt ..

and a close up of one of the edges shows GPIO0 always going high about 500nS-1uS before EN goes high.

@ajb2k3 Yes, but I am (among other things) specifically looking for schematics and documentation to the FACES keyboards and bottom plate.

@Teresa No I bought one from Banggood and the other from Amazon. I think the problems are all to do with the connectors to the back panel. I have found that applying pressure to the back has gradually allowed the +5V to rise to its proper level, as if the battery is charging. I shall see if the other one has the same problem.

user this template:
https://github.com/m5stack/M5Stack-platformio

Thank you for you help,

now I solved the problem with esp32_digital_led_lib library.

Example:
[CODE]
#include "esp32_digital_led_lib.h"

// Enumberation ob LED's
// 9 0
// 8 1
// 7 2
// 6 3
// 5 4

#define LED_PORT 15

strand_t m_sLeds = {.rmtChannel = 0, .gpioNum = 15, .ledType = LED_WS2812B_V3, .brightLimit = 32, .numPixels = 10, .pixels = nullptr, ._stateVars = nullptr};

void Led_Init(void) {
pinMode (LED_PORT, OUTPUT);
digitalWrite (LED_PORT, LOW);

if(digitalLeds_initStrands(&m_sLeds, 1)) { E_TRACE("Can't init LED driver()\n"); } digitalLeds_resetPixels(&m_sLeds); // Set led 7 to red m_sLeds.pixels[7] = pixelFromRGBW(55, 0, 0, 0); digitalLeds_updatePixels(&m_sLeds);

}

[/CODE]

@gadjet OK got it to stop making a continuous beep by adding the M5.update(); in the loop.

Volume still doesn't work though.