-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlutoSDR not working after external clock #92
Comments
Copy the plutosdr-fw-v0.38.zip as is onto the mass storage drive. Don't unzip it, etc. Regarding external clock please see here: https://wiki.analog.com/university/tools/pluto/devs/booting#examples |
hi @mhennerich So when i set
I've seen in the AD wiki pages that issues regarding external GPS clocks have been addresses and solved before, but the threads were more in depth (regardin GPIO's and and device tree etc). can you please help me thanks |
Please SSH to Pluto and run the command dmesg. Paste the output here |
This is the output i get:
when running my code in PyADI after setting external refclk i still get the error i mentioned earlier :( |
Transceiver looks fine. Can you do 2 things.
|
|
since everything works perfectly fine when redefine Because im using the Leo Bodnar GPS external clock, and from i what naively know it only starts to output square waves when there's a PLL lock with a satellite. and as per the current status of the clock now , this is what i get :
implying that there is not satellite lock and whence no square wave output of 40 MHz. is it possible that cold boot of the this type of clock itself takes time? |
Was the dmesg with internal or external clock? |
@mhennerich this is the output with external clock:
|
This means that the AD9361 device failed with error. |
I also tried setting |
When you switch from internal to external you also need to specify the external clock. |
|
Ok that means that the device expects 40MHz did you measure the clock and made sure it's available when you start the unit? |
it just worked now. strangely, i did
is it because of AD9364 ??? |
What do you mean??? Do you mean the ext clock frequency in the |
should be: iio_attr -u ip:192.168.2.1 -d |
Its not required to set the device in AD9364 mode to use an external reference. However, you need to connect and power the reference before booting Pluto. |
Phil Greenland advises against applying voltage to the external clock before turning on Pluto: Here's what he wrote about it: https://www.quantulum.co.uk/blog/private-lte-with-analog-adalm-pluto/ |
Can anyone definitively say if this Pluto Rev D is using an external Leo Bodnar frequency source please. I am copy pasting the result of SSH via Putty of DMESG command. Many thanks! login as: root | ___ \ | | | | _ \ | | | ___ v0.32-dirty dmsg-sh: dmsg: not found dmesgBooting Linux on physical CPU 0x0 |
Hi @mhennerich @tfcollins
I have a similar problem to the one in this thread. When i tried to use an external GPS clock with 40MHz output, and injected it to the pluto's CLK_IN and changed the xo_correction setting in the config.txt as per the instructions in link above, i now get this persisting error in PyADI:
the pluto was working perfectly fine before. How can i reset back to factory settings ? also, what is the correct way to properly introduce external clock
Originally posted by @Argonghost in #50 (comment)
The text was updated successfully, but these errors were encountered: