rust-card10 issueshttps://git.flow3r.garden/astro/rust-card10/-/issues2019-08-23T17:39:07Zhttps://git.flow3r.garden/astro/rust-card10/-/issues/1add gilabt-ci artifacts to download apps from this repo2019-08-23T17:39:07ZKloenkadd gilabt-ci artifacts to download apps from this repoupload example.elf and rkanoid.elf to gitlab artifacts so the user can download nightly builds from masterupload example.elf and rkanoid.elf to gitlab artifacts so the user can download nightly builds from masterKloenkKloenkhttps://git.flow3r.garden/astro/rust-card10/-/issues/4fix card10-l0dable on crates.io2019-09-04T22:33:16ZKloenkfix card10-l0dable on crates.ioFix the crates.io version of card10-l0able on crates.io.
This should be possible with using a git subtree rather than the submoduleFix the crates.io version of card10-l0able on crates.io.
This should be possible with using a git subtree rather than the submodulel0dable 0.1.3KloenkKloenkhttps://git.flow3r.garden/astro/rust-card10/-/issues/5Implement client.c in plain rust2019-09-05T09:27:49ZKloenkImplement client.c in plain rustImplement the client.c in plain rust but still depend on on the caller.cImplement the client.c in plain rust but still depend on on the caller.cKloenkKloenkhttps://git.flow3r.garden/astro/rust-card10/-/issues/7BHI160: all values are 02019-08-28T21:08:26ZPuzzlewolfBHI160: all values are 0All values read from bhi160 sensors are currently 0, e.g. in the output of the example.
According to git bisect, 77f2e073d2dc614547c02557472aa9e5cdea68d7 seems to have introduced this.
I tested with firmware versions 1.6 and 1.7.All values read from bhi160 sensors are currently 0, e.g. in the output of the example.
According to git bisect, 77f2e073d2dc614547c02557472aa9e5cdea68d7 seems to have introduced this.
I tested with firmware versions 1.6 and 1.7.https://git.flow3r.garden/astro/rust-card10/-/issues/8Allow allocator usage on card102019-09-03T19:28:13ZrndAllow allocator usage on card10It would be great if rust-card10 could provide a minimal working allocator.
The latest state of the `{WIP}` commit at https://git.card10.badge.events.ccc.de/rnd/rust-card10/commits/task/card10-alloc already contains the most of the nece...It would be great if rust-card10 could provide a minimal working allocator.
The latest state of the `{WIP}` commit at https://git.card10.badge.events.ccc.de/rnd/rust-card10/commits/task/card10-alloc already contains the most of the necessary changes on the rust side but I am still unsure about the firmware interaction part.
On a first guess i expected that the allocator just needs to call `pvPortMalloc` and `vPortFree` but I couldn't come up with all necessary changes to the build script of `card10-l0dable` to inject them. This also includes that I am still unsure if a or which version of the heap.c is actually required.https://git.flow3r.garden/astro/rust-card10/-/issues/10Make SensorDataItem retain the original input data2019-09-03T17:30:47ZPuzzlewolfMake SensorDataItem retain the original input dataSensorDataItem should retain the original input data and do the conversions in getter functions.SensorDataItem should retain the original input data and do the conversions in getter functions.https://git.flow3r.garden/astro/rust-card10/-/issues/11[Cosmetic?] Definition of `__bss_start` and `__bss_end` as u642019-09-04T22:36:20Zrnd[Cosmetic?] Definition of `__bss_start` and `__bss_end` as u64Why are the extern variables `__bss_start` and `__bss_end` both are defined as `u64` instead of `u32` shouldn't they match the definition of `__heap_start` from `l0dables/lib/hardware.c` of the firmware repo which would be u32?Why are the extern variables `__bss_start` and `__bss_end` both are defined as `u64` instead of `u32` shouldn't they match the definition of `__heap_start` from `l0dables/lib/hardware.c` of the firmware repo which would be u32?https://git.flow3r.garden/astro/rust-card10/-/issues/12Remove Jailbreak Instructions2019-09-04T22:36:20ZKloenkRemove Jailbreak InstructionsRemove the Jailbreak instructions from the readme, and replace it with the new ones for epicardium v1.9Remove the Jailbreak instructions from the readme, and replace it with the new ones for epicardium v1.9