sw/stm32 - Cryptech HSM on STM-32 ARM processor

Age	Commit message (Collapse)	Author
2017-08-31	Withdraw SysTick_hook (commit 9ffead1), because it turns out there was ↵	Paul Selkirk
	already a user-callback mechanism with HAL_SYSTICK_IRQHandler() and HAL_SYSTICK_Callback().
2017-07-31	Add a generic SysTick hook, to call a function on every 1ms tick, because ↵	Paul Selkirk
	it's easier than setting up a dedicated timer.
2017-04-29	Remove exception handlders that I probably shouldn't have defined in the ↵	Paul Selkirk
	first place.
2017-04-01	Change RPC UART to have a high-priority thread monitoring a large(ish) DMA	Paul Selkirk
	buffer, because we've observed out-of-order receives under load.
2016-09-20	Still some problem with uart receive under heavy load, so change to a 2-byte ↵	Paul Selkirk
	receive buffer with half-complete callbacks, and raise the dma priority.
2016-06-13	Only the HSM project needs the RTOS; most of the test projects can use the ↵	Paul Selkirk
	STM32 HAL code directly.
2016-06-07	fix some comments	Fredrik Thulin

2016-06-06	Split HAL_UART_RxCpltCallback into uart-specific callbacks.	Paul Selkirk

2016-06-02	Use 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-01	Implement circular buffer UART RX using interrupts.	Fredrik Thulin