Maybe the problem is about ADL_PORT_OPEN_AT_VIRTUAL_BASE… See comment under adl_callSetup ! It says that adl_callSetup runs adl_callExtSetup on ADL_PORT_OPEN_AT_VIRTUAL_BASE. Then it says that related events will NOT be forwarded to any external port as the command was running on Open AT port…
Here are the structures definitions of the adl_at.h (Open AT 3.12). The “Port” attribut you were trying to use is only available for adl_atCmdPreParser_t structure :
/****************************************************************************/
/* Body structures assosciated to AT Messages */
/****************************************************************************/
/* --------------------------------- */
/* Body for response message type : */
/* --------------------------------- */
typedef struct
{
#ifndef __REMOTETASKS__
adl_strID_e RspID;
adl_atPort_e Dest;
#else
u8 RspID;
u8 Dest;
#endif
u16 StrLength;
ascii StrData[1];
} adl_atResponse_t;
/* ------------------------------------ */
/* Body for unsolicited message type : */
/* ------------------------------------ */
typedef struct
{
#ifndef __REMOTETASKS__
adl_strID_e RspID;
adl_atPort_e Dest;
#else
u8 RspID;
u8 Dest;
#endif
u16 StrLength;
ascii StrData[1];
} adl_atUnsolicited_t;
/* -------------------------------- */
/* Body for command message type : */
/* -------------------------------- */
typedef struct
{
u16 Type; // Cmd type
u8 NbPara; // Parameters number
#ifndef __REMOTETASKS__
adl_atPort_e Port; // Source port
#else
u8 Port;
#endif
wm_lst_t ParaList; // Parameters list
u16 StrLength; // Command string length
ascii StrData[1]; // Command string
} adl_atCmdPreParser_t;
#endif // __ADL_AT_H__
Well, if you look well into the definitions i’ve post, you can see that “adl_atResponse_t” structure as an “adl_atPort_e” attribut, which is called “Dest”. That should be what you’re looking for…
About this question, you’re the only one who can answer… Where did you get this code from ? From this forum ? From Wavecom included examples ? etc…