This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
resources:tools-software:linux-software:ad9371_advanced_plugin [19 May 2016 17:42] – Michael Hennerich | resources:tools-software:linux-software:ad9371_advanced_plugin [01 Jun 2017 17:21] – Michael Hennerich | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== AD9371 Advanced Plugin ====== | + | ====== AD9371/ |
- | The AD9371 Advanced plugin works with the [[iio_oscilloscope|IIO Oscilloscope]]. You always use the latest version if possible. Changing any field will immediately write changes which have been made to the AD9371 settings to the driver, but not to the HW unless the Save Settings button is pressed. | + | The AD9371/ |
The AD9371 Advanced Plugin allows testing of different device driver initialization options and values. | The AD9371 Advanced Plugin allows testing of different device driver initialization options and values. | ||
- | In contrast to the controls on the [[ad9371_plugin|AD9371 Main Plugin]] – the controls here are not part of the main driver API. | + | In contrast to the controls on the [[ad9371_plugin|AD9371/ |
In the No-OS driver the values directly correspond to members of the (mykonosDevice_t) mykDevice init structure. | In the No-OS driver the values directly correspond to members of the (mykonosDevice_t) mykDevice init structure. | ||
Line 12: | Line 12: | ||
{{ : | {{ : | ||
- | See more details about [[resources/ | + | See more details about [[resources/ |
In order for the settings made on these plugin to take affect, the Save Settings button must be pressed. | In order for the settings made on these plugin to take affect, the Save Settings button must be pressed. | ||
Line 18: | Line 18: | ||
- | <WRAP top tip round box 60%> | + | <WRAP top tip round box 100%> |
After you customized the driver for your application needs you can read back all values from the Linux debugfs: | After you customized the driver for your application needs you can read back all values from the Linux debugfs: | ||
Line 25: | Line 25: | ||
< | < | ||
root@analog:/ | root@analog:/ | ||
- | root@analog:/ | + | root@analog:/ |
- | adi,arm-gpio-orx-mode0-pin:0 | + | adi,clocks-clk-pll-hs-div = <4>; |
- | adi,arm-gpio-orx-mode1-pin:0 | + | adi,clocks-clk-pll-vco-div = <2>; |
- | adi,arm-gpio-orx-mode2-pin:0 | + | adi,clocks-clk-pll-vco-freq_khz = < |
- | adi,arm-gpio-orx-pin-mode:0 | + | adi,clocks-device-clock_khz = < |
- | adi,arm-gpio-orx-trigger-pin:0 | + | adi, |
- | adi,arm-gpio-orx1-enable-ack:0 | + | adi,gpio-3v3-oe-mask = <0>; |
- | adi,arm-gpio-orx2-enable-ack:0 | + | adi,gpio-3v3-src-ctrl11_8 = <3>; |
- | adi,arm-gpio-rx1-enable-ack:0 | + | adi,gpio-3v3-src-ctrl3_0 = < |
+ | adi,gpio-3v3-src-ctrl7_4 = <3>; | ||
+ | adi,gpio-oe-mask = < | ||
+ | adi,gpio-src-ctrl11_8 = < | ||
+ | adi,gpio-src-ctrl15_12 = <0>; | ||
+ | adi,gpio-src-ctrl18_16 = < | ||
+ | adi,gpio-src-ctrl3_0 = < | ||
+ | adi,gpio-src-ctrl7_4 = <0>; | ||
[ -- snip -- ] | [ -- snip -- ] | ||
Line 88: | Line 96: | ||
{{ : | {{ : | ||
- | ==== JESD Framer Settings ==== | + | ==== JESD204B |
{{ : | {{ : | ||
- | ==== JESD Deframer Settings ==== | + | ==== JESD204B |
{{ : | {{ : | ||
Line 111: | Line 119: | ||
| | ||
=== BIST PRBS === | === BIST PRBS === | ||
+ | |||
Pseudorandom Binary Sequence (PRBS) that can either injected into the RX or TX path. | Pseudorandom Binary Sequence (PRBS) that can either injected into the RX or TX path. | ||