-
Notifications
You must be signed in to change notification settings - Fork 77
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
MTK: Add NR5G support to DB parser #1
Comments
I have the same problem with dimensity-800.It looks like the format of these files(such as md1rom and md1_mddb) has changed a bit on the new soc. |
Thanks for your interested in FirmWire and the associated tooling. Note that 5G modems are not officially supported by the framework; We started developing the framework before 5G modems were around. The full list of tested/supported hardware models can be found here: https://firmwire.github.io/docs/quick_start.html In any case, from what I recall, for 5G modems, MTK started to deploy MIPS I7200 cores. Instead of MIPS16e2, these cores would deploy nanoMIPS, so heavy changes in the emulation engine may be required to support emulation of those. (Note, my memory may be wrong here, it was a while ago when I looked into this.) Either way, we would be happy to accept PullRequests extending the current functionality of the framework. |
The database I believe changed to RocksDB format. We had some code that was for prototyping. We may bring this to production in the future. Can you provide the exact firmware images you were playing with so we can test later on? Even if we don't add nanomips support in the MTK machine, we could add this support to the loader for projects that just want to parse firmware |
Thanks a lot! Here is a dimensity-800(MT6873) baseband firmware which is downloaded from a third-party website. In my previous analysis of its md1rom, I was puzzled by many GFH structures with the magic number "4D4D4D". |
I dumped the DB (dimensity-900) and decoded it with your code. It can be decoded as some segments, but no further decoding.
The text was updated successfully, but these errors were encountered: