-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add address to firmware filenames #31
Comments
I will need to extract them from the platformio logs, but have not time for that in short period, any help or PR will be appreciated |
Good afternoon, I need your help, I have several esp8266(esp12e) devices and I would really like to put them into mining. please explain how to do this by programming devices through an online program, for the esp32 series there are bootloader files and others on the site, and for the esp8266 there is only a firmware version. how to flash correctly at addresses 0x0000, 0x8000, 0x10000, I really ask for help, because programming only the firmware program esp12e goes into error after a while, judging by the UART port. And there is another question for the developer, I can't find how to contact him, as far as possible to make sure that there is one esp01 device, for example, and processors such as stm32f103 are connected to it (this is an example) how is it possible to create a kind of hash board with a lot of stm? in order not to overload the Internet router too much, is the idea itself possible? I'm a ge programmer to be able to redo the code for me, it's still difficult, thanks for the answer in advance. The STM32 is cheaper than the ESP series. |
@tiger0007t for esp8266 you don't need them |
Autoupdate of v0.0.13 to 0.0.14 failed. I assume it is related to change of filename format... This is ESP8266, v0.0.13:
I tried to flash firmware 0.0.14 directly but it doesn't work, I see exception:
|
Autoupdate should be fixed now, and the crash seems related to the chipID, but I have no esp8266 board next to me to test it, let me just comment it out and force building again 0.0.14 |
I checked the device and it was already updated to 0.0.14 and mining. I confirm that autoupdate issue was fixed and the exception was fixed too. |
tell me, does it work stably for you? it runs for 8-10 minutes and stops completely. |
I was testing both 0.0.14 and 0.0.15 with Weimos D1 right now and it worked fine, I was still with serial console open |
02:01:56.297 > [I] Main: Compiled: Apr 23 2024 01:50:27
|
02:44:08.562 > [I] Network: <<< [mining.submit] {"id":68,"error":null,"result":true}
|
ESP8266 with firmware 0.0.13 fails to autoupdate to v0.0.15:
|
@PSLLSP I think now it should be fine, both for naming and auto updating, isn't it? |
It is not OK... ESP8266 with 0.0.13 cannot be autoupdated to 0.0.16:
|
It would be nice to have address of FLASH memory in the the firmware filename. It helps beginners, it is self documenting feature.
EXAMPLE.
Current filenames of firmware for LeafMiner 0.0.13 for ESP32:
Better filenames:
Other point is that flashing of firmware could be scripted and when offset address is stored in filename, it is easier to design script...
BTW, I just guessed addresses in my example, it is possible that addresses I used are not correct...
This is list of suggested filenames, work in progress. ESP32 and ESP8266 were verified to be correct. I do not have ESP-S2 device and GeekMagic-smallTV (I assume it is based on ESP8266).
The text was updated successfully, but these errors were encountered: