USB Device raw IP driver

Highly prioritized access.

Endpoint with lower number has always higher priority and its data would be transfered first. OUT endpoints ale processed before IN endpoints

Round robin scheme.

All endpoints are processed in round-robin scheme. It means that when one endpoint is processed next in order would be the nearest with lower number. When no endpoints with lower number requires processing - then all endpoints from 0 are tested.

Helper macro to create endpoint transfer event.

Create identifier for IN endpoint.

Simple macro to create IN endpoint identifier for given endpoint number.

Parameters

[in]

n

Endpoint number.

Returns

Endpoint identifier that connects endpoint number and endpoint direction.

Create identifier for OUT endpoint.

Simple macro to create OUT endpoint identifier for given endpoint number.

Parameters

[in]

n

Endpoint number.

Returns

Endpoint identifier that connects endpoint number and endpoint direction.

Number of bytes in the endpoint.

Constant that informs about endpoint size

Number of bytes for isochronous endpoints.

Number of bytes for isochronous endpoints in total. This number would be shared between IN and OUT endpoint. It may be also assigned totaly to one endpoint.

See Also

nrf_usbd_isosplit_set

nrf_usbd_isosplit_get

Helper macro for declaring IN transfer item ( nrf_drv_usbd_transfer_t )

Parameters

name	Instance name
tx_buff	Buffer to transfer
tx_size	Transfer size

Helper macro for declaring OUT transfer item ( nrf_drv_usbd_transfer_t )

Parameters

name	Instance name
rx_buff	Buffer to transfer
rx_size	Transfer size

USBD event callback function type.

Parameters

[in]

p_event

Event information structure.

USBD event callback for the endpoint.

Parameters

[out]	p_next	Structure with the data for the next transfer to be filled. Required only if the function returns true.
[in]	p_contex	Contex variable configured with the endpoint.

Return values

false	Nothing more to transfer
true	Settings to the next transfer filled into p_next .

Possible endpoint error codes.

Error codes that may be returned with NRF_DRV_USBD_EVT_EPTRANSFER

Endpoint identifier.

Endpoint identifier used in the driver. This endpoint number is consistent with USB 2.0 specification.

Events generated by the library.

Enumeration of possible events that may be generated by the library.

Disable the USBD port.

After calling this function USBD peripheral would be disabled. No events would be detected or processed by the library. Clock for the peripheral would be disconnected.

Enable the USBD port.

After calling this function USBD peripheral would be enabled. It means that High Frequency clock would be requested and USB LDO would be enabled.

In normal situation this function should be called in reaction to USBDETECTED event from POWER peripheral.

Interrupts and USB pins pull-up would stay disabled until nrf_drv_usbd_start function is called.

Disable selected endpoint.

This function disables endpoint itself and its interrupts.

Parameters

ep	Endpoint number to disable

Enable selected endpoint.

This function enables endpoint itself and its interrupts.

Parameters

ep	Endpoint number to enable

Note

Max packet size is set to endpoint default maximum value.

See Also

nrf_drv_usbd_ep_max_packet_size_set

Check if endpoint buffer is ready or is under USB IP control.

Function to test if endpoint is busy. Endpoint that is busy cannot be accessed by MCU. It means that:

• OUT (TX) endpoint: Last uploaded data is still in endpoint and is waiting to be received by the host.
• IN (RX) endpoint: Endpoint is ready to receive data from the host and the endpoint does not have any data. When endpoint is not busy:
• OUT (TX) endpoint: New data can be uploaded.
• IN (RX) endpoint: New data can be downloaded using nrf_drv_usbd_ep_transfer function.

Get configured endpoint packet size.

Function to get configured endpoint size on the buffer.

Parameters

[in]

ep

Endpoint number

Returns

Maximum pocket size configured on selected endpoint

Configure packet size that should be supported by the endpoint.

The real endpoint buffer size is always the same. This value sets max packet size that would be transmitted over the endpoint. This is required by the library

Parameters

[in]	ep	Endpoint number
[in]	size	Required maximum packet size

Note

Endpoint size is always set to NRF_DRV_USBD_EPSIZE or NRF_DRV_USBD_ISOSIZE / 2 when nrf_drv_usbd_ep_enable function is called.

Stall endpoint.

Stall endpoit to send error information during next transfer request from the host.

Note

To stall endpoint it is safer to use nrf_drv_usbd_setup_stall

Stalled endpoint would not be cleared when DMA transfer finishes.

Parameters

