- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some commands (join, counters, .. etc.) are returned errors under 9600 or 1200 bps.
Are the results of mfg test dependent on the UART speed?
Solved! Go to Solution.
- Labels:
-
SDK 3.x
-
UART
-
Wi-Fi Direct
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I mentioned - some of the commands are timing sensitive when data and/or parameters are passed back and forth between the client and the server
We don't officially support the wl tools below 19200
The wl tools are meant for manufacturing test and it is generally expected that in the production line you can run at least at 19200
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are some timing related constraints. Generally not recommended or tested below 19200. Any reason to want to use 1200 or 9600?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mfg_test app normally performs on the device ported WICED-SDK,
but wl_test program returns error depending on UART speed when a command (join or counters) was inserted.
"wl43362A2.exe --serial <portNum> ver" successively operated under 9600 and 1200bps, but a commands returned a error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I mentioned - some of the commands are timing sensitive when data and/or parameters are passed back and forth between the client and the server
We don't officially support the wl tools below 19200
The wl tools are meant for manufacturing test and it is generally expected that in the production line you can run at least at 19200
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I checked the uart Rx/Tx with Oscilloscope, Rx data is good but Tx data is broken form MCU.
I guess that MCU's uart driver has some bug or needs to be set a configuration related timing.
Currently, UART driver of this MCU is set polling instead of interrupts setting.
Anyway, the apps or test tools well perform on WICED reference board without any problem.