I'll see if I can find something in project to toggle that may relate to psram.
I don't see a define for it in the config file but you can add #define PSRAM_EN 1 in the project_config.file or in the compiler. I wasn't able to find any specific info about psram on the chip so I just left it all at default.
hold up, hold up. I've soldered up TX so I can properly see what's happening. Also dropped ICE Clk and am verifying flash write each time. Turns out it's been failing half the time, which is why original upload here failed to boot when I tried. The key seems to be to power cycle STM32 between flashes.
That's amazing! The folder where all the stream and video/audio stuff is handled is sdk>app>spook. From what I remember the default web page it should be streaming to is [the cams ip]/webcam
Try giving that a go. Or maybe use Wireshark to see what it's doing.
Added after 3 [minutes]:
looks like in the newer SDK's it's a little different but the folder and files in it still exist.
I just found this but it's in an if statement in tcp.c: rtsp://192.168.1.1:7070/webcam
might also need to change some pins for some things but I think (at least for my board) they used the default pin configuration for the camera sensor though I'm not 100% sure.
I just found this but it's in an if statement in tcp.c: rtsp://192.168.1.1:7070/webcam
yes. I see it.
sebek2435 wrote:
might also need to change some pins for some things but I think (at least for my board) they used the default pin configuration for the camera sensor though I'm not 100% sure.
yes. wondered about this. it'll be a pain for a cam that's deviated from template
2.5.3.7? Weird because it was enabled for me. (Maybe I tampered with it before I don't remember) But it doesn't have any SDIO pin definitions even though SDH_EN is also enabled. Anyway, does it work?
yes, I ditched old and started afresh with 2.5.3.7
sebek2435 wrote:
Anyway, does it work?
not getting any rtsp or web page action yet. let me know if you want current state of project. can't remember all the things ive changed at this point.
correct. I need to make a repo starting with new SDK then layer some changes I've made on top as commits. I've lost track of what's been done. Lots of buffers and socket adjustments and things.
No FS, no SD, no audio, no HTTP currently.
It'd be good for others to see code changes
Added after 1 [minutes]:
no idea how one transforms this into OpenTXW81X. It's just an rtsp POC at this point.
Shame most of these Taixin cams appear to be 1mb
Added after 14 [minutes]:
quality and frame rate is actually better than I expected
Upload the current code to Github, I guess there is some kind of version of LWIP and RTOS inside. Also ,how do you build that? Maybe I could help with porting OBK to it "blindly", without having physical device.
>>21645812 You've made me very interested.
I have one TXW817-810 cam (HQ6_V0.1).
Is CK-Link required? Or can i use J-Link/DAPLINK?
I have a spare STM32F103 to convert to CK-Link if needed.
I don't think I have record of exactly where unless I've linked in some of the TXW817 topics dotted around. As you know it's sometimes BK7252U/N, XF16, TXW81x
p.kaczmarek2 wrote:
it has LVGL as well? For which purpose?
I assumed for display support. baby monitor with LCD?
divadiow wrote:
I need to make a repo starting with new SDK then layer some changes I've made on top as commits. I've lost track of what's been done. Lots of buffers and socket adjustments and things.
>>21645938 Flashed your firmware, camera works for me.
+ camera from BK7252U cam works (GC0310 if i remember it right).
OV7670 from doorbell is too big, can't fit it in.
Flashed your firmware, camera works for me.
+ camera from BK7252U cam works (GC0310 if i remember it right).
OV7670 from doorbell is too big, can't fit it in.
excellent.
I've not tried any other cams yet, but expect them to be OK given how interchangeable they've been in other devices
Why do you think it will be hard? We basically need a main timer (every second), and a quick timer (25 ms?), both of them can be behind HAL. We also need HTTP server to work, but that's just a single place to stub... anything else?
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.
