* firmware error in case of low stack only on HW CI
* send date
* I don't java good
* I still don't java good
* send the right command
* I guess we can check it on every single test?
* javaaaaaa
* atoi breaks on later non-digit
* avoid sscanf use (for atoi)
to avoid bloating the stack
* less churn
* less churn
Co-authored-by: Nathan Schulte <nmschulte@desmas.net>
sscanf(isoDateTime, "%4lu-%2hhu-%2hhuT%2hhu:%2hhu:%2hhu", ...) would not
parse beyond the month when built for rusEFI, for unknown reasons,
though it works with a simplified test with GCC, hence the splayed
parsing
use sscanf over atoi for improved memory safety
* java_console: use UTC ISO 8601 for CMD_DATE format
* ChibiOS RTC avoids ctime
* firmware: controller sets time via ISO 8601
* avoid ctime in CAN dash
* most of the plumbing
* easy tests
* trigger types that are rise only
* configs
* change mode of various triggers
* vvt
* 898 test is now impossible 🥳
* s
* instant rpm test
* actually remove useOnlyRisingEdgeForTrigger
* remove vvtCamSensorUseRise
* s
* print
* one happy test
* another test
* happy testSomethingWeird
* happy testCamInput
* maybe fix it a different way
* better
* quad cam
* nb2 happy
* bad merge
* vvt test
* trigger.test1995FordInline6TriggerDecoder
* hellen gm e67
* changelog
* implement sensor checker
* use default
* s
* fix
* properly report non-timeout errors
* it's not safe to read Value when invalid
* it's not safe to read Value when invalid
* less dependence on that logger
* comma
* refactor a bit, make it clear what this thing actually *does*
* static
* shrink the buffer a bit and make names useful
* dead util that's just subtraction lol
* limp manager handles engine stop
* use timer
* dead relevant fsio
* this stuff needs its own ticket
* if we can comment out 'business logic' and tests do not fail it's not a great sign :(
Co-authored-by: Matthew Kennedy <matthewkennedy@outlook.com>
Co-authored-by: rusefillc <sdfsdfqsf2334234234>
* ignition controller detects rising edge on voltage
* update test
* comment
* ignore negative transients
* tweak
* test
* priming happens on ignition-on
* priming has its own scheduling
* config & UI
* dead config
* implementation
* look, the test caught a bug
* keep the watchdog happy
* bad merge
* changelog
* easier to read the test
* test naming