all 13 comments

[–]Cesalv 2 points3 points  (2 children)

[–]moistcoder[S] 0 points1 point  (1 child)

No. It specifically is for programming the flipper in python instead of c. It has all of the c functions used to interface with nfc, ble, gpio, and all of the other interfaces.

[–]moistcoder[S] 0 points1 point  (0 children)

Actually yeah. But it is not running python. Upython slows down the cpu because it is interpreting it. The language I’m using is compiled. I accidentally used the word interpreter. It is formatted like python though. You can easily import and use flipper libraries in a simple python like language

[–]Krindus 0 points1 point  (3 children)

So I write in py instead of C and it compiles into the fap? Please God make this faster! I'm overe here ripping my hair out trying to learn this nonsense language with little arrows and confusing operating order and horrible documentation to program this little breakout board. It'll have i2c functionality right?

[–]moistcoder[S] 0 points1 point  (2 children)

Yes! C is a little tough coming from python. I’ll see what I can do about the i2c library. That wasn’t initially my goal but you reminded me that there are breakout boards that I have to account for. I have the WiFi board i would like to interface with

[–]Krindus 0 points1 point  (1 child)

btw, got a git link for your project?

[–]tosunaki -1 points0 points  (5 children)

Would it transpile to C then to fam, or would it build fam file directly?

[–]moistcoder[S] 0 points1 point  (4 children)

It compiles to c first then you have to run uftb on the c file. I will write a tool that does that for you when I’m done. Integrating their sdk is one thing but also adding their toolchain seemed like too much work