1. One hour of writing a reply DOWN THE DRAIN, because this didn't autosave... Here I go again. (GRRRRR)
(1.a IT DID IT AGAIN! Lucky for me I'm smart enough to learn NOT to trust this site... I copied it before I hit post and lost everything. )
2. Why is this NOT sending me notifications that a reply was posted??
3. On to the problem,
I am using TIROTS, so I defined it in the settings.h
I am NOT using any configure build tool. (Most nothing works right in these environments anyway, and usually requires a bloat-load of other freeware tools installed to make the scripts work).
I brought in the source, and built it in a TI CCS project.
All I need to do is provide the definitions to include the cipher suites that allow this to connect as an SSL client to a server, typically an IIS server. It works in the Windows build, but not in the ARM TIRTOS build.
So I am fumbling around in the dark of lacking doc trying to figure out how to enable the suites. Probably need to enable most of them to accommodate a wide variety of potential servers that will have to be connected to.
https://www.wolfssl.com/docs/frequently … r_wolfSSL?
Tells me to put all the settings in "user_settings.h" and define WOLFSSL_USER_SETTINGS in the APPLCATION...
If I DON"T define it in the library how does it get those #defines into the lib? They are already defined in the application, aren't they needed?
And those settings...
Are they supposed to be mimicked between "settings.h" and "user_settings.h" ? Because they are in both...
The examples in IDE/GCC-ARM/Headers/user_settings.h have #defines that are redundant to the ones in sections of "settings.h" (TIRTOS, FREERTOS, ARDUINO, etc...)
If I #define one of those systems in "user_settings.h" should they be removed from "settings.h"?
What if they conflict? What if I don't want one, but it's defined in the other??
Of course... Windows build doesn't have ANYTHING from the "settings.h" And gets everything from it's "user_settings.h".
I have already created a SSL Server in this ARM TIRTOS environment and selected the limited suites using wolfSSL_CTX_set_cipher_list(...) and that all works fine. But now I need a client. And something in the ARM build isn't working.
(What fun... retyping this all over again)
<Code shown is not to scale>