Skip to content
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

Compiling and bugs #38

Open
mpiani opened this issue May 1, 2020 · 3 comments
Open

Compiling and bugs #38

mpiani opened this issue May 1, 2020 · 3 comments

Comments

@mpiani
Copy link

mpiani commented May 1, 2020

I'm sorry to ask a very newbie question, but given the relevance of the project would someone care to give some hints on how to compile the project? I was able to extract the firmware. Although the firmware version was the same, the checksum was different, fixed that, the compiler asks for breath.Bin and asks if I performed make, which I did without result. Another problem is stubs which says there is no target. How should I proceed, please?

@dblunk88
Copy link

dblunk88 commented May 1, 2020

Technically (as far as I understand it) you do not need to make, unless you want breath and graph. For patch-airsense, just comment out patch_code or reference #33

@mpiani
Copy link
Author

mpiani commented May 1, 2020

Thank you for the reply. I was able to generate unlocked-stm32.bin by adjusting the hash on the patch, but my understanding is that without breath.bin the cvap and other functions would not become available. Can anyone confirm that? If so, how to compile breath.c or breath.o and the others?

@dblunk88
Copy link

dblunk88 commented May 1, 2020

I'm not sure, but I think the compilation requires a xml generated by Ghidra (could try importing it using cortex as the language). Haven't really looked into it too deeply this far. Nonetheless, if you do compile it and generate the firmware, be aware the hex comparisons revealed that the breath.bin offset location for 306 is different than the 401 one, but it may still run (like said, haven't taken the time yet to test this yet).

Perhaps someone with better knowledge can help you with this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants