When trying to connect to SSID with a non-utf8 apostrophe (in our case, it's the "right single quote" U+2019: https://www.compart.com/en/unicode/U+2019), DA16K successfully connects to the AP but then when querying WFJAP, responds with erroneous SSID (in this case 0617061e2809973207769666 as opposed to papa's wifi). See attached log screenshot.
0617061e2809973207769666
papa's wifi)
Chip: DA16200
SDK: RTOS 3.2.8.5
Hi ST-Kon,Thank you for posting your question online.Let me try to recreate this issue.
ST-Kon said:SDK: RTOS 3.2.8.5
Are you sure that this is the SDK FreeRTOS version? The latest version is v3.2.8.1. If you have another version, it might be a custom version.Best Regards,OV_Renesas
Sorry, it's 3.2.8.1. That was a typo.
Hi ST-Kon,Apologies for the delay.I was able to recreate this issue.The right apostrophe you tried to use is not supported.I tried to configure my Laptop (Windows) and I got the following message:The default ' character can be used and I was able to connect with the DA16200MOD EVK with this specific character.Best Regards,OV_Renesas
The apostrophe should be in the SSID, not the password. The windows may not allow it, but some routers do. I was able to set up my router with a right apostrophe in the SSID name.
Try with a different router if you can't do it in windows because we have customers that have right apostrophes in their SSID name and I was able to set it up on my router as well.
This is definitely an issue for us.
Hi ST-Kon,Thank you for the reply and the clarifications.First, I changed the SSIDs name using the ' character:I did not face any issues. Then I copied the apostrophe character as shown in the link you shared and I was able to replicate the issue:I am not really sure why this issue happens, let me check on this and I will get back to you as soon as possible.Best Regards,OV_Renesas
Hi ST-Kon,
In the Easy Setup, as you can see, the non-printable characters in the SSID are displayed in the hex string. This is expected behavior.
However, we have confirmed that in the SDK v3.2.8.1, there is a problem where an SSID containing non-printable characters is sent to the host in the format of a hex string.
So we have made changes to fix the problem and attached the diff file.Please test this on your side and let us know if you have any issues.Best Regards,OV_Renesas0001-changes_to_fix_non-printable_ssid_issue.zip
The hex string `0617061e2809973207769666` doesn't appear to be a hex representation of papa's wifi.
papa's wifi.
OV is OOO, I will check on this and back to you as soon as possible.
BR,
Jason
Any update on this?
Hi ST-Kon,Apologies for this delay.
ST-Kon said:The hex string `0617061e2809973207769666` doesn't appear to be a hex representation of papa's wifi.
You are correct, the hex representation is shown only in the Easy Setup (via UART0). Have you tested the patch we provided? The patch has solved the issue on our side with AT commands. Best Regards,OV_Renesas