A Feb 2024 FTY A9 WiFi Mini Camera variant uses a Taixin TXW817-810 MCU and a black PCB marked 20240112JC 817_V1.3.
Inside, it pairs the QFN48 TXW817-810 with a 640x480 SuperPix SP0A19 sensor, identified as LT1757-OA-10 V1.0.
DebugIO (PA9) and DebugCLK (PA10) are correctly labelled, enabling a 1 MB firmware backup with C-SKY Flash Programmer.
The camera is detected by ftycampro, HD IOT Camera, and YsxLite, and cam-reverse enables local use without cloud.
PA10 shares the blue LED, so timing is critical because GPIO switching quickly interrupts the boot-time debug window.
Generated by the language model.
Another FTY A9 camera variation. This was bought in Feb 2024 and I no longer have record of where from exactly - Ali Express for sure. Not seen this posted anywhere I don't think, so here's some info:
Choice SKU: 742329872052
Item: A9 WIFI Mini Camera Recorder Security Monitoring Wireless Video Mini Camera Recorder Voice Camera Smart Home For Infants And P Sensor
Hunan Shiyue Technology Co. Ltd
Room 514,515,516, 517-208. Building 3, Yulong Tianxia Jiayuan II Complex, No. 799 Youmutang Road, Guanshaling Street, Yuelu District Changsha City, Hunan Province, PR China
AP SSID broadcast is FTYC535866GRDBZ
I don't know which battery it came with as I have several in a pile from a few cams.
For once DebugIO (PA9) and DebugCLK (PA10) are correctly labelled so a backup can be taken with those - see topic C-SKY Flash Programmer with STM32 CK-Link Lite: Reading/Writing to Taixin TXW817-810 MCU for firmware backup instructions. BUT note that PA10 is shared with the blue LED so almost immediately the GPIO switches to flashing the LED. Precise timing is required to catch the firmware before it boots far enough to change GPIO function. In the T-Head Debugging Server once connected:
Code: Text
Log in, to see the code
and 1mb dump with C-SKY Flash Programmer
Cam is detected by ftycampro, HD IOT Camera and YsxLite apps
Cam can also be used locally, without cloud, thanks to cam-reverse - Elektroda guide.
Do you still have it?
I remember you used a different one in dev thread. [Read more]
divadiow
02 Sep 2025 09:24
yes. there might be another variation or two too. I have only tried on that X6 PCB to date. Also want to try on the TXW816 Otoscope
Added after 1 [minutes]:
and to see what might be involved in adding... [Read more]
insmod
02 Sep 2025 09:31
That might not necessarily mean that it's not supported (even though it most likely isn't).
I have one GC0310 camera - and it worked, even though there is no mention of it in SDK.
(Init sequence for... [Read more]
divadiow
02 Sep 2025 09:38
OK sure.
here's another, my first https://www.elektroda.com/rtvforum/viewtopic.php?p=20946310#20946310
Added after 2 [minutes]:
that would explain why both worked at this stage when I think... [Read more]
divadiow
12 Sep 2025 22:06
and now for OpenTXW817
https://obrazki.elektroda.pl/4428373900_1757704409_bigthumb.jpg
AP joined and browsed to at 192.168.4.1 after initial boot
https://obrazki.elektroda.pl/4442866000_1757704955_thumb.jpg... [Read more]
insmod
12 Sep 2025 22:15
Try changing
https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/project/project_config.h#L894 to PA_11
and https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/project/project_config.h#L895... [Read more]
divadiow
13 Sep 2025 09:32
I guess maybe they do. I was expecting some to work https://www.elektroda.com/rtvforum/viewtopic.php?p=21646042#21646042
https://obrazki.elektroda.pl/8730256600_1757708202_thumb.jpg
Added after... [Read more]
divadiow
13 Sep 2025 13:18
With GPT I made an IO probe thing to see which pairs might report back an address
https://github.com/divadiow/txw81xcam/blob/9daa9c4733668a03eb4174948a653c327da1096f/sdk/lib/video/dvp/cmos_sensor/csi_v2.c#L26
... [Read more]
insmod
13 Sep 2025 13:42
I see that after PB_8/9 no other pin combinations are checked.
Remove it from array and check again?
Did you attempt to trace it? Camera pinout is known (https://github.com/daniel-dona/beken7252-o... [Read more]
divadiow
13 Sep 2025 14:32
will do, if I can get back to the working scanner code ;o
negative. not yet. mostly because of:
but I'm sure I could get a thin wire on SDA right at the end. surely.
I am aware of that... [Read more]
divadiow
16 Sep 2025 21:03
oh my days. finally. Should have spent more time probing what other test pad looking things are on the PCB.
these work
//默认sdk匹配学习板,使用PC_2和PC_3作为dvp的i2c
#define PIN_IIC2_SCL PC_3
#define PIN_IIC2_SDA... [Read more]
insmod
16 Sep 2025 22:22
Is DVP_PDN pin required?
Added after 16 [minutes]:
Hm, and does softi2c scan in OBK works? (without camera init ofc) [Read more]
Nope, not even close.
ETA is 4 days to 2 weeks. It's still in China.
I believe it may take even longer than 2 weeks. [Read more]
divadiow
16 Sep 2025 23:58
:(
https://obrazki.elektroda.pl/3647419200_1758055902_bigthumb.jpg
you just get the megalist on soft scan
Info:MAIN:Started i2c.
Info:CMD:[WebApp Cmd 'startdriver i2c' Result] OK
Info:I2C:Address... [Read more]
insmod
17 Sep 2025 00:29
Configurable i2c pins via softsda and softscl
https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/17780650758
What are your init bytes for HI704? [Read more]
Not init table, but init like https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/sdk/lib/bus/iic/sensor/sensor_gc0308.c#L663 [Read more]
divadiow
17 Sep 2025 08:06
oic. driver file attached to previous post, but:
const _Sensor_Ident_ hi704_init =
{
/* id , w_cmd, r_cmd, addr_num, data_num, id_reg */
0x96,0x60,0x61,0x01,0x01,0x04
};
Added after... [Read more]
FAQ
TL;DR: This FAQ identifies a 1 MB FTY A9 2024 variant with Taixin TXW817-810 and, as the teardown notes, "another FTY A9 camera variation." It helps buyers, reverse engineers, and OpenTXW81X users match the black 817_V1.3 PCB, find the working camera pins, and back up firmware before experimenting with local or cloud-free control. [#21563286]
Why it matters: This variant looks like other A9 cameras, but its PCB markings, UART logs, debug timing, and camera pin routing differ enough to change backup, app compatibility, and OpenTXW81X bring-up.
Option
Works for this variant
Access path
Main limitation
Stock firmware + cloud apps
Yes
Vendor apps detect the camera
Cloud-dependent by default
Local AP on stock firmware
Yes
AP mode, device shows 192.168.1.1 in logs
Uses stock firmware behavior
OpenTXW81X / OpenTXW817
Yes, partially
AP at 192.168.4.1 after boot
Factory SP0A19 module initially gave no image
cam-reverse
Yes
Local, cloud-free workflow
Requires reverse-engineering setup
Key insight: The breakthrough was not the first scanner hit. The camera finally worked only after using PC_3/PC_4 for I2C and leaving DVP_RESET = 255, while PA_6 for DVP_PDN turned out to be optional on this board. [#21691354]
Quick Facts
The identified board uses a Taixin TXW817-810 MCU, a 1 MB flash dump, black PCB, and PCB markings 20240112JC 817_V1.3. The stock camera sensor module was reported as SuperPix SP0A19, 640×480. [#21563286]
Stock UART output was captured from the RX pad at 921600 baud and showed hgSDK-v2.5.1.7-26745 with app build time Jan 18 2024 21:55:13. [#21563286]
The factory AP used SSID FTYC535866GRDBZ with password 1234abcd, and the stock network log showed IP 192.168.1.1, netmask 255.255.255.0, and Wi‑Fi channel 8 / 2447 MHz. [#21563286]
OpenTXW81X booted on this hardware with AP OpenTXW81X_75663814, exposed 192.168.4.1 after initial boot, and reported 5 seconds to boot-complete in the log. [#21688413]
The working OpenTXW81X camera configuration used PIN_IIC2_SCL PC_3, PIN_IIC2_SDA PC_4, PIN_DVP_RESET 255, and initially PIN_DVP_PDN PA_6; later testing showed DVP_PDN was not required. [#21692256]
1. How can I identify the 2024 FTY A9 WiFi Mini Camera variant with a Taixin TXW817-810, black PCB, and 817_V1.3 markings?
Identify it by four markers: the black PCB, PCB text 20240112JC 817_V1.3, the Taixin TXW817-810 QFN48 MCU, and the stock AP SSID format beginning with FTYC. The teardown also listed AliExpress Choice SKU 742329872052 and a stock camera sensor reported as SuperPix SP0A19 640×480. Those details separate it from other A9 and XF16-family variants that use different boards, sensors, or pin routing. [#21563286]
2. What is the default AP SSID and password on this FTY A9 TXW817-810 camera, and how do I connect to it locally?
The stock AP SSID is FTYC535866GRDBZ and the password is 1234abcd. Connect to that Wi‑Fi network, then browse to the device on its local AP network. The stock log shows IP 192.168.1.1 with 255.255.255.0 netmask. Under OpenTXW817/OpenTXW81X, the AP changes and local access moves to 192.168.4.1 after boot, so stock and custom firmware use different local entry points. [#21563286]
3. Which camera apps work with this FTY A9 variant, including ftycampro, HD IOT Camera, and YsxLite?
The stock camera was reported as detected by ftycampro, HD IOT Camera, and YsxLite. Those are the three confirmed apps in the thread for this TXW817-based A9 variant. They work with the factory firmware and stock cloud workflow. The same post also notes that the camera can be used locally without cloud through a separate reverse-engineered route, so app support and local support are both documented for this device. [#21563286]
4. What is DebugIO and DebugCLK on the TXW817-810 board, and how are they used for firmware backup?
They are the board’s exposed debug pads for the C-SKY interface. "DebugIO is a board-level debug data pin that carries the target communication signal, while DebugCLK is the matching debug clock pin that synchronizes reads and writes during MCU access." On this camera, they are correctly labeled and map to PA9 and PA10, which lets you attach CK-Link Lite tools and attempt a firmware readout before normal boot reassigns the pins. [#21563286]
5. How do I dump the 1 MB flash from a Taixin TXW817-810 using CK-Link Lite and the C-SKY Flash Programmer?
Use the labeled debug pads and catch the chip early in boot. 1. Connect CK-Link Lite to PA9/PA10 on the board’s DebugIO/DebugCLK pads. 2. Start the T-Head Debugging Server and confirm a CK803SG target is detected. 3. Read the flash with C-SKY Flash Programmer, which produced a 1 MB dump on this board. The thread explicitly confirms both the target ID and a successful 1 MB backup image. [#21563286]
6. Why is precise timing needed when reading firmware from PA9 and PA10 on this camera board?
Precise timing is needed because PA10 is shared with the blue LED. The board starts with debug access available, but almost immediately the firmware switches the GPIO function to LED flashing. That change can block or break the read if you attach too late. The author states you must catch the firmware before it boots far enough to repurpose the pin, which makes this board more timing-sensitive than variants with dedicated debug pins. [#21563286]
7. What is DVP_PDN in the OpenTXW81X camera configuration, and when does it matter for TXW817 camera bring-up?
DVP_PDN is the camera sensor power-down control pin. "DVP_PDN is a camera-control GPIO that forces the image sensor into or out of power-down mode, which matters when the board routes sensor standby separately from I2C and pixel data lines." On this TXW817 board, the first working setup used PIN_DVP_PDN PA_6, but later testing showed the camera still worked with DVP_PDN effectively unused, so it was not required for successful bring-up here. [#21692256]
8. How do I get OpenTXW817 or OpenTXW81X running on this FTY A9 camera and access it at 192.168.4.1?
Flash OpenTXW817/OpenTXW81X, let it boot into AP mode, join that AP, and open 192.168.4.1 in a browser. The log shows OpenTXW81X version 1.18.172, SSID OpenTXW81X_75663814, and a boot-complete message after 5 seconds. That confirms the custom firmware boots cleanly on this TXW817 board even before camera streaming is fully solved. The thread later shows the txwcam driver starting once the correct camera pins were found. [#21688413]
9. Why does OpenTXW81X detect the mic and RTSP audio but fail to produce an image with the factory SuperPix SP0A19 module?
It fails because the board’s camera wiring and sensor handling were not matched yet, even though audio initialized correctly. The log showed the mic working and RTSP audio present, but no image stream appeared with the factory SuperPix SP0A19 LT1757-OA-10 V1.0 module. The author suspected routing differences on the TXW817 board, including the possibility of different camera-related pin choices on the MCU. Later posts confirmed the real fix was finding the correct I2C and control pins, not the microphone path. [#21688413]
10. Which I2C pin assignments finally worked for the camera on this TXW817 board, including PIN_IIC2_SCL, PIN_IIC2_SDA, PIN_DVP_RESET, and PIN_DVP_PDN?
The working configuration was PIN_IIC2_SCL PC_3, PIN_IIC2_SDA PC_4, PIN_DVP_RESET 255, and PIN_DVP_PDN PA_6. With those settings, OpenTXW81X detected a matching sensor, initialized at 640×480, and started the txwcam driver. The same post later notes DVP_PDN was not actually required, but the key breakthrough was the PC_3/PC_4 I2C pair and leaving reset disabled with 255. [#21691354]
11. What caused the PB8/PB9 scanner result to be misleading, and how should I verify the real camera I2C pins on a TXW817 board?
The PB_8/PB_9 result was misleading because the scanner found an ACK, but it did not lead to real sensor detection or working image capture. The author later called that earlier scanner result “a load of bunk.” Verify the pins by combining three checks: a real sensor ID match, successful driver init, and an actual image stream. On this board, only PC_3/PC_4 passed those practical checks. Multimeter tracing and checking hidden test pads also helped confirm the real routing. [#21691354]
12. How does soft I2C scanning in OpenBK7231T_App behave before and after starting the txwcam driver, and why can it show false-positive address lists?
Soft I2C scanning can mislead you badly on this hardware. Before camera init, one scan returned a “megalist” of addresses from 0x1 upward, which is a classic false-positive pattern. After startdriver txwcam, results changed: one non-working camera showed 0x30, another unmatched case showed 0x18, and a working GC0329 setup showed no useful soft-scan result. That means soft scanning depends on bus state and driver ownership, so you must trust real sensor init logs more than raw scan lists. [#21692269]
13. GC0310 vs GC0312 vs GC0329 on Taixin TXW81x: how does sensor detection differ from driver compatibility?
Detection and compatibility are not the same thing. A module believed to be GC0310 initialized using the GC0312 TXW driver, while GC0329 matched directly with ID 0xc0 and initialized at 640×480. The discussion also notes that some modules seen as GC0328 on XF16 were not detected by TXW despite a GC0328 driver existing. One expert observation sums it up: matching an ID is useful, but a different driver can still be the one that actually produces a working image. [#21691354]
14. What init settings and sensor ID values were used to get the Hynix HI704 working on OpenTXW81X, and how good was the image quality compared with XF16 firmware?
The working HI704 identification used ID 0x96, write/read addresses 0x60/0x61, 1-byte register addressing, ID register 0x04, and a 640×480 init path. In log form, OpenTXW81X reported sensor match: name=hi704 id=0x96 addr7=0x30 mclk=24000000. Image quality was usable but not clearly superior. The comparison post says the XF16 image looked better, while TXW was still good enough for a first driver and could be tuned later. [#21693152]
15. Which local, cloud-free options exist for the FTY A9 camera, and how does cam-reverse compare with the stock cloud apps?
The confirmed local, cloud-free option is cam-reverse. The thread states this FTY A9 variant can run locally without cloud through that project, while the stock route uses apps such as ftycampro, HD IOT Camera, and YsxLite. In practice, stock apps are easier for quick setup, but cam-reverse is better if you want local control and to avoid vendor cloud dependence. For firmware-level customization, OpenTXW81X is the deeper route, but it requires pin mapping and sensor work. [#21563286]
Comments
Do you still have it? I remember you used a different one in dev thread. [Read more]
yes. there might be another variation or two too. I have only tried on that X6 PCB to date. Also want to try on the TXW816 Otoscope Added after 1 [minutes]: and to see what might be involved in adding... [Read more]
That might not necessarily mean that it's not supported (even though it most likely isn't). I have one GC0310 camera - and it worked, even though there is no mention of it in SDK. (Init sequence for... [Read more]
OK sure. here's another, my first https://www.elektroda.com/rtvforum/viewtopic.php?p=20946310#20946310 Added after 2 [minutes]: that would explain why both worked at this stage when I think... [Read more]
and now for OpenTXW817 https://obrazki.elektroda.pl/4428373900_1757704409_bigthumb.jpg AP joined and browsed to at 192.168.4.1 after initial boot https://obrazki.elektroda.pl/4442866000_1757704955_thumb.jpg... [Read more]
Try changing https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/project/project_config.h#L894 to PA_11 and https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/project/project_config.h#L895... [Read more]
I guess maybe they do. I was expecting some to work https://www.elektroda.com/rtvforum/viewtopic.php?p=21646042#21646042 https://obrazki.elektroda.pl/8730256600_1757708202_thumb.jpg Added after... [Read more]
With GPT I made an IO probe thing to see which pairs might report back an address https://github.com/divadiow/txw81xcam/blob/9daa9c4733668a03eb4174948a653c327da1096f/sdk/lib/video/dvp/cmos_sensor/csi_v2.c#L26 ... [Read more]
I see that after PB_8/9 no other pin combinations are checked. Remove it from array and check again? Did you attempt to trace it? Camera pinout is known (https://github.com/daniel-dona/beken7252-o... [Read more]
will do, if I can get back to the working scanner code ;o negative. not yet. mostly because of: but I'm sure I could get a thin wire on SDA right at the end. surely. I am aware of that... [Read more]
oh my days. finally. Should have spent more time probing what other test pad looking things are on the PCB. these work //默认sdk匹配学习板,使用PC_2和PC_3作为dvp的i2c #define PIN_IIC2_SCL PC_3 #define PIN_IIC2_SDA... [Read more]
Is DVP_PDN pin required? Added after 16 [minutes]: Hm, and does softi2c scan in OBK works? (without camera init ofc) [Read more]
actually, no. https://github.com/divadiow/OpenBK7231T_App/actions/runs/17778112136 https://obrazki.elektroda.pl/3811114200_1758054773_thumb.jpg will try, assuming i2c driver builds and... [Read more]
Nope, not even close. ETA is 4 days to 2 weeks. It's still in China. I believe it may take even longer than 2 weeks. [Read more]
:( https://obrazki.elektroda.pl/3647419200_1758055902_bigthumb.jpg you just get the megalist on soft scan Info:MAIN:Started i2c. Info:CMD:[WebApp Cmd 'startdriver i2c' Result] OK Info:I2C:Address... [Read more]
Configurable i2c pins via softsda and softscl https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/17780650758 What are your init bytes for HI704? [Read more]
0x03, 0x00, 0x01, 0xf1, 0x01, 0xf3, 0x01, 0xf1, 0x11, 0x90, 0x12, 0x04, 0x20, 0x00, 0x21, 0x04, 0x22, 0x00, 0x23, 0x04, 0x24, 0x01, 0x25, 0xe0, 0x26, 0x02, 0x27, 0x80, 0x40, 0x01, 0x41, 0x58,... [Read more]
Not init table, but init like https://github.com/NonPIayerCharacter/OpenTXW81X/blob/81d5621babdd6aed434d33c0ebc010859c9d3314/sdk/lib/bus/iic/sensor/sensor_gc0308.c#L663 [Read more]
oic. driver file attached to previous post, but: const _Sensor_Ident_ hi704_init = { /* id , w_cmd, r_cmd, addr_num, data_num, id_reg */ 0x96,0x60,0x61,0x01,0x01,0x04 }; Added after... [Read more]