I have the following observation (is not really a problem yet, but..)
My T3.1, 144MHz overclocked, writes 896 bytes over USB to a PC win8.1.
I use multiple 'usb_serial_write' (each 64 bytes), each followed by 'usb_serial_flush_output'
I have two timings
1) NO PC connection, i.e. no program that reads the data, the time spent to 'upload' data to usb_serial system: 10 us (+-).
OK, this is the time could represent the time required to load the different the data into the usb buffers etc.
2) PC reading data, the T3 time to upload data into usb : 660 us.
Now, while the timings are reasonable, it seems the T3 is blocking CPU while transferring data over usb as 660 us correspond to about 1 Mbit transfer rate (T3 to PC).
Is this correct? Does T3 blocks (or uses) the CPU while transferring data over usb_serial?
If yes, is there any option, to upload data to usb driver and not to wait for transmission?
grazie
Walter
My T3.1, 144MHz overclocked, writes 896 bytes over USB to a PC win8.1.
I use multiple 'usb_serial_write' (each 64 bytes), each followed by 'usb_serial_flush_output'
I have two timings
1) NO PC connection, i.e. no program that reads the data, the time spent to 'upload' data to usb_serial system: 10 us (+-).
OK, this is the time could represent the time required to load the different the data into the usb buffers etc.
2) PC reading data, the T3 time to upload data into usb : 660 us.
Now, while the timings are reasonable, it seems the T3 is blocking CPU while transferring data over usb as 660 us correspond to about 1 Mbit transfer rate (T3 to PC).
Is this correct? Does T3 blocks (or uses) the CPU while transferring data over usb_serial?
If yes, is there any option, to upload data to usb driver and not to wait for transmission?
grazie
Walter