ADF5355 no-OS driver

Me_ said:

I came accross a Linux driver for this part developped by you. I have then been trying to port it on my no-OS application but I'm stuck at some point.

Hi Me_,

We don't offer a no-OS driver for this part, it's true.

We also don't have a step-by-step guide to porting from Linux -> no-OS. But can you please tell us in more detail where did you get stuck ? Perhaps we can help with the port.

Hi Buha,

Thanks for your reply.

I suppose these functions are used for scaling purpose (from_ccf_scaled and to_ccf_scaled()) but I haven't found any info on how they are implemented. Could you please tell more about them?

Plus, could you please provide the initial state of the structure : adf5355_platform_data ?

Thanks

Hi,

We have just started to create a no-OS driver for ADF5355. It should be ready in a few days.

Thanks,
Dragos

Hi DragosB,

Thank you for the reply. That's a wonderful news.

It will be nice to compare my no-OS driver for ADF5355 with yours. Actually, I have followed the steps you provided (in another Q&A), I'm just waiting for my Hardware to test it.

I'm looking forward to seeing your no-OS driver.

Thanks.

Hello Me_,

An initial no-OS driver for ADF5355 is added with https://github.com/analogdevicesinc/no-OS/pull/987

Regards,

Antoniu

Hi amiclaus,

Thank you for the reply. I have a question regarding the function spi_write_and_read.

Is this function documented in spi.h ? or Did you mean "spi_write_then_read" (as in AD9361 no-OS driver) ?

Thanks in advance.

Pedro

Hi amiclaus,

Thank you for the reply. I have a question regarding the function spi_write_and_read.

Is this function documented in spi.h ? or Did you mean "spi_write_then_read" (as in AD9361 no-OS driver) ?

Thanks in advance.

Pedro

Hello Me_,

Both AD9361 and ADF5355 drivers should use the same spi.h that can be found here:

https://github.com/analogdevicesinc/no-OS/blob/master/include/spi.h

The implementation of the SPI driver depends on the platform used:

https://github.com/analogdevicesinc/no-OS/tree/master/drivers/platform

But the signature should be the same everywhere: `spi_write_and_read`

Can you point out where did you find `spi_write_then_read` in the AD9361 no-OS driver?

Regards,

Antoniu

As for code documentation you might want to check out our no-OS doxygen:

http://analogdevicesinc.github.io/no-OS/

Regards,

Antoniu

Hello Amiclaus,

Thank you for the reply. You can find it here :https://github.com/analogdevicesinc/linux/blob/master/drivers/iio/adc/ad9361.c

also here (mentionned by DragonB) : https://ez.analog.com/microcontroller-no-os-drivers/f/q-a/85843/about-no-os-support-for-adf5355-on-ad-fmcomms5-ebz

And from here https://wiki.analog.com/resources/eval/user-guides/ad-fmcomms2-ebz/software/baremetal and that's where I found ad9361_spi_write_then_read in the AD9361 no-OS driver, but it's no longer available.

Thanks.

The no-OS repository went through a lot of infrastructure changes lately.

`spi_write_then_read` is no longer supported and it is currently replaced by `spi_write_and_read'  function used by all out SPI based no-OS drivers.

Regards,

Antoniu

I see, then I'm using the old version of the driver. I haven't found where the function "spi_write_and_read" is written (declared in spi.h), could you please point it out ?

I'm asking because I would like to compare "spi_write_then_read (uses Xilinx core functions like XSpiPs_WriteReg) with "spi_write_and_read " before I change anything.

Thanks

Me_

Sure,

We use an intermediary SPI generic layer to access platform specific functions:

https://github.com/analogdevicesinc/no-OS/blob/master/drivers/spi/spi.c

Here is the SPI implementation for Xilinx:

https://github.com/analogdevicesinc/no-OS/blob/master/drivers/platform/xilinx/xilinx_spi.c

In your case, `xil_spi_write_and_read` is the implementation that you would want to check out.

Regards,

Antoniu

Hello Antoniu,

Could you please provide the initial values of the structure : adf5355_init_param ? Or one can use the default register values ?

Some of them are straightforward (ex.: dev_id, neg bleed, etc.)  but others not.

Thanks in advance

Hello @Me_,

The initialization structure might differ depending on the end application for which de the device is used.

Currently we don't have a concrete no-OS example of initialization structure. We intend to add one in the near future.

But you can have a look at following dts which contains initialization structure for the adf5355 linux driver:

github.com/.../zynq-zc706-adv7511-ad9361-fmcomms5-ext-lo-adf5355.dts

Most attributes are similar to the no-OS ones.

Regards,

Antoniu

Hello Antoniu,

Thank you for the reply. I forgot to press the reply button. That's correct, I managed to get it working according to my needs.

The No-OS driver seems to work but there is a little problem. The PLL is not delivering the exact frequency requested (there is an uncertenty of around 20 MHz) and for frequencies below 800 MHz, it simply doesn't output any frequency. I will further investigate when I have the time.

Thanks for your support.

Me