KCC's Quizzes AQQ306 about a fish stick challenge
1. First the quote of the month: " I am so clever that sometimes I don't understand a single word of what I am saying" - Oscar Wilde
2. New quiz AQQ306 about a fish stick challenge:
Here below is a pseudo fish diagram swimming to the right.
Question
View All
October Monthly Blog Quiz! Read the blog, take the quiz, and you could win a gift card
Finding Your Circuit Chi — EMC Quiz!
Think you know EMC? Test your knowledge with our 5-question quiz!
Read the blog first, then take the challenge: Finding Your Circuit Chi
Every current flowing creates electromagnetic fields.
Strong EMC design
View All
I'm interested in whether it would be possible to use the ADALM-PLUTO time-of-arrival localization. This requires a very stable clock. I wonder whether it will be possible to feed in an external reference clock? In the revision-B schematics, it looks like there is no connector or jumper to switch from the built-in 40MHz oscillator to an external clock.
Also, if I do feed the clock from an external source (even if this involves removing the 40MHz oscillator), how difficult will it be to switch from 40MHz to 10Mhz? I see that the AD9363 does support 10MHz clocks, but will it is reasonably easy to configure the firmware for this clock frequency?
Thanks, Sivan Toledo, Tel-Aviv University
Sivan:
Yes - you should be able to lift off the current oscillator, and use an external clock. There is a hole in the PCB specifically for this purpose. All you need to do is lift C123, and put a 1.3V p-p clock into that node.
Since we have a 1.8V oscillator, we are using C123/C124 as an AC divider to get things down to 1.3V p-p. The internal capacitance of the pin means we don't actually need to stuff C124 to achieve this.
The Input Frequency Range for the reference clock is from 10 - 80 MHz. That is spec'ed in the datasheet. After that, it should be a simple matter of updating the device tree to tell the Linux driver you are using something different than 40MHz.
-Robin
hi,
as a suggestion since is not so easy to solder and external clock input instead the C123 maybe should be great in rev. C to add some kind of test point (or even a connector) to feed the external clock with a jumper to select the input source.
This is the typical solution in most fpga development kits but maybe you have a better solution.
Thanks.
External clock for ADALM-PLUTO SDR
AD recommends/necessary steps are:
- remove TCXO 40.0 MHz and
- provide the external synchronisation via C123
It would be very helpful if AD could foresee on the PCB a Land Pattern for the installation of Ultra Miniature Coaxial Connector, UMCC, Part No. 128-0711-201 from Emerson Network Power (or install this connector):
Therefore, the external synchronisation can be easily provided via UMCC:
See https://coherent-receiver.com/pluto-sdr for more details.
Thanks in advance.
Hi,
Thanks for the write-up.
We will take this into consideration if/when we release a new rev of the PCB.
Thanks,
Mihai
All you have to change is this line in the device tree:
linux/zynq-pluto-sdr.dtsi at master · analogdevicesinc/linux · GitHub
However you need to rebuild the plutosdr-fw image to apply the change.
Have a look also here -
Coherent Transceivers based on ADALM-PLUTO SDR | RTL-SDR Multi-Channel Coherent Receivers
-Michael
hi ,
I have discover this post and want to use an external 10MHz clock.
could you explain what I need to do to "updating the device tree to tell the Linux driver you are using something different than 40MHz".
changing the clock, I don't have to change any in the FPGA design?
Can you do a cat /sys/kernel/debug/clk_summary?
Then also the AD936x is very sensitive to the external clock source. Square wave inputs don't work well, and also the Vpp must be inside the specs.
-Michael
Hello Michael,
I'd like to use external 10MHz reference clock.
I have made the changes according post:
I have rebuild Pluto with changed zynq-pluto-sdr.dtsi (clock-frequency = <10000000>;)
and update it successfully.
I am running modified ad9361-iiostream.c from examples to output 1GHz SW
When external reference is 10MHz I see about 678MHz SW on spectrum.
But when I external frequency is 40MHz there is exactly 1GHz SW.
What could be wrong?
Do I need to make another changes in sources.
Thanks,
Boris.
Please see here:
Pluto reads the calibration value from the SPI uboot environment. And patches the device tree on boot.
You can avoid this behavior by setting ad936x_skip_ext_refclk uboot env variable.
-Michael
Thanks for rapid answer, Michael.
I have used square wave, may be this was a problem.
I have assembled oscillator back now.
I'll remove it and try sine now.
cat /sys/kernel/debug/clk_summary did not work for me.
See teraterm output below:
cat /sys/kernel/debug/clk_summary
cat: can't open '/sys/kernel/debug/clk_summary': No such file or directory
cd /sys/kernel/debug
ls
bdi hid pm_qos suspend_stats
ci_hdrc.0 ieee80211 ras usb
clk iio regmap wakeup_sources
fault_around_bytes memblock regulator zynq_rst
gpio pinctrl sleep_time
#
Boris.