Post Go back to editing

Power error in FDD for Frequency hoppoing

Category: Software
Product Number: ADRV9002
Software Version: NO-OS2021R2

Because I can't generate a FDD hopping profile using TES. So I try to modify the profile that has been generated. I noticed an error in my power configuration API after I changed it. The error content is as follows

[ERROR]: Error number  1 (0x00000001), Recovery action -2.In file ../noos/drivers/rf-transceiver/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure_Validate, in line  39, variable name readPattern.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
[ERROR]: Error number  1 (0x00000001), Recovery action -2.In file ../noos/drivers/rf-transceiver/navassa/devices/adrv9001/public/src/adi_adrv9001_powermanagement.c, in function adi_adrv9001_powermanagement_Configure, in line  70, variable name NULL.Error message ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board.
adrv9002_power_mgmt_config, 614: failed with "ARM memory is not accessible. Check whether device clock and/or power is connected to the ADRV9001 board" (1)

I didn't have any of these problems with  only Tx in TDD, and I want to know if I modified the parameters correctly, or which parameters I ignored to modify.

The main changes I made from launch only to double hop are
one:
  \"rx1LoSelect\": 1, \
   \"rx2LoSelect\": 1, \
    \"tx1LoSelect\": 1, \
    \"tx2LoSelect\": 1, \
to
    \"rx1LoSelect\": 1, \
    \"rx2LoSelect\": 2, \
    \"tx1LoSelect\": 1, \
    \"tx2LoSelect\": 2, \
two:
    \"duplexMode\": 0, \
to
    \"duplexMode\": 1, \
this is my profile . Can you check for me ?


IN TDD
[edited by: JS1998 at 12:23 AM (GMT -4) on 14 Mar 2024]

Thread Notes

  • To add what I think might be causing this problem: I'm using dgpio to control hop signals. I assigned to dpio directly by using reg in system.top, which was fine the first time I ran it. Every time I re-run for a second time, I found that there was a problem with the power supply. I think it may be that dgpio kept turning over, which affected some of the power supply provided to the board.

  • Hi JS1998,

    After seeing the error message it looks like device clock supply is not provided to the ADRV9001. Can you confirm if the device clock is provided at the correct frequency as configured in the TES?

    Regards

    Rahul