# Measuring data rate of ASF USB Device CDC example

Atmel Studio 6.1 provides an example project for Atmel Software Framework (ASF) 3.12.1, called USB Device CDC Example - EVK1101. EVK1101 is an evaluation kit for the AT32UC3B0256 part, that has 256 KB of flash memory. The example though is equally valid for other variants of that part, with more or less flash memory.

I modified the sample code so that

• It can be programmed to part AT32UC3B0512 (used by my target board)
• Code in callback uart_rx_notify of uart_uc3.c is commented out so it does nothing
• The while loop in main.c echoes back characters received over USB, as shown below
int value;

while (true) {
value = udi_cdc_getc();
// Fifo full
udi_cdc_signal_overrun();
}
else
{
udi_cdc_putc(value);
}
}
}


I then compiled the code and programmed it to my target using a JTAGICE mkII. Connecting the target to a Windows PC results in creation of a serial port on the PC. A driver is provided with the example. If you use Windows 8, you’ll require a (self-)signed driver, that is, if you haven’t disabled that check.

Measuring data rate is then a matter of sending a known amount of data and dividing it by the time required to send it. Since I’m echoing back data, I divided that result by 2. Just to be sure that my code modifications were reliable, I compared the echoed back data with the original. To communicate over the serial port, I used a handy tool called SerialTool I created a while back (requires .NET framework 4.5 or mono 3.2.x).

The average data rate that I was able to measure is in the range of 3200 bytes per seconds or just shy of 26000 bits per second. Pretty lame, I think.

## Improving data rate

The trick to improving the data rate is to use alternate functions that receive/transmit multiple bytes per read/write. Atmel’s AVR4907: ASF - USB Device CDC Application note hints to the existence of these functions in udi_cdc.h.

The modified while loop in main.c produces a much more respectable 458000 bytes per second or 3664000 bits per second. That too while debugging using JTAG.

int len;
const int BUF_SIZE = 10;
char buf[BUF_SIZE];

while (true) {

// blocks until BUF_SIZE bytes are received

The echo logic above has a slight design flaw. If data is not a multiple of 10 bytes, the code will be stuck in the call to udi_cdc_read_buf towards the end of the data. I chose 10 quite arbitrarily.