|Subject:||Re: [lwip-users] lwIP with mbedTLS|
|Date:||Mon, 28 Jan 2019 10:36:37 +0100|
This is TI CC1312R microcontroller (Cortex M4F, 80 kB RAM, 352 kB Flash). uC has got some crypto accelerators built in which I plan to use after establishing proper communication.At the moment about 20 kB RAM free (I'm sure that I could make some additional savings). PBUF_POOL_BUFSIZE 1516 bytes (TCP_MSS 1460).MBEDTLS_SSL_MAX_CONTENT_LEN and MBEDTLS_MPI_MAX_SIZE are set to 4096.
pon., 28 sty 2019 o 08:24 tomek wilkxt <address@hidden> napisał(a):HiWhich CPU do you use and how much free RAM do you have?Ethernet frame size is 1514, how is your PBUF_POOL_BUFSIZE size?niedz., 27 sty 2019 o 20:40 Paweł <address@hidden> napisał(a):Hi Jan,I encountered memory problems in the beginning (cpu hang - insufficient heap memory) but after little tuning the application works well.Sometimes when Server Hello message is delayed a bit (what I'm contantly observing on Wireshark) handshake will just end with WANT_READ error before it could even read this message.Also I don't see any memory problems on mbedTLS debug and no errors on lwip_stats.Please look at logs below. I'm attaching also Wireshark packets with Handshake beginning. Packet 6510 is a client hello message (compared with Wireshark). Look when it is ready, and when it is sent out on interface - just after returning error on parsing Server Hello which couldn't be there as Client Hello is still in buffer!This is why I supposed threading problems.
|[Prev in Thread]||Current Thread||[Next in Thread]|