Post Go back to editing

FFH control in GPIO Direct Mode in Kuiper Linux

Thread Summary

The user encountered issues testing the AD9084_EBZ GPIO hop mode on a VPK180 running Kuiper Linux. The problem was resolved by using the ad9088-ffh-fixes branch, removing the gpio-exports line, and correcting a mismatched GPIO pin (31 in gpiochip0 is not connected to the Apollo).
AI Generated Content
Category: Software
Product Number: AD9084
Software Version: Kuiper Linux

Hello,

I am trying to test the AD9084_EBZ GPIO hop mode, using a VPK180 running Kuiper Linux, but facing difficulties. 

Here is what I have done so far:

I am using device-profile-fw-name = "204C_M4_L4_NP16_20p0_4x4.bin", which has the quick profile cfg set to 0.

I updated ad9088_ffh.c line 40, as the bit count was being overwritten by the error return value of read_u32_array. 

I have also added the following lines to my device tree in the ad9084@0 section, to expose the GPIO hop control pins to the drivers. This matches quick_config_profile_3. 

gpio-export becomes gpiochip3 here, and the hop parameters get attributed correctly looking through dmesg. 



I then set the mode as follows: ``` echo 3 > in_voltage0_i_ffh_fnco_mode  ``` and do the same for the CNCO, after running through a profile setup script, which simply fills all FNCO and CNCO profiles. 

I then try to toggle the hop on the RX0 FNCO by using block = 0x0, terminal = 0x1, and writing a random value for the profile. No matter if I use gpioset/get methods on gpiochip3 or gpiochip0 I am unable to see the frequency shift. 

I have also tried writing directly to the axi-gpio module using devmem, which resulted in the same. 

Any help would be greatly appreciated, thank you

Thread Notes

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.