mbedTLS + 0/6 examples
SourceVu will show references to mbedtls_ssl_write() from the following samples and libraries:
Examples
STM32469I_EVAL
Applications
mbedTLS
STM324x9I_EVAL
Applications
mbedTLS
STM324xG_EVAL
Applications
mbedTLS
 
Symbols
loading...
Files
loading...
SummarySyntaxArgumentsRelatedReferences

Return value

The (non-negative) number of bytes actually written if successful (may be less than \p len). #MBEDTLS_ERR_SSL_WANT_READ or #MBEDTLS_ERR_SSL_WANT_WRITE if the handshake is incomplete and waiting for data to be available for reading from or writing to the underlying transport - in this case you must call this function again when the underlying transport is ready for the operation. #MBEDTLS_ERR_SSL_ASYNC_IN_PROGRESS if an asynchronous operation is in progress (see mbedtls_ssl_conf_async_private_cb()) - in this case you must call this function again when the operation is ready. #MBEDTLS_ERR_SSL_CRYPTO_IN_PROGRESS if a cryptographic operation is in progress (see mbedtls_ecp_set_max_ops()) - in this case you must call this function again to complete the handshake when you're done attending other tasks. Another SSL error code - in this case you must stop using the context (see below).

Notes

When this function returns #MBEDTLS_ERR_SSL_WANT_WRITE/READ, it must be called later with the *same* arguments, until it returns a value greater that or equal to 0. When the function returns #MBEDTLS_ERR_SSL_WANT_WRITE there may be some partial data in the output buffer, however this is not yet sent. If the requested length is greater than the maximum fragment length (either the built-in limit or the one set or negotiated with the peer), then: - with TLS, less bytes than requested are written. - with DTLS, MBEDTLS_ERR_SSL_BAD_INPUT_DATA is returned. \c mbedtls_ssl_get_max_frag_len() may be used to query the active maximum fragment length. Attempting to write 0 bytes will result in an empty TLS application record being sent.

References

from examples