Hello,
maxv_ufm maxv_ufm_block1 ( .arclk(1'b0), .ardin(1'b0), .arshft(1'b0), .bgpbusy(), .busy(), .drclk(1'b0), .drdout(), .drshft(1'b0), .osc(wire_maxv_ufm_block1_osc), .oscena(oscena) `ifdef FORMAL_VERIFICATION `else // synopsys translate_off `endif , .drdin(1'b0), .erase(1'b0), .program(1'b0) `ifdef FORMAL_VERIFICATION `else // synopsys translate_on `endif // synopsys translate_off , .ctrl_bgpbusy(), .devclrn(), .devpor(), .sbdin(), .sbdout() // synopsys translate_on ); defparam maxv_ufm_block1.address_width = 9, maxv_ufm_block1.osc_sim_setting = 500000, maxv_ufm_block1.lpm_type = "maxv_ufm"; This was taken from AN494 oscillator example. For parameter "osc_sim_setting", I cannot find exact definition except for a similarly spelled "OSC_FREQUENCY", which says Specifies the oscillator frequency for the user flash memory. Values are 180000 ps (5.56 MHz) or 300000 ps (3.33 MHz). If omitted, the default is 180000 ps. The OSC_FREQUENCY setting controls the oscillator frequency during simulations and does not affect the device’s oscillator frequency, which can range from 3.33 MHz (300000 ps) to 5.56 MHz (180000 ps). which is for simulation only. 1. Could you point to the exact definition of parameter? 2. The oscillator frequency is a fixed intrinsic electrical property. Please confirm that non of (osc_sim_setting/ OSC_FREQUENCY) could change that. greg链接已复制
0 回复数
