You are not logged in.
Dear sir,
I have encountered the following problem: the RF A light of my WARP V3 board is continuously blinking when launching the board. There is an error code E2 on the digital display. All the other three RF lights do not blink. Could you help to tell how to solve it?
Thanks!
Offline
The photo is here: https://www.dropbox.com/s/pk7xnjz790t9s … e.JPG?dl=0
Last edited by shanggdlk (2017-Sep-08 22:12:43)
Offline
Blinking LEDs on an RF interface indicate the radio PLL is not locked. This can occur if you have a clock module installed but do not supply an external clock. It can also occur if the hardware is damaged. If you're not using a clock module, it's likely the board requires repair. You can attempt repairs locally or email us at support[at]mangocomm.com to discuss repair options via our manufacturer. If your application only requires 1 RF interface you can also modify the C code to ignore the unlocked condition on RF A and continue using RF B normally.
Offline
murphpo wrote:
Blinking LEDs on an RF interface indicate the radio PLL is not locked. This can occur if you have a clock module installed but do not supply an external clock. It can also occur if the hardware is damaged. If you're not using a clock module, it's likely the board requires repair. You can attempt repairs locally or email us at support[at]mangocomm.com to discuss repair options via our manufacturer. If your application only requires 1 RF interface you can also modify the C code to ignore the unlocked condition on RF A and continue using RF B normally.
Thanks, Murphpo. Appreciate!
I tried two ways: 1): supplying clock using its own clock (CM-MMCX) 2): using an external clock. Unfortunately, both of them fail. So I think I need to contact for repairs.
Anyway, thanks a lot!
Offline
murphpo wrote:
Blinking LEDs on an RF interface indicate the radio PLL is not locked. This can occur if you have a clock module installed but do not supply an external clock. It can also occur if the hardware is damaged. If you're not using a clock module, it's likely the board requires repair. You can attempt repairs locally or email us at support[at]mangocomm.com to discuss repair options via our manufacturer. If your application only requires 1 RF interface you can also modify the C code to ignore the unlocked condition on RF A and continue using RF B normally.
By the way, could you tell me which C file/part should I modify to make the WARP ignore the RF_A error?
Thanks
Offline