| Electronic Components Datasheet Search |
|
NRF9160-SICA-R7 Datasheet(PDF) 80 Page - Nordic Semiconductor |
|
|
|||||||||||||||||||||||||||||
NRF9160-SICA-R7 Datasheet(HTML) 80 Page - Nordic Semiconductor |
|
80 / 400 page ![]() Peripherals • Prime field: secp160k1, secp192k1, secp224k1, secp256k1 • Edwards/Montgomery curves: • Ed25519, Curve25519 • ECDH/ECDSA support • Secure remote password protocol (SRP) • Up to 3072-bit operations • Hashing functions • SHA-1, SHA-2 up to 256 bits • Keyed-hash message authentication code (HMAC) • AES symmetric encryption • General purpose AES engine (encrypt/decrypt, sign/verify) • 128-bit key size • Supported encryption modes: ECB, CBC, CMAC/CBC-MAC, CTR, CCM/CCM* (CCM* is a minor variation of CCM) • ChaCha20/Poly1305 symmetric encryption • Supported key size: 128 and 256 bits • Authenticated encryption with associated data (AEAD) mode 6.1.1 Usage The CRYPTOCELL state is controlled via a register interface. The cryptographic functions of CRYPTOCELL are accessible by using a software library provided in the device SDK, not directly via a register interface. To enable CRYPTOCELL, use register ENABLE on page 82. Note: Keeping the CRYPTOCELL subsystem enabled will prevent the device from reaching the System ON, All Idle state. 6.1.2 Always-on (AO) power domain The CRYPTOCELL subsystem has an internal always-on (AO) power domain for retaining device secrets when CRYPTOCELL is disabled. The following information is retained by the AO power domain: • 4 bits indicating the configured CRYPTOCELL lifecycle state (LCS) • 1 bit indicating if the hard-coded RTL key, KPRTL (see RTL key on page 81), is available for use • 128-bit device root key, KDR (see Device root key on page 81) A reset from any reset source will erase the content in the AO power domain. 6.1.3 Lifecycle state (LCS) Lifecycle refers to multiple states a device goes through during its lifetime. Two valid lifecycle states are offered for the device - debug and secure. The CRYPTOCELL subsystem lifecycle state (LCS) is controlled through register HOST_IOT_LCS on page 85. A valid LCS is configured by writing either value Debug or Secure into the LCS field of this register. A correctly configured LCS can be validated by reading back the read-only field LCS_IS_VALID from the abovementioned register. The LCS_IS_VALID field value will change from Invalid to Valid once a valid LCS value has been written. 4418_1315 v2.0 80 |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |