...
Anchor
to
enable the SPI chip select of the wireless device.Files
Anchor
net_bsp.c
Prototype
...
HTML Table | summary | |||
---|---|---|---|---|
class | Code_Listing | |||
Table Row (tr) | ||||
Table Cell (td) | ||||
| ||||
Anchor | 1145036 | 1145036 | static CPU_INT32U||
Code Block | ||||
static CPU_INT32U NetDev_WiFi_SPI_ChipSelEn (NET_IF *p_if, Anchor | | 1151589 | 1151589 | NET_ERR|
Table Row (tr) |
Anchor
NetDev_WiFi_SPI_ChipSelEn()
is accessed only by function pointer via a BSP interface structure, it doesn’t need to be globally available and should therefore be declared as ‘static’.static
’.Arguments
p_if
Anchor
Pointer to specific interface to enable the chip select.
...
p_err
Pointer to variable that will receive the return error code from this function:
...
...
NET_DEV_ERR_NONE
...
NET_DEV_ERR_FAULT
...
Returned Value
...
None.anchor
Required Configuration
...
Notes / Warnings
...
...
NetDev_WiFi_SPI_ChipSelEn() should be called only after the SPI lock has been acquired by calling NetDev_WiFi_SPI_Lock()
.
...
- Since each network device requires a unique
NetDev_WiFi_SPI_ChipSelEn()
, it is recommended that each device’sNetDev_WiFi_SPI_ChipSelEn()
function be named using the following convention:
...
NetDev_WiFi_[Device]SPI_ChipSelEn[Number]()
...
[Device]
...
Network device name or type, e.g. RS9110 (optional if the development board does not support multiple devices)
...
[Number]
Network device number for each specific instance of device (optional if the development board does not support multiple instances of the specific device)
...
...
For example, the NetDev_WiFi_SPI_ChipSelEn()
function for the #2 RS9110 wireless device on an Atmel AT91SAM9263-EK should be named NetDev_WiFi_RS9110_SPI_ChipSelEn2()
, or NetDev_WiFi_RS9110_SPI_ChipSelEn_2()
with additional underscore optional.
...
See also Chapter 6, “Network section Network Board Support Package” on page 121Package.