shimun/solo
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

Change firmware-hacker ROP level, add ST DFU udev

Browse Source 
- later we can set ROP=1 for hacker firmware builds again,
  right now it causes issues in solo-python tool
This commit is contained in:
Nicolas Stalder 2019-02-17 02:28:52 +01:00
parent 991530f88b
commit 0d2e03a5a9
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
99-solo.rules
View File

@ -10,9 +10,12 @@ LABEL="mm_usb_device_blacklist_end"
# Solo
## access
## bootloader + firmware access
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a2ca", TAG+="uaccess", GROUP="plugdev"
## DFU access
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", TAG+="uaccess", GROUP="plugdev"
## Solo Secure symlink
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a2ca", ATTRS{product}=="Solo [1-9]*", SYMLINK+="solokey"
## Solo Hacker symlink

2
targets/stm32l432/Makefile
View File

@ -13,7 +13,7 @@ merge_hex=../../tools/solotool.py mergehex
# The following are the main targets for reproducible builds.
# TODO: better explanation
firmware-hacker:
$(MAKE) -f $(APPMAKE) -j8 solo.hex PREFIX=$(PREFIX) DEBUG=0 EXTRA_DEFINES='-DSOLO_HACKER -DFLASH_ROP=1'
$(MAKE) -f $(APPMAKE) -j8 solo.hex PREFIX=$(PREFIX) DEBUG=0 EXTRA_DEFINES='-DSOLO_HACKER -DFLASH_ROP=0'
firmware-secure:
$(MAKE) -f $(APPMAKE) -j8 solo.hex PREFIX=$(PREFIX) DEBUG=0 EXTRA_DEFINES='-DUSE_SOLOKEYS_CERT -DFLASH_ROP=2'