mirror of
https://salsa.debian.org/gnuk-team/gnuk/gnuk.git
synced 2024-09-20 02:40:08 +00:00
configure default change
This commit is contained in:
NIIBE Yutaka
parent
41f5145fe1
commit
a695ad03ab
@ -1,5 +1,11 @@
|
||||
2014-12-12 Niibe Yutaka <gniibe@fsij.org>
|
||||
|
||||
* src/configure (target): Default is FST-01.
|
||||
(--with-dfu): FST-01 doesn't have DFU. If set, it must be
|
||||
mistake.
|
||||
|
||||
* boards/STBEE_MINI: Remove, since it is now supported by Chopstx.
|
||||
|
||||
* test/features/802_get_data_static.feature: Reflect the change
|
||||
of extended capabilities.
|
||||
* test/features/402_get_data_static.feature: Ditto.
|
||||
|
||||
27
NEWS
27
NEWS
@ -1,5 +1,32 @@
|
||||
Gnuk NEWS - User visible changes
|
||||
|
||||
* Major changes in Gnuk 1.1.4
|
||||
|
||||
Released 2014-12-13, by NIIBE Yutaka
|
||||
|
||||
** Experimental RSA-4096 support.
|
||||
Although it takes too long (more than 8.7 second), RSA-4096
|
||||
is now implemented.
|
||||
|
||||
** ECDH support.
|
||||
ECDH is now supported. You need development branch (master)
|
||||
of GnuPG to use this feature.
|
||||
|
||||
** ECDSA and EdDSA is not that experimental.
|
||||
You don't need to edit DEFS variable in src/Makefile.
|
||||
|
||||
** STM8S_DISCOVERY is not supported any more.
|
||||
It's flash ROM size (64KiB) is a bit small to have all features of
|
||||
Gnuk now. If you manually edit code to limit the size of executable,
|
||||
it still could run Gnuk, though.
|
||||
|
||||
** configure's default target is now FST-01.
|
||||
Receiving reports from those who complain default target, I
|
||||
reconsidered. Those who has Olimex STM32 H103 usually has JTAG
|
||||
debugger, while FST-01 users don't. So, to be safe, the default
|
||||
target is now FST-01, instead of Olimex STM32 H103.
|
||||
|
||||
|
||||
* Major changes in Gnuk 1.1.3
|
||||
|
||||
Released 2014-04-16, by NIIBE Yutaka
|
||||
|
||||
31
README
31
README
@ -65,8 +65,6 @@ A2: It takes a second and a half or so.
|
||||
|
||||
Q3: What's your recommendation for target board?
|
||||
A3: Orthodox choice is Olimex STM32-H103.
|
||||
If you have skill of electronics and like DIY, STM32 part of STM8S
|
||||
Discovery Kit might be the best choice.
|
||||
FST-01 (Flying Stone Tiny 01) is available for sale, and it is a
|
||||
kind of the best choice, hopefully.
|
||||
|
||||
@ -176,16 +174,14 @@ It is known not-working well:
|
||||
Targets
|
||||
=======
|
||||
|
||||
We use Olimex STM32-H103 board and Flying Stone Tiny 01 (FST-01). We
|
||||
also use STM32 part of STM8S Discovery Kit.
|
||||
We use Olimex STM32-H103 board and Flying Stone Tiny 01 (FST-01).
|
||||
|
||||
With DfuSe support, STBee is also our targets. But this target with
|
||||
DfuSe is for experiment only, because it is impossible for DfuSe to
|
||||
disable read from flash. For real use, please consider killing DfuSe
|
||||
and enabling read protection using JTAG debugger.
|
||||
|
||||
For PIN-pad support, I connect a consumer IR receive module to FST-01
|
||||
and STM8S Discovery Kit, and use controller for TV. PIN verification
|
||||
For PIN-pad support, I connect a consumer IR receive module to FST-01, and use controller for TV. PIN verification
|
||||
is supported by this configuration. Yes, it is not secure at all,
|
||||
since it is very easy to monitor IR output of the controllers. It is
|
||||
just an experiment. Note that hardware needed for this experiment is
|
||||
@ -416,29 +412,6 @@ OpenOCD 0.6.1 now supports ST-Link/V2. We can use it:
|
||||
But it doesn't support option bytes handling (protection) yet.
|
||||
|
||||
|
||||
STM8S Discovery Kit
|
||||
-------------------
|
||||
|
||||
If you are using FTDI-2232D module and the connection is standard, type:
|
||||
|
||||
$ openocd -f interface/openocd-usb.cfg -f target/stm32f1x.cfg
|
||||
|
||||
Initially, the flash ROM of the chip is protected. you need to do:
|
||||
|
||||
$ telnet localhost 4444
|
||||
> reset halt
|
||||
> stm32f1x unlock 0
|
||||
> reset
|
||||
> shutdown
|
||||
$
|
||||
|
||||
and re-connect the board. Note that power-off / power-on sequence is
|
||||
required to reset flash ROM.
|
||||
|
||||
Then, invoke OpenOCD again and telnet to connect OpenCD and write
|
||||
image as above example of Olimex STM32-H103.
|
||||
|
||||
|
||||
STBee
|
||||
-----
|
||||
|
||||
|
||||
18
src/configure
vendored
18
src/configure
vendored
@ -3,7 +3,8 @@
|
||||
#
|
||||
# This file is *NOT* generated by GNU Autoconf, but written by NIIBE Yutaka
|
||||
#
|
||||
# Copyright (C) 2010, 2011, 2012, 2013 Free Software Initiative of Japan
|
||||
# Copyright (C) 2010, 2011, 2012, 2013, 2014
|
||||
# Free Software Initiative of Japan
|
||||
#
|
||||
# This file is a part of Gnuk, a GnuPG USB Token implementation.
|
||||
# Gnuk is free software: you can redistribute it and/or modify it
|
||||
@ -22,7 +23,7 @@
|
||||
# Default settings
|
||||
help=no
|
||||
vidpid=none
|
||||
target=OLIMEX_STM32_H103
|
||||
target=FST_01
|
||||
verbose=no
|
||||
with_dfu=default
|
||||
debug=no
|
||||
@ -93,12 +94,13 @@ Defaults for the options are specified in brackets.
|
||||
Configuration:
|
||||
-h, --help display this help and exit [no]
|
||||
--vidpid=VID:PID specify vendor/product ID [<NONE>]
|
||||
--target=TARGET specify target [OLIMEX_STM32_H103]
|
||||
--target=TARGET specify target [FST_01]
|
||||
supported targets are:
|
||||
OLIMEX_STM32_H103
|
||||
STM8S_DISCOVERY
|
||||
FST_01
|
||||
FST_01_00
|
||||
OLIMEX_STM32_H103
|
||||
STBEE
|
||||
STBEE_MINI
|
||||
FST_01_00 (unreleased version with 8MHz XTAL)
|
||||
--enable-debug debug with virtual COM port [no]
|
||||
--enable-pinpad=cir
|
||||
PIN entry support [no]
|
||||
@ -169,6 +171,10 @@ fi
|
||||
|
||||
# --with-dfu option
|
||||
if test "$with_dfu" = "yes"; then
|
||||
if test "$target" = "FST_01" -o "$target" = "FST_01_00"; then
|
||||
echo "FST-01 doesn't have DFU loader, you should not enable this."
|
||||
exit 1
|
||||
fi
|
||||
echo "Configured for DFU"
|
||||
ORIGIN=0x08003000
|
||||
FLASH_SIZE=`expr $FLASH_SIZE - 12`
|
||||
|
||||
Loading…
Reference in New Issue
Block a user