Https disconnect crash issue on SDK 3.1.0

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hi,

We saw a major issue on calling wiced_tcp_disconnect with tis context that will lead to system crash.. This can be very easily reproduced on the demo code snip.https_client sample in the SDK.

Best Regards,

Aaron Lee

0 Likes
1 Solution
Anonymous
Not applicable

This has been root caused to a bug in gcc producing an invalid instruction sequence under some circumstances.

Recommended fix is to modify the wiced_toolchain_ARM_GNU.mk and change line 102/103 from "-O3" to "-Os"

View solution in original post

8 Replies
Anonymous
Not applicable

Can you please do a test for me - can you build and run in debug mode and see if the issue still happens or not? add "-debug" to the makefile command

Anonymous
Not applicable

Hi,

Enabling the debug on snip.https_client will help but still crashes if you loop the https get. It will crash after few loop.

Aaron Lee

Sent from my iPhone

0 Likes
Anonymous
Not applicable

This has been root caused to a bug in gcc producing an invalid instruction sequence under some circumstances.

Recommended fix is to modify the wiced_toolchain_ARM_GNU.mk and change line 102/103 from "-O3" to "-Os"

Anonymous
Not applicable

Was this fixed in 3.1.1? If not what parameter (and line number if possible) needs to fixed in:

wiced_toolchain_ARM_GNU.mk


COMPILER_SPECIFIC_RELEASE_CFLAGS?



0 Likes
Anonymous
Not applicable

Yes this has been fixed in SDK 3.1.1. No changes required

Anonymous
Not applicable

Hi

Is this problem solved in SDK 3.1.1? 

I had similar problem in SDK 3.1.1. Web access seem not to be valid.

so if connection is done , and try get another page then it takes long time.

Test env : SDK 3.1.1 + FreeRTOS+LwIP

I changed OS from FreeRTOS to ThreadX, Web access is working well and no problem occured.

So I thought that this is driven from

  - memory usage(management ) difference is from each OS, so some of malloc fail happen.

  - socket count management in http server

  - socket connection timeout

Test env : SDK 3.1.1 + ThreadX+NetX

With changing to ThreadX, all works fine.

Additionally,  ThreadX has some other issues in different function.

TKS

0 Likes
Anonymous
Not applicable

Hi Alex,

We use SDK 3.1.1 + ThreadX+NetX setup and so far is working alright.  I suggest to post another thread specific for 3.1.1 with your setup and see how Broadcom response.

0 Likes
Anonymous
Not applicable

Hi  aaron

   it is good to hear that you are all right.

   With 4390, I am doing test with 4390 module  and you can see our module's web.

  It is working well with ThreadX

   http://damosys.com:9990

   It is 4390's EVB and our web in module.

   We are planing our own module with good antenna design.

   

  TKS

0 Likes