文件列表:

Board.h (2832, 2016-08-16)
CC1310.custom_argvars (146, 2016-08-16)
CC1310.eww (222, 2016-08-16)
CC1310DK_7XD.c (15052, 2016-08-16)
CC1310DK_7XD.h (7437, 2016-08-16)
Debug (0, 2016-08-16)
Debug\Exe (0, 2016-08-16)
Debug\Exe\SimpleUART.out (345380, 2016-08-16)
Debug\Exe\SimpleUART.sim (24485, 2016-08-16)
Debug\Exe\SimpleUARTRX.out (352572, 2016-08-16)
Debug\Exe\SimpleUARTRX.sim (25597, 2016-08-16)
Debug\Obj (0, 2016-08-16)
Debug\Obj\CC1310DK_7XD.o (35331, 2016-08-16)
Debug\Obj\CC1310DK_7XD.pbi (2008072, 2016-08-16)
Debug\Obj\CC1310DK_7XD.pbi.cout (10743, 2016-08-16)
Debug\Obj\EasyLink.o (91493, 2016-08-16)
Debug\Obj\EasyLink.pbi (995804, 2016-08-16)
Debug\Obj\EasyLink.pbi.cout (10762, 2016-08-16)
Debug\Obj\SimpleUART.pbd (2198718, 2016-08-16)
Debug\Obj\SimpleUART.pbd.browse (2198718, 2016-08-16)
Debug\Obj\SimpleUARTRX.pbd (2178880, 2016-08-16)
Debug\Obj\SimpleUARTRX.pbd.browse (2178880, 2016-08-16)
Debug\Obj\ccfg.o (4918, 2016-08-16)
Debug\Obj\ccfg.pbi (131378, 2016-08-16)
Debug\Obj\ccfg.pbi.cout (10749, 2016-08-16)
Debug\Obj\rfEasyLinkRx.o (31513, 2016-08-16)
Debug\Obj\rfEasyLinkRx.pbi (1480469, 2016-08-16)
Debug\Obj\rfEasyLinkRx.pbi.cout (10757, 2016-08-16)
Debug\Obj\rfEasyLinkTx.o (35578, 2016-08-16)
Debug\Obj\rfEasyLinkTx.pbi (1496916, 2016-08-16)
Debug\Obj\rfEasyLinkTx.pbi.cout (10743, 2016-08-16)
Debug\Obj\smartrf_settings.o (22561, 2016-08-16)
Debug\Obj\smartrf_settings.pbi (848733, 2016-08-16)
Debug\Obj\smartrf_settings.pbi.cout (10778, 2016-08-16)
Debug\Obj\smartrf_settings_predefined.o (30993, 2016-08-16)
Debug\Obj\smartrf_settings_predefined.pbi (851653, 2016-08-16)
Debug\Obj\smartrf_settings_predefined.pbi.cout (10781, 2016-08-16)
Debug\Obj\uartstdio.o (43780, 2016-08-16)
Debug\Obj\uartstdio.pbi.cout (10740, 2016-08-16)
... ...

Example Summary --------------- Example includes the EasyLink API and uses it to configure the RF driver to RX packets. This project should be run in conjunction with the rfEasyLinkTx project. For more information on the EasyLink API and usage refer to http://processors.wiki.ti.com/index.php/SimpleLink-EasyLink Peripherals Exercised --------------------- Board_LED1 Indicates an abort which is expected to happen 300 ms after RX has been scheduled Board_LED2 Indicates that a Packet has been received Board_LED1 and Board_LED2 Indicates an error Resources & Jumper Settings --------------------------- Please refer to the development board's specific "Settings and Resources" section in the Getting Started Guide. For convenience, a short summary is also shown below. | Development board | Notes | | ================= | ====================================================== | | CC1310DK | N/A | | ----------------- | ------------------------------------------------------ | Example Usage ------------- Run the example. Board_LED2 will toggle indicating a packet has been received. Board_LED1 will toggle indicating an abort, which is expected to happen if a packet is not received within 300 ms of the RX being scheduled. Board_LED1 and Board_LED2 indicates an error (not expected to happen under normal conditions, but may occur if there is some interference). After running this application you should start the rfEasyLinkTx on a second board to transmit packets. Until the rfEasyLinkTx has been started the receiver will be continuously RX. Application Design Details -------------------------- This example shows how to use the EasyLink API to access the RF drive, set the frequency and receive packets. The board will blink LED1 when a packet has been received. When a second board is running rfEasyLinkTx example then the expected behaviour is that Board_LED2 will blink every 100ms 10 times, the TX will then wait for 300 ms before transmitting the next packets and if RFEASYLINKRX_ASYNC is defined (as it is by default) then this will cause the rfEasyLinkRx example to timeout and exercise the EasyLink_abort API. When an RX has been aborted Board_LED1 should toggle. The rfEasyLinkTx board will then transmit another burst of packets and Board_LED2 should blink another 10 times and the cycle should repeat. If RFEASYLINKRX_ADDR_FILTER is defined (as it is by default) then the RX address filter will be enabled for address 0xaa. This will cause the rfEasyLinkRx to only accept packets with a destination address of 0xaa, which the rfEasyLinkTx example transmits. When using the rfEasyLinkTx example there will be no difference in behaviour when defining/undefining RFEASYLINKRX_ADDR_FILTER as the rfEasyLinkTx example will use a destination address of 0xaa. However, if transmitting from another source like SmartRF Studio and not using an address of 0xaa, then defining RFEASYLINKRX_ADDR_FILTER will result in packets not being received. A single task, "rfEasyLinkRxFnx", configures the RF driver through the EasyLink API and receives messages. EasyLink API ------------------------- # Overview # The EasyLink API should be used in application code. The EasyLink API is intended to abstract the RF Driver in order to give a simple API for customers to use as is or extend to suit their application[Use Cases] (@ref USE_CASES). # General Behaviour # Before using the EasyLink API: - The EasyLink Layer is initialized by calling EasyLink_init(). This initializes and opens the RF driver and configures a modulation scheme passed to EasyLink_init. - The RX and TX can operate independently of each other. The following is true for receive operation: - RX is enabled by calling EasyLink_receive() or EasyLink_receiveAsync() - Entering RX can be immediate or scheduled - EasyLink_receive() is blocking and EasyLink_receiveAsync() is non-blocking - The EasyLink API does not queue messages so calling another API function while in EasyLink_receiveAsync() will return EasyLink_Status_Busy_Error - An Async operation can be cancelled with EasyLink_abort() The following apply for transmit operation: - TX is enabled by calling EasyLink_transmit() or EasyLink_transmitAsync() - TX can be immediate or scheduled - EasyLink_transmit() is blocking and EasyLink_transmitAsync() is nonblocking - EasyLink_transmit() for a scheduled command, or if TX cannot start - The EasyLink API does not queue messages so calling another API function while in EasyLink_transmitAsync() will return EasyLink_Status_Busy_Error - An Async operation can be cancelled with EasyLink_abort() # Error Handling # The EasyLink API will return EasyLink_Status containing success or error code. The EasyLink_Status codes are: EasyLink_Status_Success EasyLink_Status_Config_Error EasyLink_Status_Param_Error EasyLink_Status_Mem_Error EasyLink_Status_Cmd_Error EasyLink_Status_Tx_Error EasyLink_Status_Rx_Error EasyLink_Status_Rx_Timeout EasyLink_Status_Busy_Error EasyLink_Status_Aborted # Power Management # The TI-RTOS power management framework will try to put the device into the most power efficient mode whenever possible. Please see the technical reference manual for further details on each power mode. The EasyLink Layer uses the power management offered by the RF driver Refer to the RF Driver documentation for more details. # Supported Functions # | Generic API function | Description | |-------------------------------|---------------------------------------------------| | EasyLink_init() | Init's and opens the RF driver and configures the | | | specified modulation | | EasyLink_transmit() | Blocking Transmit | | EasyLink_transmitAsync() | Non-blocking Transmit | | EasyLink_receive() | Blocking Receive | | EasyLink_receiveAsync() | Non-blocking Receive | | EasyLink_abort() | Aborts a non blocking call | | EasyLink_EnableRxAddrFilter() | Enables/Disables RX filtering on the Addr | | EasyLink_GetIeeeAddr() | Gets the IEEE Address | | EasyLink_SetFreq() | Sets the frequency | | EasyLink_GetFreq() | Gets the frequency | | EasyLink_SetRfPwr() | Sets the TX Power | | EasyLink_GetRfPwr() | Gets the TX Power | # Frame Structure # The EasyLink implements a basic header for transmitting and receiving data. This header supports addressing for a star or point-to-point network with acknowledgements. Packet structure: _________________________________________________________ | | | | | 1B Length | 1-***b Dst Address | Payload | |___________|___________________|_________________________| Note: For IAR users using any SensorTag(STK) Board, the XDS110 debugger must be selected with the 4-wire JTAG connection within your projects' debugger configuration.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：