ESP Easy Flasher

Message

grovkillen · #51 Post by **grovkillen** » 09 Jan 2018, 22:20

Did you run it in debug mode or normal mode?

I think we're close now!! I will make some effort tomorrow. Thanks for your persistent.

grovkillen · #52 Post by **grovkillen** » 10 Jan 2018, 09:37

budman1758 wrote: ↑09 Jan 2018, 22:05

grovkillen wrote: ↑09 Jan 2018, 21:35 I have now hopefully squished the last two bugs (the date/time and the FTDI problem)...

Methinks you be making great progress dude!! It WORKS!!!

Found the correct ports for both of my devices.
Tried to flash a new -01 module and it flashed it fine but the app says it ended with an error. I had it set to post flash options and I think that's where the error might be cause the unit flashed fine. I connected with Putty and set the wifi stuff and its up and running. Here is the log output.

Code: Select all

######2018-01-09######
#######0.00.017#######
######FLASH INFO######
BIN file: ESP_Easy_v2.0.0-dev13_test_ESP8266_1024.bin
COM port: (COM5) USB Serial Port
Baud rate: 115200
######POST FLASH######
Unit name: test
Unit number: 26
Admin password: 
WiFi SSID 1: xxxxxxxxxx
WiFi password 1: xxxxxxxxxx
WiFi SSID 2: 
WiFi password 2: 
IP: <DHCP>
######FLASH LOG######
[esptool.exe -vv -cd nodemcu -cb 115200 -cp COM5 -ca 0x00000 -cf "C:\Users\Budman\Documents\Arduino Docs\ESPeasy Stuff\Flash Utilities\ESP_Easy_Flasher-master\BIN\ESP_Easy_v2.0.0-dev13_test_ESP8266_1024.bin"]
[1/9/2018 12:50:04 PM] esptool v0.4.12 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
[1/9/2018 12:50:04 PM] 	setting board to nodemcu
[1/9/2018 12:50:04 PM] 	setting baudrate from 115200 to 115200
[1/9/2018 12:50:04 PM] 	setting port from  to COM5
[1/9/2018 12:50:04 PM] 	setting address from 0x00000000 to 0x00000000
[1/9/2018 12:50:04 PM] 	espcomm_upload_file
[1/9/2018 12:50:04 PM] 	espcomm_upload_mem
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] opening bootloader
[1/9/2018 12:50:04 PM] resetting board
[1/9/2018 12:50:04 PM] trying to connect
[1/9/2018 12:50:04 PM] 	flush start
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	flush complete
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2013 bytes of data
[1/9/2018 12:50:04 PM] 	read 0, requested 1
[1/9/2018 12:50:04 PM] error: failed reading byte
[1/9/2018 12:50:04 PM] warning: espcomm_send_command: can't receive slip payload data
[1/9/2018 12:50:04 PM] trying to connect
[1/9/2018 12:50:04 PM] 	flush start
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	flush complete
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	read 0, requested 1
[1/9/2018 12:50:04 PM] trying to connect
[1/9/2018 12:50:04 PM] 	flush start
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	flush complete
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	serialport_receive_C0: 72 instead of C0
[1/9/2018 12:50:04 PM] resetting board
[1/9/2018 12:50:04 PM] trying to connect
[1/9/2018 12:50:04 PM] 	flush start
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	flush complete
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	read 0, requested 1
[1/9/2018 12:50:04 PM] trying to connect
[1/9/2018 12:50:04 PM] 	flush start
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	flush complete
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] Uploading 623136 bytes from C:\Users\Budman\Documents\Arduino Docs\ESPeasy Stuff\Flash Utilities\ESP_Easy_Flasher-master\BIN\ESP_Easy_v2.0.0-dev13_test_ESP8266_1024.bin to flash at 0x00000000
[1/9/2018 12:50:04 PM] 	erasing flash
[1/9/2018 12:50:04 PM] 	size: 098220 address: 000000
[1/9/2018 12:50:04 PM] 	first_sector_index: 0
[1/9/2018 12:50:04 PM] 	total_sector_count: 153
[1/9/2018 12:50:04 PM] 	head_sector_count: 16
[1/9/2018 12:50:04 PM] 	adjusted_sector_count: 137
[1/9/2018 12:50:04 PM] 	erase_size: 089000
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:50:04 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 15000 ms
[1/9/2018 12:50:04 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:50:04 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:50:04 PM] 	writing flash
[1/9/2018 12:50:13 PM] ................................................................................ [ 13% ]
[1/9/2018 12:50:21 PM] ................................................................................ [ 26% ]
[1/9/2018 12:50:30 PM] ................................................................................ [ 39% ]
[1/9/2018 12:50:39 PM] ................................................................................ [ 52% ]
[1/9/2018 12:50:48 PM] ................................................................................ [ 65% ]
[1/9/2018 12:50:57 PM] ................................................................................ [ 78% ]
[1/9/2018 12:51:06 PM] ................................................................................ [ 91% ]
[1/9/2018 12:51:12 PM] .................................................                                [ 100% ]
[1/9/2018 12:51:12 PM] starting app without reboot
[1/9/2018 12:51:12 PM] 	espcomm_send_command: sending command header
[1/9/2018 12:51:12 PM] 	espcomm_send_command: sending command payload
[1/9/2018 12:51:12 PM] 	espcomm_send_command: receiving 2 bytes of data
[1/9/2018 12:51:12 PM] closing bootloader
[1/9/2018 12:51:12 PM] 	flush start
[1/9/2018 12:51:12 PM] 	setting serial port timeouts to 1 ms
[1/9/2018 12:51:12 PM] 	setting serial port timeouts to 1000 ms
[1/9/2018 12:51:12 PM] 	flush complete
[2018-01-09 12:49:55] STOPPED due to errors! (try reset on the unit, then start a new flash attempt)

