You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you look at CellularAtParseTokenHandler_t, however, you'll see it's defined as a function pointer to a function that does not return a value whereas Cellular_CommonUrcProcessCgreg returns a CellularError_t. Are the implementations wrong to use this function in this manner or is there a flaw in the interface design?
The text was updated successfully, but these errors were encountered:
@thirtytwobits
URC parsing error is handled in port URC handler implementation. Therefore, it is defined as a function pointer with no return value. Cellular_CommonUrcProcessCgreg is common handler implementation for 3GPP URC. The return value helps to indicate the URC parsing status to the port. Cellular port can make use of this common handler with the following example code:
Most of the implementations I've seen of this interface are like FreeRTOS-Cellular-Interface-Reference-Quectel-BG96/source/cellular_bg96_urc_handler.c where an array of
CellularAtParseTokenMap_t
is defined using functions likeCellular_CommonUrcProcessCereg
fromcellular_common_api.h
:If you look at
CellularAtParseTokenHandler_t
, however, you'll see it's defined as a function pointer to a function that does not return a value whereasCellular_CommonUrcProcessCgreg
returns aCellularError_t
. Are the implementations wrong to use this function in this manner or is there a flaw in the interface design?The text was updated successfully, but these errors were encountered: