AnsweredAssumed Answered

FMCOMMS5-EZB remove GPIO_BD from reference design

Question asked by Quamstar on Jan 21, 2017
Latest reply on Jan 25, 2017 by CsomI

Hi,

 

i do have a similar question to this topic (https://ez.analog.com/message/263674). I want to use some of the gpio_bd ports for my User IP outputs (FMCOMMS5 references design). I want those outputs connected to a PMOD header of the ZC702. 

 

Only updating the constraints file would runs into a failure, so as you guys mentioned, i need to modify the system_top.v file. But, what happens when i change the width of the gpios and remove all, or some of the 16 gipo_bd? Does change this has any effect to functionality of the other IOs. Does the address for alle gpios changes? What about the linux drivers, do i have to modify them too?

 

This is a part of the system_top.v which needs to be modified in my eyes, right?

 

ad_iobuf #(.DATA_WIDTH(60)) i_iobuf (
.dio_t (gpio_t[59:0]),
.dio_i (gpio_o[59:0]),
.dio_o (gpio_i[59:0]),
.dio_p ({ gpio_resetb_1, // 59
gpio_ad5355_lock, // 58
gpio_ad5355_rfen, // 57
gpio_calsw_4_1, // 56
gpio_calsw_3_1, // 55
gpio_calsw_2_0, // 54
gpio_calsw_1_0, // 53
gpio_txnrx_1, // 52
gpio_enable_1, // 51
gpio_en_agc_1, // 50
gpio_txnrx_0, // 49
gpio_enable_0, // 48
gpio_en_agc_0, // 47
gpio_resetb_0, // 46
gpio_open_45_45, // 45
gpio_open_44_44, // 44
gpio_debug_4_1, // 43
gpio_debug_3_1, // 42
gpio_debug_2_0, // 41
gpio_debug_1_0, // 40
gpio_ctl_1, // 36
gpio_ctl_0, // 32
gpio_status_1, // 24
gpio_status_0, // 16
gpio_bd})); // 0

 

Thanks for your support

Jan

Outcomes