Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESPhome flasher mess with bootloader #183

Open
1 task done
Canditi890 opened this issue Nov 12, 2024 · 11 comments
Open
1 task done

ESPhome flasher mess with bootloader #183

Canditi890 opened this issue Nov 12, 2024 · 11 comments
Labels
wontfix This will not be worked on

Comments

@Canditi890
Copy link

What happened?

Somehow, when I flash using esphome flasher the batch loads in the wrong place and messes with the bootloader

A month ago everything was ok, I had to reload the file because I messed with the wifi settings

Probably this is esphome's fault, just reload the bootloader at 0x0 and everything works

To Reproduce Bug

image

Expected Behavior

Proper flashing

Install Method

Self-Compiled or other

What version/release of MM WLED?

Huidu HD-WF2 ESP32-S3

Which microcontroller/board are you seeing the problem on?

ESP32-S3

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Canditi890 Canditi890 added the bug Something isn't working label Nov 12, 2024
@dosipod
Copy link

dosipod commented Nov 12, 2024

@Canditi890 Have you tried the one modified for wled ? https://github.com/srg74/WLED-wemos-shield/tree/master/resources/Firmware/WLED_%20ESP_Flasher , esphome flasher caused issues since a long time ago

For s3 you may also try to flash directly from this site https://wled-install.github.io/

@softhack007
Copy link
Collaborator

This reminds me of an old warning that was put into the WLED knoledge base:
image

Please consider using WLED ESP Flasher, or the web installer or esptool.

@dosipod
Copy link

dosipod commented Nov 12, 2024

I was trying to verify from the installer but I just noticed that the OP listed HD-WF2 which would need the
MM env esp32S3_4MB_S but that is not available for MM on https://wled-install.github.io/ .Only ESP32-S3 8 MB
is listed for MM @wled-install

@Canditi890
Copy link
Author

I was trying to verify from the installer but I just noticed that the OP listed HD-WF2 which would need the MM env esp32S3_4MB_S but that is not available for MM on https://wled-install.github.io/ .Only ESP32-S3 8 MB is listed for MM @wled-install

You can get it from here https://github.com/MoonModules/WLED/actions

This reminds me of an old warning that was put into the WLED knoledge base: image

Please consider using WLED ESP Flasher, or the web installer or esptool.

I flashed after this error by esptool, but why was it working fine a month ago? And the firmware wasn't broken after uploading just the bootlooader didn't need flashing again

@Canditi890
Copy link
Author

I also have a small question about the two 128x64 panels, one works by setting up two chains because it has a 1/32 scan and can it manage to run the other one through the other HUB75 port? or is it still a problem?
I can't even create 256x64 by display errors, it either splits in half width or clones the same thing on two

@dosipod
Copy link

dosipod commented Nov 12, 2024

That note is not meant to you but to the owner of the installer site to include HD-WF2 bin.
I do not recall how did I flash my HD-WF2 but I think I used the wled flasher linked to you so try that and call it a day .
As to the size of the panels I only used one 64x64 with HD-WF2 but might be that is better for you to check discord as
I did not test

@Canditi890
Copy link
Author

bin will probably be added sometime from what I remember this board is still in the testing phase

@dosipod
Copy link

dosipod commented Nov 12, 2024

I do not think HD-WF2 with wled can handle that many as it does not have PSRAM but sure everything is improving with time

@softhack007
Copy link
Collaborator

softhack007 commented Nov 12, 2024

I also have a small question about the two 128x64 panels, one works by setting up two chains because it has a 1/32 scan and can it manage to run the other one through the other HUB75 port? or is it still a problem?

Unfortunately no, and it will be a problem for some time.

  • you can't use the second HUB75 port, because the driver we use (the one from mrFaptastic) cannot handle more than one port.
  • you could try to chain both panels, and use only one port on the HD-wf2.
  • 128x64 is quite a lot of pixels for poor ESP32-S3, especially when you don't have PSRAM. So practically speaking, going beyond 128x64 will not make you happy because the esp will be very unstable.

@softhack007
Copy link
Collaborator

@Canditi890 @dosipod

One thing you can always do if you have more panels than WLED can manage - for example you have two 128x64:
HUB75 duplicates the input signal for panels not driven by the controller. So you can have a "mirror" effect for free, meaning you can run an effect on 128x64, and the second 128x64 will show the same effect.

For this you simply configure the first panel only, but leave out the second panel which is chained to the first one.

@dosipod
Copy link

dosipod commented Nov 13, 2024

I only have two 64x64 to test with but I thought the OP plan to test 256x64 might be a bit unstable but to be honest might be things could be somewhat usable even if not very stable but others would just need to spare the time to test and report back

@troyhacks troyhacks added wontfix This will not be worked on and removed bug Something isn't working labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants