-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HardFault when running Greentea netsocket tests #17
Comments
This might also be due to too low values for TX/RX buffers (see here). |
I tested with few buffers sizes (512, 640, 768, 1024) for TX/RX buffers but no improvement. |
How often will |
In my understanding _ifup() is called only once during the test setup phase. |
Could you pls. provide a complete execution trace? |
Full trace below.
|
Feels like a stack overflow. Can you increase the stack size of the dynamically created Threads in the test? |
First execution tests on my side seem to confirm that we are facing stack overflows. |
Yes, I agree. Increasing thread stack size fixes the issue. I saw random crash when test case TCPSOCKET_ECHOTEST_BURST_NONBLOCK was running. Lets see if I can reproduce it. |
I did not have problems with TCPSOCKET_ECHOTEST_BURST_NONBLOCK, but pls. note that both TCPSOCKET_RECV_100K tests will fail (see #11). |
I would furthermore suggest the following mofification:
|
Thank you for suggesting improvements. I was able to reproduce the hardfault with TCPSOCKET_ECHOTEST_BURST:
|
How deterministic is this behavior and which FW version are you using? |
Any update on this issue? |
Sorry for the late reply. I'm using the latest FW version 3.6. |
@betzw Looks good to me. If you don't mind could you please raise a PR? I can also do it myself but it might take a while. You also want to include the stack size increase I assume. Would be good to increase the TCP_OS_STACK_SIZE size as it also gets hit if one compiles with debug profile. |
Not sure when I will have some time to create a PR, but I'll keep you informed. |
Can we close this issue? |
Stack size is insufficient for debug profile Stack size is insufficient for NUCLEO_F401RE+IDW01M1 Please see ARMmbed/wifi-x-nucleo-idw01m1#17
@juhaylinen @betzw The issue can be closed. |
Stack size is insufficient for debug profile Stack size is insufficient for NUCLEO_F401RE+IDW01M1 Please see ARMmbed/wifi-x-nucleo-idw01m1#17
Stack size is insufficient for debug profile Stack size is insufficient for NUCLEO_F401RE+IDW01M1 Please see ARMmbed/wifi-x-nucleo-idw01m1#17
NUCLEO_F401RE+IDW01M1
Mbed-os SHA: 3c25b9644
Steps to reproduce:
mbed_app.json:
HardFault:
The text was updated successfully, but these errors were encountered: