I have a small collection of X6, A9 and X5 mini spy cams with main chips from Taixin, Beken and XRadioTech. One commonality is the 18-pin FFC (flexible flat cable) ZIF (zero insertion force) connector that the cam modules are connected to the main PCB with. From looking at strings in the...

And from a Tuya mini doorbell (not this one but very similar). Contacts are on the opposite side of ribbon for this one as the cam points back through a hole in the PCB. GalaxyCore GC0309 SI2309 ST2309 -M7-39-V1 Init Code: TextLog in, to see the code

from a new BK7252UQN48 device GalaxyCore GC0312 STD-8136V0 STD-8136VO Init Code: TextLog in, to see the code

from user @LuckyLuca | see GalaxyCore GC0328C YD-A13-GA19-18pin Init Code: TextLog in, to see the code GalaxyCore GC0328C 0328C-A Init Code: TextLog in, to see the code

SuperPix SP0828 S282-2156V1 Init Code: TextLog in, to see the code Added after 30 [minutes]: GalaxyCore GC0311 X5-G11-2365V1 Init Code: TextLog in, to see the code Added after 17 [minutes]:GalaxyCore GC0329 XLT-X5-0329-V1.0 Init Code: TextLog in, to see the code

Hynix HI704 LT1888-704 V1.0 LT1889(?) Init Code: TextLog in, to see the code

GalaxyCore GC0312 X5-G12-236V1 Init Code: TextLog in, to see the code

SuperPix SP0A20 A9-P20-2295V1 Init Code: TextLog in, to see the code

GalaxyCore GC0328C M9-G28-2527V1 Init Code: TextLog in, to see the code

GalaxyCore GC0328C - LT033-A9-0328C-V1 Code: TextLog in, to see the code

GalaxyCore GC0329 LT010-A9-0329-V4 Code: TextLog in, to see the code

Identifying Mini Cam Modules: Hynix HI704 - GalaxyCore GC0329,GC0309,GC0310 - SuperPix SP0A19,SP0828

divadiow 5421 12

Report a violation of the law

Reply | New topic

XF16 boot logs identify GC0329 camera module
#1 21549325 14 May 2025 21:42

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author

XF16 boot logs identify GC0329 camera module
Post #1 21549325 14 May 2025 21:42

I have a small collection of X6, A9 and X5 mini spy cams with main chips from Taixin, Beken and XRadioTech. One commonality is the 18-pin FFC (flexible flat cable) ZIF (zero insertion force) connector that the cam modules are connected to the main PCB with.

From looking at strings in the firmware dump of an XRadio XF16 chip it seems the XF16 might support this list of cams:

Code: Text
Log in, to see the code

The XF16's uart log out is helpful enough to print which one it detects is connected. This presents a good opportunity to identify each cam, assuming the pins are the same. Often identifying text printed on the ribbon doesn't make it immediately obvious what make/model the cam is. Here'll I'll present pics and the relevant XF16 boot log to show initialisation. Maybe this will help others to identify their cameras. It is also a record for me of what I have.

GalaxyCore GC0329 DC-H8-G2 DC-H8-C2 9-1303V2

Init
Code: Text
Log in, to see the code

GalaxyCore GC0329 X5-G29-2364V1

Init
Code: Text
Log in, to see the code

GalaxyCore GC0310 LY023-A9-0310-V1 LT023-A9-0310-V1

Init
Code: Text
Log in, to see the code

Hynix HI704 DC-H8-704-6182V1 DC-H0-7040-6182V1

Code: Text
Log in, to see the code

SuperPix SP0A19 LT1757-OA-10 V1.0 LT1757-QA-19 V1.0

Init
Code: Text
Log in, to see the code

SuperPix SP0828 LT1888-0828(?) V1.0 L11888-0828(?)

Init
Code: Text
Log in, to see the code

SuperPix SP0828 HT12577-A9-B H12577-A9-8

Init
Code: Text
Log in, to see the code
eufyMake E1 - łatwa personalizacja za pomocą druku UV [sponsorowany]
ADVERTISEMENT
GC0309 detected in Tuya mini doorbell module
#2 21550528 16 May 2025 06:36

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (+1)

GC0309 detected in Tuya mini doorbell module
Post #2 21550528 16 May 2025 06:36

And from a Tuya mini doorbell (not this one but very similar). Contacts are on the opposite side of ribbon for this one as the cam points back through a hole in the PCB.

GalaxyCore GC0309 SI2309 ST2309 -M7-39-V1

Init
Code: Text
Log in, to see the code
GC0312 detected on BK7252UQN48 device
#3 21583310 18 Jun 2025 22:43

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

GC0312 detected on BK7252UQN48 device
Post #3 21583310 18 Jun 2025 22:43

from a new BK7252UQN48 device

GalaxyCore GC0312 STD-8136V0 STD-8136VO

Init
Code: Text
Log in, to see the code
ADVERTISEMENT
GC0328C module identified by init logs
#4 21607771 15 Jul 2025 18:49

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

GC0328C module identified by init logs
Post #4 21607771 15 Jul 2025 18:49

