#[solved] FLY E3 V3 PRO Bootlooping?

1 messages · Page 1 of 1 (latest)

swift marten
#

Hi, my friends and I are working on a print farm. While setting up our second printer, we encountered some issues.

For the first board, I set up the file structure, which included the DWC components in the WWW directory and the firmware.bin file in the root directory. This setup worked flawlessly on the first attempt without any issues.

However, when setting up the second board, I had my friend replicate the process, and I double-checked his work to ensure that all the necessary files were present. After inserting the SD card and powering on, the board recognizes the firmware.bin file, proceeds to install and then delete it. But, I suspect it's entering a boot loop afterwards. The two LEDs near the fan controllers start blinking every 20 seconds, coinciding with my USB terminal disconnecting. YAT does receive responses, indicating that RRF is installed. However, there's no activity from the WIFI module, and for some reason, the runonce.g file isn't being executed and deleted as it should be.

We're currently running version 3.5.0 RC.3.

hallow terrace
#

Can you zip the contents of the SD card and post them here please. Don't edit any of the files or even open any

#

Then, once you have zipped the files, edit the board.txt file and remove every line except the board = line. Try booting it and it should be stable

peak gazelle
swift marten
#

Thanks for the epic support @hallow terrace

peak gazelle
#

Tried to boot again after adding back the board.txt config but I'm not seeing anything printer related on zenmap.

hallow terrace
#

did it boot with the single board.txt line?

peak gazelle
#

booted but no wifi connection

#

I think

hallow terrace
#

yea, thats expected as it doesn't have any of the wifi lines in and you won't have flashed the module yet

swift marten
#

@peak gazelle use USBC cable and YAT to dump the current status useing M122

#

just to see if alive

peak gazelle
#

Reprap is active after sending that command thru serial, the connection is stable

hallow terrace
#

great. now put this stuff pack in your board.txt and continue ```board = fly_e3_prov3
//WiFi pins
8266wifi.espDataReadyPin = PE_13
8266wifi.TfrReadyPin = PE_14
8266wifi.espResetPin = PE_15

//ESP32 RX/TX Settings
8266wifi.serialRxTxPins = { PD_9, PD_8 }
heat.tempSensePins = { PA_3, PA_4, PA_1 }
stepper.numSmartDrivers = 5```

swift marten
#

Okay... this is WEIRD. M587 followed by the credentials causes the board to crash and terminal disconnect.

#

behavior of the ESP is buggy in general...

hallow terrace
#

Have you flashed the WiFi module?

swift marten
#

yes but we will retry

hallow terrace
#

Did you flash the correct WiFi firmware?

swift marten
#

now it is getting stuck trying to connect when we run M997 S1

#

instalation failed due to comm write error

hallow terrace
#

Send M552 S0 and then M997 S1

swift marten
#

yup we did just that

#

Could be a hardware problem. I should check if anyone knocked any resistors off or something dumb while installing it. next time I'm there

hallow terrace
#

Post the output of M122 P200

subtle panther
#

=== Diagnostics ===<LF>RepRapFirmware for STM32F4 based Boards (fly_e3_prov3) version 3.5.0-rc.3+101 running on STM32F4 at 168Mhz<LF>Bootloader: Unknown<LF><LF>== Supported boards ==<LF>Board 0.0: generic iomode 254 Signatures:<LF>Board 1.0: biquskrpro_1.1 iomode 0 Signatures: 0x768a39d6 0x50da391 0xa79a1917<LF>Board 2.0: biqugtr_1.0 iomode 1 Signatures: 0x94a2cc03<LF>Board 3.0: fly_e3_pro iomode 2 Signatures: 0xd0c680ae<LF>Board 4.0: fly_e3_prov3 iomode 2 Signatures: 0xd0c680ae<LF>Board 5.0: fly_f407zg iomode 2 Signatures: 0x8a5f5551 0xd0c680ae<LF>Board 6.0: fly_e3 iomode 2 Signatures: 0xd0c680ae 0xfd2146b0<LF>Board 7.0: fly_e3_v2 iomode 2 Signatures: 0xd0c680ae<LF>Board 8.0: fly_cdyv2 iomode 2 Signatures: 0x8a5f5551 0xd0c680ae<LF>Board 8.1: fly_cdyv3 iomode 2 Signatures: 0x8a5f5551 0xd0c680ae<LF>Board 9.0: fly_super8 iomode 2 Signatures: 0x8a5f5551 0xd0c680ae<LF>Board 10.0: biquskr_rrf_e3_1.1 iomode 2 Signatures: 0x94a2cc03 0xb173b733<LF>Board 11.0: biquskr_2 iomode 2 Signatures: 0xb75b00a7 0x35f4602c<LF>Board 12.0: biqoctopus_1.1 iomod[Warning: Maximal number of characters per line exceeded! Check the line break settings in [Terminal > Settings... > Text...] or increase the limit in [Terminal > Settings... > Advanced...].]

hallow terrace
#

You'll have to change the YAT settings so get the full output

subtle panther
#

got ya my b

hallow terrace
#

It appears to be detected correctly and has the right pins set

#

Can you post the full output of you send M997 S1? How are you powering the board?

peak gazelle
#

24v power supply, came with the ender its being used on

slender gullBOT
#

GG @peak gazelle, you just advanced to level 1!

swift marten
#

Power inputs for heater are 16 AWG with a thinner wire daisy chained to the MCU power input.

swift marten
#

I'll take a look at it to make sure ther are no damaged traces etc and get back to this later

subtle panther
#

<LF>T:21.1 /0.0 T0:21.1 /0.0 B:20.6 /0.0<LF>Trying to connect at 230400 baud: failed<LF>Trying to connect at 115200 baud: failed<LF>Trying to connect at 74880 baud: failed<LF>Trying to connect at 9600 baud: failed<LF>E
rror: Installation failed due to comm write error<LF>ok

peak gazelle
#

response from m997 s1

swift marten
slender gullBOT
#

GG @swift marten, you just advanced to level 4!

peak gazelle
swift marten
#

Checked the front and back for damage or bad solder, checked connections. Put this on the SD card and powered it up.

#

The bottom two LEDs turn off for a second every 20-30 seconds

swift marten
#

Still unable to flash wifi firmware through M997 S1 but I am able to disable it through M552 S0

#

This looks like it might be a problem…

swift marten
#

We will try this

#

Didn't fix it. Ill reflow the other sides just in case

swift marten
#

@hallow terrace got it working!! There was also a resistor next to it that was possibly soldered badly.

swift marten
#

Might want to forward this to mellow. Seems like the ESP32 was not flat against the main board