Does it have to be an ultra-slim one?
Where did you get that battery holder? Can you simply open and close it? What’s the switch for?
So many questions… 
The RTC battery connector (JST SH 1.0mm) for the Raspberry Pi 5 didn’t fit, so I did some research and found that the MOLEX 51146 is compatible.
The product description says “ultra-thin,” and I’m not sure if other types exist, but it won’t fit unless it’s thin.
https://ja.aliexpress.com/item/1005011557685518.html
I used a battery holder I already had on hand.
You can find similar products on sites like AliExpress.
The holder comes with a switch, but I didn’t need it for this application. (It stays ON all the time.)
https://ja.aliexpress.com/item/1005006365822576.html
3 Likes
This is a rather nice one. It has the right connector on it and with a bit of blue tack, it sits in an unused space.
3 Likes
Could you please share a link?
I have my AIO installed, just the kit that gives me the extra ports and the NVME battery holder, but no matter what I do or what NVME drive I try, the NVME is not detected at all.
I tried the dtparam=pciex1=on and dtparam=pciex1 and nothing.
Tried different drives, nothing. LSPCI does not report anything, and LSBLK does not report anything. I have seated and reseated the ribbon cable multiple times, made sure my eeprom is updated but for whatever reason the NVME is just not detected at all.
I don’t know what to look for in dmesg, either.
Red light is on next to the drive, confirmed the drive works in my laptop, tried a different drive that I also know works in my laptop, I feel like for whatever reason it’s just not detecting the NVME components.
This is on a uConsole with a CM4
My guess is the problem is that you’re using a CM4. I don’t think it can do PCIe, only the CM5 can. I think the NVMe works by wiring the PCIe cable to the CM5’s internal PCIe handling. (Somebody correct me if I’m guessing this incorrectly!) Seems like I was wrong, see others responding below!
I had the same issue (CM5).
- Did you inserted a battery and is it charged?
The NVME does not have enough energy without. It will not be detected or at best be flacky.
Yes, and I just tested it with a fresh flash of Debian Trixie and Trixie sees it now, so it’s something to do with Debian Bookworm.
has anyone gotten PCIe/NVMe actually working on Radxa CM5 (not RPi CM5) specifically? Last confirmed report I could find is gaze13’s post from March 2026 with LTSSM stuck at 0x3 after 21 different approaches. Wondering if this got resolved since, before I commit to using a Samsung 970 EVO Pro 1TB as the main drive on Radxa CM5.
Can you post a link to this please? 
Not sure if these are the same from Toml, but I just ordered these. Specs seem to match.
I took out the smd and put in a 3.6k and it’s still not working.. What now? Is bluetooth not working normal?
Have you enabled the power of the internal USB-C?
Yes wifi is working. When I scan bt wifi drops out.
Is it normal or broken? I tried everything I can. Any options?
I don’t often use Bluetooth on the AC1200 Wi-Fi card. I will try it later to see what happens.
1 Like
Is anyone able to help me trying to install the GUI tray for AIO V2 but I keep getting the errors and don’t seem to install.
@AceMedia can you help on this one using latest Trixie.
Just tried again but keep getting the same error this is really annoying as i done this before and it worked. Any help would be very apreciated as i need to get this AIO v2 GUI working to make my life esier enabling stuff on and off.
@vileer: Request for pinouts for the Radxa CM5 adapter and the AIO v2, and a LoRa question
Hi HackerGadgets team,
thanks you so much for the boards. I’m running a Radxa CM5 in the uConsole with your Radxa CM5 adapter and the AIO v2 on a mainline kernel. GPS, RTL-SDR, the USB hub, Ethernet and the RTC work. LoRa does not, and I’d like to understand why rather than guess.
What I measured with a multimeter, all boards unpowered:
- AIO v2: HT-RA62 pad 13 (MISO) has continuity to mPCIe finger 20; the other module lines to fingers 22 (MOSI), 24 (SCK), 18 (NSS), 30 (BUSY), 34 (DIO1) and 32 (RST).
- Adapter on a uConsole mainboard, no module fitted: mPCIe finger 20 has continuity to Connector 1 pin 26; fingers 26/28 to pins 55/51, 36 to pin 48, 50/52 to pins 82/80.
- Radxa’s CM5 pinout sheet lists Connector 1 pin 26 as NC.
Over SPI4 on the Radxa the SX1262 answers every read with 0xFF, and a scan of the SoC’s free GPIOs while clocking the chip found no line following MISO.
I cannot see what else may be on those nets, and I may well be missing something in how the adapter routes this line. Could you tell me where the LoRa MISO is meant to arrive at the module on the Radxa CM5 adapter, and whether LoRa is expected to work with this combination? If it works for anyone on a Radxa CM5, the adapter and AIO revisions would help me compare.
Pinouts. Could you publish, or share here, the pinout tables for both boards?
- Radxa CM5 adapter: SO-DIMM pin → module connector position for thts GPIO28–45), the fan header PWM, the RPITX header, and the PCIe,USB 3.0 and CSI paths. You’ve already said the PCIe FPC follows the Pi 5 pinout, which helped a lot.
- AIO v2: which mPCIe finger carries each signal, the SX1262 lines,X/RX and PPS, and the four rail enables, with the board revision.
Thank you so much and all the best,
- alexg
1 Like
