Topic: Hardfault with Atmel Client / Server TLS example
I was hoping to evaluatie WolfSSL + ATECC508, so I went ahead and purchased the hardware listed as requirements in https://www.wolfssl.com/wolfSSL/wolfssl-atmel.html in an attempt to test the first example (client/server). After building the associated projects and flashing the devices I see the client open a socket with the server before both devices hardfault. As far as I can tell, there appears to be an uninitialized memory access causing this fault. I see the following output:
-- TLS SERVER starts with ATECC508A over WINC module -- (APP)(INFO)Chip ID 1503a0 (APP)(INFO)Firmware ver : 19.3.0 (APP)(INFO)Min driver ver : 19.3.0 (APP)(INFO)Curr driver ver: 19.3.0 M2M_WIFI_RESP_CON_STATE_CHANGED: CONNECTED M2M_WIFI_REQ_DHCP_CONF: IP is 10.1.4.119 WINC is connected to TempE successfully! Socket Event : BIND socket event socket callback : bind success! Socket Event : LISTEN socket event socket callback : listen success! Socket Event : ACCEPT socket event socket callback : accept success! Hard fault handler (all numbers in hex): R0 = 0 R1 = f R2 = 2deb5 R3 = 2ded3 R12 = ca62c1d6 LR [R14] = 22aa7 subroutine call return address PC [R15] = 2135a program counter PSR = 1000000 CFSR = 0 HFSR = 0 DFSR = 0 AFSR = 0 MMAR = 0 BFAR = 0
Is there modifications or perhaps a missing build step that I am missing? Alternatively is there a specific version of atmel studio that is recommended for evaluating this demo? Another post (https://www.wolfssl.com/forums/topic965 … c508a.html) mentioned this port may not be completely finished. I did however see example output in the Readme that leads me to believe I have made a mistake somewhere along the line.
If anyone has had success with this example I would really appreciate the help getting past this point.