Thank you for that log. If possible please download 0.00.019 and test. I changed some code but are not really able to test it since the old code works for me as well.

https://github.com/Grovkillen/ESP_Easy_Flasher

EDIT: I found that your log contained an small error (error: failed reading byte) and this is interpreted by my wrapper as an error big enough for close down. Maybe I should only report the error, and carry on the rest of the post flash stuff?...

EDIT2: Updated the version to 0.00.019 and will let errors slide if flash seems to be done allright anyway...

budman1758 · #53 Post by **budman1758** » 10 Jan 2018, 19:46

OK. Tried your latest version. It flashed the unit just fine but when it was time to do the post flash options I think it failed there because the unit did not reboot first b4 the flasher tried to save the post flash settings. After the flasher was done I immediately connected to the unit with Putty and there was no activity at all. Once I reset the module it booted up fine and went into AP mode and none of the post flash settings were saved to it. I uploaded the log to your dropbox.

grovkillen · #54 Post by **grovkillen** » 10 Jan 2018, 19:51

Ah, I see. I might need to do a wait before the post flash... hm... let me think about that one for a little while.

PS: if you reflash the same unit, does it respond to the serial communication?

budman1758 · #55 Post by **budman1758** » 10 Jan 2018, 20:31

grovkillen wrote: ↑10 Jan 2018, 19:51 PS: if you reflash the same unit, does it respond to the serial communication?

Same thing. I don't think the unit is resetting at all. There was no activity light flashing on my usb unit and the module was doing nothing when I connected after the flasher was done. I had to reset the module b4 there was anything in the serial console.

grovkillen · #56 Post by **grovkillen** » 10 Jan 2018, 22:10

budman1758 wrote: ↑10 Jan 2018, 20:31
grovkillen wrote: ↑10 Jan 2018, 19:51 PS: if you reflash the same unit, does it respond to the serial communication?
Same thing. I don't think the unit is resetting at all. There was no activity light flashing on my usb unit and the module was doing nothing when I connected after the flasher was done. I had to reset the module b4 there was anything in the serial console.

I might need the user to actually press the reset switch? Hmm... My nodeMCU and D1 mini that I use accept the serial commands right away.

grovkillen · #57 Post by **grovkillen** » 11 Jan 2018, 15:07

https://github.com/Grovkillen/ESP_Easy_Flasher/releases

Version 0.00.020 is released with a new checkbox which will let the user manually reboot the device after flash.

I made a small error in the latest release, will update it tomorrow.

budman1758 · #58 Post by **budman1758** » 12 Jan 2018, 05:06

grovkillen wrote: ↑11 Jan 2018, 15:07 https://github.com/Grovkillen/ESP_Easy_Flasher/releases
Version 0.00.020 is released with a new checkbox which will let the user manually reboot the device after flash.

Tried it. Flashed fine but after flash settings still no workie. I uploaded a debug file to your dropbox.
Tried to get a screenshot of one of the powershell windows but they flash on and off too fast. Might help if they stay visible. Pretty sure the problems are related to Powershell. Are admin privileges transferring to them?

grovkillen · #59 Post by **grovkillen** » 12 Jan 2018, 09:48

budman1758 wrote: ↑12 Jan 2018, 05:06
grovkillen wrote: ↑11 Jan 2018, 15:07 https://github.com/Grovkillen/ESP_Easy_Flasher/releases
Version 0.00.020 is released with a new checkbox which will let the user manually reboot the device after flash.
Tried it. Flashed fine but after flash settings still no workie. I uploaded a debug file to your dropbox.
Tried to get a screenshot of one of the powershell windows but they flash on and off too fast. Might help if they stay visible. Pretty sure the problems are related to Powershell. Are admin privileges transferring to them?

https://github.com/Grovkillen/ESP_Easy_Flasher/releases

I have now tried to fix the issue regarding serial commands not being accepted. Please update to latest 0.00.021 version...

budman1758 · #60 Post by **budman1758** » 12 Jan 2018, 19:14

grovkillen wrote: ↑12 Jan 2018, 09:48 I have now tried to fix the issue regarding serial commands not being accepted. Please update to latest 0.00.021 version...

Hate to rain on the parade but post flash still no workie. You have a new debug file in yer dropbox.

grovkillen · #61 Post by **grovkillen** » 12 Jan 2018, 19:24

I will send you some test files to try to use powershell manually to send serial data to the esp.

Zeric · #62 Post by **Zeric** » 15 Jan 2018, 19:46

I did some testing with version 00.021 (Win 10 64bit) and wanted to give some feedback. I really like the idea of being able to configure as many settings as possible during the initial flash and haven’t seen that attempted before in other flash utilities or wrappers. Hopefully this software can be further developed so people have that feature in a general purpose esp easy gui flash program.

The first time I ran it in a directory already populated with other files and folders. It failed to run giving me the following pop up message [much later I tried to reproduce this and was unable to (??)].

Windows cannot find 'M:\[...]\%RUN_FILE_NAME%'. Make sure you typed the name correctly, and then try again.

Next, I ran it in an empty directory. It started, created subfolders and populated them. This surprised me as I didn’t expect this behavior. I was curious what would happen if some of those directories already existed, so I tried again in another folder after manually creating conflicting directories and files. The program assumed that any directories that are there are fine to use and that any files in those directories are the correct ones. I’m not sure this is the best approach, but at least it’s safer than silently over writing over existing files. It would be much better to warn the user what is going happen during this first run and get confirmation before proceeding.

Operations
The program had no problem finding my generic CH340 based serial converter. I only had one attached and it defaulted to it correctly.

Initially, I couldn’t figure out how to browse to the directory where the binary was contained. I eventually realized one has to put the binary in the bin directory under the program. This is not the standard way of doing things and will be confusing. Additionally, people with multiple esp easy project trees would likely want to keep binaries for each esp easy project near the respective source tree and browse to the correct one when they flash. As it is, either one has to mix all the binaries together in the same folder and be sure the names are unique, or have a separate flasher program tree for each respective project. Neither are great solutions, it’s much better to just have the user browse to the directory with the binaries and remember the last location of the bin files between runs.

I then set the post flash actions to populate the name and WiFi information, and set it off. It seemed to finish the first phase of downloading the firmware then hung when trying to set post flash actions requiring me to kill it in task manager to fully exit all the background processes.

