aboutsummaryrefslogtreecommitdiff
path: root/projects/cli-test/mgmt-cli.c
AgeCommit message (Collapse)Author
2019-01-12Timing tests for RSA signing and sub-components thereof.Paul Selkirk
This is not the sort of thing that should go anywhere near production code, so it's on a dangling branch. I may rebase it from time to time.
2018-09-11Cleanup, move 'keywrap core' command to the hsm project, where it will ↵Paul Selkirk
actually be useful for short-term testing.
2018-08-15Add support for Joachim's keywrap core.Paul Selkirk
2017-10-17Overhaul UART APIPaul Selkirk
MGMT is the default UART, and no one should have to explicitly refer to the UART unless they need USER (hsm.c:hal_serial_send_char). The default UART is now exposed in the header file, so that the default-using functions can be macros, which saves a few bytes in code space, and a few microseconds in function call overhead.
2017-10-11Cleanup 'unused parameter' warnings, a couple of which are actual coding errors.Paul Selkirk
2017-10-11Cleanup: signed/unsigned mismatches, mostly in loop countersPaul Selkirk
2017-04-29cli-test doesn't use the tasker, even though it might have previously used a ↵Paul Selkirk
semaphore from the rtos
2017-04-29Port cli-test to the new task API.Paul Selkirk
2016-10-07strcasecmp() is not a standard function.Rob Austein
2016-07-21Use a fresh port of libcli, which retains more of the original API.Paul Selkirk
2016-07-12re-enable masterkeyFredrik Thulin
2016-07-09Merge more code from projects/hsm.Fredrik Thulin
2016-07-08merge test code from projects/hsm/Fredrik Thulin
2016-06-07Don't reboot when CLI logout is intended.Paul Selkirk
2016-06-02Use DMA for UART RX instead of interrupts.Fredrik Thulin
DMA is more efficient and less prone to miss characters than interrupts. An open question is if circular mode is really the best. If someone copy-pastes more than the RX buffer size of configuration into the CLI, we risk the DMA controller catching up with the reader and overwriting data not yet read. Since we don't have flow control back to the users terminal, we will always fail if too much data is entered before we can process it. The question is if failing to stuff new data at the end of a buffer might be better than data being overwritten - thus messing up the commands in unpredictable ways.
2016-06-01Implement circular buffer UART RX using interrupts.Fredrik Thulin
2016-05-24non-working code to upload an application and jump to itFredrik Thulin
Committing my work in progress in case someone else wants to help.
2016-05-23SDRAM initialization and test code from Pavel.Fredrik Thulin
Integrated into the cli-test program as such: cryptech> test sdram Initializing SDRAM Starting SDRAM test (n = 0) Run sequential write-then-read test for the first chip Run random write-then-read test for the first chip Run sequential write-then-read test for the second chip Run random write-then-read test for the second chip Run interleaved write-then-read test for both chips at once SDRAM test (n = 0) completed SDRAM test completed successfully cryptech>
2016-05-18put some generic CLI code in mgmt-cli.cFredrik Thulin