Post Go back to editing

NO_OS Example for CN0585 using AD3552r driver

Category: Software
Product Number: CN0585

I'm having an issue using the no_os AD3552r example for the CN0585 design since there is no no_os project for CN0585. I get an error that the AD3552r is failing the scratch pad test. I ported the AD3552r_fmcz project for the CN0585 by updating the following base addresses and copying the CN0585 HDL xsa file into the project. Note this is just for the first AD3552r of the two for now. Any idea why my implementation wouldn't be talking to the AD3552r?

#define TX_CORE_BASEADDR XPAR_AXI_AD35XXR_0_BASEADDR
#define TX_DMA_BASEADDR XPAR_AXI_DAC_0_DMA_BASEADDR
#define TX_CLKGEN_BASEADDR XPAR_AXI_CLKGEN_BASEADDR

I'm also unsure how the GPIO bank indexes in the no_os driver relate to the zync pin numbers so I can update the reset and LDAC GPIO offsets accordingly. 

Parents
  • Regarding your last question, Zynq has 54 MIO pins so when working with EMIO pins you have to add the 54 offset. Same with ZynqMP, but it's a 78 offset. So you take whavever EMIO number from your HDL and add the offset to it, the resulting number being the pin number that you configure in the no_os_gpio_init_param structure.

Reply
  • Regarding your last question, Zynq has 54 MIO pins so when working with EMIO pins you have to add the 54 offset. Same with ZynqMP, but it's a 78 offset. So you take whavever EMIO number from your HDL and add the offset to it, the resulting number being the pin number that you configure in the no_os_gpio_init_param structure.

Children