OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/benchmarks/mbedtls/prj.conf

27 lines
600 B
Plaintext
Raw Normal View History

tests: add missing CONFIG_TEST=y in test suites In several test suites CONFIG_TEST was missing. Define CONFIG_TEST=y, so testing-related Kconfig options (depending on TEST) get switched-on. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-03-17 17:41:21 +08:00
CONFIG_TEST=y
samples: net: Port mbedtls benchmark sample to zephyr This application benchmarks the various cryptographic primitives offered by mbed TLS. Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2018-12-04 16:47:38 +08:00
# Kernel options
CONFIG_MAIN_STACK_SIZE=10000
CONFIG_ENTROPY_GENERATOR=y
CONFIG_INIT_STACKS=y
# Logging
CONFIG_PRINTK=y
CONFIG_MBEDTLS_DEBUG=y
modules: mbedtls: convert mbedTLS log levels to Zephyr log levels So far LOG_DBG() was used inside debug hook for mbedTLS library. This meant that it was hard to distinct log messages by simply looking at the log level number, even though Zephyr logging subsystem supports colorful logs depending on log level. Choose an appropriate Zephyr LOG_*() macro based on log level coming from mbedTLS library. Remove log level number from formatted log messages, as it is now redundant. One controversial thing about this change is that mbedTLS' "2 State change" log level is mapped to Zephyr's "warning" log level. Those are not really warnings in real life, but rather informational messages. However, using "warning" log level for those allows to clearly distinguish between "2 State change" and "3 Informational" debug messages from mbedTLS. Additionally, mbedTLS debug message implementation does not seem to be safe to use in production, so keeping in mind MBEDTLS_DEBUG will be enabled just during debugging phase, printing "2 State change" logs as warnings should not be a big deal. Set default MBEDTLS_DEBUG_LEVEL value depending on selected Zephyr logging module level, so that only single option needs to be configured in application project. Remove prompt for MBEDTLS_DEBUG_LEVEL, so that interactively (e.g. via menuconfig) adjusting MBEDTLS_LOG_LEVEL will always result in automatically updating MBEDTLS_DEBUG_LEVEL option. This is to prevent so called "stuck symbol syndrome". Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
2022-06-15 06:32:24 +08:00
CONFIG_MBEDTLS_LOG_LEVEL_DBG=y
samples: net: Port mbedtls benchmark sample to zephyr This application benchmarks the various cryptographic primitives offered by mbed TLS. Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2018-12-04 16:47:38 +08:00
# TLS configuration
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_BUILTIN=y
CONFIG_MBEDTLS_ENABLE_HEAP=y
CONFIG_MBEDTLS_HEAP_SIZE=64000
CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN=2048
CONFIG_MBEDTLS_TLS_VERSION_1_2=y
CONFIG_MBEDTLS_KEY_EXCHANGE_ALL_ENABLED=y
CONFIG_MBEDTLS_CIPHER_ALL_ENABLED=y
CONFIG_MBEDTLS_ECP_ALL_ENABLED=y
CONFIG_MBEDTLS_MAC_ALL_ENABLED=y
CONFIG_MBEDTLS_GENPRIME_ENABLED=y
CONFIG_MBEDTLS_HMAC_DRBG_ENABLED=y