clock rates > 15MHz cause a hardware baudrate of 30MHz

krzysztofgawrys / libmpsse

Automatically exported from code.google.com/p/libmpsse

0 stars 0 forks source link

What steps will reproduce the problem? case 1. run b.c from issue #10, measure the clock rate case 2. change the clock rate to 15000000 (15MHz), rebuild and run case 3. change the clock rate to 15000001 (15.000001MHz), rebuild and run What is the expected output? What do you see instead? case 1. expected = 25MHz, seen = 30MHz (bad) case 2. expected = 15MHz, seen = 15MHz (good) case 3. expected = 15MHz, seen = 30MHz (bad) What version of the product are you using? On what operating system? verified with libmpsse-1.1 and -1.2 Please provide any additional information below. ubuntu 11.04 running on 3.0.0-23-generic/x64 The hardware in use is the MPSSE-3.3V cable from FTDI based on the FTDI232H

This is expected behavior, and is a limitation of the FTDI chips themselves. 

As with many pieces of hardware that accept a programmable clock rate, the FTDI 
chips accept not an absolute clock rate, but rather a divisor that is used to 
derive the desired clock rate from the primary clock. These divisors are 
finitely precise; in the case of the FTDI chips, the divisor is a 16 bit value. 
 So you can't set the clock rate so something as specific as 15.000001MHZ. 

If you take a look at the freq2div code in the support.c file, you'll see the 
algorithm used to derive a divisor from a given clock frequency, as specified 
in the FTDI data sheet (not complicated). Basically, any value above 15MHz will 
result in a divisor of 0, which gives you a clock rate of 30MHz. Any value 
between 10 and 15MHz gives you a 15MHz clock rate and a value between 6 and 
10MHz gives you a 10MHz clock rate. Values from 1-6MHz can be specified 
exactly, in 1MHz steps.

Original comment by heffne...@gmail.com on 25 Jul 2012 at 7:29

Changed state: Invalid

krzysztofgawrys / libmpsse

clock rates > 15MHz cause a hardware baudrate of 30MHz #11