SUB-20 User Manual - Dimax

More documents

Recommendations

Info

50SUB-20SUB-20 APIrx_msg_us>0 rx_byte_us>0 First byte reception will last no more then rx_msg_us time. Every nextbyte should be received in rx_byte_us timeReturn valueOn success function returns 0. Otherwise error code.Example/* Request message transmit and after that receipt *//* No space between transmitted bytes *//* Message should be received in 1s */sub_rs_timing( hndl, RS_RX_AFTER_TX, 0, 1000000, 0 );3.10.4 sub_rs_xferSynopsisint sub_rs_xfer( sub_handle hndl, char* tx_buf, int tx_sz,char* rx_buf, int rx_sz )Transmit and/or receive message(s) via UART configured with sub_rs_set_config and in accordance withtransfer timing set with sub_rs_timing.Parameters· tx_buf - buffer with data to be transmitted· tx_sz - number of bytes to transmit (can be 0 if transmit not required)· rx_buf - buffer to store received data· rx_sz - maximal number of bytes to receive (can be 0 if reception is not required)rx_sz and tx_sz should not be grater then 62 bytes.Function will terminate after following conditions fulfilled: tx_sz bytes transmitted and either rx_sz bytes receivedor one of the timeouts occurs (see sub_rs_timing)For 9bit transfer data in tx_buf and rx_buf has following formatbyte 0 byte 1 ... byte n byte n+1bit ..8 LSB bits 7..0 ... bit ..8 LSB bits 7..0Even bytes (0,2,4,....) contain 8'th bit in LSB. Odd bytes (1,3,5,...) contain bits 7..0. Data is shifted out beginningfrom bit 0 (see RS232 RS485 Frame format). Parameters tx_sz and rx_sz should correspond to total number ofbytes in tx_buf and rx_buf.Return valueOn success function returns non negative value that denotes number of received bytes. It can be less thenrx_sz if timeout occurs.Otherwise -1 will be returned and sub_errno will contain error code.Example/* Set timing */sub_rs_timing( hndl, RS_RX_AFTER_TX, 0, 1000000, 200000 );/*Transmit 3 bytes and try to receive up to 5 bytesin 1s with 200ms byte to byte timeout*/© 2013 xdimax.com rev 2.17
51SUB-20SUB-20 APIsub_rs_xfer( hndl, "at\r", 3, rx_buf, 5 );CompatibilityFW version9-bit transfer support - 0.2.2 or grater3.11 FIFO, Streaming, Slave ModesFIFO is used for implementation of streaming data transfer and slave modes functionality such as SPI slave, I2Cslave. Below is simplified block diagram of the SUB-20 FIFO module.3.11.1 FIFO Functionssub_fifo_configsub_fifo_readsub_fifo_write© 2013 xdimax.com rev 2.17
Page 4 and 5: 4SUB-20© 2013 xdimax.com
Page 6 and 7: 6SUB-20SUB-20 Layout2 SUB-20 Layout
Page 8 and 9: 8SUB-20SUB-20 Layout2.2 SPI HeaderH
Page 10 and 11: 10SUB-20SUB-20 LayoutJP1JP2JP3JP4JP
Page 12 and 13: 12SUB-20SUB-20 Layoutvoltage can be
Page 14 and 15: 14SUB-20SUB-20 API3.1 Device Initia
Page 16 and 17: 16SUB-20SUB-20 APIGet version of sh
Page 18 and 19: 18SUB-20SUB-20 APIsub_i2c_freqsub_i
Page 20 and 21: 20SUB-20SUB-20 APIfollowing format:
Page 22 and 23: 22SUB-20SUB-20 API};where:· sa - S
Page 24 and 25: 24SUB-20SUB-20 APIReturn ValueOn su
Page 26 and 27: 26SUB-20SUB-20 APIError Codes, I2C
Page 28 and 29: 28SUB-20SUB-20 APISPI_CLK_8MHZSPI_C
Page 30 and 31: 30SUB-20SUB-20 APIL SS Low Byte Tra
Page 32 and 33: 32SUB-20SUB-20 API3.6 MDIO Function
Page 34 and 35: 34SUB-20SUB-20 API· *content - 16
Page 36 and 37: 36SUB-20SUB-20 APIGPIO Pin configur
Page 38 and 39: 38SUB-20SUB-20 APIGPIO in input sta
Page 40 and 41: 40SUB-20SUB-20 API3.7.7.1 sub_edge_
Page 42 and 43: 42SUB-20SUB-20 API3.7.8.1 sub_fpwm_
Page 44 and 45: 44SUB-20SUB-20 API· res_us - PWM m
Page 46 and 47: 46SUB-20SUB-20 APIParameters· data
Page 48 and 49: 48SUB-20SUB-20 API· Required DLL v
Page 52 and 53: 52SUB-20SUB-20 API3.11.1.1 sub_fifo
Page 54 and 55: 54SUB-20SUB-20 API3.11.3 I2C SlaveC
Page 56 and 57: 56SUB-20Electrical Characteristics4
Page 58: 58SUB-20Ordering Information© 2013

SUB-20 User Manual - Dimax

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?