Merge pull request #49 from SoloKeysSec/its-stm32l432

we use l432, not l442
This commit is contained in:
nickray 2019-01-05 02:04:38 +01:00 committed by GitHub
commit 4072a51a5b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
106 changed files with 12 additions and 18 deletions

View File

@ -41,13 +41,13 @@ If you have a Solo for Hacker, here's how you can load your own code on it. You
git clone --recurse-submodules https://github.com/SoloKeysSec/solo
cd solo
cd targets/stm32l442
cd targets/stm32l432
make cbor
make all-hacker
python ../../tools/programmer.py solo.hex
```
For example, if you want to turn off any blue light emission, you can edit [`led_rgb()`](https://github.com/SoloKeysSec/solo/blob/master/targets/stm32l442/src/led.c#L15) and force:
For example, if you want to turn off any blue light emission, you can edit [`led_rgb()`](https://github.com/SoloKeysSec/solo/blob/master/targets/stm32l432/src/led.c#L15) and force:
```
uint32_t b = 0;
```

View File

@ -21,7 +21,7 @@ To program your build, you'll need one of the following programs.
Enter the `stm32l4xx` target directory.
```
cd targets/stm32l442
cd targets/stm32l432
```
Build the cbor library.

View File

@ -2,11 +2,11 @@ We are very open to contributions!
[Currently](https://github.com/solokeyssec/solo/issues), most work will go towards
* implementing STM32L442
* implementing STM32L432
* implementing NFC
* adding documentation and improving accessability of the code
In the future, we would love to see creative plugins/extensions, putting the TRNG and other features of the STM32L442 to good use!
In the future, we would love to see creative plugins/extensions, putting the TRNG and other features of the STM32L432 to good use!
Feel free to send a [pull request](https://github.com/SoloKeysSec/solo/pulls) at any time, we don't currently have a formal contribution process.

View File

@ -2,7 +2,7 @@
Solo has a bootloader that's fixed in memory to allow for signed firmware updates. It is not a built-in bootloader provided by the chip
manufacturer, it is our own. We plan to use Ed25519 signatures, which have [efficient constant-time implementations on Cortex-M4 chips](http://www.cs.haifa.ac.il/~orrd/LC17/paper39.pdf).
On the STM32L442, there is 256 KB of memory. The first 14 KB of memory is reserved for the bootloader.
On the STM32L432, there is 256 KB of memory. The first 14 KB of memory is reserved for the bootloader.
The bootloader is the first thing that boots, and if the button of the device is not held for 2 seconds, the
application is immediately booted.

View File

@ -24,10 +24,8 @@ CFLAGS= $(INC)
TARGET=solo
HW=-mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb
# Nucleo board
#CHIP=STM32L432xx
# Solo
CHIP=STM32L442xx
# Solo or Nucleo board
CHIP=STM32L432xx
DEFINES = -D$(CHIP) -DAES256=1 -DUSE_FULL_LL_DRIVER
DEFINES += -DTEST_SOLO_STM32 -DTEST

View File

@ -36,10 +36,8 @@ CFLAGS= $(INC)
TARGET=solo
HW=-mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb
# Nucleo board
#CHIP=STM32L432xx
# Solo
CHIP=STM32L442xx
# Solo or Nucleo board
CHIP=STM32L432xx
ifndef DEBUG
DEBUG=0

View File

@ -34,10 +34,8 @@ CFLAGS= $(INC)
TARGET=bootloader
HW=-mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb
# Nucleo board
#CHIP=STM32L432xx
# Solo
CHIP=STM32L442xx
# Solo or Nucleo board
CHIP=STM32L432xx
ifndef DEBUG
DEBUG=0

Some files were not shown because too many files have changed in this diff Show More