aboutsummaryrefslogtreecommitdiff
path: root/projects
AgeCommit message (Collapse)Author
2016-07-05Add horrible kludge of a script to probe USB ports and report whichRob Austein
ones look like console and RPC ports for the HSM.
2016-06-30RPC wire format now includes client handle in all requests, and opcode andPaul Selkirk
client handle in all responses.
2016-06-29add commands to clear pin or whole keystoreFredrik Thulin
2016-06-29cleanupFredrik Thulin
2016-06-28Only SO and wheel are allowed to upload.Paul Selkirk
Also add bootloader upload.
2016-06-28Fix the bootloader to accept firmware (with PIN login).Paul Selkirk
This involves entirely too much duplication of the CLI.
2016-06-27Remove old default user.Paul Selkirk
2016-06-27Modify cli-test/filetransfer to prompt for PIN.Paul Selkirk
2016-06-26PIN-based loginPaul Selkirk
2016-06-25Merge branch 'alternate_dma'Paul Selkirk
2016-06-25Split LIB*_DIR into _SRC and _BLD.Paul Selkirk
Also rename all instances of GNUmakefile to Makefile.
2016-06-25Finish unwinding subrepository hairball: VPATH setup.Rob Austein
2016-06-24Masterkey functions now return hal_error_t as suggested by Rob.Fredrik Thulin
2016-06-23Add masterkey and keystore commands.Fredrik Thulin
2016-06-16keystore_erase_sectors takes start and stop arguments nowFredrik Thulin
2016-06-16Merge branch 'master' into ft-ks_flashFredrik Thulin
2016-06-15Use a 1-byte DMA buffer for management UART receives.Paul Selkirk
It sounds silly, but this gives us completion callbacks, so we don't spend out entire time slice polling the receive buffer for new characters (which kills performance for tasks that are doing real work). Besides, libcli wants to process a character at a time, so uart_cli_read just waits on the completion callback.
2016-06-14Import cli-test into hsm pretty much as-is.Paul Selkirk
2016-06-13RSA keygen needs even more stack space than I thought.Paul Selkirk
Also, it turns out the linker wants to include initializers for sdram variables in the .elf and .bin files, even though it should handle it like bss. So now we manage sdram directly with a pseudo-malloc.
2016-06-13Only the HSM project needs the RTOS; most of the test projects can use the ↵Paul Selkirk
STM32 HAL code directly.
2016-06-09Put thread stack buffers in SDRAM, because pkey uses a lot of stack.Paul Selkirk
Also rearchitect the way we handle RPC requests - have a bunch of waiting dispatch threads rather than continually creating and deleting threads.
2016-06-09Rename main.c to hsm.c for consistency and a slightly simpler Makefile.Paul Selkirk
2016-06-09Put all the keystore commands under 'keystore' instead.Fredrik Thulin
Makes more sense to keep them together, at least in the cli-test.
2016-06-09updated test-code for keystore functionalityFredrik Thulin
2016-06-08Include strings.h, for strcasecmp().Rob Austein
2016-06-08Test code for ks_flash in corresponding branch of libhal.Fredrik Thulin
2016-06-08bootloader doesn't need stm-fmc eitherFredrik Thulin
2016-06-07Don't reboot when CLI logout is intended.Paul Selkirk
2016-06-07Check the HARDWARE_EARLY_DFU_JUMP flag as soon as possible in the boot process.Paul Selkirk
This avoids the situation where the bootloader systick happens during firmware initialization, and freaks out. Also build the bootloader with the minimum resources needed (no RTOS, no SPI, no I2C).
2016-06-06Use refactored slip/serial code.Paul Selkirk
Client daemon sends client ID, echo it back in response.
2016-06-06Remove the 6-second blue blink for alpha board.Paul Selkirk
2016-06-06Remove unused hex file.Paul Selkirk
2016-06-06Remove unused projects.Paul Selkirk
2016-06-02Merge branch 'ft-uart_it'Fredrik Thulin
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-02Move the rest of the CLI commands out of cli-test.c.Fredrik Thulin
2016-06-01Implement circular buffer UART RX using interrupts.Fredrik Thulin
2016-06-01Move FPGA related commands to mgmt-fpga.cFredrik Thulin
2016-06-01Wait for FPGA_DONE on startup (available on Alpha board)Fredrik Thulin
2016-05-31Update huart names to reflect change in stm-uart.Fredrik Thulin
2016-05-27DFU working - but no signature validation for now.Fredrik Thulin
2016-05-27cli_command_root_node: bugfix missing command callbackFredrik Thulin
2016-05-26Implement a bootloader.Fredrik Thulin
This bootloader is now the application at 0x08000000 (FLASH start), which the STM32 will execute upon reset. The other applications are now loaded at 0x08030000 (128 KB into the flash) and will never get started unless the bootloader has been programmed into flash too.
2016-05-25More DFU code. This might actually work.Fredrik Thulin
The applications to be uploaded using 'dfu upload' have to have another FLASH defined in their linker script. Have to recompile some firmware tomorrow and test if this actually works.
2016-05-25Merge remote-tracking branch 'origin/master' into ft-dfu-code-loadingFredrik Thulin
2016-05-24Merge branch 'master' of git.cryptech.is:sw/stm32Paul Selkirk
2016-05-24Add test-mkmifPaul Selkirk
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-24make 'test sdram' take number of iterations as argumentFredrik Thulin
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>