Part Number Hot Search : 
XP829 ZMM15HC 150K120A 1H101J RCA9228A 24C00 A1030 PDTC1
Product Description
Full Text Search
 

To Download VNC1L Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
  future technology devices international ltd. version 1.07 http://www.vinculum.co m vinculum VNC1L firmware - vdap ftdi usb slave device and usb flash disk interface with fxed monitor port the vinculum VNC1L-1a is the frst of f.t.d.i.s vinculum family of embedded usb host controller integrated circuit devices. not only is it able to handle the usb host interface, and data transfer functions but owing to the inbuilt mcu and embedded flash memory, vinculum can encapsulate the usb device classes as well. when interfacing to mass storage devices such as usb flash drives, vinculum also transparently handles the fat file structure communicating via uart, spi or parallel fifo interfaces via a simple to implement command set. vinculum provides a new cost effective solution for providing usb host capability into products that previously did not have the hardware resources available. the VNC1L-1a is available in pb-free (rohs compliant) compact 48-lead lqfp package. ? ? preliminary - subject to change
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 2 preliminary - subject to change 1 . o v e r v i e w 1.1 introduction this document describes the vdap version of vinculum VNC1L usb fash disk / usb device interface and command monitor frmware. vdap uses the VNC1Ls confgurable i/o interface fxed as the command monitor port. the i/o interface is confgured using a set of jumpers which pull up or pull down two of the VNC1L s pins. these jumpers are used to select between a uart interface, a parallel fifo interface, or a spi interface. the main function of this frmware is to allow an embedded device, based around the VNC1L, to communicate via the VNC1L-1as uart, parallel fifo or spi interface port with usb slave peripheral devices. these include usb flash disks, ftdis ft232, ft245 and ft2232 usb slave i.c. as well as devices that are printer or hid (human input device) compatible. other devices may also be supported if they have a suitable interface such as mobile phones. the vinculum VNC1L i.c. hardware specifcation is described separately in its own datasheet which is available from the vinculum websit e .
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 3 preliminary - subject to change 2.1 vdap - vinculum disk and peripheral interface the vdap frmware is designed to allow an ftdi vinculum VNC1L device to act as an interface between a usb fash disk (or other usb mass storage class device) on usb port 2, and the VNC1L s i/o interface, or a suitable ftdi usb peripheral device on usb port 1. this frmware allows the VNC1Ls i/o interface to be externally confgured as a uart, parallel fifo or spi, using external jumpers. the device connected to the serial uart / parallel fifo / spi interface can issue commands which allow operations to be performed on the usb fash disk and / or usb slave device using the command set defned herein. the VNC1L port which is confgured to receive these commands is know as the command monitor port . in this case command monitor port is always the VNC1Ls i/o port, i.e. the serial uart / parallel fifo / spi interface. the current frmware supports all ftdi usb slave devices (eg. ft232r, ft245r, ft232b, ft245b and ft2232d) as well as giving support for printer class and hid class. a usb flash disk can only be used on port 2. 2.1.1 vdap command monitor port selection the vdap frmware always uses the VNC1Ls i/o port to act as the command monitor port. usb port 1 is a usb host port for connecting peripheral devices based on ftdi usb slave i.c. devices. usb port 2 is available as a usb fash disk interface (or other usb mass storage class device). the jumper confgurable uart / parallel fifo / spi interface port always acts as the command monitor port. the vdap frmware will use the device interface mode as selected on the acbus5 (pin 46) and acbus6 (pin 47) jumper pins as the command monitor port, i.e. serial uart, parallel fifo, or spi. the jumper circuit confguration shown in figure 2, below. this circuit will default to the uart interface if no jumper links are ftted. see table 1 for the port selection jumper pin confguration. usb port 1 is a usb host port for connecting peripheral devices based on ftdi usb slave i.c. devices. usb port 2 is available as a usb fash disk interface only (or other usb mass storage class device). the VNC1L uart / parallel fifo / spi to ft232 / ft245 interface works in command mode or data mode in a similar way to a modem. command mode is used to communicate with the VNC1L. data mode is used to communicate with the slave device on usb port 1 or 2. commands are provided to confgure both the VNC1L s uart and for an ftdi slave uart device on usb port 1 or 2. figure 2 - vdap firmware model vnc 1 l - 1 a p o r t a c p o r t b d p o r t b c central hardware core uart spi fifo interface select command monitor monitor is via i / f select select i / f mode for uart or spi or 245 p o r t a d firmware usb port 2 usb port 1 vcc 3 gnd interface select acbus 5 acbus 6 usb flash disk ft 232 / ft 245 based usb peripheral allow pass through from i / f port to usb port 1 check for command / data mode 47 k 47 k 2 . f i r m w a r e d e s c r i p t i o n table 2.1 - port selection jumper pins
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 4 preliminary - subject to change acbus6 (pin 47) acbus5 (pin 46) mode pull-up pull-up serial uart pull-up pull-down spi pull-down pull-up parallel fifo pull-down pull-down serial uart there are three i/o interface options which use adbus and acbus which are confgured using jumpers - serial uart, parallel fifo and spi. two additional signals, dataack# and datareq#, allow for switching between command mode and data mode are added. in uart interface mode they are on the dtr# and dsr# interface pins. in parallel fifo and spi modes they are on pins 45 and 46. the VNC1L device pin defnitions according to i/o mode selected are shown on table 2.1. table 2.2 - i/o interface options pin no. name type description interface mode uart interface parallel fifo interface spi slave interface 31 adbus0 i/o 5v safe bidirectional data / control bus, ad bit 0 txd d0 sclk 32 adbus1 i/o 5v safe bidirectional data / control bus, ad bit 1 rxd d1 sdi 33 adbus2 i/o 5v safe bidirectional data / control bus, ad bit 2 rts# d2 sdo 34 adbus3 i/o 5v safe bidirectional data / control bus, ad bit 3 cts# d3 cs 35 adbus4 i/o 5v safe bidirectional data / control bus, ad bit 4 dtr# / dataack# d4 36 adbus5 i/o 5v safe bidirectional data / control bus, ad bit 5 dsr# / datareq# d5 37 adbus6 i/o 5v safe bidirectional data / control bus, ad bit 6 dcd# d6 38 adbus7 i/o 5v safe bidirectional data / control bus, ad bit 7 ri# d7 41 acbus0 i/o 5v safe bidirectional data / control bus, ac bit 0 txden# rxf# 42 acbus1 i/o 5v safe bidirectional data / control bus, ac bit 1 txe# 43 acbus2 i/o 5v safe bidirectional data / control bus, ac bit 2 wr# 44 acbus3 i/o 5v safe bidirectional data / control bus, ac bit 3 rd# 45 acbus4 i/o 5v safe bidirectional data / control bus, ac bit 4 datareq# datareq# 46 acbus5 i/o 5v safe bidirectional data / control bus, ac bit 5 dataack# dataack# 2.2 uart interface confguration when using the uart interface as the command monitor port the default baud rate used is 9600 baud, although this can be changed while in command mode. the standard data format is 8 data bits, 1 start bit, 1 stop bit, and no parity with rts/cts hardware handshaking enabled. when the frmware is used with the VNC1L i/o confgured as a uart the dtr# and dsr# pins also take on the dataack# and datareq# functions respectively. see table 2. 2.3 vdap system operation - command mode this frmware starts in command mode. in this mode the dataack# signal is high. the datareq# line should be held high in order to stay in command mode. while in command mode the frmware will accept commands to modify the uart interface on the VNC1L. if a suitable ftdi usb slave device has been found on usb port 1 it can also be sent confguration commands. in this mode a usb fask disk on usb port 2 can also be accessed. 2.4 vdap system operation - data mode in order to switch to data mode the datareq# line should be asserted low. once the dataack# line goes low, any data sent to the uart (or parallel fifo or spi) port on the VNC1L will be sent to the ftdi slave device connected to usb port 1. any data received will be coming from the ftdi slave device connected to usb port 1. in this mode the VNC1L ignores the data, and simply passes it between usb and the uart / parallel fifo / spi interface. note : pins acbus5 and 6 are only read after reset. they may become output after the interface choice has been selected (e.g. acbus5 becomes dataack# if fifo mode is selected). these pins should therefore not be tied directly to gnd or vcc but should be pulled using a resistor of around 47 kohm.
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 5 preliminary - subject to change 3 . c o m m u n i c a t i n g t o a u s b s l a v e d e v i c e connect and disconnect when a device is attached to one of the usb ports a message will be sent to monitor port saying : device detected p1 or device detected p2 when one is removed from a usb port a message will be sent to monitor port saying : device removed p1 or device removed p2 query port 1 and query port 2 commands table 3.1 - query port 1 and query port 2 commands qp1 and qp2 commands first byte bit number meaning bit 0 ftdi 232/245 device attached bit 1 reserved bit 2 printer class device attached bit 3 hid class device attached bit 4 cdc class device attached bit 5 boms class device attached bit 6 unknown device bit 7 reserved second byte bit number meaning bit 0-7 reserved to query the device there are new commands available C qp1 and qp2. these will tell you all the interfaces types available on port 1 and port 2 respectively.
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 6 preliminary - subject to change table 3.2 - query device command qd n command byte number meaning 1 usb address 2 control ep 0 size 3 pipe in ep no. 4 pipe in size 5 pipe out ep no. 6 pipe out size 7 data toggles 8 device type - see query port command 9 reserved 10 location 11 mi index 12 device class 13 device sub class 14 device protocol 15 vid low 16 vid high 17 pid low 18 pid high 19 bcd low 20 bcd high 21 device speed 22 reserved 23 reserved 24 reserved 25 reserved 26 reserved 27 reserved 28 reserved 29 reserved 30 reserved 31 reserved 32 reserved some devices have more than 1 interface ( such as the ft2232d chip ). to select which device you want to talk to, you can request in - formation on up to 8 interfaces with the query device command : qd n where n is a number 0 C 7. this will return a block of 32 bytes to you as shown in table 3.2 . this information will give you the device type as well as the usb class codes and usb vid pid and bcd numbers. from this you can decide if you want to talk to this particular device. query device command
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 7 preliminary - subject to change example 1 : talking to an ft2232 device as an example, here is what you get if you are in ascii input mode (see later) when you query an ft2232 dual chip device on port 1. qd 0 $01 $08 $81 $40 $02 $40 $00 $01 $01 $01 $00 $ff $ff $ff $03 $04 $10 $60 $00 $05 $01 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 d:\> qd 1 $01 $08 $83 $40 $04 $40 $00 $01 $01 $01 $01 $ff $ff $ff $03 $04 $10 $60 $00 $05 $01 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 d:\> this shows they share the same address but have a different interface number at byte 11 and different endpoint num - bers. the frst one is port a on a ft2232 chip and the second one is port b. it is important that before you attempt to talk to a device you must set it to be the current device with the set current sc n command. sc 0 d:\> will select device 0 or port a of the ft2232 chip. sc 1 d:\> will select device 1 or port b of the ft2232 chip. important note : once you have selected the device you want to talk to you can then issue commands as if it were the only device con - nected to the vnc1 chip. the sc command opens up channels to use that devices address and endpoint numbers for transferring data. in this example sc 0 ( select device 0 ) d:\> fbd $384100 ( set baud rate to 9600 ) d:\> fmc $0303 ( set rts and dtr active) d:\> ffc $01 ( set rts / cts flow control) d:\> you can now enter direct connection mode by setting datareq# active ( low) and waiting for dataack# (low). once you have the acknowledge (dataack# low ) anything you then type will go to port a of the ft2232 chip and anything that comes back from the vnc1 came from the port a of the ft2232 chip. hello world! this will then be sent out of the uart on port a of the ft2232 chip at 9600 baud. example 2 : talking to an ftdi device that does not have the default vid and pid you may have a device that contains an ftdi chip but you have a different vid and pid programmed into it. you can still use the above method to talk to your device but you need to use another command before doing so. the com - mand is sf n where n is a number 0 C 7. the command means set as ftdi device n. here is an example of an ft232bm chip with a non ftdi vid and pid
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 8 preliminary - subject to change d:\> qd 0 $01 $08 $81 $40 $02 $40 $00 $40 $01 $02 $00 $ff $ff $ff $34 $12 $78 $56 $00 $04 $01 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 d:\> this has vid $1234 and pid $5678 ( which are made up for this example ). the device type at location 8 is $40, which, from the table, means unknown. in order to use this device you need to tell the chip that it is an ftdi device. to do this type : sf 0 d:\> if you then issue the query device command again you will get : qd 0 $01 $08 $81 $40 $02 $40 $00 $01 $01 $02 $00 $ff $ff $ff $34 $12 $78 $56 $00 $04 $01 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 $00 d:\> byte 8 is now $01 which means ftdi. you can then use the set baud rate command etc. and go into data mode as you would with a normal ftdi device. you must remember to issue the set current command after changing the device type example 3 : transferring data to or from a usb device without using data mode as well as using the datareq# line to enter data mode, it is possible to send or receive data to or from a usb device by issuing a command while still in command mode. the frst step is to set the device number using the sc command as mentioned in the previous section. to send data use the dsd command as follows ( this assumes the device is device 1): d:\> ipa ( ensure ascii input mode ) d:\> sc 1 ( set current device to 1 ) d:\> dsd 12 ( device send data 12 bytes) hello world ! d:\> this will send the string hello world! to the out endpoint of device 1. to check for data available use the command drd as follows : d:\> ipa ( ensure ascii input mode ) d:\> sc 1 ( set current device to 1 ) d:\> drd ( do a read of device 1) $05 hellod:\> device 1 sent the string hello through its in endpoint.
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 9 preliminary - subject to change command entry format C ascii input mode there are 2 commands to switch the way numbers are sent or received by the chip. these are ipa ( input ascii ) and iph (input hex). the default starting condition is hex. if the command ipa is used then numbers can be entered from an ascii terminal as ascii characters. for example to read twelve bytes from an open fle in iph ( hex default mode) : rdf $00 $00 $00 $0c in terms of actual bytes sent to the chip this would be $72 $64 $66 $20 $00 $00 $00 $0c $0d to enter the same command in ipa (ascii mode) : decimal rdf 12 in terms of actual bytes sent to the chip this would be $72 $64 $66 $20 $31 $32 $0d or hex $ format rdf $c in terms of actual bytes sent to the chip this would be $72 $64 $66 $20 $24 $43 $0d or hex 0x0 format rdf 0xc in terms of actual bytes sent to the chip this would be $72 $64 $66 $20 $30 $78 $43 $0d in hex mode the exact number of bytes specifed for the command must be entered. in ascii mode leading zeros are removed and the number is terminated by the carriage return ( = $0d ) in this way for ascii mode : 12 == $c == $000000c == 0xc == 0xc == 0x000c firmware defaults after reset the default condition for the frmware after a reset is hex mode and extended command set.
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 10 preliminary - subject to change 4.1 monitor port commands this VNC1L frmware command monitor system uses the following command set. there is an extended ascii command set which is designed for use with a terminal, and there is a shortened hexadecimal command set designed for use with a microprocessor. table 4.1 - monitor port commands extended ascii com - mand for terminal mode shortened hexadecimal command for microproc - essor mode command function response switching between shortened and extended command sets scs $10,$0d switches to the shortened com - mand set this will return the prompt >,$0d to indicate that the device is in shortened command set mode. ecs $11,$0d switches to the extended com - mand set this will return the prompt d:\>,$0d to indicate that the device is in extended command set mode. e e echo this will return e,$0d for syn - chronisation purposes e e echo this will return e,$0d for syn - chronisation purposes ipa $90,$0d input numbers in ascii $0d iph $91,$0d input numbers in hex $0d responses to indicate if disk is online $0d check if online this will return the appropriate prompt or no disk message for the current command set. response to check if online for extended command mode if no valid disk is found no disk,$0d if a valid disk is found d:\>,$0d response to check if online for short command mode if no valid disk is found nd,$0d if a valid disk is found >,$0d directory operations dir $01,$0d lists the current directory a list of fle names and directory names are returned. each entry is terminated by $0d. a directory en - try has dir after the name and before the $0d. dir $01,$20, ,$0d lists the fle name followed by the size. use this before doing a fle read to know how many bytes to expect. $0d, $0d dld $05,$20,, $0d delete directory deletes the directory from the current directory. $0d mkd $06,$20, ,$0d make directory creates a new directory in the current directory. $0d cd $02,$20, $0d the current directory is changed to the new directory $0d cd.. $02,$20,$2e,$2e,$0d move up one directory level. $0d 4 . f i r m w a r e c o m m a n d s e t
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 11 preliminary - subject to change file operations rd $04,$20, $0d read fle this will send back the entire fle in binary to the monitor. the size should frst be found by using the dir command so that the ex - pected number of bytes is known. $0d rdf $0b,$20,size in hex(4 bytes) , $0d reads the data of from the current open fle. this will send back the requested amount of data to the monitor. $0d dlf $07,$20, $0d delete fle this will delete the fle from the current directory and free up the fat sectors. $0d wrf $08,$20,size in hex(4 bytes) , $0d $data,$0d writes the data of to the end of the current open fle. $0d opw $09,$20, ,$0d opens a fle for writing to with wrf $0d opr $0e,$20, ,$0d opens a fle for reading to with rdf $0d clf $0a,$20, ,$0d closes a fle for writing. $0d ren $0c,$20, ,$20, rename a fle or directory $0d fs $12,$0d returns free space in bytes on disk. for disks of over 4 gbytes in size this will return $ffffffff if more than 4 gbyte available. otherwise use fse command $0d fse $93,$0d $0d $0d sek $28,$0d seek to an offset within the fle $0d commands for uart monitor mode only sbd $14, $20,divisor (3 bytes) lsb frst >,$0d set baud rate (see baud rate table) $0d power management commands sud $15,$0d suspend the disk when not in use to conserve power. the disk will be woken up automatically the next time a disk command is sent to it. $0d wkd $16,$0d wake disk and do not put it into suspend when not in use. $0d sum $17,$0d suspend monitor and stop clocks $0d commands to ft232 / ft245 / ft2232 on usb port 1 or 2 fbd $18,$20,$0d set baud rate (see baud rate table 7) $0d fmc $19, $20,,$0d set modem control for rts/dtr (see table 8) $0d fsd $1a, $20,value (2 bytes)lsb frst >,$0d set data characteristics (see table 9) $0d ffc $1b, $20,value (1 byte),$0d set fow control (see table 10) $0d fgm $1c,$0d get modem status (see table 8) returns the modem and line status (2 bytes),$0d fsl $22, $20,value (1 bytes),$0d set latency timer set the latency timer in millisec - onds. the default value is 16 ms $0d table 4.1 - monitor port commands (continued)
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 12 preliminary - subject to change fsb $23,$20,$bitmask, $enable, $0d set bit mode sends the setbitmode command $0d fgb $24, $0d get bit mode returns the state of the pins (1 byte ),$0d commands to unused i/o pins ior $29,$20,port number ad = $00 ac = $01 bd = $02 bc = $03, $0d read i/o port reads the i/o port and returns the data iow $2a,$20,port number ad = $00 ac = $01 bd = $02 bc = $03, $direction (1=output), $value $0d write i/o port writes to the i/o port if it is not being used (i.e. adbus 0 -7 will all be used when uart or fifo interface is active. acbus0 will be used in uart mode but acbus1- 7 are available) printer class commands pgs $81, $0d get printer status returns the status byte of the printer (1 byte ), $0d, ( bit 5 C paper empty bit 4 C selected bit 3 C not error the rest of the bits are 0 ) $0d psr $82, $0d printer soft reset $0d usb device commands dsd $83,$20, size (1byte) ,$0d, data of size ,$0d send data to usb device $0d drd $84 read data from usb device sends back a byte with the number of bytes n available then then sends n data bytes then $0d qp1 $2b,$0d query device port 1 status sends back 2 bytes showing the device types connected to port 1 ( see table ) $0d qp2 $2c,$0d query device port 2 status sends back 2 bytes showing the device types connected to port 2 ( see table ) $0d qd n (where n is a number in hex of 0 to 7) $85,$20,n, $0d (where n is a number in hex of 0 to 7) query device n this returns the device data for device n ,$0d$0d see table sc n (where n is a number in hex of 0 to 7) $86,$20,n, $0d (where n is a number in hex of 0 to 7) set current device to n so if the datareq# dataack mode is entered, then this device interface will be used for it. useful if a ft2232c chip with 2 interfaces is connected for example $0d table 4.1 - monitor port commands (continued)
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 13 preliminary - subject to change sf n (where n is a number in hex of 0 to 7) $87,$20,n, $0d (where n is a number in hex of 0 to 7) set device to be an ftdi device. this is useful if the vid of a ft232r/ft245r ( or bm etc) has been changed from the ftdi default. use qd n to fnd your device. sf n to set the device to ftdi and then sc n to set as the current device. $0d vmusic commands - only with vmsc frmware not standard vdap vpf $1d, $20,,$0d play an mp3 fle sends fle to spi interface ( i/o pins between vnc1 and vlsi1003 ) then returns $0d vwr
(1 byte) $1e, $20,
(1 byte) ,$0d write to command register of vs1003 $0d vrd
(1 byte) $1f, $20,
(1 byte),$0d read from command register of vs1003 returns 2 bytes followed by $0d vst $20,$0d stop playing current track $0d v3a $21,$0d play all tracks with mp3 as the extention. sends all mp3 fles in all sub directories to spi interface then returns $0d vsf $25,$0d skip to next track. $0d vsb $26,$0d skip to beginning of current track. if pressed twice within 1 second it will go to the beginning of the previous track.. $0d debug commands sd $03,$20,$0d sector dump. this is used for debug purposes and may be removed. e.g. sd 0000>cr> will dump sec - tor 0000. sd 0010 will dump sector 16 decimal. sends back 512 bytes from the sector specifed in hex converted to ascii. every 16 bytes is fol - lowed by a $0d. $0d sw $92,$20,$0d,< 512 bytes of data> sector write. this writes a block of data to the sector specifed. mis - use of this command may destroy the disk contents. $0d idd $0f,$0d identify disk drive. this will display information about the at - tached disk. sends idd data block and then $0d idde $94,$0d identify disk drive extended. this will display information about the attached disk allowing for a disk capacity up to 2 terra bytes. sends idde data block and then $0d fwv $13,$0d get firmware versions displays the version numbers of the main frmware and the reprogramming frmware in the VNC1L-1a main x.xx$0d rprg x.xx$0d then $0d
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 14 preliminary - subject to change table 4.2 - error reporting error command mode result if command is unrecognised extended command set bad command,$0d shortened command set bc,$0d if command fails extended command set command failed,$0d shortened command set cf,$0d table 4.3 - idd command results format idd / idde - identify disk drive results usb vid = $, 2 bytes in ascii, $0d usb pid = $, 2 bytes in ascii, $0d vendor id = , 8 bytes in ascii, $0d product id = , 16 bytes in ascii, $0d revision level = , 4 bytes in ascii, $0d i/f = ,scsi or atapi in ascii, $0d fat12 or fat16 or fat32 in ascii, $0d bytes/sector = $, 2 bytes in ascii, $0d bytes/cluster = $, 3 bytes in ascii, $0d idd capacity = $, 4 bytes in ascii, $0d free space = $, 4 bytes in ascii, $0d idde capacity = $, 6 bytes in ascii, $0d free space = $, 6 bytes in ascii, $0d table 4.4 - baud rate table for VNC1L uart interface baud rate 1st byte 2nd byte 3rd byte 300 $10 $27 $00 600 $88 $13 $00 1200 $c4 $09 $00 2400 $e2 $04 $00 4800 $71 $02 $00 9600* $38 $41 $00 19200 $9c $80 $00 38400 $4e $c0 $00 57600 $34 $c0 $00 115200 $1a $00 $00 230400 $0d $00 $00 460800 $06 $40 $00 921600 $03 $80 $00 1000000 $03 $00 $00 1500000 $02 $00 $00 2000000 $01 $00 $00 3000000 $00 $00 $00 * default baud rate after reset is 9600 baud.
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 15 preliminary - subject to change table 4.5 - baud rate table for ft232b, ft232r or ft2232 device on usb port 1 or 2 baud rate 1st byte 2nd byte 3rd byte 300 $10 $27 $00 600 $88 $13 $00 1200 $c4 $09 $00 2400 $e2 $04 $00 4800 $71 $02 $00 9600* $38 $41 $00 19200 $9c $80 $00 38400 $4e $c0 $00 57600 $34 $c0 $00 115200 $1a $00 $00 230400 $0d $00 $00 460800 $06 $40 $00 921600 $03 $80 $00 1000000 $03 $00 $00 1500000 $02 $00 $00 2000000 $01 $00 $00 3000000 $00 $00 $00 * default baud rate after reset is 9600 baud. table 4.6 - set modem control fmc command table for ft232b, ft232r or ft2232 device on usb port 1 or 2 1st byte operation bit 0 dtr# state 0 = off, 1 = on bit 1 rts# state 0 = off, 1 = on bits 7 - 2 reserved 0 2nd byte operation bit 0 1 = change dtr, 0 = leave dtr alone bit 1 1 = change rts, 0 = leave rts alone bits 7 - 2 reserved 0 table 4.7 - set data characteristics fsd command for ft232b, ft232r or ft2232 device on usb port 1 or 2 1st byte operation bit 7-0 number of data bits - 7 or 8 2nd byte operation bit 2-0 parity : 0 - none 1 - odd 2 - even 3 - mark 4 - space bit 5-3 number of stop bits : 0 - 1 stop bit 1 - 1 stop bit 2 - 2 stop bits bits 6 1 = send break, 0 = stop break
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 16 preliminary - subject to change bit 7 reserved 0 table 4.8 - set flow control ffc command table for ft232b, ft232r or ft2232 device on usb port 1 or 2 1st byte operation bit 0 hardware handshake rts/cts bit 1 hardware handshake dtr/dsr bits 2 software handshake xoff / xoff bits 7 - 3 reserved 0
vdap - vinculum VNC1L disk and peripheral interface firmware ? future technology devices international ltd. 2006 datasheet version 1.07 page 17 preliminary - subject to change disclaimer copyright ? future technology devices international limited, 2006. version 1.07 - created december 2006 - added information for frmware 2.08 and later version 1.06 - initial frmware datasheet created august 2006 neither the whole nor any part of the information contained in, or the product described in this manual, may be adapted or reproduced in any material or electronic form without the prior written consent of the copyright holder. this product and its documentation are supplied on an as-is basis and no warranty as to their suitability for any particular purpose is either made or implied. future technology devices international ltd. will not accept any claim for damages howsoever arising as a result of use or failure of this product. your statutory rights are not affected. this product or any variant of it is not intended for use in any medical appliance, device or system in which the failure of the product might reasonably be expected to result in personal injury . this document provides preliminary information that may be subject to change without notice. contact ftdi head offce - future technology devices international ltd. 373 scotland street, glasgow g5 8qb, united kingdom tel. : +(44) 141 429 2777 fax. : +(44) 141 429 2758 e-mail (sales) : sales1@ftdichip.co m e-mail (support) : support1@ftdichip.co m e-mail (general enquiries) : admin1@ftdichip.co m regional sales offces - future technology devices international ltd. (taiwan) 4f, no 16-1, sec. 6 mincyuan east road, neihu district, taipei 114, taiwan, r.o.c. tel.: +886 2 8791 3570 fax: +886 2 8791 3576 e-mail (sales): tw.sales1@ftdichip.co m e-mail (support): tw.support@ftdichip.co m e-mail (general enquiries): tw.admin@ftdichip.co m future technology devices international ltd. (usa) 5285 ne elam young parkway, suite b800 hillsboro, or 97124-6499 usa tel.: +1 (503) 547-0988 fax: +1 (503) 547-0987 e-mail (sales): us.sales@ftdichip.co m e-mail (support): us.support@ftdichip.co m e-mail (general enquiries): us.admin@ftdichip.co m website url : http://www.ftdichip.co m


▲Up To Search▲   

 
Price & Availability of VNC1L

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X