April 27, 2026, 03:42:37 PM

Recent posts

#1
ESP32 / Re: Board "olimex_esp32-c5-dev...
Last post by LubOlimex - Today at 10:52:19 AM
Thank you for the working version. I am sure people would find it helpful.

If it is not much of a trouble can you test what happens if you change:

"f_flash": "80000000L",

with

"f_boot": "40000000L",

instead.

#2
A64 / Re: Debian GNU/Linux 13 (Trixi...
Last post by LubOlimex - Today at 08:53:29 AM
1. If we could do it, we would but as it is we focused solely on Olimage Linux, the main problem is the audio and video support. They contain some blobs that will never be accepted by mainline and when a customer buys a board with HDMI connector and audio jack he expects to see video output and audio output.

2. Yes, latest image should work with all older revisions of the board.

3. We do that in our images. We read the EEPROM. EEPROM is prepared during testing.

4. There is but maintainers are lazy and it is probably incomplete: https://images.olimex.com/changelog.txt

However, all changes can be seen at the GitHub sources for the u-boot, kernel, etc. All are available. Check chapter 5 of the manual "5. Build information and sources" to find the proper links with sources:

https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf
#3
ESP32 / Re: ESP32-POE-ISO-EA-16MB full...
Last post by LubOlimex - Today at 08:20:05 AM
These are metal boxes and we don't have CAD models from them, they are manufactured by 3d party manufacturer. We have this plastic box for LIME2 and battery which can be used for LIME too:

https://github.com/OLIMEX/OLINUXINO/tree/master/BOXES/LIME2-PLASTIC-BOX

Also there are many free 3D designs for boxes for LIME board if you search online in yeggi or pritables:

https://www.yeggi.com/q/olimex+a20+olinuxino+lime/

https://www.printables.com/model/1149553-limebox-remix-olimex-olinuxino-lime-a10
#4
A64 / Re: Debian GNU/Linux 13 (Trixi...
Last post by Roman - April 26, 2026, 03:56:21 PM
I asked on linux-sunxi mailing list whether the changes could be mainlined. Could you please comment on the following questions?

  • Does Olimex work towards or plan mainlining the changes?
  • Are the current devicetrees in Olimex's image compatible with all revisions of the board, including backward compatible with the older revisions? Which revisions of A64-OLinuXino are compatible with the current image?
  • Assuming that the choice of a devicetree depends on the revision of the board, is there a way to determine the revision of the board at runtime, probably by a difference in hardware?
  • Is there a changelog for software changes between revisions of the board in addition to the hardware revision changes log, which is at "HARDWARE/A64-OLinuXino" in Olimex's "OLINUXINO" GitHub repository?
#5
ESP32 / Re: ESP32-POE-ISO-EA-16MB full...
Last post by faraz - April 26, 2026, 11:12:51 AM
Are there step files or CAD models for this one as well?

I would like to 3D print them

https://www.olimex.com/Products/OLinuXino/BOXES/BOX-LIME/

I couldnt find them on the website.
#6
A64 / Re: Bookworm upgrade availabil...
Last post by mossroy - April 25, 2026, 01:27:30 PM
Many 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.
#7
New Product Ideas / MIPI-HDMI Revision for I2S Sup...
Last post by ramblecube - April 25, 2026, 12:14:27 PM
Hello there  ;D

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
#8
ESP32 / Re: Board "olimex_esp32-c5-dev...
Last post by winfried - April 25, 2026, 11:45:25 AM
Thanks 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:

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:
*** 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:
    "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:

{
  "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:

[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
#9
A64 / Re: Bookworm upgrade availabil...
Last post by ilario - April 24, 2026, 04:32:40 PM
Have you seen that Olimex released a Debian 12 image for A64-Olinuxino in March? I did not try it yet though...
#10
A64 / Re: Bookworm upgrade availabil...
Last post by mossroy - April 24, 2026, 04:20:45 PM
I'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.