for aws mqtt connection, the API seems to accept only pointer memory location or fat fs paths.
What's the best way of doing this if the aws cert is not embedded in the binary and stored in NVS?
It seems like a waste memory to have to copy the certs and keys from NVS into memory before passing onto the MQTT/TLS interface.
Someone mentioned passing a pointer from the nvs blob. Is that possible?
TIA
-a
is copy-less read operations possible for nvs blobs?
Re: is copy-less read operations possible for nvs blobs?
@WiFive. Thanks for the pointer.
Who is online
Users browsing this forum: No registered users and 106 guests