logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Mini 1080p wifi camera from Aliexpress, how to use without app (FtyCamPro)?

Wuppiduppi 32409 164
ADVERTISEMENT
Reply | New topic
  • #121 21653893
    p.kaczmarek2
    Moderator Smart Home  
    This looks strange?
    Code: text Expand Select all Copy to clipboard
    
Build TXW81X (OpenTXW81X, default)
The process 'C:\Windows\system32\wsl.exe' failed with exit code 100
Semantic Release Images and Artifacts
Unable to download artifact(s): Artifact not found for name: OpenBK7231T_App_1.18.167 Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md

    Let's start with retry, i will run it again
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #122 21687516
    d1nuc0m
    Level 5  
    Hi all, I got a variation of the A9 camera

    Camera module and circuit board with electronic components
    Electronics PCB with camera module, micro USB, and microSD slot

    with a TXW817 (TXW817-810 CWCN4A G2523)

    I come here from a GitHub issue [ @divadiow ] on cam-reverse, as I'd like to destroy experiment with my camera and open firmwares

    If I understand correctly, to try OpenBeken (and maybe contribute if I can XD) I need:

    * a USB/serial adapter (got a CH340G)
    * cables, soldering iron etc. (got it)
    * knowledge on coding/compiling etc.
    * a STM32F103 to be adapted as C-SKY Flash Programmer (as in https://www.elektroda.com/rtvforum/topic4120455.html)
    * a J-Link programmer/debugger clone to flash said STM32
    * a MQTT/HomeAssistant endpoint to use the flashed A9

    Did I miss something?
  • ADVERTISEMENT
  • #123 21687537
    insmod
    Level 28  
    >>21687516
    Nothing missed, though several things aren't necessary (no knowledge on coding/compiling required, compiled binary is available in releases on github, and serial adapter while good for debugging is not truly needed)
    I suggest removing battery, since there is no support for sleep in OpenBeken and it will just work until battery is discharged to the point chip is no longer able to boot.
  • #124 21688251
    d1nuc0m
    Level 5  
    >>21687537 Thanks, I wrote about coding as I'd like to experiment with the code too
    I think I'll keep the battery as I want to be able to place it not near a wall socket (then recharge when needed).

    While I get all the necessary hardware, will a STM32F103 also allow me to take a backup of the original firmware? So that I have a known working point
  • #126 21688375
    divadiow
    Level 36  
    indeed.

    just taking a final backup of that black PCB A9 before trying OpenTXW817 on it

    Software interface for reading BIN file data from device memory

    Electronic boards connected with wires on a wooden table

    Added after 2 [minutes]:

    this bit in that guide

    divadiow wrote:
    Under "Local JTAG" tab set ICE Clk to 1200Khz


    appears to suggest it has to be that frequency. It doesn't. I've had to go lower to achieve write success before. I'll adjust wording.
  • #128 21688386
    divadiow
    Level 36  
    I think I mostly am tbh. Dodgy cut-up dupont on one occasion maybe
  • #129 21688501
    d1nuc0m
    Level 5  
    >>21688266 Thanks, I think I'll be back in a couple of weeks (while I get the necessary)
  • ADVERTISEMENT
  • #131 21694556
    d1nuc0m
    Level 5  
    Hi, I got all the necessary - the STM32 is flashed and now shows as CKLink-Lite in device management, but when I try to run the flash programmer I get "Error - DebugServer Start error, can't connect to target"

    Maybe is the pinout wrong? I connected (A9/STM32) GND/GND, PA9/A5 and PA10/A1; both powered through USB
  • #132 21694605
    divadiow
    Level 36  
    sounds right. cables too long? could try lower ICE Clk?

    A couple of things I've had with these - pads have been labelled wrong (discovered with multi-meter from test pad to IC leg) and with the black PCB A9 above one of the pads was shared with an LED so I had a split second to catch the connection before the LED started flashing. It took a few goes and the ability to switch USB power on and off with a button was a great help.

    USB hub with multiple connected cables and a rotary switch on a wooden desk

    or something else..
  • #133 21694718
    d1nuc0m
    Level 5  
    >>21694605
    Cables are less than 10 cm soldered to the pads (soldered badly in photo as a removed/resoldered multiple times, last time didn't turn out well); which value could I use for ICE?

    Maybe the pads are labelled wrong, on my board orange cable is PA9, red cable is PA10 and brown cable is GND - are they in the same position as yours?

    Mini 1080p wifi camera from Aliexpress, how to use without app (FtyCamPro)?


    Also, if I want to check, to which IC leg should these lead?
  • #135 21694727
    divadiow
    Level 36  
    with a decent enough pic it looks like you could easily trace to which pin the pads go visually without multi-meter
  • #136 21694902
    d1nuc0m
    Level 5  
    Good news - lowering clk to 4000 made it work

    Bad news - forgot to do a backup

    Now what? OpenTXW81X_1.18.176.bin has been flashed, when connecting the board to power LEDs do not turn on (and that I guess it's ok as it's not implemented), and I get garbage on serial, which baudrate/pins should I use now? Also, should it show up in Bluetooth to config or what else?
  • #137 21694922
    insmod
    Level 28  
    >>21694902
    Baud is 921600
    It should show up as an access point
    Leds do not turn on because they need to be configured first
  • #138 21694939
    divadiow
    Level 36  
    d1nuc0m wrote:
    Bad news - forgot to do a backup

    :( oh well

    I just noticed you left battery soldered up too.

    I wonder if your board uses SDK default PC2/PC3 for SDA/SCL. Soon find out I guess

    Added after 13 [minutes]:

    is your cam ribbon marked like either of these? I can't quite make out half of it


    Close-up of a camera ribbon marked LT1757-QA 19 V1.0 on a blue background
    Close-up of a camera ribbon labeled “0828 V1.0” on a black surface
  • #139 21694984
    d1nuc0m
    Level 5  
    Just desoldered the battery, now powering the device through USB and with adapter DX on camera DM I got a serial output (just part of it):
    Code: text Expand Select all Copy to clipboard
    
OpenTXW81X, version 1.18.176
Entering initLog()...Commands registered!initLog() done!EasyFlash V4.1.0 is initialize succuser_eloop_run:312::run
ess.
You can get the latest version on https://github.com/armink/EasyFlash .


    I see an OpenTXW81X_9D772F14 network too and I can connect the phone to it, any suggestion on which app can I use for initial config? (Or if there is a browser interface)
    EDIT: never mind, 192.168.4.1 when connected to the WiFi

    And my camera ribbon is LT1888 / 0828 V1.0, so I guess the same as the second image

    Added after 14 [minutes]:

    Solved, when connected to the AP, 192.168.4.1 as for Tasmota, now I connected it to the WiFi.
    Can I somehow check the video without setting up Home Assistant etc?
  • #140 21695014
    insmod
    Level 28  
    >>21694984
    Either execute custom command "startdriver TXWCAM"
    Or change startup command to the same and reboot
    Camera should be available at rtsp://{ip}:7070/webcam
  • #141 21695022
    divadiow
    Level 36  
    d1nuc0m wrote:
    And my camera ribbon is LT1888 / 0828 V1.0, so I guess the same as the second image


    Hmm. I am trying to get a Superpix SP0828 driver going at the moment. None of drivers currently in the build initialise the sensor for me
  • #142 21695035
    d1nuc0m
    Level 5  
    >>21695022
    Ran the command manually, got "Info:MAIN:Started TXWCAM. OK", if I run it again "Info:MAIN:Drv TXWCAM is already loaded." but VLC can't open rtsp://{ip}:7070/webcam (I replaced it with the ip the cam has, 192.168.1.9)

    nmap sees that the port is open (together with 80 and 9000)

    Maybe is it possible to check the mic?
  • #143 21695166
    divadiow
    Level 36  
    I think I would have expected an RTSP audio stream if the mic was the default pin, even if video won't work at the moment (no driver).

    I get audio but no video often.

    Maybe a start would be to establish which pins your cam is using.
    If you flash this build: https://github.com/openshwprojects/OpenBK7231...actions/runs/17838457506/artifacts/4049109736 (log in to github first)

    then run this in custom command in web gui

    Code: Text
    Log in, to see the code


    it should come back with the i2c address if your device uses these default pins

    Code: Text
    Log in, to see the code


    Screenshot of OpenTXW81X interface showing command log and connection status

    Added after 36 [minutes]:

    divadiow wrote:
    If you flash this build: https://github.com/openshwprojects/OpenBK7231...actions/runs/17838457506/artifacts/4049109736 (log in to github first)


    now part of release 1.18.177
  • #144 21695193
    insmod
    Level 28  
    >>21695166
    I2C is not enabled in this build
    So UART log is needed.
  • #145 21695195
    divadiow
    Level 36  
    insmod wrote:
    I2C is not enabled in this build

    darn, yes

    Added after 1 [hours] 4 [minutes]:

    with i2c https://github.com/divadiow/OpenBK7231T_App/actions/runs/17877285235/artifacts/4062310290

    Mini 1080p wifi camera from Aliexpress, how to use without app (FtyCamPro)?
  • #146 21695467
    d1nuc0m
    Level 5  
    >>21695195
    Thanks, flashed this one, the output is

    Code: text Expand Select all Copy to clipboard
    
Info:I2C:DRV_I2C_Init: registering scanI2C/scanI2Cdump/peek/poke
Info:MAIN:Started i2c.
Info:MAIN:Started txwcam.
Info:I2C:Address 0x1 (dec 1) 


    After a couple of seconds then the camera stops working, with this serial output (repeated many times in loop)

    Code: text Expand Select all Copy to clipboard
    
[213192]fv
[213192]sip reset DVP
hgdvp_close...............................................................


    After reboot the serial output is normal, but it doesn't connect to WiFi nor it shows the access point

    A couple of unrelated questions:
    * is there a way to make the serial output the IP address the camera got? My router has some issues with DHCP and fixed addresses...
    * Experimenting with the web UI I discovered which pins are used for left LED (blue one, works on high) and right LED (red one, works when pin is low), can I do something with this?
  • ADVERTISEMENT
  • #147 21695625
    divadiow
    Level 36  
    im sorry, wrong link. that's one of my experiment builds trying to get a working SP0828 driver. this is main release but with I2C enabled:

    https://github.com/openshwprojects/OpenBK7231T_App/actions/runs/17877315908

    to be clear, I wouldn't expect SP0828 to work at present, this is for detecting i2c devices so you can determine SDA/SCL pin assignments for if/when SP0828 can be made to work - either by me or someone with greater skillz
  • #148 21697869
    divadiow
    Level 36  


    I wonder if these TXW cams should go into device list, the ones that meet a certain working threshold perhaps - SDA/SCL confirmed maybe. They could be marked as WIP or something. Just somewhere for what we know about each one to be acknowledged in some way in a central place. They can be revised as buttons, LEDs etc are confirmed.

    eg the X6 would currently be

    Code: JSON
    Log in, to see the code


    thoughts?
  • #149 21698111
    p.kaczmarek2
    Moderator Smart Home  
    I think that all devices should be added to devices list, even the WIP ones, or the ones we didn't flash yet. It's the same approach which is taken by Tasmota devices list, as far as I remember.
    Helpful post? Buy me a coffee.
  • #150 21699663
    d1nuc0m
    Level 5  
    >>21695625
    Thanks, I'll try it ASAP, my Windows box is KO actually... Is it somehow possible to flash these chips under Linux? (Just a small hope, I know it's closed hw+source)

    >>21697869
    It would be nice to be able to have "alternative names" the hw is also known under (for example I got mine as "A9" camera, nothing related to Xiaomi)
Reply | New topic
Report a violation of the law

Topic summary

A mini 1080p WiFi camera from Aliexpress priced under 3€ uses a Beken BK7252UQN48 AU3437XB chip and requires the proprietary "FtyCamPro" app for operation. The device creates its own WiFi network and assigns an IPv4 address but shows no open ports on scanning. Opening the case reveals the Beken chip, and firmware resources for this chip are available on GitHub (beken7252-opencam), enabling potential firmware backup and custom flashing after identifying the flashing pins. Some similar cameras use the Taixin TXW817 chipset, which has a different ecosystem including SDKs and programming tools like TXProgrammer and CK-Link debuggers. Attempts to access internal flash memory via QSPI/SPI have been made, but require delicate soldering and specialized hardware. The Taixin TXW81x IoT SDK and C-SKY Development Kit (CDK) support firmware development and compilation. TXProgrammer can be configured to English for easier use. A 2MB flash dump from a TXW817-810 based camera has been obtained, and a demo application runs on this hardware using hgSDK. Overall, the discussion covers hardware identification, firmware extraction, SDK availability, and programming tool usage to bypass the official app and enable local control of these low-cost WiFi cameras.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT