-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Gaps" in flash readout? #8
Comments
Edit: please ignore, this didn't help at all Still checking, but this might be due to bad "block" size, or read size, it defaults in the code to 0x100; I've read somewhere that flash block size is 4kb, It's still downloading but maybe I have better results (or maybe because I'm reading out-of bound or wrapped-around, as The current read offset is over 1M :P ) will update If I have further information |
Flash dumps (FullFlash bin) of some ZTU modules can be found in these descriptions: And also for other devices - https://github.com/pvvx/pvvx.github.io |
Wow! thanks, wasn't aware you have other readouts. This is a list of what I have in my possession (installed):
|
Use hardware versions of programmers with a SWM<->SWS connection. |
I need to buy these modules or I can Implement them on arduino / Texas instruments etc? |
STM, like UART, emulates the Telink SWire protocol. But on an SPI controller. All other emulators will work unreliably, since the Telink protocol requires specific processing of timings for each bit in a stream greater than 1 megabit per second. And the protocol is self-synchronizing. |
Hi! The tool seem to work for me - Thanks
I picked this one as it requires the least amount of wires relatively to the other solutions (other also requires tx rx)
I'm currently trying to read / backup Tuya "TZU" chip from this common-chinses in-wall zigbee module (for making dumb switches, smart).
According to some resource online, Tuya TZU module has TLSR8258 Inside.
I can grab some readouts, but there seem to be A LOT OF "gaps" when I try to read, by gap I mean the read command failed and no data returned. I have bits and pieces of data, no consecutive read
I have 2 relatively big readouts,
All of the other dumps are around few hundreds bytes at maximum; This doesn't seem to be like a wiring issue, as the data is persistent and repeatable, also the sections in which I am and am not getting data are reproduceable.
What kind of issue or configuration might cause such data interruption on read?
The text was updated successfully, but these errors were encountered: