Screen 2
1 Like
Hi Rex！I have issue about RTC.I buy a CR1220 battery and connect it to board like this picture. But my uconsole show this log when I put into sudo he lock -w I think the reason is uconsole cannot find RTC ,but I don’t know why.Thx
Can you check your kernel messages to see if the RTC was detected in the first place?
try
dmesg | grep rtc
you should see something like this
rtc-pcf85063 10-0051: registered as rtc0
my RTC is on the AIOv2. if you are using that, it should be similar outputs.
If you don’t see it, then check if the battery is inserted the right way, coz its not detected at the hardware layer. Once you confirm that the kernel sees it, hwclock command should work.
BTW, just FYI… rex maintains his kernels and packages for the uconsole for the community… but he doesn’t do the AIO hardware. vileer from hackergadgets does that. this seems to be more a hardware related thing as there are different RTC chips. 
I updated the readme for this here for with clearer instructions and a method for auto start.
@vineer if you wanna pull this, I already put in the request.
This looks like RTC of AIO board.But
Doesn’t CM5 also have RTC? I connect battery to back of adaptboard.
bored99 <notifications@clockworkpi.discoursemail.com>于2026年1月18日 周日下午11:11写道：
1 Like
the RTC on CM5 would require its own battery connected to the adapter board. if you have placed a battery in the AIO, then you would be using the AIO RTC.
Given that the hardware is detected, the odd issues would be the power messages that you are seeing. Try setting the time first to see if it works.
Do note that
- you need
sudofor all commands. - this assumes that the output of your “date” command is correct
the commands and its output should be something like this
$ date
Mon 19 Jan 2026 04:02:58 PM +08
$ sudo hwclock --set --date "$(date)"
$ sudo hwclock -r
2026-01-19 16:05:52.163701+08:00
But My cr1220 battery can’t fit. It’s very loose because the battery is too thin and the battery slot is too thick.The battery has a suitable width but an unsuitable thickness
bored99 <notifications@clockworkpi.discoursemail.com> 于2026年1月19日周一 16:16写道：
i think the CR1220 is correct. i checked the screenshots from the hackergadgets page.
you can just put a small coin or some aluminium foil to help increase the thickness. it doesn’t need to be too tight.. it just needs to conduct electricity and have enough power.
also make sure that you did setup the RTC in the config.
check the link HackerGadgets uConsole AIO V1/V2 Extension Board setup Guide – Hacker Gadgets and see the RTC section.
make sure you have this to disable the onboard RTC
# Clock CM5
# disable the CM5 internal RTC
dtparam=rtc=off
# i2c_csi_dsi0, remap the i2c0 to GPIO38/39 on CM5
dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi0
1 Like
Thank you for your feedback.
Now SDR++ is working, Tar1090 is working, pyGPSclient is working, and USB is working as well. Meshtastic is the only thing that is still not working. Could I send you my config.txt /yaml file so you can check if there is any mistake in it? Thank you very much.
1 Like
My GPS or LORA is not working but SDR works Fine
I seen some screenshots that they had multiple serial port not sure what to do
My GPS or LORA is not working but SDR works Fine
I seen some screenshots that they had multiple serial port not sure what to do
I got the LORA to work with this
sudo systemctl restart meshtasticd
but currently still investigating GPS
for the AIO v2,
GitHub - hackergadgets/aiov2_ctl: This is a client for controll the aiov2 - not having this tripped me up for a bit… activate the on boot option.
then.. remember that on boot , meshtasticd service attempts to run and fails… so… you need to enable LORA and restart the service for it to work… might want to write a bash script to do it..
- in meshtastic - add your png maps to .portduino/default/map - then put in the x/y/z map folders like a t-deck - i tried maps.. but the map selection drop down wasn’t coming up for me like it does on t-deck
-on CM5 for pyGPSClient ya gotta do the second option - then click the usb/uart button…
-for my CM5 on SDR had to go do the new audio sink
really what it comes down to is.. follow the original post clearly and doesn’t skip any steps…
2 Likes
I did a clean install on another micro SD Card and everything works,
So on my main SD card the /dev/ttyS0 is not available to select but on my other SD ttyS0 has it with a clean install it appears and the GPS works.
I got to figure out how to add it on my main install,
Anyone have a clue?
I Fixed the Missing tty by creating it using this command on my CM4 then i reboot
run with sudo
mknod /dev/ttyS0 c 4 64
chmod 666 /dev/ttyS0
reboot
# these is my config settings
# /boot/firmware/config.txt
[pi4]
dtparam=spi=on
dtoverlay=i2c-rtc,pcf85063a
#dtoverlay=clockworkpi-devterm
dtoverlay=clockworkpi-uconsole
dtoverlay=vc4-kms-v3d-pi4,cma-384
gpu_mem=384
dtoverlay=spi1-1cs
enable_uart=1
im glade it’s all working i just need to add maps to meshtastic
I am getting this issue when trying to run the command to start the aiov2 gui
I have installed the controller from the HackerGadgets GitHub page but am getting the error. Installed of fresh copy of bookworm. Any ideas? Thanks
It’s telling you what’s missing and how to fix it.
1 Like
yes sir it is…and I did that in the example. I copied and pasted the cmd in and it told me I already had the most current version. Am I missing something?
Try installing the dependency with pip, raspberry pi does some weird stuff with their version of Debian and Python and it might not be picking up qt6 that’s installed.
After I modified this configuration, the screen can’t be used. May I ask whether dtoverlay should write the original configuration annotation to this line or add this line on the original basis?
bored99 <notifications@clockworkpi.discoursemail.com>于2026年1月19日 周一下午8:51写道：