Note: The httpsrv_ssl_frdmk64f project might fail to compile due to the incorrect order of the builds. If this happens just wait until all the libraries complete their builds, then try to build httpsrv_ssl_frdmk64f again.

13. Now make sure the target board is plugged in to the USB for the debug connection. (Marked “SDA USB” on FRDM-K64F).

14. Select the httpsrv_ssl_frdmk64f project, and click on the arrow next to the image of the Bug and select Debug Configurations

17. When the download is finished, the IDE will then switch to the debug view and stop at the mqx rtos main function. Click the Resume button.

18. Open up the terminal program of your choice. Select the COM port provided by the board. For the default debug firmware (cmsis-dap) it will enumerate as mbed Serial Port (COM:xx). Select 115200 baud rate.

19. Type enter a few times to see the MQX Shell command line.

shell>

20. Type ipconfig. This will show the static IP address the demo software assigns itself by default.

shell> ipconfig

Eth# : 0

Link : off

MTU : 1496

MAC : 00:00:5e:a0:01:ca

IP4 : 192.168.1.202 Type: MANUAL

IP4 Mask : 255.255.255.0

IP4 Gate : 0.0.0.0

IP4 DNS : 0.0.0.0

Link status task stopped

shell>

21. Connect an Ethernet cable between your board and computer

22. Configure your computer network adaptor to be on the same IP subnet as the board. For example, set your PC to use a static IP address of 192.168.1.100

25. Your browser will report that there is a problem with the certificate. Don’t worry, this is expected! It is because the certificate used in the demo is self-signed. Thus, the browser is suspicious of the authenticity, like it should be!

The SSL Certificate and Key are pre-compiled into a Trivial File System (C Array) format and loaded to the Flash memory along with the program code. These can be used in development, but if you go into production and start shipping your own products, you will need to get a certificate signed by a Certificate Authority (CA) that verifies you are who you say you are.

28. Now you will have encrypted access to the RTCS webserver demo pages through your browser. (Note: Chrome crosses out the https because of the self-signed certificate used in this example.)

Note: The WebSocket example currently is not functional with SSL. All other examples are working.

29. You can check the traffic with WireShark or another traffic analysis tool.

30. See _readme.txt file at <Kinetis SDK>\tcpip\rtcs\examples\httpsrv for more details about the HTTP Server, including how to set up static DNS to avoid typing IP addresses and allow for certificates to function properly for both IPv4 and IPv6.

It shows the sample web pages in browser using HTTPS. But after some time web server crashes/hangs.Some times the web server will not even start(doesn't show the web pages) on flashing the code to tower board.

I see below Task Errors in IAR Task Summary.

Please let me know how to fix this issue.

Also, currently web pages and certificates are implemented in Trivial File System(TFS) in sample project given.

Please let me know how I should proceed further if I want use SD card to store web pages and certificates.

About switching the location of the certificate storage from internal flash using TFS to SD card, you can use MFS which is a FAT file system library provided with MQX RTOS. There is an SD card example in the MFS example projects. This should show how to use the MFS API.

Depending on the version of MQX you are using, the example will be in one of these locations:

If hello world is not working then I think there is a fundamental issue with your setup. Maybe the libraries didn't build correctly or perhaps an issue with your board or jumper settings. I think this is a separate topic than cyassl for MQX. I think this thread should be branched and addressed separately.