from user @LuckyLuca | see https://github.com/daniel-dona/beken7252-opencam/issues/16

GalaxyCore GC0328C YD-A13-GA19-18pin

Init
Code: Text
Log in, to see the code

GalaxyCore GC0328C 0328C-A

Init
Code: Text
Log in, to see the code
ADVERTISEMENT
SuperPix SP0828 init register dump
#5 21710596 05 Oct 2025 12:33

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

SuperPix SP0828 init register dump
Post #5 21710596 05 Oct 2025 12:33

SuperPix SP0828 S282-2156V1

Init
Code: Text
Log in, to see the code

Added after 30 [minutes]:

GalaxyCore GC0311 X5-G11-2365V1

Init
Code: Text
Log in, to see the code

Added after 17 [minutes]:

GalaxyCore GC0329 XLT-X5-0329-V1.0

Init
Code: Text
Log in, to see the code
HI704 chip ID read success 0x96
#6 21712521 06 Oct 2025 21:35

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (+1)

HI704 chip ID read success 0x96
Post #6 21712521 06 Oct 2025 21:35

Hynix HI704 LT1888-704 V1.0 LT1889(?)

Init
Code: Text
Log in, to see the code
GC0312 chip id read success on X5-G12-236V1
#7 21713076 07 Oct 2025 13:20

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

GC0312 chip id read success on X5-G12-236V1
Post #7 21713076 07 Oct 2025 13:20

GalaxyCore GC0312 X5-G12-236V1

Init
Code: Text
Log in, to see the code
SP0A20 sensor identified with 640×480 init logs
#8 21714889 09 Oct 2025 11:55

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

SP0A20 sensor identified with 640×480 init logs
Post #8 21714889 09 Oct 2025 11:55

SuperPix SP0A20 A9-P20-2295V1

Init
Code: Text
Log in, to see the code
ADVERTISEMENT
GC0328C identified by 0x9d sensor ID
#9 21721711 16 Oct 2025 08:12

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (+1)

GC0328C identified by 0x9d sensor ID
Post #9 21721711 16 Oct 2025 08:12

GalaxyCore GC0328C M9-G28-2527V1

Init
Code: Text
Log in, to see the code
GC0328C sensor identified with 640x480 init log
#10 21733459 27 Oct 2025 19:38

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (+1)

GC0328C sensor identified with 640x480 init log
Post #10 21733459 27 Oct 2025 19:38

GalaxyCore GC0328C - LT033-A9-0328C-V1

Code: Text
Log in, to see the code
GC0329 identified at 0x31 with 0xc0 sensor ID
#11 21741973 05 Nov 2025 08:14

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

GC0329 identified at 0x31 with 0xc0 sensor ID
Post #11 21741973 05 Nov 2025 08:14

GalaxyCore GC0329 LT010-A9-0329-V4

Code: Text
Log in, to see the code
GC0311 chip id read success at 0xbb
#12 21762384 25 Nov 2025 21:16

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

GC0311 chip id read success at 0xbb
Post #12 21762384 25 Nov 2025 21:16

GalaxyCore GC0311 LT1823-0311 V1.0-V1

Code: Text
Log in, to see the code
OV7690 identified by I2C readId 145
#13 21832957 08 Feb 2026 18:00

divadiow divadiow

Level 38

Posts: 5184

Help: 445

Rate: 912
Topic author Helpful post? (0)

OV7690 identified by I2C readId 145
Post #13 21832957 08 Feb 2026 18:00

OmniVision OV7690 H22136-A

Code: Text
Log in, to see the code
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Perplexity AI, Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply | New topic

Report a violation of the law

Topic summary

✨ The discussion identifies camera modules used in mini spy cams and doorbells by matching firmware/UART boot logs against sensor driver detection strings. Several modules are confirmed, including GalaxyCore GC0309, GC0312, GC0328C, GC0329, GC0311, SuperPix SP0828, SP0A20, Hynix HI704, and OmniVision OV7690. Logs show sensor ID reads, initialization sequences, and successful auto-detection on BK7252/XRadio-based devices using 18-pin FFC/ZIF-connected camera modules. The thread builds a reference list of compatible sensors for XRadio XF16 and related mini camera platforms, helping identify unknown ribbon-connected modules by chip ID and init output.
AI summary based on the discussion. May contain errors.

FAQ

