Open PSLLSP opened 5 months ago
Hello hello, would you share pictures of your ESPDuinos front and backside and also the pinout that you use? Maybe it is similar to the one that I have, so I can give it a try as well?
Boris
I have this board (source AE):
My board doesn't have capacitor close to UART; maybe it has different UART chip (but with compatible pinout). Both boards do not use crystal oscillator, it is missing on the board...
My ESPDUIONO-32:
I believe this is the same board, just another clone from other manufacturer... Well, it is not the same, PCB differs in layout of crystal oscillator (close to UART, only pads).
I tried to fix the issue by adding 10k pull up resistor between 3.3V and GPIO0. At first I thought that the issue was fixed but after several test I do not think it was fixed, maybe it is better. Board still enters "not mining" state, it could be randomly when it is powered from USB connector.
This is the picture of board patched with 10k pull up resistor:
Hello
I have tested with my board which is labeled as ESP32 D1 R32. I have similar issue. It works perfectly fine and is connected to a 5V power supply only. No serial connection. Sometimes after reset it doesn't instantly starts mining. But later, after around ten minutes it starts mining, so I'm not sure if this is really a hardware issue.
I flashed the board with PLATFORMIO using the Nerd Miner V2 master branch and I selected the ESP32 2432S028R as env.
Only one thing I changed compared to the default library setup for ESP32-2432S028 - I have setup IO22 as TFT_CS pin. By default IO15 is setup as TFT_CS pin but for this one is no socket soldered on the board.
Actually I didn't check how this behaves with other boards I have here as I usually didn't really check if they had connection issues before your post.
I will try this as well.
Boris
Btw this is the board I used:
Boris
ESPDUINO-32 with UART HL-340 (1a86:7523), flashed with NerdMiner firmware 1.6.3, flashed with WebFlasher. Configured to mine at vkbit.com mining pool. Device has chip ESP-WROOM-32. Board has no BOOT button (that should be connected to GPIO0, active in LOW). My board us not genuine but some clone from AE; it has label HW-729.
PDF with schematic. Button on the board is connected to GPIO0 and the same GPIO pin can be controlled with signals DTR and RTS. When I press the button, board reboots. Blue LED is connected to GPIO2. Schematic has button EN1 that is connected to EN pin but I think it is missing on the ESPDUINO-32 board.
The schematic is wrong. :-( The schematic is not ESPDUINO-32 but for module with 38-pin header... Schematic miss some other parts that are on ESPDUINO-32 board... I cannot find real schematic fir this board. Web "doit.am" is down and manufactures of board clones do not publish any documentation... :-( Wemos was manufacturing similar board, "Wemos D1 R32", but I cannot find any documentation for it.
This looks like schematics for "WeMos D1 R32":
The button on the ESPDUINO-32 board is connected to RST header and it controls EN pin. It looks like button KEY1, that should control BOOT (GPIO0) is missing... GPIO0 is not on any header pins, GPIO0/BOOT signal is controlled only from UART (signals DRT & RTS) and that is the source of this issue...
I do not see 10k pullup resistor for GPIO0 in "D1 R32" schematics, it could be the issue... UPDATE, resistor added but issue is not fixed, maybe that situation is better but board still sometimes enters "not mining: state after reset...
When ESPDUINO-32 board is power with DC connector (12V DC), it mines, blue LED blinks fast! But there is no BOOT button, so it is difficult to change miner configuration, to enter WiFi configuration mode... Voltage at GPIO0 pin is in this state 3.84V.
When ESPDUINO-32 is connected to USB charger, I measure about 4V at pin GPIO0; it doesn't enter mining state. When it is connected to PC and serial terminal is active, GPIO0 has voltage about 3.2V and it mines at full speed... I can close serial terminal and miner still runs at full speed but GPIO0 has voltage 0V in this case... When I reset it, GPIO0 is set to 4V and miner doesn't start to mine.
When it is connected to PC and serial console is active, ESPDUINO-32 starts to mine, blue LED blinks fast. no issue.
When it is connected to the same PC, with the same USB cable and USB port but serial terminal is not active, it doesn't mine. Blue LED is "ON" after reset and after about 50s it starts to blink slowly, like ESPDUINO-32 is in WiFi configuration mode. But I do not see NerMinerAP network in the air. The same happens when it is connected to USB charger.
This is what I see in serial console (console has to be activated few seconds after reset, when blue LED is ON):
I am not sure if this issue is there from the beginning and I missed it for 2 months or something was broken on the chip. I was doing a cleanup today, I have found that this device doesn't mine on the pool so I started to checking what is wrong. I re-flashed firmware but nothing was changed.
This is what I see when serial terminal is active and I press RESET; no issue, it mines:
I tried and build
duino-coin
miner for ESP32 duino-coin@ESP32 and I see the same issues. When serial console is not active, it doesn't start and doesn't mine. When serial console is active, it mines. When it is powerd from DC connector, it mines. It proves that something is wrong with the hardware (design issue). duino-coin was designed for Arduino IDE and ESPDUINO-32 was designed as "Arduino" board. duino-coin doesn't use WiFi manager, WiFi and all miner details are hardcoded in source code. Something is wrong with ESPDUINO-32 hardware...My board has UART
HL-340
and one explanation could be that original design used different UART (with the same pinout) and that UART had different electrical properties of DTR & RTS signals. I have found that I have two other ESP-WROOM-32 modules those have the same UART (HL-340) and those mine fine; these modules have two buttons and no power DC connector... UART chip is HL-340 (1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter), it is identified in Linux as HL-340; it is handled by "CH341 driver".Other explanation could be that UART is not genuine but it is a "fake" chip, cloned design from other manufacturer; it is a clone but not a perfect clone... Or that UART chip has a defect.
Info about CH340 UART.