After inspecting the log, it was obvious what the problem was. The call to esptool.exe is hard coded for nodemcu. This is a big issue as espeasy runs on many boards, not just those that support nodemcu style of GPIO0 and RESET control. The software needs to have the user select the board type, pass it to esptool.exe, and if the board type is none, pause between esptool.exe operations so the user can manually reset the board. For most of my boards, this is a show stopper on using the post flash action feature.

Running it again without using the post flash action, it ran to completion without error, however the firmware was corrupted on the board and wouldn’t boot getting a checksum error. This took some time to figure out. This particular board I had not flashed before and I determined that it needed a slow flash clock to flash correctly.

Any flasher has to give the user the option to set the flash chip speed (20m/26m/40m/80m) and the flash mode (DIO/DOUT/QIO/QOUT). Not all boards work with the same settings. For my particular board, this was a total showstopper. Esptool.py and esptool.exe have these options for a reason and they must be supported by any wrapper to provide broad compatibility.

Feature enhancements
It would be nice if the software provides a full chip erase option before writing firmware. I’ve found many times going from one type of esp firmware to another requires a full erase for it to work properly. FYI- esptool.exe as far as I know does not correctly support a full erase so one has to write a blank file that is the same size of the flash chip to accomplish this.

As it stands, this flasher only supports boards that are highly compatible with nodemcu so it’s not of use to me as is. I would love to see the project finished so it can support most esp8266 boards.

grovkillen · #63 Post by **grovkillen** » 15 Jan 2018, 23:01

It's still in a early stage. Will improve but main focus is standard boards (covered by the official supported ESP hardware found on wiki). I personally don't own them all though. DOUT is possible to use but that is it for now. Erase flash will be supported in time. Thanks for the feedback.

Zeric · #64 Post by **Zeric** » 16 Jan 2018, 03:11

Thanks for working on it, I know it's early and my intent was to be helpful.

The board I was testing it on is listed as a known supported ESPEasy board on www.letscontrolit.com/wiki/index.php/ESP_Hardware. It is a recently purchased Sonoff basic. None of the Sonoff devices support nodemcu style control of GPIO0 and RESET, they all need to be manually reset between esptool operations, and Sonoff boards are *very* popular. Some people use an Arduino as ISP mode to program them, I use an inexpensive USB/Serial converter that supports both 5V and 3.3V and works very well (cost about $2 from ebay/china, $7 on amazon).

Thanks for pointing out the "force DOUT" option, I don't know how I missed the checkbox at the bottom. This latest sonoff basic I purchased needed to slow down the memory clock. I'm guessing the manufacturer changed to a different memory chip. Other sonoff devices I have used (over a dozen) did not require this.

I'm also wondering if I have some sort of font issue, the windows looks a little odd especially along the bottom and different from the one in your first post. Here is a image of how it displays for me:

Any idea of what the problem might be with the window?

grovkillen · #65 Post by **grovkillen** » 16 Jan 2018, 05:58

Yeah, the problem is that windows 10 is rendering the window in a different way compared to windows 7. I will take care of that issue once I get the basic function working.

Have you used the "halt" checkbox for manual reboot? I have successfully flashed several basic units with the tool. Older versions though.

grovkillen · #66 Post by **grovkillen** » 16 Jan 2018, 19:22

Zeric wrote: ↑16 Jan 2018, 03:11 Thanks for working on it, I know it's early and my intent was to be helpful.

The board I was testing it on is listed as a known supported ESPEasy board on www.letscontrolit.com/wiki/index.php/ESP_Hardware. It is a recently purchased Sonoff basic. None of the Sonoff devices support nodemcu style control of GPIO0 and RESET, they all need to be manually reset between esptool operations, and Sonoff boards are *very* popular. Some people use an Arduino as ISP mode to program them, I use an inexpensive USB/Serial converter that supports both 5V and 3.3V and works very well (cost about $2 from ebay/china, $7 on amazon).

Thanks for pointing out the "force DOUT" option, I don't know how I missed the checkbox at the bottom. This latest sonoff basic I purchased needed to slow down the memory clock. I'm guessing the manufacturer changed to a different memory chip. Other sonoff devices I have used (over a dozen) did not require this.

