Fsio eval check (#2068)

* FSIO error signaling

- wrong keyword in FSIO now shows up as nice TS error message
- added f7 debug option for vsCode as well.

* Keep unit_test happy
This commit is contained in:
shadowm60 2020-12-13 03:03:52 +02:00 committed by GitHub
parent 9b3e4404cc
commit 593be1c943
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 1 deletions

13
.vscode/launch.json vendored
View File

@ -56,6 +56,19 @@
"svdFile": "${workspaceRoot}/firmware/ext/cmsis-svd/data/STMicro/STM32F427.svd",
"servertype": "openocd",
"configFiles": ["interface/stlink.cfg", "target/stm32f4x.cfg"],
"runToMain": true
},
{
"name": "Debug F7x6",
"type": "cortex-debug",
"request": "launch",
"cwd": "${workspaceFolder}",
"executable": "${workspaceRoot}/firmware/build/rusefi.elf",
"device": "STM32F767V",
"v1": false,
"svdFile": "${workspaceRoot}/firmware/ext/cmsis-svd/data/STMicro/STM32F7x6.svd",
"servertype": "openocd",
"configFiles": ["board/stm32f7discovery.cfg"],
"runToMain": true
}
]

View File

@ -422,7 +422,9 @@ LEElement *LEElementPool::parseExpression(const char * line) {
/**
* Cannot recognize token
*/
warning(CUSTOM_ERR_PARSING_ERROR, "unrecognized [%s]", parsingBuffer);
#if ! EFI_UNIT_TEST
firmwareError(CUSTOM_ERR_PARSING_ERROR, "unrecognized FSIO keyword [%s]", parsingBuffer);
#endif
return nullptr;
}
n->init(action);