REALTEK_RTL8195AM - WiFi implementation not complete? #4683
Labels
Comments
It doesn't get very far. |
|
cc @Archcady |
|
That K K K print and "KIFI" is also a bit strange. |
|
This "K" message can be switch off by undefine CONFIG_DEBUG_LOG in platform_autoconf.h inside of REALTEK's target directory. However I didn't get |
|
Yes, please modify the |
|
Remember to also use the .mbedignore in case you have a compilation problem with Atmel RF. |
|
Pushed new commit to Remember |
|
Ok, now we managed to get it to register ONCE with UDP- seems every run is a bit different and it either hangs or dies. Other issues we see
I think that's a bug and it shouldn't happen? |
|
I've got log like this, the register didn't success. |
|
Hi @Archcady - you seem to have some connection problem, it's not able to connect to the COAP server. Can you reach this address How large are the buffers in your WiFi stack? The certificate downloads are getting 2381 bytes a chunk, it seems to repeat that. Also the TLS handshaking is really slow, which might cause problems as well. Is the SSL acceleration enabled in the Ameba board with mbed OS 5.5? |
|
For wifi poor connection and no beacon behaviors, we think the reason is probably poor signal if you didn't attach antenna to board. |
|
Hi @Archcady I have placed the white antenna to the board and the phone I'm using to host the Wifi hotspot for it is within centimetres of the Ameba board. Checking the connectivity - if you have any device that can run for example |
|
Hi @JanneKiiskila , |
|
Hi @Archcady I found out that if I just repeatedly restart the There also seem to be some random crashes/freezes as well, we should found out the root cause for those. I.e. if you run the client 10 times, it should always end up with the same end result. Now it does not. |
|
With UDP & logs disabled I seem to have better luck, multiple passes now. |
|
Yes, indeed. The mbed-os-example-client is a bit complicated with all the LWM2M stuff and the problem is clearly the TLS handshake - that we can see from the logs. So, if you get #4700 resolved - it will likely resolve the mbed-os-client-example issue as well. Good work @marcuschangarm - smaller test case typically makes life easier. Enabling logs with UDP also makes the success rate drop, so extra load from serial tracing seems to impact this as well. |
|
I've closed the other issue since it turned out to be unrelated. When I run the mbed-os-example-client example, it often crashes before the TCP socket is even created, so the fix in the other thread wont help. @Archcady what tools do you use for debugging the RTL8195AM? We currently don't have pyOCD support for that board so we can't debug using gdb. |
|
@marcuschangarm, sadly we don't have some decent debugging methods, making debugging progress really slow. |
|
@0xc0170 @c1728p9 - could we get the PyOCD support? Everyone would be needing it... Ah, @marcuschangarm - you were faster again, issue raised already by you (pyocd/pyOCD#317). |
|
@sg- can we label is OSCA, due to the PyOCD dependency. |
|
@JanneKiiskila with #4754, TLS handshake should now work fine. |
|
Is there any work needed still on this issue from realtek side? |
|
I would close this one for now and file new issues via new issues. No point in hanging this for much longer unless more details can be surfaced. Though I have to admit that least I haven't been able to do much stress testing with this board anyway and it would likely be beneficial to run the stress tests for example for WiFi. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: This is just a template, so feel free to use/remove the unnecessary things
Description
#4665Bug
Target
REALTEK_RTL8195AM
Toolchain:
GCC_ARM
Toolchain version:
gcc-arm-none-eabi-6-2017-q1-update/
mbed-cli version:
(
mbed --version)1.1.1
meed-os sha:
(
git log -n1 --oneline)commit a3a7846817d7eefe59731762f681f53d2fc80da7 (HEAD -> enable_sdram, origin/enable_sdram)
Enable sdram usage of REALTEK_RTL8195AM #4665
Previous commit;
commit a39ac60
Merge: 4fc4405 ec72ac0
Author: Jimmy Brisson [email protected]
Date: Wed Jun 28 09:31:25 2017 -0500
DAPLink version:
?
Expected behavior
mbed-os-example-client should be able to connect to the mbed Connector.
Actual behavior
mbed-os-example-client is not able to connect, absolutely nothing seems to happen.
(Problem now that we can't enable the full logset due to the other issues).
Steps to reproduce
Question - has the ASYNC network API been implemented fully to the REALTEK_RLT8195AM?
Please note that mbed-os-example-wifi does not exercise the ASYNC API at all.
The text was updated successfully, but these errors were encountered: