- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
We try to certicate our product by an EMC laboratory and this laboratory asks to genarate this radio mode :
We use the USI module and to realize the software, I've took the snip.console example compiled with the WL commands, to generate the different mode with the following command :
But each time, I execute the pkteng_start command, I've the result “wl unsupported”.
So my question is how to realize the demand of the laboratory ?
Thank you for your help.
Baptiste
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version windows you run the wl43362.exe !
Basic the wlXXXX.exe buit-in SDK is build for Win32! We try it under WinXP is work!
But if you run wlXXXX.exe under Win64 environment will run-into some problem!
maybe you could find one PC run WinXP to check it could pass your WiFi test
or re-build the wlXXXX under your Windows platform!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which USI are you using in your design? WICED or Linux based? The module is not pre-certified?
I ask because typically the module partner themselves will work with you on the regulatory process.
jone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jone,
We use the WM-N-BM-14 with the integrated antenna with the SDK WiCED 3.5.2 and 3.7.0. Yes the module is pre-certified but apparently because we have implanted another radio chip (a BLE chip) with this module, the laboratory want to do this test on the wifi. I have contacted USI about my problem but since last week, I've no answer.
Baptiste
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will need to check internally with the Apps team to see who should support this type of inquiry as we normally have customers work with the module maker, but in this instance, I'm not sure USI can help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. for Radio test you have to load the apps/test/mfg_test embedded MFG F/W !
Otherwise most wl command will response not supported
Please refer. WICED™ Development System, Manufacturing Test User Guide
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello jone
I've tried the to follow the manufacturing test user guide but I've the same respond for all command :
query_info_fe: remote cdc header return error code -1
Wifi adapter unsupported
I've rebuild the wiced mfg_test and the windows mgt_test executable with more debug:
>wl43362A2.exe --serial 10 ver
send sync
w 0001 > 25
send CDC header
Command: WLC_GET_MAGIC
w 0036 > 00 00 00 00 04 00 00 00 02 00 00 00 00 00 00 00 04 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00
Send Data
w 0004 > 62 11 3C 77
Waiting on receive sync
r 0001 < 30
r 0001 < 20
r 0001 < 34
r 0001 < 20
r 0001 < 32
r 0001 < 20
r 0001 < 34
r 0001 < 0D
r 0001 < 0D
r 0001 < 0A
r 0001 < 52
r 0001 < 45
r 0001 < 43
r 0001 < 20
r 0001 < 3A
r 0001 < 20
r 0001 < 63
r 0001 < 6D
r 0001 < 64
r 0001 < 20
r 0001 < 30
r 0001 < 09
r 0001 < 20
r 0001 < 6D
r 0001 < 73
r 0001 < 67
r 0001 < 20
r 0001 < 6C
r 0001 < 65
r 0001 < 6E
r 0001 < 20
r 0001 < 34
r 0001 < 20
r 0001 < 20
r 0001 < 6D
r 0001 < 73
r 0001 < 67
r 0001 < 20
r 0001 < 66
r 0001 < 6C
r 0001 < 61
r 0001 < 67
r 0001 < 20
r 0001 < 32
r 0001 < 09
r 0001 < 20
r 0001 < 6D
r 0001 < 73
r 0001 < 67
r 0001 < 20
r 0001 < 73
r 0001 < 74
r 0001 < 61
r 0001 < 74
r 0001 < 75
r 0001 < 73
r 0001 < 20
r 0001 < 30
r 0001 < 0D
r 0001 < 0A
asked 1 bytes got 0 bytes
r 0001 < 52
r 0001 < 45
r 0001 < 53
r 0001 < 50
r 0001 < 20
r 0001 < 3A
r 0001 < 20
r 0001 < 63
r 0001 < 6D
r 0001 < 64
r 0001 < 20
r 0001 < 30
r 0001 < 09
r 0001 < 20
r 0001 < 6D
r 0001 < 73
r 0001 < 67
r 0001 < 20
r 0001 < 6C
r 0001 < 65
r 0001 < 6E
r 0001 < 20
r 0001 < 34
r 0001 < 0D
r 0001 < 0A
r 0001 < 25
Receive CDC header
r 0036 < FF FF FF FF 04 00 00 00 04 00 00 00 00 00 00 00 04 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00
IOCTL Status: Success
query_info_fe: remote cdc header return error code -1
Receive data
r 0004 < 62 11 3C 77
Wifi adapter unsupported
Have you any idea ?
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version windows you run the wl43362.exe !
Basic the wlXXXX.exe buit-in SDK is build for Win32! We try it under WinXP is work!
But if you run wlXXXX.exe under Win64 environment will run-into some problem!
maybe you could find one PC run WinXP to check it could pass your WiFi test
or re-build the wlXXXX under your Windows platform!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
jone wrote:
maybe you could find one PC run WinXP to check it could pass your WiFi test
or re-build the wlXXXX under your Windows platform!
Asking users to run WinXP does not make sense. It's already EOL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The trace in the post are the trace from a rebuild of wl43362A2.exe (I've compiled with the define DEBUG_SERIAL) and we have no computer with Win XP.
But I think the programs work well, but the response from the module is strange :
r 0036 < FF FF FF FF 04 00 00 00 04 00 00 00 00 00 00 00 04 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00
the msg.cmd is set to FFFFFFFF (line 667 wlu_client_shared.c).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
After re-download the sdk and restart from original project, the apps/test/mfg_test embedded MFG F/W working fine.
Thanks for the help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Baptiste,
Glad to hear you have the software running and can perform the tests.
Just remember to always send a pkteng stop command once you've finished each tx test.
Regards
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jone,
Thank you for your answer,
My contact in USI is Stone Shih.