A new way to flash the modules

[PeterN]

I updated the online flasher enabling the selection of the flash memory size.
If someone want test, it should enable the full memory of the modules

Hi Francesco
I'm not sure if this should have had a positive effect on an M5 stack core with 16MB - but 1.47.2 still doesn't work there.

[cicciocb]

I updated the online flasher enabling the selection of the flash memory size.
If someone want test, it should enable the full memory of the modules

Hi Francesco
I'm not sure if this should have had a positive effect on an M5 stack core with 16MB - but 1.47.2 still doesn't work there.
[/quote

Yes Peter, I know.
I have a new version to release with the latest SDK 2.0.5 that, maybe, could work]

[Michel Alexander]

Hallo,
auf 2 Heltec esp32 Lora mit SW 1.44.2 läuft das Oled ohne Probleme,
bei der SW 1.47.2 funktioniert das Oled leider nicht.


Mein Programmcode:
' LoRa test program
' Using the WIFI LoRa 32 module

pin.mode 16, output
pin(16) = 1
ti$ =""
I2C.SETUP 4, 15 ' set I2C port on pins 4 and 15
Oled.Init 2, 1 ' initialise the OLED
Oled.Cls ' clear the screen
Oled.Font 2
Oled.Color 1
Oled.Print 0, 10, "LORA XMT/RCV"
r$ = "Lora Start"
pin.mode 25, output ' enable the internal white led
LoRa.Setup 18, 14, 26 ' SS, RESET, DIO0
print LoRa.Begin(866e6) ' 886 MHz
LoRa.SpreadFactor(7)
LoRa.SignalBandwidth 125e3
LoRa.SyncWord &h34 'default if &h34
LoRa.TXpower 020
onLoRa receive
LoRa.Receive
pkt = 0
timer0 5000, send

receive:
r$ = LoRa.Message$
ti$ = time$
pin(25) = 1 ' blinks the internal white led
pause 200
pin(25) = 0
return

send:

Oled.Cls
Oled.Font 2
Oled.Print 0, 1, "LORA "+ left$(Time$,5)
Oled.Font 1
Oled.Print 0, 20, r$
Oled.Print 0, 40, ti$
Oled.Print 0, 50, "RSSI: " + str$(LoRa.RSSI)
Oled.Print 60, 50, "SNR: " + str$(LoRa.SNR)
wlog r$
return

[cicciocb]

Hello,
on 2 Heltec esp32 Lora with SW 1.44.2 the Oled runs without problems,
Unfortunately, the Oled does not work with SW 1.47.2.

Thanks, I'll check it

[BeanieBots]

Not sure if this is hardware or firmware failure.
I have a development board with ESP32 + 360*240 TFT + SD card.
It has been working well for several years.
Upgraded from 1.44.2 to 1.47.2
A few files became corrupt.
Replaced files and all seemed OK.
Have been developing some programs with no further issues until yesterday.
Tried to change the autorun file run name but it refused to save the change. No error, just didn't do it.
Kept on booting from old file name despite no file name at all on the config page.
It then lost a large chunk of the file I was working on.
Decided to go back to 1.44.2 using toolkit. Tried several time but keep getting faiure as below:-
------------------------------------------------------------------------------------------------------------------------
esptool.py v2.6
Serial port COM3
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 94:b9:7e:e5:a3:10
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 15856 bytes to 10276...

Writing at 0x00001000... (100 %)
Wrote 15856 bytes (10276 compressed) at 0x00001000 in 0.9 seconds (effective 138.2 kbit/s)...
File md5: 66ba7fa3a11e53e48ecfacb231992004
Flash md5: 80649d98576e76d21e26deb852dca27a
MD5 of 0xFF is 5712c0fba5d6d98e8c49b568ff9fdc83

A fatal error occurred: MD5 of file does not match data in flash!
----------------------------------------------------------------------------------------------------------------------
Re-flashed to 1.47.2 using webtool. Re-flashed without error but still refuses to change autoboot filename.

All of this repeatable.
Cannot flash with toolkit.
Can flash with webtool.
Cannot change ANY parameters in config.
Will try to find another module to see if any of the issues repeat on different hardware.

[cicciocb]

Not sure if this is hardware or firmware failure.
I have a development board with ESP32 + 360*240 TFT + SD card.
It has been working well for several years.
Upgraded from 1.44.2 to 1.47.2
A few files became corrupt.
Replaced files and all seemed OK.
.....

Are you sure that the correct flash size has been selected ?

[BeanieBots]

Quite sure. 4Mb
Auto detect also shows 4Mb
I've done a complete flash erase and re-flash to1.44.2 with toolkit and now get this.
------------------------------------------------------------------------------------
ets Jun 8 2016 00:22:57



rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

flash read err, 1000

ets_main.c 371

ets Jun 8 2016 00:22:57



rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0018,len:4

load:0x3fff001c,len:1044

load:0x40078000,len:8896

load:0x40080400,len:5828

entry 0x400806ac

Annex initializing...

BLE support enabled

module Type 0 Display 93 SD_Card 1
display res 240 320 orientation 1
OK

No SD cards found. Reverts to FFAT



Annex32 WiFi BLE CAN 1.44.2

(C) ciccioCB 2022

Personal use only, commercial use strictly prohibited


Chip revision 1 Freq 240
STARTING


Switched to AP Mode ESP94:B9:7E:E6:7D:AD

IP address: 192.168.4.1
'-------------------------------------------------------------------------------------------------------------
I get exactly the same with another device.
What is flash read err, 1000 ?
Also, now there is NO tft connect. Why is detecting one?
Meanwhile, I'll have a go with the webtool.

EDIT:
Flashed with web tool and got this
--------------------------------------------------------------------------------------------------------------
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0
Annex initializing...
BLE support enabled
module Type 0 Display 255 SD_Card 0
OK
No SD cards found. Reverts to FFAT
FFat Mount Failed
Formatting FFAT ...
Format completed.

Annex32 BLE CAN 1.47.2
(C) ciccioCB 2022
Personal use only, commercial use strictly prohibited

Chip revision 1 Freq 240
STARTING

Switched to AP Mode ESP94:B9:7E:E6:7D:AD
IP address: 192.168.4.1
--------------------------------------------------------------------------------------------------------------
Looks hopeful. At least no flash read error.
Will configure WiFi and try some programs.

[cicciocb]

The TFT is automatically selected when flashing an "empty" device

[BeanieBots]

What is "flash read err, 1000 ?"
I have two devices reporting this error.
One has now been flashed with 1.47.2 and no longer reports it. (as shown in previous edited post)

[cicciocb]

What is "flash read err, 1000 ?"
I have two devices reporting this error.
One has now been flashed with 1.47.2 and no longer reports it. (as shown in previous edited post)

It is a message coming from the bootloader.
A simple search on internet gives that :
https://esp32.com/viewtopic.php?f=12&t=19176

"The firmware flashed is not valid"