I'm also wondering if I have some sort of font issue, the windows looks a little odd especially along the bottom and different from the one in your first post. Here is a image of how it displays for me:

Any idea of what the problem might be with the window?

Okay, I just flashed (+post flashed) a Basic but the new ones need to be flashed using the ESP8255 bin file. Everything worked then... at least for me.

Zeric · #67 Post by **Zeric** » 16 Jan 2018, 21:07

I just tried an older sonoff (with "Force -DOUT" unchecked, and "Halt app before port flash" checked). After FW flashing, it waited for the manual reset, then proceeded. The Wifi information was set correctly and connected to my network (cool), however the name of the device remained the default "ESP_Easy" and did not change to the name I specified "sonoff_a". The unit number did update correctly. The log clearly showed where the name was set to what I specified and I didn't see any errors, maybe a bug? Rebooting made no difference. Changing the name in the web interface worked fine. I did not try updating any rule sets.

As far as the memory chip...
I closely looked at both the sonoff boards, the one I successfully flashed today with ESP Easy Flasher (with DOUT unchecked), and the one that gave me issues before (not only in this wrapper program). The part number on the former is PN25F08 and the latter PN25F08B and they seem to be different manufacturers (ID 0xE0 vs 0x5E). There are many posts saying the "B" suffix chips need DOUT. As mentioned earlier, I had to set mode to DOUT and slow down the write speed in esptool.py after doing a full flash wipe to get a good write. I need to experiment more with that board, maybe the slow write requirement was a fluke.

On your use of the esp8285 FW bin
The esp8285 requires DOUT, just like esp8266 boards using PN25F08B chips. I saw a post where someone confirmed that the esp8285 bin file would work with an esp8266 board using a PN25F08B chip.

Feedback on Halt check box
When I first saw this setting, I misunderstood what it was for and it may just be a language issue. "Halt" normally means the abrupt total termination of a program (the has been true from old mainframes to modern day linux). But the intent of the checkbox is not for the program terminate, it's to wait for a user action. I think it would be more clear to say something like "Wait for user to reset before post flash".

Feedback on visual Layout
To me anyway, the current layout is scattered with comm related settings at both the top (COM port) and bottom (baud rate), and the board related settings in the middle (Halt app before post flash) and bottom (Force -DOUT). I suggest the top section have all the comm and board related settings. Top section: COM port, serial baud rate, board type, memory speed, memory write method, etc first. Next, the firmware location, then next the Post flash settings, then status window window near the bottom as you have it.

grovkillen · #68 Post by **grovkillen** » 16 Jan 2018, 21:17

Great feedback! It's my first attempt in making something for the public so I totally get your points. I will rename the "halt" checkbox but the overhaul of GUI will have to wait. But I have noted the feedback and will take it into the final release (1.00.000).

grovkillen · #69 Post by **grovkillen** » 28 Mar 2018, 20:35

I have just added serial monitoring using plink.exe: https://github.com/Grovkillen/ESP_Easy_Flasher/releases

Please observe that the serial monitoring will lock the COM port and making it un-responsive if you try to flash at the same time. Nothing bad will happen except that you get an error. With this new feature you can use the ESP Easy Flasher to quickly open a serial monitor for an attached ESP Easy unit, even though you might not want to re-flash that unit.

grovkillen · #70 Post by **grovkillen** » 16 Jul 2018, 10:10

