USB interaction with GenericApp

Hi, refer to this thread, you might find it helpful

Hi,

When you open this thread, go to the bottom of the page, and click on the left arrow (bold gray), all the answers will be displayed now.

A have attached a picture that shows this arrow.

Hi,

In this case USB functionality (access) is wrapped by UART module, for example, search for HalUARTRx through entire project

(use Ctrl+Shift+F) which is a Rx function for UART. There you'll notice, under '#if HAL_UART_USB', a call for HalUARTRx(buf, len);

HalUARTRx() and other USB related functions are found in _hal_uart_usb.c, this file included with #include, means you won't

find it in the workspace tree, it can be found here: "...\ZStack istallation folde\Components\hal\target\CC2530USB"

Good luck

Not sure, it depends on how the USB dongle is recognized by windows, is it a HID device (in this case you don't need install

any driver), or a CDC device, for CDC device you may need install LUFA driver (serial over USB): lufa_driver.zip

The VID and PID must be changed according to the information you get from device manager

You can also refer to Z-Stack Monitor and Test API.pdf.

Hi,

The function is added in GenericApp.c. It is initialised inside in GenericApp_Init.

BR

Srikanth

Hi, pls see my generic app init below:

halUARTCfg_t uartConfig;

void GenericApp_Init( uint8 task_id )
{
GenericApp_TaskID = task_id;
GenericApp_NwkState = DEV_INIT;
GenericApp_TransID = 0;

// Device hardware initialization can be added here or in main() (Zmain.c).
// If the hardware is application specific - add it here.
// If the hardware is other parts of the device add it in main().

GenericApp_DstAddr.addrMode = (afAddrMode_t)AddrNotPresent;
GenericApp_DstAddr.endPoint = 0;
GenericApp_DstAddr.addr.shortAddr = 0;

// Fill out the endpoint description.
GenericApp_epDesc.endPoint = GENERICAPP_ENDPOINT;
GenericApp_epDesc.task_id = &GenericApp_TaskID;
GenericApp_epDesc.simpleDesc
= (SimpleDescriptionFormat_t *)&GenericApp_SimpleDesc;
GenericApp_epDesc.latencyReq = noLatencyReqs;

// Register the endpoint description with the AF
afRegister( &GenericApp_epDesc );

// Register for all key events - This app will handle all key events
RegisterForKeys( GenericApp_TaskID );

// Update the display
#if defined ( LCD_SUPPORTED )
HalLcdWriteString( "GenericApp", HAL_LCD_LINE_1 );
#endif

ZDO_RegisterForZDOMsg( GenericApp_TaskID, End_Device_Bind_rsp );
ZDO_RegisterForZDOMsg( GenericApp_TaskID, Match_Desc_rsp );

#if defined( IAR_ARMCM3_LM )
// Register this task with RTOS task initiator
RTOS_RegisterApp( task_id, GENERICAPP_RTOS_MSG_EVT );
#endif




uartConfig.configured = TRUE;
uartConfig.baudRate = HAL_UART_BR_115200;
uartConfig.flowControl = FALSE;
uartConfig.flowControlThreshold = 48;
uartConfig.rx.maxBufSize = 128;
uartConfig.tx.maxBufSize = 128;
uartConfig.idleTimeout = 6;
uartConfig.intEnable = TRUE;
uartConfig.callBackFunc = GenericApp_CallBack;
HalUARTOpen (HAL_UART_PORT_0, &uartConfig);
}

BR
Srikanth

Hi,

Found out the issue with write function inside the call back function.

static void GenericApp_CallBack(uint8 port, uint8 event)
{
static uint8 s_RxBuf [128]; 
uint16 bufLen; 
bufLen = Hal_UART_RxBufLen(HAL_UART_PORT_0);
HalUARTRead(HAL_UART_PORT_0, s_RxBuf , bufLen);
HalUARTWrite( HAL_UART_PORT_0, s_RxBuf, (uint8)osal_strlen( (char*)s_RxBuf )); 
}

correct version of HalUARTWrite is as below and not as given in the above function. It is the issue with length of the data being written

HalUARTWrite( HAL_UART_PORT_0, s_RxBuf, bufLen ); 

BR

Srikanth