Hi Marcus
The voltage level of my PPS is 5.04V,from a trimble thunderbolt.
This is the complete output log when I run test_pps_input.
itupac@itupac:~/workarea-uhd/uhd/host/build/examples$ ./test_pps_input
--source external
[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501;
UHD_3.14.0.HEAD-0-g6875d061
[WARNING]
[UHD] Unable to set the thread priority. Performance may be negatively
affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparamCreating the usrp
device with: ...
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
[WARNING] [USRP2] Unable to identify device - assuming USRP2/N-Series device
[WARNING] [UHD] Unable to set the thread priority. Performance may be
negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N???
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: BasicRX (AB)
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Unknown (0xffff) - 0
Attempt to detect the PPS and set the time...
[INFO] [MULTI_USRP] 1) catch time transition at pps edge
[WARNING] [UHD] Unable to set the thread priority. Performance may be
negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
[WARNING] [UHD] Unable to set the thread priority. Performance may be
negatively affected.
Please see the general application notes in the manual for instructions.
[WARNING] [UHD] Unable to set the thread priority. Performance may be
negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Error: RuntimeError: Board 0 may not be getting a PPS signal!
No PPS detected within the time interval.
See the application notes for your device.
El mié, 20 oct 2021 a las 20:40, Marcus D. Leech (<patchvonbr...@gmail.com>)
escribió:
> On 2021-10-20 4:19 p.m., isaac mario tupac davila wrote:
>
> Hi Marcus
>
> Curiosity and quickness possessed me. I tried first to burn it with the
> usrp_n210_r4_fpga.bit as I have a N210 but it failed. Later, I could burn
> it with the usrp_n200_r4_fpga.bit. I changed the Ip and installed the
> usrp_n200_fw.bin and usrp_n200_r4_fpga.bin. It could recognize it. My
> FPGA is a Spartan 3 XC3SD1800A.
>
> That FPGA type unambiguously makes it an N200, not an N210, so loading the
> N210 FPGA into it would be guaranteed to fail.
>
> The N210 has the XC3SD3400A.
>
> What is the voltage level of your PPS signal?
>
> COuld you share the complete output log of the test_pps_input program?
>
> Also, are you specifying the --source external option? It may be looking
> at the PPS from the GPSDO, which you don't have installed.
>
>
>
>
>
>
> EnvironmentError: OSError: error in pthread_setschedparam
> _____________________________________________________
> /
> | Device: USRP2 / N-Series Device
> | _____________________________________________________
> | /
> | | Mboard: N???
> | | mac-addr: 00:00:00:00:40:00
> | | ip-addr: 192.168.10.3
> | | subnet: 0.0.0.104
> | | gateway: 255.255.255.255
> | | gpsdo: none
> | | serial: 0
> | | FW Version: 12.4
> | | FPGA Version: 11.1
> | |
> | | Time sources: none, external, _external_, mimo
> | | Clock sources: internal, external, mimo
> | | Sensors: mimo_locked, ref_locked
>
> The problem is when I run the ./test_pps_input from the uhd my USRP fails
> finding the PPS.
>
> Please see the general application notes in the manual for instructions.
> EnvironmentError: OSError: error in pthread_setschedparam
> Error: RuntimeError: Board 0 may not be getting a PPS signal!
> No PPS detected within the time interval.
> See the application notes for your device.
>
> What could be the problem? Maybe the firmware? I'm not completely sure
> about it
>
> Any help or advice will be appreciate
>
> Regards
> Isaac T.
>
> El vie, 15 oct 2021 a las 20:12, Marcus D. Leech (<patchvonbr...@gmail.com>)
> escribió:
>
>> On 2021-10-15 5:57 p.m., isaac mario tupac davila wrote:
>> > Hello
>> >
>> > I'm Isaac. I have a tricky thing here instaling images. I have a USRP
>> > N210 with FW Version: 12.1 FPGA Version: 10.0. When I prove the pps
>> > test, it says: No PPS detected within the time interval. I believe it
>> > is for the FPGA image(v10). So I tried to update the image and
>> > firmware doing: ./uhd_images_downloader.py and later:
>> > ./uhd_image_loader
>> > --args="type=usrp2,addr=192.168.10.2,overwrite-safe"
>> > --fw-path=/usr/local/share/uhd/images/usrp_n210_fw.bin
>> > --fpga-path=/usr/local/share/uhd/images/usrp_n210_r4_fpga.bin, only
>> once.
>> >
>> > I turned off my USRPN210 and now I can't find it (doesn't have IP
>> > anymore) and any light(A,B,C or D) has turned on.
>> >
>> > The interesting thing is that I have a second USRP (N200,FW Version:
>> > 12.3 FPGA Version: 10.0) with the same PPS problem and I don't want to
>> > make the same mistake again. So...
>> >
>> > 1. What do you think I did wrong? ¿Do I have to eliminate
>> > overwrite-safe in the command?
>> Why did you use overwrite-safe? What possessed you to do that? Most of
>> the time there is NO reason to overwrite the safe-mode image, since it
>> is an image specifically to help you get through loading a bad "main"
>> image.
>>
>> > 2. How could I save my first USRP? Do I have to burn the FW and image
>> > with a burner JTAG directly on the motherboard?
>> Almost certainly you do now.
>>
>>
>> https://kb.ettus.com/N200/N210_Device_Recovery#Unbricking_an_N-Series_Device
>>
>>
>> >
>> > Any help will be appreciate it.
>> > Thanks
>> > Regards
>> > Isaac T.
>> >
>>
>>
>>
>