ep	Endpoint number to stall

Check if endpoint is stalled.

This function gets stall state of selected endpoint

Parameters

ep	Endpoint number to check

Clear stall flag on endpoint.

This function clears endpoint that is stalled.

Note

If it is OUT endpoint (receiving) it would be also prepared for reception. It means that busy flag would be set.

In endpoint (transmitting) would not be cleared - it gives possibility to write new data before transmitting.

Get the information about last finished transfer.

Function returns the status of the last buffer set for transfer on selected endpoint. The status considers last buffer set by nrf_drv_usbd_ep_transfer function or by transfer callback function.

Parameters

[in]	ep	Endpoint number.
[out]	p_transfer	Structure that would be filled by transfer details: buffer pointer and number of bytes received.

Return values

NRF_SUCCESS	Transfer already finished
NRF_ERROR_BUSY	Ongoing transfer
NRF_ERROR_DATA_SIZE	Too much of data received that cannot fit into buffer and cannot be splited into chunks. This may happen if buffer size is not a multiplication of endpoint buffer size.

Start sending data over endpoint.

Function initializes endpoint transmission. This is asynchronous function - it finishes immediately after configuration for transmission is prepared.

Note

Data buffer pointed by p_data have to be kept active till NRF_DRV_USBD_EVT_EPTRANSFER event is generated.

Parameters

[in]	ep	Endpoint number. For IN endpoint sending would be initiated. For OUT endpoint receiving would be initiated.
[in]	p_transfer
[in]	p_handler	Description of transfer handler to be called when buffer is ready. Can be NULL when not required by the caller.

Return values

NRF_ERROR_BUSY	Selected endpoint is pending.
NRF_ERROR_INVALID_ADDR	Unexpected transfer on EPIN0 or EPOUT0.
NRF_ERROR_FORBIDDEN	Endpoint stalled.
NRF_SUCCESS	Transfer queued or started.

Get number of received bytes.

Get the number of received bytes. The function behavior is undefined when called on IN endpoint.

Parameters

ep	Endpoint number.

Returns

Number of received bytes

Library initialization.

Parameters

[in]

event_handler

Event handler provided by the user.

Check if driver is enabled.

Return values

false	Driver is disabled
true	Driver is enabled

Check if driver is initialized.

Return values

false	Driver is not initialized
true	Driver is initialized

Check if driver is started.

Return values

false	Driver is not started
true	Driver is started (fully functional)

Note

The USBD peripheral interrupt state is checked

Get the information about expected transfer SETUP data direction.

Function returns the information about last expected transfer direction.

Return values

NRF_DRV_USBD_EPOUT0	Expecting OUT (Host->Device) direction or no data
NRF_DRV_USBD_EPIN0	Expecting IN (Device->Host) direction

Clear setup endpoint.

This function acknowledges setup when SETUP command was received and processed. It has to be called if no data respond for the SETUP command is sent.

When there is any data transmission after SETUP command the data transmission itself would clear the endpoint.

Clear only for data transmission on setup endpoint.

This function may be called if any more data in control write transfer is expected. Clears only OUT endpoint to be able to take another OUT data token. It does not allow STATUS stage.

See Also

nrf_drv_usbd_setup_clear

Get parsed setup data.

Function fills the parsed setup data structure.

Parameters

[out]

p_setup

Pointer to data structure that would be filled by parsed data.

Stall setup endpoint.

Mark and error on setup endpoint.

Start USB functionality.

After calling this function USBD peripheral should be fully functional and all new incoming events / interrupts would be processed by the library.

Also only after calling this function host sees new connected device.

Call this function when USBD power LDO regulator is ready - on USBPWRRDY event from POWER peripheral.

Parameters

enable_sof

The flag that is used to enable SOF processing. If it is false, SOF interrupt is left disabled and will not be generated. This improves power saving if SOF is not required.

Note

If the isochronous endpoints are going to be used, it is required to enable the SOF. In other case any isochronous endpoint would stay busy after first transmission.

Stop USB functionality.

This function disables USBD pull-up and interrupts.

Note

This function can also be used to logically disconnect USB from the HOST that would force it to enumerate device after calling nrf_drv_usbd_start .

Drop transfer on OUT endpoint.

Parameters

[in]

ep

OUT endpoint ID

Note

This function locks interrupts that may be costly. It is good idea to test if the endpoint is still busy before calling this function:

(m_ep_dma_waiting & (1U << ep2bit(ep)))

This function would check it again, but it makes it inside critical section.