awneil
March 29, 2010, 1:53pm
1
“Devices Services” or “raw” UART access:
ADL User Guide forOpen AT® OS v6.21:
identity:
This field is mandatory. It allows the service user to choose the UART
service provider it wants to work with. Setting this field to NULL generates
an error. Any non NULL value is considered by the UART service provider as
a pointer of a NULL terminated string. Supported string contents are listed
below:
• “UART1”: to get access to the Wireless CPU® UART1
• “UART2”: to get access to the Wireless CPU® UART2
• “UART3”: to get access to the Wireless CPU® USB serial port
So I should be able to use the USB (UART3) - yes?
So, again, I should be able to use the USB (UART3) - yes?
But, when I try it in that sample, I just get:
AT+WDU=1,“UART3”,115200
ERROR
The return value from adl_OpenDevice success is -1 - which is uncodumented
In the trace, I see:
Which is typically unhelpful - as it gives no indication as to which parameter is “wrong”, nor how it is “wrong”!
So, does anyone know the “trick” to getting this to work??
awneil
April 1, 2010, 10:30am
2
The trick is to fix Wavecom’s sample so that it works properly!
The ADL User Guide states that UART3 (USB) supports the “DCE” role only; but the sample application is hard-coded to use only the “Null-Modem” role - therefore the sample cannot possibly ever work with UART3 (USB)