... | ... | @@ -22,7 +22,35 @@ probably, just lacks of a couple new attributes. |
|
|
|
|
|
Officially, we support version *3.2.43-rt63* on 32bit system, and
|
|
|
*3.6.11-rt30* on 64bit system. This is not a strict constraint, it
|
|
|
should compiles and works correctly from version *2.6.37*
|
|
|
should compiles and works correctly from version
|
|
|
*2.6.37*
|
|
|
|
|
|
### The EEPROM of my fmc-adc is empty and the driver won't load, what should I do?
|
|
|
|
|
|
a): Calibrate the board using a Production Test Suite (PTS) system.
|
|
|
|
|
|
- [Fmc-adc testing
|
|
|
project](https://www.ohwr.org/project/fmc-adc-100m14b4cha-tst/wikis)
|
|
|
|
|
|
b): Base eeprom image containing dummy calibration data (offsets=0,
|
|
|
gains=1):
|
|
|
|
|
|
- [Dummy fmc-adc eeprom
|
|
|
image](https://www.ohwr.org/project/fmc-adc-100m14b4cha/uploads/1711cbd4515984d6bbf51eb14d0117d6/fmc-adc_dummy_eeprom_image.out)
|
|
|
|
|
|
Once you get your eeprom image (option *a*, or *b*), you have to write
|
|
|
it on the ADC eeprom. To do that
|
|
|
|
|
|
cd /sys/bus/fmc/devices/<device-name>-<device-id>
|
|
|
cat /path/to/your/eeprom/image > eeprom
|
|
|
|
|
|
Where `<device-name>-<device-id>` depends on: mezzanine, carrier and
|
|
|
slot.
|
|
|
Of course, you can dump/read the current eeprom image:
|
|
|
|
|
|
cd /sys/bus/fmc/devices/<device-name>-<device-id>
|
|
|
cat eeprom
|
|
|
hexdump eeprom
|
|
|
|
|
|
### FAQs don't help me
|
|
|
|
... | ... | @@ -46,6 +74,10 @@ order to help us to understand your problem we recommend you to: |
|
|
/sys/bus/fmc/devices/`
|
|
|
- if you are using code of your own, please share it with us
|
|
|
|
|
|
-----
|
|
|
|
|
|
Federica Vaga, Matthieu Cattin - August 2014
|
|
|
|
|
|
|
|
|
|
|
|
### Files
|
... | ... | |