CC3135MOD: P2P Device Name. No Random Part

Oleksandr Bogush

Part Number: CC3135MOD

Hi,

According to the SWRU455M “SimpleLink Wi-Fi® CC3x20, CC3x3x Network Processor. User’s Guide” p.65 “The device name is compound of the URN and two random characters. Users can set only the URN; the random characters are internally generated. Default = mysimplelink_XX (xx = random two characters).” There is no random part after P2P device name transmitted over WiFi; only the URL name set by: sl_NetAppSet (SL_NETAPP_DEVICE_ID,SL_NETAPP_DEVICE_URN,…)

Thanks,

Olek

over 1 year ago

0 Kobi Leibovitch over 1 year ago

TI__Guru 61436 points

Are you checking the URN in the packets over the air? can you provide a sniffer log?

Do you see the random number with mysimplelink_XX? (i.e. without setting the URN)?

0 Oleksandr Bogush over 1 year ago in reply to Kobi Leibovitch

Intellectual 290 points

No, I check the list of available WiFi devices on my phone. Can you recommend a sniffer, I would really appreciate it.

I did not check the original setting. It is irrelevant to me - I need to replace mysimulink anyway in my product.

0 Kobi Leibovitch over 1 year ago in reply to Oleksandr Bogush

TI__Guru 61436 points

You can always add the 2 bytes yourself.

You can use the NWP TRNG.

- SL_NETUTIL_TRUE_RANDOM:
\code
uint32_t randNum;
int32_t len = sizeof(uint32_t);

sl_NetUtilGet(SL_NETUTIL_TRUE_RANDOM, 0, (uint8_t *)&randNum, &len);
\endcode
<br>
*/

0 Oleksandr Bogush over 1 year ago in reply to Kobi Leibovitch

Intellectual 290 points

Well, if you do not plan to fix this, it could be a solution. If you fix it in a future service pack, I will end up with two random parts…

0 Kobi Leibovitch over 1 year ago in reply to Oleksandr Bogush

TI__Guru 61436 points

As we are not providing new SPs for these devices frequently and since there is a relatively easy patch on the application side - i would not expect this to be fixed in the short term.

I recommend that you will implement the fix and check the release notes when you update the SDK or SP.

0 Oleksandr Bogush over 1 year ago in reply to Kobi Leibovitch

Intellectual 290 points

The problem is that you do not reveal a detailed errata list. I asked for changes from a specific SP and driver versions in a separate post and did not get an answer. If I implement this fix on my side, I will have to lock SP/Driver updates for my product.

0 Kobi Leibovitch over 1 year ago in reply to Oleksandr Bogush

TI__Guru 61436 points

Please assume that this will not be fixed (anyway i won't be able to commit for a date for that).

There are not many P2P users and probably even less that needs to update the name - so we can keep with this workaround for now.

Just verify that this works as expected over the air.

As for a sniffer, you can check for adapters compatible with Wireshark (I currently use wlanpi, see https://github.com/WLAN-Pi/WLANPiShark2).

0 Oleksandr Bogush over 1 year ago in reply to Kobi Leibovitch

Intellectual 290 points

Ok - I understand this. Thanks a lot for the sniffer reference.

Wi-Fi

Wi-Fi forum

CC3135MOD: P2P Device Name. No Random Part