- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#31
ESP32 / Re: can not flash olimex esp32...
Last post by RobLatour - September 02, 2025, 06:37:33 PMSo I got the other board to work too
What I did:
1. Erased the exiting flash
python -m esptool --chip esp32 --port COM5 erase-flash
2. Used with Ardunio 1.8.19 ( thanks LubOlimex )
3. Used board manager: esp32 by Espressif Systems board library v3.3.0
4. Used:
Board: "OLIMEX ESP32-POE-ISO"
Upload Speed: "921600"
Flash Frequency: "80MHz"
Flash Mode: "QI0"
Flash Size: "4MB (32Mb)"
Partition Scheme: "Default 4MB with ffat (1.2MB APP/1.5MB FATFS)"
Core Debug Level: "None"
PSRAM: "Disabled (WROOM)"
Erase All Flash Before Sketch Upload: "Disabled"
Hope this will be of help to others, and again with thanks to LubOlimex
What I did:
1. Erased the exiting flash
python -m esptool --chip esp32 --port COM5 erase-flash
2. Used with Ardunio 1.8.19 ( thanks LubOlimex )
3. Used board manager: esp32 by Espressif Systems board library v3.3.0
4. Used:
Board: "OLIMEX ESP32-POE-ISO"
Upload Speed: "921600"
Flash Frequency: "80MHz"
Flash Mode: "QI0"
Flash Size: "4MB (32Mb)"
Partition Scheme: "Default 4MB with ffat (1.2MB APP/1.5MB FATFS)"
Core Debug Level: "None"
PSRAM: "Disabled (WROOM)"
Erase All Flash Before Sketch Upload: "Disabled"
Hope this will be of help to others, and again with thanks to LubOlimex
#32
ESP32 / Re: can not flash olimex esp32...
Last post by RobLatour - September 02, 2025, 05:07:27 PMThanks for your help.
I got it to work on one board. Will post back here later with explanation if I can get it to work on the other as well.
I got it to work on one board. Will post back here later with explanation if I can get it to work on the other as well.
#33
ESP32 / Re: can not flash olimex esp32...
Last post by RobLatour - September 02, 2025, 03:34:20 PMso I tried 1.8.19 but got the same results as in my original post.
#34
ESP32 / Re: can not flash olimex esp32...
Last post by RobLatour - September 02, 2025, 02:54:58 PMThank you I will give 1.8.19 a try and post back here with the results.
Also, yes, I tried both DIO and QIO, and a different partition scheme.
Additionally, I tried googling for "esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0" but recommended solutions from others - like trying DIO and erasing the flash didn't help.
Also, yes, I tried both DIO and QIO, and a different partition scheme.
Additionally, I tried googling for "esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0" but recommended solutions from others - like trying DIO and erasing the flash didn't help.
#35
A64 / Re: HDMI: A64 Board not detect...
Last post by LubOlimex - September 02, 2025, 08:45:52 AMHard to tell what is wrong or what has to be done without doing it, probably there is something wrong with the script that doesn't save the auto detection option. The script is supposed to save the configuration you've selected.
Automate the changes to apply on start up like you did maybe add a cronjob so it does it automatically on startup.
Automate the changes to apply on start up like you did maybe add a cronjob so it does it automatically on startup.
#36
ESP32 / Re: can not flash olimex esp32...
Last post by LubOlimex - September 02, 2025, 08:35:43 AMThis can be related to Arduino IDE 2.3.6. Some libraries might not work properly with Arduino IDE 2.x.x. Try using 1.8.x.
In the board selector what did you select? Make sure it is "OLIMEX ESP32-POE-ISO". Try different Flash Mode - QIO - DIO. Try different partition scheme.
Search online for solutions for the first error:
"esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0"
In the board selector what did you select? Make sure it is "OLIMEX ESP32-POE-ISO". Try different Flash Mode - QIO - DIO. Try different partition scheme.
Search online for solutions for the first error:
"esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0"
#37
ESP32 / can not flash olimex esp32 poe...
Last post by RobLatour - September 02, 2025, 02:04:16 AMI have a couple olimex esp32 poe iso boards.
One of the boards was running this project: https://hackaday.io/project/189309-esp32-ntp-time-server-stratum-1
The other board was spare.
However, after two years the board that was running my time server suddenly stopped working. I opened up the case and notice the capacitor on the board had blow up.
No problem I though, I will just flash the same (Arduino) project to the spare board and use it.
Been working on that for a day now.
I keep getting an error that says:
E (386) esp_littlefs: ./managed_components/joltwallet__littlefs/src/littlefs/lfs.c:1378:error: Corrupted dir pair at {0x0, 0x1}
E (386) esp_littlefs: mount failed, (-84)
E (390) esp_littlefs: Failed to initialize LittleFS
assert failed: xTaskGetIdleTaskHandleForCore freertos_tasks_c_additions.h:453 (( xIdleTaskHandle[ xCoreID ] != ((void *)0) ))
Backtrace: 0x40082078:0x3ffe39a0 0x4008e805:0x3ffe39c0 0x40094a29:0x3ffe39e0 0x40091eee:0x3ffe3b20 0x400e40b9:0x3ffe3b40 0x400d975b:0x3ffe3b60 0x400d97c6:0x3ffe3b80 0x400d30f1:0x3ffe3bb0 0x400d315a:0x3ffe3bd0 0x400d4472:0x3ffe3bf0 0x400eabc6:0x3ffe3c10 0x40082455:0x3ffe3c40 0x4007977e:0x3ffe3c90 |<-CORRUPTED
ELF file SHA256: 00053b6ca
E (437) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
E (445) esp_core_dump_elf: Elf write init failed!
E (449) esp_core_dum
I've tried:
- erasing the flash with the pytool,
- updating the board version Ardunio is using to the current version (this needed code changes too),
- changing partition selections, etc.
I also tried to flash the old broken board, it generates the same error.
I am using the Arduino IDE 2.3.6.
Any ideas how to flash this board and get it to work.
One of the boards was running this project: https://hackaday.io/project/189309-esp32-ntp-time-server-stratum-1
The other board was spare.
However, after two years the board that was running my time server suddenly stopped working. I opened up the case and notice the capacitor on the board had blow up.
No problem I though, I will just flash the same (Arduino) project to the spare board and use it.
Been working on that for a day now.
I keep getting an error that says:
E (386) esp_littlefs: ./managed_components/joltwallet__littlefs/src/littlefs/lfs.c:1378:error: Corrupted dir pair at {0x0, 0x1}
E (386) esp_littlefs: mount failed, (-84)
E (390) esp_littlefs: Failed to initialize LittleFS
assert failed: xTaskGetIdleTaskHandleForCore freertos_tasks_c_additions.h:453 (( xIdleTaskHandle[ xCoreID ] != ((void *)0) ))
Backtrace: 0x40082078:0x3ffe39a0 0x4008e805:0x3ffe39c0 0x40094a29:0x3ffe39e0 0x40091eee:0x3ffe3b20 0x400e40b9:0x3ffe3b40 0x400d975b:0x3ffe3b60 0x400d97c6:0x3ffe3b80 0x400d30f1:0x3ffe3bb0 0x400d315a:0x3ffe3bd0 0x400d4472:0x3ffe3bf0 0x400eabc6:0x3ffe3c10 0x40082455:0x3ffe3c40 0x4007977e:0x3ffe3c90 |<-CORRUPTED
ELF file SHA256: 00053b6ca
E (437) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
E (445) esp_core_dump_elf: Elf write init failed!
E (449) esp_core_dum
I've tried:
- erasing the flash with the pytool,
- updating the board version Ardunio is using to the current version (this needed code changes too),
- changing partition selections, etc.
I also tried to flash the old broken board, it generates the same error.
I am using the Arduino IDE 2.3.6.
Any ideas how to flash this board and get it to work.
#38
A64 / Re: HDMI: A64 Board not detect...
Last post by a7med3365 - September 01, 2025, 09:33:10 PMJust add one more thing, We are patching this by running an X11 startup script and running xrandr commands to add and set the right resolution every time.
But it would be ideal if we can find a native solution to this
But it would be ideal if we can find a native solution to this
#39
A64 / Re: HDMI: A64 Board not detect...
Last post by a7med3365 - September 01, 2025, 09:11:56 PMwe bought a third board and it got the same issue as the second one. all three boards has the same state for the Ethernet/PHY reset jumper.
i tried the olinuxino-display script and set it to DISABLE option, did not solve it. we tried 'AUTO DETECTION', it solved the problem temporarily, we rebooted the board multiple time and it was taking the right resolution every time and it seemed like the issue was solved. but when we shutdown and power on the board again we lost the hdmi signal all together.
i restored it by using the serial debug interface by editing /boot/uEnv.txt to comment out the lcd overlay that was added by the display script.
i strongly feel its a driver issue, please advise on some things we could try
thank you and best regards
i tried the olinuxino-display script and set it to DISABLE option, did not solve it. we tried 'AUTO DETECTION', it solved the problem temporarily, we rebooted the board multiple time and it was taking the right resolution every time and it seemed like the issue was solved. but when we shutdown and power on the board again we lost the hdmi signal all together.
i restored it by using the serial debug interface by editing /boot/uEnv.txt to comment out the lcd overlay that was added by the display script.
i strongly feel its a driver issue, please advise on some things we could try
thank you and best regards
#40
RK3188 / Re: [RK3328-SOM-EVB] Using UA...
Last post by cybernox - September 01, 2025, 04:57:33 PMI slightly modified the procedure because the armbian-config you included in the bookworm distribution doesn't have the DTC entry.
So I decompiled the rk3328-som.dtb file with the command
than edited the serial node serial@ff120000 switching from "disabled" to "okay"
recompiled the dts and updated the /boot/armbianEnv.txt file for using the modified version changing the line
fdtfile=rockchip/rk3328-som-mod.dtb
instead of
fdtfile=rockchip/rk3328-som.dtb
Now, when I boot
seems that the ttyS1 i recognized. I can open the port without errors but when I try to send out a string nothing exit from the TX pin. I used a digital oscilloscope to see if any signal i s present but the pin stay at high fixed level (3.3V)
Any suggestion?
So I decompiled the rk3328-som.dtb file with the command
Code Select
sudo dtc -I dtb -O dts -o rk3328-som.dts /boot/dtb/rockchip/rk3328-som.dtb
than edited the serial node serial@ff120000 switching from "disabled" to "okay"
Code Select
sudo nano rk3328-som.dts
recompiled the dts and updated the /boot/armbianEnv.txt file for using the modified version changing the line
fdtfile=rockchip/rk3328-som-mod.dtb
instead of
fdtfile=rockchip/rk3328-som.dtb
Code Select
sudo dtc -I dts -O dtb -o /boot/dtb/rockchip/rk3328-som-mod.dtb rk3328-som.dts
sudo nano /boot/armbianEnv.txt
sudo reboot
Now, when I boot
Code Select
sudo dmesg | grep ttyS*
[ 0.000000] Kernel command line: root=UUID=3440d0ff-bb26-49a0-92cb-65352124c942 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 consoleblank=0 loglevel=1 ubootpart=ec32f700-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory
[ 0.856367] ff120000.serial: ttyS1 at MMIO 0xff120000 (irq = 21, base_baud = 1500000) is a 16550A
[ 0.858993] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 22, base_baud = 1500000) is a 16550A
[ 0.859126] printk: console [ttyS2] enabled
[ 7.750167] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[ 7.780739] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
[ 7.841357] systemd[1]: Expecting device dev-ttyS2.device - /dev/ttyS2...
[ 10.293542] systemd[1]: Found device dev-ttyS2.device - /dev/ttyS2.
seems that the ttyS1 i recognized. I can open the port without errors but when I try to send out a string nothing exit from the TX pin. I used a digital oscilloscope to see if any signal i s present but the pin stay at high fixed level (3.3V)
Any suggestion?