- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
A20 / Re: DEBIAN 13 and up to date k...
Last post by oly - September 23, 2026, 09:15:00 PMI apologize. While my SD card was physically writable, it was not in fact and without warning. I dd the image on another one.
Now it is correct :
Now it is correct :
Code Select
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/" #2
ARDUINO / Re: NB-IoT-BC660H-ANT Rev D — ...
Last post by LubOlimex - September 23, 2026, 09:29:17 AMThis is not very surprising since we just recently switched to revision E of NB-IoT-BC660 boards. Boards from hardware revision E has different print on the PCB that says "NB-IoT-BC660 Rev. E" at the bottom. Based on your description I believe you received the hardware revision D board.
Both revision D and revision E designs use the same main chip BC660K-GL.
Revision D still uses the regulators. Power consumption in deep sleep is the main difference between revisions. The current consumption in deep sleep is minimum around 125uA when powered from external power source and around 85uA when powered from battery. The extra current comes mainly from the AP1231 regulator and two TXB0108 level translators. Aside from that they behave the same. Revision D board is still completely fine.
Comparing revision D to revision B the changes are unnoticeable for the customer (one is not even visible in the schematic). There are only two changes:
1. Revision C:
Changed the the sim card holder with SIMNANO-6P-1.3H, this required some other components to be moved to fit.
2. Revision D:
Updated the module package for better soldering.
My advice for future purchases is to ask beforehand about the hardware revision available.
Both revision D and revision E designs use the same main chip BC660K-GL.
Revision D still uses the regulators. Power consumption in deep sleep is the main difference between revisions. The current consumption in deep sleep is minimum around 125uA when powered from external power source and around 85uA when powered from battery. The extra current comes mainly from the AP1231 regulator and two TXB0108 level translators. Aside from that they behave the same. Revision D board is still completely fine.
Comparing revision D to revision B the changes are unnoticeable for the customer (one is not even visible in the schematic). There are only two changes:
1. Revision C:
Changed the the sim card holder with SIMNANO-6P-1.3H, this required some other components to be moved to fit.
2. Revision D:
Updated the module package for better soldering.
My advice for future purchases is to ask beforehand about the hardware revision available.
#3
ARDUINO / NB-IoT-BC660H-ANT Rev D — powe...
Last post by Dijkmeneer - September 22, 2026, 05:10:05 PMHi all,
I'm posting this in the Arduino section since I found an older thread here about the NB-IoT BC66 module (the "Security mode change issue" thread) where LubOlimex replied — figured this was the closest existing home for NB-IoT-related questions since there doesn't seem to be a dedicated category.
I recently got an NB-IoT-BC660H-ANT board via DigiKey. The PCB silkscreen reads "Rev D," and the module soldered on it is a BC660K-GL (confirmed by reading the chip marking directly). The board also has a populated NETLIGHT LED, and the silkscreen at that pin position is labeled NETLIGHT rather than GPIO6, both of which match BC66's pin function at that position rather than BC660K-GL's. I'm assuming the board layout was carried over unchanged from before the BC66→BC660K-GL module swap (Olimex's blog confirms that transition happened), but I'm curious whether that LED still does anything meaningful with BC660K-GL populated, since that pin is just GPIO6 on this chip rather than a dedicated network-status output.
Separately — the thing I haven't been able to figure out: Olimex's product page FAQ mentions that starting with hardware revision E, the design was optimized for low-power operation by removing a voltage translator and regulator present in older revisions.
Does Rev D already include that optimization, or does it still have the older, higher-current design?
Is there any chance someone could share the Rev D schematic? I've only found Rev B and Rev E published online.
I'm building a battery-powered prototype, so the sleep-current characteristics of my specific board matter for planning battery life.
Thanks in advance for any help!
I'm posting this in the Arduino section since I found an older thread here about the NB-IoT BC66 module (the "Security mode change issue" thread) where LubOlimex replied — figured this was the closest existing home for NB-IoT-related questions since there doesn't seem to be a dedicated category.
I recently got an NB-IoT-BC660H-ANT board via DigiKey. The PCB silkscreen reads "Rev D," and the module soldered on it is a BC660K-GL (confirmed by reading the chip marking directly). The board also has a populated NETLIGHT LED, and the silkscreen at that pin position is labeled NETLIGHT rather than GPIO6, both of which match BC66's pin function at that position rather than BC660K-GL's. I'm assuming the board layout was carried over unchanged from before the BC66→BC660K-GL module swap (Olimex's blog confirms that transition happened), but I'm curious whether that LED still does anything meaningful with BC660K-GL populated, since that pin is just GPIO6 on this chip rather than a dedicated network-status output.
Separately — the thing I haven't been able to figure out: Olimex's product page FAQ mentions that starting with hardware revision E, the design was optimized for low-power operation by removing a voltage translator and regulator present in older revisions.
Does Rev D already include that optimization, or does it still have the older, higher-current design?
Is there any chance someone could share the Rev D schematic? I've only found Rev B and Rev E published online.
I'm building a battery-powered prototype, so the sleep-current characteristics of my specific board matter for planning battery life.
Thanks in advance for any help!
#4
A20 / Re: DEBIAN 13 and up to date k...
Last post by LubOlimex - September 22, 2026, 04:32:13 PMI cannot confirm your findings. I tested both A64-OLinuXino-bookworm-minimal-20260630-091355.img and images and A64-OLinuXino-bookworm-base-20260630-091355.img I get only:
> May be Olimex could maintain two branches of Olimage linux images, one with a fully operational hardware management, one with less proposed peripheral hardware but a more up-to-date OS and kernel versions
You can just run the latest distribution and it will boot, refer to this: https://wiki.debian.org/InstallingDebianOn/Allwinner
I understand the desire for bleeding edge images and so but at the moment this is what we can provide. Unfortunately, not a lot of contribution to our software efforts and we do all the heavy lifting. Of course, our work can be used for free as basis if you wish to build own images.
Code Select
root@a64-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/"
root@a64-olinuxino:~# cat /etc/debian_version
12.14
root@a64-olinuxino:~# ls -l /etc/os-release
lrwxrwxrwx 1 root root 21 May 8 17:15 /etc/os-release -> ../usr/lib/os-release
root@a64-olinuxino:~#
> May be Olimex could maintain two branches of Olimage linux images, one with a fully operational hardware management, one with less proposed peripheral hardware but a more up-to-date OS and kernel versions
You can just run the latest distribution and it will boot, refer to this: https://wiki.debian.org/InstallingDebianOn/Allwinner
I understand the desire for bleeding edge images and so but at the moment this is what we can provide. Unfortunately, not a lot of contribution to our software efforts and we do all the heavy lifting. Of course, our work can be used for free as basis if you wish to build own images.
#5
A20 / Re: DEBIAN 13 and up to date k...
Last post by oly - September 22, 2026, 01:50:07 PMHello,
Thank you for your answers.
The /etc/os-release file in the A64-OLinuXino-bookworm-base-20260630-091355.img displays information for VERSION="12 (bookworm)".
The one in the A64-OLinuXino-bookworm-minimal-20260630-091355.img displays information shown in my initial post.
I understand your marketing approach, but I draw your attention on the fact that, nowadays, state of the art security features should be part of IT products line.
Thus, using the most stable kernel version in a production environment seems not optional.
May be Olimex could maintain two branches of Olimage linux images, one with a fully operational hardware management, one with less proposed peripheral hardware but a more up-to-date OS and kernel versions ?
So, customers could choose regarding their needs and product constraints.
Thank you for your answers.
Quote from: LubOlimex on 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:Code Selectroot@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/"
The /etc/os-release file in the A64-OLinuXino-bookworm-base-20260630-091355.img displays information for VERSION="12 (bookworm)".
The one in the A64-OLinuXino-bookworm-minimal-20260630-091355.img displays information shown in my initial post.
Quote from: LubOlimex on September 21, 2026, 09:12:31 AMWe 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 understand your marketing approach, but I draw your attention on the fact that, nowadays, state of the art security features should be part of IT products line.
Thus, using the most stable kernel version in a production environment seems not optional.
May be Olimex could maintain two branches of Olimage linux images, one with a fully operational hardware management, one with less proposed peripheral hardware but a more up-to-date OS and kernel versions ?
So, customers could choose regarding their needs and product constraints.
#6
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.
#7
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.
#8
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 ?
#9
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.
#10
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