- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
A64 / Re: Bookworm upgrade availabil...
Last post by mossroy - April 25, 2026, 01:27:30 PMMany thanks for the info. I was not aware of their new image.
I find surprising that it's based on Debian 12 instead of Debian 13. Debian 12 end of regular support is 2 months from now (even if LTS support should extend for 2 more years)
Debian 13 would have given 2 extra years of support. https://www.debian.org/releases/index.en.html
Anyway, I did not test their new image either.
I'll first test if my Debian 13 installations are sustainable. If they are, they would probably be a better fit for my use-case (headless servers): in terms of features (more recent distro), security updates (much more frequent kernel upgrades), and future dist-upgrades (Olimex has never supported in-place dist-upgrades).
The official Olimex image probably has a more complete board support (screens, audio etc), but it's useless in my use-case.
I find surprising that it's based on Debian 12 instead of Debian 13. Debian 12 end of regular support is 2 months from now (even if LTS support should extend for 2 more years)
Debian 13 would have given 2 extra years of support. https://www.debian.org/releases/index.en.html
Anyway, I did not test their new image either.
I'll first test if my Debian 13 installations are sustainable. If they are, they would probably be a better fit for my use-case (headless servers): in terms of features (more recent distro), security updates (much more frequent kernel upgrades), and future dist-upgrades (Olimex has never supported in-place dist-upgrades).
The official Olimex image probably has a more complete board support (screens, audio etc), but it's useless in my use-case.
#2
New Product Ideas / MIPI-HDMI Revision for I2S Sup...
Last post by ramblecube - April 25, 2026, 12:14:27 PMHello there 
I posted in "New Products Release" in December, but I think that was the wrong place to post.
I am interested in adding sound support to the MIPI-HDMI bridge design.
The datasheet for the LT8912B says that pins 58 (I2S DATA) 59 (I2S WS) and 60 (I2S CLK) are for I2S, but the MIPI-HDMI bridge schematic/PCB KiCad files show that they are not connected on the board.
Would it be possible to add a connector for the I2S lines to the board?
Thank you for your amazing work,
-ramblecube
I posted in "New Products Release" in December, but I think that was the wrong place to post.
I am interested in adding sound support to the MIPI-HDMI bridge design.
The datasheet for the LT8912B says that pins 58 (I2S DATA) 59 (I2S WS) and 60 (I2S CLK) are for I2S, but the MIPI-HDMI bridge schematic/PCB KiCad files show that they are not connected on the board.
Would it be possible to add a connector for the I2S lines to the board?
Thank you for your amazing work,
-ramblecube
#3
ESP32 / Re: Board "olimex_esp32-c5-dev...
Last post by winfried - April 25, 2026, 11:45:25 AMThanks for the explanation and corrections,
I tried the corrected board definition, using stable pioarduino as platformio, but still got on configuration process:
Maybe your configuration works on other environment, but here for Info:
After adding URL, I got on compilation:
So adding in section build:
Also I add the openocd part, so debug and upload with "esp-builtin" works (still some errors reading some memory areas, but usable).
My working solution for platformio.ini and board definition below:
my-olimex_esp32-c5-devkit-lipo.json:
platformio.ini:
I tried the corrected board definition, using stable pioarduino as platformio, but still got on configuration process:
Maybe your configuration works on other environment, but here for Info:
Code Select
Resolving ESP32-C5-DevKit-Lipo dependencies...
UserSideException: Please specify name, url and vendor fields for /home/winfried/repos/art/pfb/pfb-bees/experiments/07-test-ESP32-C5/boards/olimex_esp32-c5-devkit-lipo.json
After adding URL, I got on compilation:
Code Select
*** ValueError `invalid literal for int() with base 10: ''' trying to evaluate `${__get_board_f_boot(__env__)}'
File "/home/winfried/.platformio/packages/framework-arduinoespressif32/tools/pioarduino-build.py", line 94, in generate_bootloader_image
So adding in section build:
Code Select
"f_flash": "80000000L",
solved this.Also I add the openocd part, so debug and upload with "esp-builtin" works (still some errors reading some memory areas, but usable).
My working solution for platformio.ini and board definition below:
my-olimex_esp32-c5-devkit-lipo.json:
Code Select
{
"build": {
"core": "esp32",
"cpu": "esp32c5",
"f_cpu": "240000000L",
"f_flash": "80000000L",
"mcu": "esp32c5",
"variant": "esp32c5",
"flash_mode": "dio",
"psram_type": "opi",
"extra_flags": [
"-DBOARD_HAS_PSRAM",
"-DARDUINO_USB_MODE=1",
"-DARDUINO_USB_CDC_ON_BOOT=1"
]
},
"connectivity": [
"wifi",
"bluetooth"
],
"debug": {
"openocd_target": "esp32c5.cfg"
},
"frameworks": [
"arduino",
"espidf"
],
"name": "Olimex ESP32-C5-DevKit-Lipo (WROOM-N8R4)",
"upload": {
"flash_size": "8MB",
"maximum_ram_size": 327680,
"maximum_size": 8388608,
"require_upload_port": true,
"speed": 921600
},
"vendor": "Olimex"
,"url": "https://www.olimex.com/Products/IoT/ESP32-C5/ESP32-C5-DevKit-Lipo/"
}
platformio.ini:
Code Select
[platformio]
description = "ESP32-C5 test"
[env]
;platform=https://github.com/pioarduino/platform-espressif32.git
platform = https://github.com/pioarduino/platform-espressif32/releases/download/stable/platform-espressif32.zip
framework = arduino
[env:ESP32-C5-DevKit-Lipo]
board = my-olimex_esp32-c5-devkit-lipo
monitor_speed = 115200
upload_speed = 921600
; debugging with openocd on JTAG/serial USB-C port
debug_tool = esp-builtin
debug_init_break = tbreak setup ; Stoppt automatisch am Anfang von setup()
; upload methods working on JTAG/serial USB-C port
upload_protocol = esp-builtin
;upload_protocol = esptool
#4
A64 / Re: Bookworm upgrade availabil...
Last post by ilario - April 24, 2026, 04:32:40 PMHave you seen that Olimex released a Debian 12 image for A64-Olinuxino in March? I did not try it yet though...
#5
A64 / Re: Bookworm upgrade availabil...
Last post by mossroy - April 24, 2026, 04:20:45 PMI've made some huge progress (without any help from Olimex, unfortunately).
I managed to install (with Debian Installer), and run Debian 13 (Trixie) on my A64-OLinuXino-2Ge8G-IND boards. It seems to be stable (at least I see no issue after leaving a board idle for 10 days), but it has to be confirmed after using them for real.
In short, I converted file sun50i-a64-olinuxino-2Ge8G.dtb from Olimex to .dts readable format, modified it a bit, and converted it back to .dtb format. Then I made Debian use my .dtb.
A tricky part was with the eMMC itself: even if I did not want to use it at all, it apparently has to be in a certain state (else the board is confused on startup and does not start): u-boot installed on it, and no other previous partition
I'll test it a bit more seriously.
What I did is certainly not the cleanest and best way to achieve the result. But hopefully, it should avoid trashing my A64-OLinuXino-2Ge8G-IND boards, and seriously expand their lifespan.
I managed to install (with Debian Installer), and run Debian 13 (Trixie) on my A64-OLinuXino-2Ge8G-IND boards. It seems to be stable (at least I see no issue after leaving a board idle for 10 days), but it has to be confirmed after using them for real.
In short, I converted file sun50i-a64-olinuxino-2Ge8G.dtb from Olimex to .dts readable format, modified it a bit, and converted it back to .dtb format. Then I made Debian use my .dtb.
A tricky part was with the eMMC itself: even if I did not want to use it at all, it apparently has to be in a certain state (else the board is confused on startup and does not start): u-boot installed on it, and no other previous partition
I'll test it a bit more seriously.
What I did is certainly not the cleanest and best way to achieve the result. But hopefully, it should avoid trashing my A64-OLinuXino-2Ge8G-IND boards, and seriously expand their lifespan.
#6
ESP32 / Re: Board "olimex_esp32-c5-dev...
Last post by LubOlimex - April 24, 2026, 01:46:53 PMQuoteWith 240Mhz it blinks, but is it save to operate ?
As long as it works it is safe to use, might draw more current.
QuoteWhat is the difference:
"flash_mode": "dio", "psram_type": "opi" are not "qio" ?
These are just different modes to flash and different interface for the PSRAM. Depends on the internal hardware of the ESP32-C5 module and revision. What is suggested by Espressif should be used. I think for ESP32-C5 should be dio and qio.
QuoteIs there a reason for other ram size ?
It is probably a mistake in our json, the chip has 320KB RAM. I have uploaded improved version.
#7
ESP32 / Board "olimex_esp32-c5-devkit ...
Last post by winfried - April 24, 2026, 11:03:26 AMUsing your board definition with provided file: `olimex_esp32-c5-devkit-lipo.json`
with pioarduino and simple blink test drops an error on compilation:
using `board=esp32-c5-devkitc1-n8r4` Code compiles, uploads and runs.
So comparing and testing this file with `esp32-c5-devkitc1-n8r4.json` from platformio, I found adding the definition of "f_flash": "80000000L" in the build section makes it to work.
So the question is now: Is this a proper value ?
Other questions, for info, because of the difference is:
- "f_cpu": "160000000L" vs "f_cpu": "240000000L",
With 240Mhz it blinks, but is it save to operate ?
- What is the difference:
"flash_mode": "dio", "psram_type": "opi" are not "qio" ?
- "maximum_ram_size": 524288, "maximum_size": 8388608,
vs
"maximum_ram_size": 327680, "maximum_size": 8388608,
Is there a reason for other ram size ?
Any explanation is appreciated.
mfg winfried
platformio.ini:
with pioarduino and simple blink test drops an error on compilation:
Code Select
*** ValueError `invalid literal for int() with base 10: ''' trying to evaluate `${__get_board_f_boot(__env__)}'
File "/home/winfried/.platformio/packages/framework-arduinoespressif32/tools/pioarduino-build.py", line 94, in generate_bootloader_image
using `board=esp32-c5-devkitc1-n8r4` Code compiles, uploads and runs.
So comparing and testing this file with `esp32-c5-devkitc1-n8r4.json` from platformio, I found adding the definition of "f_flash": "80000000L" in the build section makes it to work.
So the question is now: Is this a proper value ?
Other questions, for info, because of the difference is:
- "f_cpu": "160000000L" vs "f_cpu": "240000000L",
With 240Mhz it blinks, but is it save to operate ?
- What is the difference:
"flash_mode": "dio", "psram_type": "opi" are not "qio" ?
- "maximum_ram_size": 524288, "maximum_size": 8388608,
vs
"maximum_ram_size": 327680, "maximum_size": 8388608,
Is there a reason for other ram size ?
Any explanation is appreciated.
mfg winfried
platformio.ini:
Code Select
[platformio]
description = "LoRaBees gateway ESP32-C5 and MOD-LoRa868-ANT"
include_dir = src
[env]
platform=https://github.com/pioarduino/platform-espressif32.git
framework = arduino
[env:ESP32-C5-DevKit-Lipo]
board = olimex_esp32-c5-devkit-lipo
; board = esp32-c5-devkitc1-n8r4
monitor_speed = 115200
upload_speed = 921600
#8
ESP32 / Re: ESP32-POE-ISO-EA-16MB full...
Last post by LubOlimex - April 23, 2026, 01:54:26 PMIt is a good idea to also look at a ready 3D designs, there are many box designs online for ESP32-POE-ISO that can be used as basis. Our boxes also have 3D design files available for download:
https://www.olimex.com/Products/IoT/ESP32/BOX-ESP32-POE-ISO/
Now for the ESP32-POE-ISO I have exported STEP here:
https://ftp.olimex.com/TEMP/ESP32-PoE-ISO-step-export/ESP32-PoE-ISO_Rev_L.step
Notice that I haven't double checked if the dimensions in the export are 100% consistent with each component. We don't need component height during manufacturing so some components can be a bit off. My advice is to also always compare the STEP file with the real board (empirically measure heights).
In future you can export from KiCAD on your won, it is the free software we use to design these boards. Install KiCAD and download the sources from the GitHub page for ESP32-POE-ISO, open the project file in KiCAD, open the PCB layout editor, and click File -> Export and chose one of the formats. Furthermore, there is a built-in 3D viewer in KiCAD, again open the PCB and navigate to View -> 3D Viewer.
https://www.olimex.com/Products/IoT/ESP32/BOX-ESP32-POE-ISO/
Now for the ESP32-POE-ISO I have exported STEP here:
https://ftp.olimex.com/TEMP/ESP32-PoE-ISO-step-export/ESP32-PoE-ISO_Rev_L.step
Notice that I haven't double checked if the dimensions in the export are 100% consistent with each component. We don't need component height during manufacturing so some components can be a bit off. My advice is to also always compare the STEP file with the real board (empirically measure heights).
In future you can export from KiCAD on your won, it is the free software we use to design these boards. Install KiCAD and download the sources from the GitHub page for ESP32-POE-ISO, open the project file in KiCAD, open the PCB layout editor, and click File -> Export and chose one of the formats. Furthermore, there is a built-in 3D viewer in KiCAD, again open the PCB and navigate to View -> 3D Viewer.
#9
ESP32 / ESP32-POE-ISO-EA-16MB full ass...
Last post by Ol!mexGoody - April 22, 2026, 06:13:46 PMI have the ESP32-POE-ISO-EA-16MB and would like a full assembly .step file so I can design a rack mount for it in Fusion.
I found this https://github.com/OLIMEX/ESP32-POE/tree/master/HARDWARE and tried to make sense of KiCad to extract the full assembly, but I keep running into export errors.
Is the full assembly of the ESP32-POE-ISO-EA-16MB available anywhere in .step and/or .stl without requiring knowledge of how to navigate KiCad?
I found this https://github.com/OLIMEX/ESP32-POE/tree/master/HARDWARE and tried to make sense of KiCad to extract the full assembly, but I keep running into export errors.
Is the full assembly of the ESP32-POE-ISO-EA-16MB available anywhere in .step and/or .stl without requiring knowledge of how to navigate KiCad?
#10
A64 / Re: Debian GNU/Linux 13 (Trixi...
Last post by LubOlimex - April 22, 2026, 08:24:17 AMI can't remember what required it, but maybe it is this hardware change in revision E:
"Serial resistors were added to the Ethernet PHY's Tx lines for better EMI suppression and RLC filters to the clock lines."
But there was a lot of routing changes also with placement of components to reduce EMI from the Ethernet, so it could be just the routing changed and required different delays.
"Serial resistors were added to the Ethernet PHY's Tx lines for better EMI suppression and RLC filters to the clock lines."
But there was a lot of routing changes also with placement of components to reduce EMI from the Ethernet, so it could be just the routing changed and required different delays.