Home
last modified time | relevance | path

Searched refs:RTS (Results 1 – 4 of 4) sorted by relevance

/nrf_hw_models-latest/src/HW_models/
DNHW_UART_backend_pty.c57 bool RTS; member
139 if ((u_el->RTS == new_level) || !(u_el->respect_RTS)) { in nhw_upty_RTS_pin_toggle()
142 u_el->RTS = new_level; in nhw_upty_RTS_pin_toggle()
143 if (u_el->RTS) { //Not ready to receive in nhw_upty_RTS_pin_toggle()
DNHW_UART.c162 NRF_UARTE_regs[i].PSEL.RTS = 0xFFFFFFFF; in nhw_uarte_init()
DNRF5340_peri_types.h241 …__IOM uint32_t RTS; /*!< (@ 0x00000000) Pin select for RTS … member
252 …__IOM uint32_t RTS; /*!< (@ 0x00000000) Pin select for RTS signal … member
/nrf_hw_models-latest/docs/
DUART.md43 This backend just connects an instance Tx to its Rx, including the RTS and CTS signals.
50 In these pipes it will carry both the data, information about the CTS/RTS pin toggles,
67 For performance reasons, the backend does not react immediately to a CTS/RTS pin toggle from the
70 and that it toggles RTS while there are still 4 spaces left. So even though this will, in some case…
100 if data should be held while RTS is high, if the simulation should be held until a terminal has been