Serial programing only is now supported as of 0.00.026 (https://github.com/Grovkillen/ESP_Easy_Flasher/releases)

In other words, you can reprogram a unit without the need to reflash it. Doh!

grovkillen · #71 Post by **grovkillen** » 23 Jul 2018, 11:09

I have now released the first beta (0.01.000) https://github.com/Grovkillen/ESP_Easy_Flasher/releases

This version supports spaces in SSID and removes special characters in Unit Name. I hope it'll be of use

mrshark · #72 Post by **mrshark** » 23 Jul 2018, 11:48

hi
can it be used to flash other firmwares, too? I actually use the flasher included in every espeasy 2.0 release package, with no issues, so i think yes... the wifi credential setting is a standard, or it changes from one board/firmware to an other? If it's usable, i could pass credentials to tasmota and espurna, too, which would be nice... i have to try, of course it's not what your tool is intended for... i remember once when changing from one firmware to an other, the latter was already connected to my wifi without me doing anything... thanks in advance

grovkillen · #73 Post by **grovkillen** » 23 Jul 2018, 15:15

Flashing the ESP with whatever bin file is not a problem. Pushing the credentials will probably not work since the commands that ESP Easy use is not likely the same as other firmware use.

puppetmaster886 · #74 Post by **puppetmaster886** » 26 Jul 2018, 00:50

nice program. It works great with esp8285.
It would be greater if you could add the config file after flashing.

grovkillen · #75 Post by **grovkillen** » 26 Jul 2018, 07:07

I will consider that. Thanks for the feedback

grovkillen · #76 Post by **grovkillen** » 30 Oct 2018, 20:15

I have just updated the flasher (0.02.000) which fixed a bug if you had high density screens. With new Patreon supporters we're getting closer to the point of doing this full time. Thanks to those of you who support us!

https://github.com/Grovkillen/ESP_Easy_ ... g/0.02.000

martin8310 · #77 Post by **martin8310** » 20 Nov 2018, 18:11

Hello everyone,

I am enthusiastic about the espeasy project and would like to give feedback on the esp easy flasher.

I have also the font issue (letters are too big) and therefore not readable.

My Sytem is Windows 10 64bit with the ESP Easy Flasher in Version 0.02.004.Screen Resolution 2560x1600

will there be a working version?

Thank you in advance.

regards martin

grovkillen · #78 Post by **grovkillen** » 20 Nov 2018, 18:57

Did you drag and drop the font file?

martin8310 · #79 Post by **martin8310** » 20 Nov 2018, 20:57

Unfortunately not. Thanks for the tip, the problem is solved. It's just a bit too complicated

Now I understand why all the windows are always open.

Thank you.

grovkillen · #80 Post by **grovkillen** » 20 Nov 2018, 21:50

I put the info in the message box

riker1 · #81 Post by **riker1** » 07 Dec 2018, 10:41

Hi

loving this tool.

MAybe an enhancement request.

for fixed ip, I would recommend to be aple to set all IP datails.

Gateway
Subnetmask

Does this make sence?
Can this be added?

Thanks Thomas

grovkillen · #82 Post by **grovkillen** » 07 Dec 2018, 11:26

I could make it optional yes.

ThomasB · #83 Post by **ThomasB** » 08 Dec 2018, 02:41

@grovkillen, thank you for creating this flashing tool. I started using it this week and appreciate its user interface.

Today I noticed that it has a file name length problem. For example, this file is ignore (not shown in the drop down):
ESP_Easy_mega-20181207_normal_core_241_ESP8266_1024.bin

The workaround is to rename it so it is shorter. For example, this works:
ESP_Easy_mega-20181207_normal_241_ESP8266_1024.bin

BTW, my PC is WIN10 Pro 64 bit, build 16299.

- Thomas

grovkillen · #84 Post by **grovkillen** » 08 Dec 2018, 10:36

I will make the window wider. Release Monday.

grovkillen · #85 Post by **grovkillen** » 08 Dec 2018, 11:52

By the way. Latest release allows for custom serial commands using an external txt file.

@riker1 you can add your special subnet and gateway in this file. They will be added after the standard commands so you will see the "wrong" subnet and gateway first but these will be overrun by the custom commands right before the save is made.

giobbe · #86 Post by **giobbe** » 08 Dec 2018, 16:24

Hi,
how do I flash Espeasy on new esp32 (Wroom32)?
Thanks
Giobbe

grovkillen · #87 Post by **grovkillen** » 08 Dec 2018, 17:31

giobbe wrote: ↑08 Dec 2018, 16:24 Hi,
how do I flash Espeasy on new esp32 (Wroom32)?
Thanks
Giobbe

ESP32 is not yet supported by the flasher. Sorry! It's on the road map though.

riker1 · #88 Post by **riker1** » 10 Dec 2018, 18:28

grovkillen wrote: ↑07 Dec 2018, 11:26 I could make it optional yes.

that would be great
Thanks

riker1 · #89 Post by **riker1** » 10 Dec 2018, 18:34

grovkillen wrote: ↑08 Dec 2018, 11:52 By the way. Latest release allows for custom serial commands using an external txt file.

@riker1 you can add your special subnet and gateway in this file. They will be added after the standard commands so you will see the "wrong" subnet and gateway first but these will be overrun by the custom commands right before the save is made.

ok, thanks will check

riker1 · #90 Post by **riker1** » 11 Dec 2018, 18:24

grovkillen wrote: ↑08 Dec 2018, 11:52 By the way. Latest release allows for custom serial commands using an external txt file.

@riker1 you can add your special subnet and gateway in this file. They will be added after the standard commands so you will see the "wrong" subnet and gateway first but these will be overrun by the custom commands right before the save is made.

Hi
wanted to test this,
how do I have to name the gateway and subnet in settings file?

Fixed IP=True
IP1=192
IP2=168
IP3=3
IP4=9

?
gateway=192.168.0.1
subnet=255.255.0.0

.

The checkbox is disabled for this action.....how to enable it?

Thanks Thomas

grovkillen · #91 Post by **grovkillen** » 11 Dec 2018, 18:58

Save the commands in a file called "SerialCommands.txt" in the settings folder.

Commands are syntaxed just as any serial commands.

Code: Select all

gateway,192.168.0.1
subnet,255.255.0.0

riker1 · #92 Post by **riker1** » 11 Dec 2018, 19:00

Hi

ok, but how to enable the checkbox?

to use serialcommands?

grovkillen · #93 Post by **grovkillen** » 11 Dec 2018, 19:14

If it's there [the file] it will be enabled upon start of app or rescan (button for rescanning COM ports).

riker1 · #94 Post by **riker1** » 11 Dec 2018, 22:13

strange, not working for me.

see hardcopy

file in settings/SerialCommands.txt exists

refreshed often, and restarted

default is stored in settings folder.

: easyflasher.PNG (95.12 KiB) Viewed 57060 times

But still disabled ?

Thanks for checking Thomas

riker1 · #95 Post by **riker1** » 11 Dec 2018, 22:34

...ups solved..

user error.

strangewise the extention ini was not shown and file was

serialcommand.txt.ini

now having the file without ini it is working.

Sorry

Thomas

grovkillen · #96 Post by **grovkillen** » 12 Dec 2018, 06:09

Ah! Great!

grovkillen · #97 Post by **grovkillen** » 14 Dec 2018, 06:15

New version is delivered with today's release.

kenkoknz · #98 Post by **kenkoknz** » 17 Dec 2018, 09:22

Hi,
Version mega 20181216; Just a minor in convenience, as I normally set the scree to 125% (win7) to make it eaisier for my eyes; I am missing the bottom part of the flasher gui, does not seems to able to scale or resize, so I cant click flash.
However if I change display size back to 100% it is ok.
Thansk,
kEN

grovkillen · #99 Post by **grovkillen** » 17 Dec 2018, 14:16

kenkoknz wrote: ↑17 Dec 2018, 09:22 Hi,
Version mega 20181216; Just a minor in convenience, as I normally set the scree to 125% (win7) to make it eaisier for my eyes; I am missing the bottom part of the flasher gui, does not seems to able to scale or resize, so I cant click flash.
However if I change display size back to 100% it is ok.
Thansk,
kEN

ALT+S will save current settings to the Settings/Default.ini change the "pixels per inch" value and the zoom will work better. Save and restart the app.

riker1 · #100 Post by **riker1** » 24 Jan 2019, 17:27

Hi
I have a questions

How do I set IP
via Serial commands?

Thanks Thomas

do I just enter those command in console? putty?

Name ESP01S
Unit 202
ip xx.xx.xx.xx
WifiSSID ssid

etc?

I found it: just have to enter the commands in arduino serial command line.

Thanks

Who is online