TL;DR: Most X5/X6/A9 mini cams use an 18‑pin FFC/ZIF; the "uart log prints which one it detects." Use boot logs to map ribbon labels to sensors like GC0329 (0xC0), GC0311 (0xBB), GC0312 (0xB3), HI704 (0x96). [Elektroda, divadiow, post #21549325]

Why it matters: This FAQ helps repairers and tinkerers quickly identify camera modules and avoid wrong sensor inits.

Quick Facts

GC0329 auto‑detect returns chip ID 0xC0; typical VGA 640×480 init shown. [Elektroda, divadiow, post #21741973]
GC0311 auto‑detect returns chip ID 0xBB; stable AP brings up logs after init. [Elektroda, divadiow, post #21762384]
GC0312 auto‑detect returns chip ID 0xB3; 24 MHz MCLK used in examples. [Elektroda, divadiow, post #21713076]
HI704 auto‑detect returns chip ID 0x96; logs confirm AP and IR‑cut actions. [Elektroda, divadiow, post #21712521]
18‑pin FFC/ZIF connector is common across these mini spy cams. [Elektroda, divadiow, post #21549325]

How do I identify which sensor my X5/X6/A9 camera uses?

Open the UART console and power the board. Watch for lines like “---->detect gc0329” and “chip id read success.” The log tells the driver name and the hex ID. Match that to your ribbon’s board code photos for confirmation. “The uart log prints which one it detects.” [Elektroda, divadiow, post #21549325]

Which board codes map to GC0329?

Examples include XLT-X5-0329-V1.0 and LT010-A9-0329-V4. Their boot logs show “gc0329” detection and ID 0xC0 with 640×480 setup. Use these markings on the ribbon or tiny PCB to shortlist GC0329 modules when the silkscreen is vague. [Elektroda, divadiow, post #21741973]

What’s the chip ID for GC0309 from a Tuya‑style mini doorbell?

GC0309 reports “chip id read success 0xa0” in the init log. That sample also notes the ribbon contacts are on the opposite side because the camera points back through a PCB hole. This helps you avoid flipping the FFC during service. [Elektroda, divadiow, post #21550528]

Does GC0328C work with BK72xx boards and MJPEG streaming?

Yes. Logs show I2C probe, sensor match “0328c id_data:9d,” then “GC0328C init finish,” followed by “start web camerar” and an MJPEG server thread. This confirms capture and streaming on BK7231/7252 class devices. [Elektroda, divadiow, post #21607771]

Are there limitations with SuperPix SP0828 on these cams?

Yes. After successful init, firmware prints “sp0828 not support update bitrate” and “not support update venc.” Expect fixed encoding parameters at runtime. Plan settings at compile or driver level instead of live tuning. [Elektroda, divadiow, post #21710596]

How can I quickly identify an unknown sensor (3‑step method)?

Connect UART and power the board.
Capture boot lines with “---->detect …” and any “chip id read success …”.
Match the detected driver to ribbon codes and stored photos. This yields a positive ID without desoldering. [Elektroda, divadiow, post #21549325]

What board codes and IDs confirm GC0311?

Look for LT1823-0311 V1.0-V1 or X5-G11-2365V1. The boot log prints “GC0311 chip id read success 0xbb,” then Wi‑Fi AP and tasks start. Quote: “GC0311 Init Done.” [Elektroda, divadiow, post #21762384]

What clock rates do these examples use?

Several inits set MCLK to 24 MHz and configure VGA 640×480. For example, a GC0328C sequence shows “mclk:24000000MHz,” then IRQ setup and frame capture start. This is a typical working baseline for these sensors. [Elektroda, divadiow, post #21733459]

My doorbell camera’s ribbon seems flipped. Is that expected?

Yes in some designs. One Tuya mini doorbell sample has contacts on the opposite ribbon side because the lens faces through a PCB hole. That note accompanies a GC0309 with ID 0xA0. Check orientation before insertion to avoid damage. [Elektroda, divadiow, post #21550528]

What is Tuya in this context?

Tuya is an IoT platform frequently used in low‑cost smart doorbells. The thread example labels a unit “Tuya mini doorbell,” providing context for GC0309 identification and ribbon orientation specifics. [Elektroda, divadiow, post #21550528]

What is OpenBeken/BK opencam?

It’s a community firmware effort targeting Beken BK72xx SoCs for camera projects. Shared logs show BK7231BT/BK7252 starting BLE, MJPEG server, and sensor probes for GC03xx/HI704/SuperPix families. [Elektroda, divadiow, post #21607771]

How do I confirm HI704 on my module?

Boot with UART attached. If you see “---->detect hi0704” and “HI0704 chip id read success 0x96,” you have Hynix HI704. The sample also shows AP bring‑up and IR‑cut color set messages. [Elektroda, divadiow, post #21712521]

Which GC0312 ribbons are shown and what does the log say?

Examples include X5-G12-236V1. The boot prints “---->detect gc0312” and “chip id read success 0xb3,” then AP mode and task creation. This confirms correct driver pairing for GC0312 modules. [Elektroda, divadiow, post #21713076]

What failure or edge‑case messages should I expect?

Benign errors include “Drop frame:5..1,” UMAC warnings about ifnet not valid for TX, and missing test files. Systems continue after these messages, but they flag timing or networking races. [Elektroda, divadiow, post #21762384]

Is GC0329 reliably detected on A9 boards?

Yes. A9 samples with LT010‑A9‑0329‑V4 show auto‑check tables and a sensor match at ID 0xC0. After init, the capture IRQ and audio tracks start, confirming full pipeline. [Elektroda, divadiow, post #21741973]

How do I verify SP0A20 on an A9 platform?

The log prints “初始化镜头成功镜头为SP0a20” and sets 640×480. It lists SID probes and confirms the sensor before enabling CSI interrupts. This validates SP0A20 on the tested A9. [Elektroda, divadiow, post #21714889]

AI summary based on the discussion. May contain errors.