Wt32-eth

[Francesco-Rugg]

Can I test ESPixelStick v4.0-beta4
For WT32-ETH01?

[MartinMueller2003]

that is a supported platform. I found and fixed a crash that is present in b4 so you may want to try the latest build on the google drivr

[Francesco-Rugg]

Ok, thank you. Where I can find the google drive?

[MartinMueller2003]

Here is the latest build. dist.zip | | | | dist.zip | | | On Tuesday, December 13, 2022 at 04:56:13 AM EST, Francesco-Rugg ***@***.***> wrote: Ok, thank you. Where I can find the google drive? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[Francesco-Rugg]

@MartinMueller2003 so is the same dist.zip tant you already sent to me?

[Francesco-Rugg]

Sorry, but I'm a newbie and I don't know how to use github.
I can't download any dust.zip from your answer

[forkineye]

Any reason not to use the CI builds instead? https://github.com/forkineye/ESPixelStick/actions/workflows/build.yaml

[MartinMueller2003]

Hi Shelby

Three reasons:

1. The CI builds are just images, not integrated into a dist.zip file and I am seeing a lot of people that have no idea how to use an image file or integrate it into a dist.zip.
2. In this case, the CI build and my latest changes are in sync. Very often, my builds are ahead of the CI builds (this is NOT an issue that should be addressed, It is good to have the check step).
3. The binary files do not include the FS file set so they cannot be used on their own.

So I have gotten into the habit of making sure the dist.zip on the google drive is always up-to-date and then point people to it. If the CI build also generated a dist.zip then things would get simpler and we could simply point people to it. It would be really great if the CI build ran on any push to a derived branch and created a dist on that branch. I have a script that comes close. It puts all generated bin files into a firmware dir as part of the build process but I still manually move it to the dist dir to make the zip file

[forkineye]

The Release Archive has everything including the flash tool with versioning. It's the same artifact that's used for releases. The CI builds are generated on every PR as well.

[MartinMueller2003]

It looks like the link to the google drive was damaged.
Here it is again.
https://drive.google.com/file/d/1DG3wz8lbYNc371OIbeOqkzMaY5Zd2SKA/view?usp=sharing

[Francesco-Rugg]

Ok if I have any issue where I have to post it? In this repository or where?

[MartinMueller2003]

Download the file from google drive. unzip it in any location you like. Read the readme in the unziped directory. Connect your device to the PC using a USB cable, start the flashtool. fill in the fields and upload the image

[MartinMueller2003]

Yes you can post your questions in this forum.

[Francesco-Rugg]

Thank you! @MartinMueller2003

[Francesco-Rugg]

This came out when try to flash wt32

I use the same connection that I used for flashing wled to this board so I don't think thats a connection issue

[MartinMueller2003]

The line with "Connecting ........ is telling you that the device is not in programming mode. You needed to reset the device with GPIO 0 (zero) held low. You will need to do that three times.

[Francesco-Rugg]

So I need to erase flash three times before start flashing new ones?

[Francesco-Rugg]

I use online esptool for erasing and in it I can erase the flash
https://espressif.github.io/esptool-js/

[MartinMueller2003]

My WT32 does not have a USB interface and I have to manually put the device into programming mode three times when using the FlashTool.

[Francesco-Rugg]

I also use a programmer and my wt32 doesn't have USB connection

[Francesco-Rugg]

My WT32 does not have a USB interface and I have to manually put the device into programming mode three times when using the FlashTool.

What do you mean when you say "three times"

[MartinMueller2003]

The flash tool performs three operations: Clear flash, write fs, write program. If the USB is present then the device is reset into programming mode three times. If there is no USB on the device then you need to pull gpio0 low (and keep it that way). Then reset the device each time you see the "connecting ..." message coming out. After it is done you remove the wire on GPIO 0 and do a final reset

[Francesco-Rugg]

I use a programmer CH340 USB TO TTL, si I need to erase the wt32 flash three times before start flashing new software is it right?
The connections are:
+5 to +5
GND to GND
Rx to Tx
Tx to Rx
GND (on board) to IO1

[MartinMueller2003]

No. You do not need to explicitly erase the flash. You need to put the device into programming mode every time you see the "Connecting ....." message. When using the flash tool you will see that message three times and you should do a reset (with gpio0 low) if you see the dots and dashes coming out.

[Francesco-Rugg]

@MartinMueller2003 Sorry but I receiving the same error, while in wled web istaller I don't have this issue.

I see that the erase function works but the firmware flash don't go ahead

[MartinMueller2003]

That means the first step passed and you failed to put the device back into programming mode for the next step. I just did it using my ET32 and it is a pita. I had to power cycle the device three times in the process and you have to do it at the right time and quickly.