Loading custom profile for ADRV9008-2 and ADRV9008-1

Dheeru@3 said:

How can I enable this IIO Oscilloscope feature in the custom image that is created so that I can load the profile.

You can load a profile via the sysfs API or by using libiio - please see here:

• https://wiki.analog.com/resources/tools-software/linux-drivers/iio-transceiver/adrv9009#profiles

A libiio example which reads the profile from file and writes it to the profile_config attribute can be found here:

• https://github.com/analogdevicesinc/iio-oscilloscope/blob/master/plugins/adrv9009.c#L365

Dheeru@3 said:

Also, can I load the profile while booting using UART console.

Yes, all parameters from the profile can be converted to devicetree parameters.

Please see here:

• https://wiki.analog.com/resources/tools-software/linux-drivers/iio-transceiver/adrv9009-customization
• https://wiki.analog.com/resources/tools-software/linux-software/adrv9009_advanced_plugin
• https://wiki.analog.com/resources/eval/user-guides/rf-trx-vcxo-and-profiles

-Michael

Hello Michael

Thanks for your response.

As suggested above in https://wiki.analog.com/resources/tools-software/linux-drivers/iio-transceiver/adrv9009#profiles, if I want to load the profile, where should the profile.txt file be saved so that the values shall be updated. Let me elaborate the steps that I followed while building the project using Petalinux : 

1. The corresponding .hdf file for ADRV9009 was used to configure the Peralinux project created.

2. The meta-adi-core and meta-adi-xilinx files were added in Yocto Layers on configuration window.

3. The zynqmp-zcu102-rev10-adrv9009-jesd204-fsm.dts was displayed in petalinuxbsp.conf file.

4. petalinux-build was performed.

The ambiguity is, among all these steps where should I add my profile or if I want to load profile in profile_config using : root@analog:/sys/bus/iio/devices/iio:device3# cat Tx_BW200_IR245p76_Rx_BW200_OR245p76_ORx_BW200_OR245p76_DC245p76.txt > profile_config

where should the .txt file be saved.

The doubt sounds insane, but requesting your guidance in resolving this doubt.

Thanks in advance

Deepika

The custom profile needs to be translated into the device tree if you want it loaded at boot. You can see the related setting in this example node: https://github.com/analogdevicesinc/linux/blob/master/arch/arm64/boot/dts/xilinx/adi-adrv9009.dtsi#L105

-Travis

Hello Travis

Thanks for your response.

That clarified my doubt.

Seeking another clarification. The example mentioned above is for 1 profile. If I want to change the profiles, editing the device tree and generating a new image sounds tedious. Requesting you to suggest an approach, if it is possible to change the profile in run time, I mean when the board boots.

Also, may I know the method in which I can display the current configuration in terms of Sampling Frequency, mode for which the device is configured, etc. as  it is displayed on Booting when the device is configured through Bare Metal. I tried using iio_info, but it displays a whole set of parameters configured, few of which I may not need for my application.

Requesting your guidance.

-Deepika

As long as the profile does not require changes to the JESD configuration yes. The method Michael pointed out in the first link allows you to change the profiles at runtime.

-Travis

As long as the profile does not require changes to the JESD configuration yes. The method Michael pointed out in the first link allows you to change the profiles at runtime.

-Travis

Thanks Travis

As specified by Michael in 1st link, the doubt is where should this .txt file be saved or where should that file be called in the process of building the petalinux project so that I can use it in run time. 

-Deepika

Please see here: https://support.xilinx.com/s/question/0D52E00006hpjauSAA/how-to-add-files-to-petalinux-when-building-it?language=zh_CN

-Michael