Open angelovAlex opened 4 years ago
Hello!
With your contribution, I have added support for accessing the SMR-F payload as a blob in https://github.com/jglim/ODB/commit/428815a28ab6b0e478c708c2abf35ce61a98f323 . Thank you for opening an issue!
The hashblock read behavior is unusual, and the cursor offset after the section is intentional. I have added an option to read+xor with the normal cursor behavior as it was required for reading the flash payload. Thanks for the heads up
Hi Brandon,
Yes, SMR-D and SMR-F files are renamed ODB files, and should be accepted by ObjectDB.
@brandonros could you provide a release file (compiled) of your fork?
@brandonros could you provide a release file (compiled) of your fork?
I am curious too. How did you extract the binary files from SMR-F using this tool? I have used it but it is only supplying the file info, no extraction.
Also, what compression was used on the smr-f files? Can it be seen with ObjectOBD?
Perhaps @ecumasterac can shed some light?
Hello, how do I create files SMR-d?
Hi. Thanks for a nice project.
"Unknown7 : UInt32 - Unknown, usually 0" - This value is usually zero only for smr-d files, while in smr-f files it seems to contain length of binary data for firmware update. That is the size of "additional" section that comes after Section3. That part is only XORed as other parts.
Btw, seems you have a bug in createDataSection function. For case when no bf you does XOR with offset after that section. Not sure, maybe it is supposed to be in this way for hashBlock, because I did not look at it, but for additional section that offset must be a start point of section