- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
A20 / Re: DEBIAN 13 and up to date k...
Last post by LubOlimex - September 21, 2026, 09:12:31 AMMy advice for first test is to start with base image and after first boot make sure to run apt update and apt dist-upgrade. This requires internet connection.
I don't know where you got that about "/etc/os-release" but this is what I see:
We don't have a timeline for releases but images are good as long as they still have LTS.
The point of our Olimage Linux images is mainly to demonstrate the full capabilities of the hardware and in newer kernels and file systems we sometimes face problems getting one thing or another working properly. Even the newest releases boot fine, but getting audio and video output and other peripherals working is whole another thing.
For us, the point is the customer to download Olimage image, boot the board with it, and have all or almost all of the hardware working. While keeping everything as open source as possible and available for download. We don't focus on having the latest u-boot or kernel or file system.
I don't know where you got that about "/etc/os-release" but this is what I see:
Code Select
root@a20-olinuxino:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
We don't have a timeline for releases but images are good as long as they still have LTS.
The point of our Olimage Linux images is mainly to demonstrate the full capabilities of the hardware and in newer kernels and file systems we sometimes face problems getting one thing or another working properly. Even the newest releases boot fine, but getting audio and video output and other peripherals working is whole another thing.
For us, the point is the customer to download Olimage image, boot the board with it, and have all or almost all of the hardware working. While keeping everything as open source as possible and available for download. We don't focus on having the latest u-boot or kernel or file system.
#2
A20 / Re: difference between A20-OLi...
Last post by LubOlimex - September 21, 2026, 08:23:51 AMMainly the RAM size and the Ethernet speed as you wrote but also:
- LIME is 6-layer PCB, LIME2 is 8-layer PCB;
- GPIO and LCD connectors have different layouts between the two boards, so shield boards like LIME2-SD and LIME2-SHIELD are only compatible with A20-OLinuXino-LIME2.
- LIME is 6-layer PCB, LIME2 is 8-layer PCB;
- GPIO and LCD connectors have different layouts between the two boards, so shield boards like LIME2-SD and LIME2-SHIELD are only compatible with A20-OLinuXino-LIME2.
#3
A20 / DEBIAN 13 and up to date kerne...
Last post by oly - September 20, 2026, 11:46:37 AMHi here,
As mentionned here, Debian 12 (Bookworm) became EOL by end of 2026-07.
When Olimex will make a Debian 13 image available ?
Moreover, what about using such an old version of the Linux Kernel in the last published Olimex Debian 12 Image ? Any fresher one to come ?
EDIT:
I just dd on a SD Card, the so called image : A20-OLinuXino-bookworm-minimal-20260323-113959.img
The /etc/os-release file contains this informations :
wich is consistant with the mentionned kernel version, but not with the image file name.
What is the point of this strange settings ?
As mentionned here, Debian 12 (Bookworm) became EOL by end of 2026-07.
When Olimex will make a Debian 13 image available ?
Moreover, what about using such an old version of the Linux Kernel in the last published Olimex Debian 12 Image ? Any fresher one to come ?
EDIT:
I just dd on a SD Card, the so called image : A20-OLinuXino-bookworm-minimal-20260323-113959.img
The /etc/os-release file contains this informations :
Code Select
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
(...)
wich is consistant with the mentionned kernel version, but not with the image file name.
What is the point of this strange settings ?
#4
A20 / difference between A20-OLinuXi...
Last post by oeren - September 19, 2026, 02:12:33 PMIs only difference between A20-OLinuXino-LIME and A20-OLinuXino-LIME2 size of ram and speed of ethernet? Thank you.
#5
A20 / Re: update to Debian 12 (Bookw...
Last post by oly - September 19, 2026, 12:06:01 PMQuote from: gregh on April 06, 2026, 05:23:24 PMIt seems that there are Olimex bookworm images now:
https://images.olimex.com/release/a20/
It also seems that they contain only the old kernel versions from Bullseye:
https://repository.olimex.com/dists/bookworm/main/binary-armhf/Packages
How secure are those old kernels?
https://www.cybersecurity-help.cz/vdb/soft/linux_foundation/linux_kernel/5.15.105/
https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.105
#6
New Product Ideas / Re: can a lime 2 or pico 2 xxl...
Last post by Roman - September 09, 2026, 11:16:28 AMI couldn't find a specification, but, looking at their marketing materials, it appears that the Open Printer project implements the control module as a HAT on top of a Raspberry Pi Zero W and tailors the shape of the control module to accommodate the board of that particular size. Assuming that it is the case, it sets constraints on what the board must be. I doubt that Open Printer will want to adapt their design, even in a future iteration of their printer, to accommodate the shape of one of Olimex boards, which are comparably less widespread.
Olimex doesn't sell a drop-in replacement for Raspberry Pi Zero. Olimex boards are typically larger with more interfaces and are not pin-compatible with that board. Also, the market is already crowded with Raspberry Pi Zero clones, so I assume that it is hard to justify developing yet another one.
Unfortunately, all the ARM-based clones of the board that I am aware of require some binary blobs to boot.
However, there is an existing product on the market from another manufacturer that you may consider. There is a pin-compatible board in the same form factor as Raspberry Pi Zero, which is known to boot without proprietary blobs in uboot and in the Linux kernel, and on which it should be possible to run CUPS. There are several caveats to keep in mind. It is based on Allwinner D1, and thus, is RISC-V, not ARM. Also, I could only find versions with built-in Wi-Fi, which is not expected to work without a blob. But the onboard WiFi module could be kept uninitialized, or, alternatively, desoldered completely. So, it can be used entirely with free software. And it should be possible to adapt it for use in Open Printer.
Speaking of Wi-Fi. Open Printer only lists two options to connect the printer: either over USB Type-C directly to a computer or over Wi-Fi. They left Ethernet out, so one will have to write a USB driver for the board and connect the printer to another computer. That another computer could be an Olimex board, but it does not require any customization by Olimex to work.
Considering the above, it probably makes little sense for Olimex to get interested in Open Printer at this point.
Olimex doesn't sell a drop-in replacement for Raspberry Pi Zero. Olimex boards are typically larger with more interfaces and are not pin-compatible with that board. Also, the market is already crowded with Raspberry Pi Zero clones, so I assume that it is hard to justify developing yet another one.
Unfortunately, all the ARM-based clones of the board that I am aware of require some binary blobs to boot.
However, there is an existing product on the market from another manufacturer that you may consider. There is a pin-compatible board in the same form factor as Raspberry Pi Zero, which is known to boot without proprietary blobs in uboot and in the Linux kernel, and on which it should be possible to run CUPS. There are several caveats to keep in mind. It is based on Allwinner D1, and thus, is RISC-V, not ARM. Also, I could only find versions with built-in Wi-Fi, which is not expected to work without a blob. But the onboard WiFi module could be kept uninitialized, or, alternatively, desoldered completely. So, it can be used entirely with free software. And it should be possible to adapt it for use in Open Printer.
Speaking of Wi-Fi. Open Printer only lists two options to connect the printer: either over USB Type-C directly to a computer or over Wi-Fi. They left Ethernet out, so one will have to write a USB driver for the board and connect the printer to another computer. That another computer could be an Olimex board, but it does not require any customization by Olimex to work.
Considering the above, it probably makes little sense for Olimex to get interested in Open Printer at this point.
#7
A20 / Re: Working Linux driver for U...
Last post by sasha2002 - September 08, 2026, 02:25:09 PMChipset info :
#8
ESP32 / Works! Olimex esp32-poe-iso(lx...
Last post by mihaiadrian - September 06, 2026, 10:27:09 PMSucceed doing a local voice intercom with Olimex esp32-poe-iso(lx6) as primary and ESP32-S3-DevKit-Lipo(lx7) as DSP with ECHO cancellation . The voice communication is full duplex. Initially tried without the lx7 and was impossible to make a full duplex communication due to big noise echo. So, lx7 is doing a good job in canceling the echo.
#9
New Products release / Neo6502kbd all in one neo6502 ...
Last post by olimex - September 04, 2026, 02:11:45 PMDo you remember Karateka, Lode Runner, and Cross Fire on the Apple ][? Our Neo6502kbd brings it all back — an all-in-one retro computer with a real 6502 processor which you can connect to your home TV https://olimex.wordpress.com/2026/09/04/new-open-source-hardware-variant-of-neo6502-now-includes-keyboard-4-usb-hosts-uext-power-switch-and-usb-c-for-power-and-programming-all-in-one-keyboard-body/
#retrocomputing #retrogaming #w65c02
#retrocomputing #retrogaming #w65c02
#10
A20 / Re: Working Linux driver for U...
Last post by sasha2002 - September 01, 2026, 11:15:48 AMCode Select
root@a20-olinuxino:~# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 350b:f179 ZTOP ztop CDROM
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@a20-olinuxino:~# eject /dev/sr0
lsusb
dmesg | grep -Ei '350b|9612|f179|ztop|zt9612|firmware|wlan|wifi|usb' | tail -120
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 1.828739] usbcore: registered new interface driver usbhid
[ 1.828749] usbhid: USB HID core driver
[ 2.032252] ehci-platform 1c14000.usb: EHCI Host Controller
[ 2.032504] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[ 2.033061] ehci-platform 1c14000.usb: irq 42, io mem 0x01c14000
[ 2.048376] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[ 2.048798] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.048814] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.048824] usb usb1: Product: EHCI Host Controller
[ 2.048832] usb usb1: Manufacturer: Linux 5.10.180-olimex ehci_hcd
[ 2.048840] usb usb1: SerialNumber: 1c14000.usb
[ 2.049933] hub 1-0:1.0: USB hub found
[ 2.051596] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 2.051641] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[ 2.052131] ehci-platform 1c1c000.usb: irq 47, io mem 0x01c1c000
[ 2.064494] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 2.065002] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.065017] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.065027] usb usb2: Product: EHCI Host Controller
[ 2.065035] usb usb2: Manufacturer: Linux 5.10.180-olimex ehci_hcd
[ 2.065043] usb usb2: SerialNumber: 1c1c000.usb
[ 2.066353] hub 2-0:1.0: USB hub found
[ 2.068075] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[ 2.068118] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[ 2.068768] ohci-platform 1c14400.usb: irq 43, io mem 0x01c14400
[ 2.132724] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.132749] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.132759] usb usb3: Product: Generic Platform OHCI controller
[ 2.132767] usb usb3: Manufacturer: Linux 5.10.180-olimex ohci_hcd
[ 2.132776] usb usb3: SerialNumber: 1c14400.usb
[ 2.133686] hub 3-0:1.0: USB hub found
[ 2.135445] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 2.135491] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[ 2.136113] ohci-platform 1c1c400.usb: irq 48, io mem 0x01c1c400
[ 2.196737] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.196755] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.196765] usb usb4: Product: Generic Platform OHCI controller
[ 2.196774] usb usb4: Manufacturer: Linux 5.10.180-olimex ohci_hcd
[ 2.196781] usb usb4: SerialNumber: 1c1c400.usb
[ 2.197750] hub 4-0:1.0: USB hub found
[ 2.199591] usb_phy_generic usb_phy_generic.0.auto: supply vcc not found, using dummy regulator
[ 2.199874] usb_phy_generic usb_phy_generic.0.auto: dummy supplies not allowed for exclusive requests
[ 2.201177] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[ 2.201225] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[ 2.201767] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.201782] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.201791] usb usb5: Product: MUSB HDRC host driver
[ 2.201799] usb usb5: Manufacturer: Linux 5.10.180-olimex musb-hcd
[ 2.201807] usb usb5: SerialNumber: musb-hdrc.1.auto
[ 2.202741] hub 5-0:1.0: USB hub found
[ 2.388525] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 2.546304] usb 2-1: New USB device found, idVendor=350b, idProduct=f179, bcdDevice= 2.00
[ 2.546329] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.546341] usb 2-1: Product: ztop CDROM
[ 2.546350] usb 2-1: Manufacturer: ZTOP
[ 2.548251] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2.549888] scsi host1: usb-storage 2-1:1.0
[ 2.564570] usb 3-1: new low-speed USB device number 2 using ohci-platform
[ 2.793204] usb 3-1: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
[ 2.793230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.793241] usb 3-1: Product: USB Keyboard
[ 2.793250] usb 3-1: Manufacturer: Logitech
[ 2.807901] input: Logitech USB Keyboard as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.0/0003:046D:C31C.0001/input/input1
[ 2.865050] hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-1c14400.usb-1/input0
[ 2.878423] input: Logitech USB Keyboard Consumer Control as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.1/0003:046D:C31C.0002/input/input2
[ 2.937519] input: Logitech USB Keyboard System Control as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.1/0003:046D:C31C.0002/input/input3
[ 2.938166] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-1c14400.usb-1/input1
[ 3.562006] scsi 1:0:0:0: CD-ROM S9612USB CDROM AUTORUN V1.0 PQ: 0 ANSI: 0 CCS
[ 3.704440] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.016501] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.316520] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.616554] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.912531] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.212368] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.512348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.812345] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 6.307796] usbcore: registered new interface driver uas
[ 6.520386] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 6.820356] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.120347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.420343] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.712348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.012347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.312348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.612345] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.120384] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.420352] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.720344] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.020347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.312351] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.612346] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.912344] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 11.212350] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 14.961210] systemd[1]: Reached target paths.target - Path Units.
[ 20.084539] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 20.480511] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 20.792520] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.100487] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.400510] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.692534] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.008524] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.308484] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.616537] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.932555] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.232540] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.532594] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.832491] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.152041] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.472461] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.776525] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 25.080624] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 25.948531] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.248479] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.548463] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.848439] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.144401] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.448399] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.752372] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 28.060371] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 921.293484] usb 2-1: USB disconnect, device number 2
root@a20-olinuxino:~# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 350b:9612 ZTOP 802.11ax 2x2 WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@a20-olinuxino:~#