This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Takahashi,
What are you attempting to change? What changes did you make? If the frame clock is OK, HSDC Pro will do a valid capture. If there is a problem with the frame clock, you will get the message you are receiving. There are currently six ini options available in HSDC Pro. What is your reason for attempting to create a seventh version? Please send your ini file if you made other changes than the one mentioned in your post and we will take a look at it.
Regards,
Jim
Takahashi,
Here is some more info that I hope helps you with your issue:
Regards,
Jim
Make sure the mode (Bytewise/Wordwise, 14b/16b/18b) set in the device GUI matches with the INI file selected in HSDC pro. Some information about Frame clock implementation of firmware is below. Frame clock signal is used to detect the start of a valid sample. Rising edge of Frame clock is considered as the start of a sample. check_fclk has to be set to 1 in INI file if the device has Frame clock.
When Capture button is pressed in HSDC Pro, frame_clk_en signal (Config_7[3:3] register in dumpmem_config module) would be set to high from HSDC Pro. Firmware would then keep sending the data of frame clock, sampled with clk_adc. Please refer pack_data module to know the format of frame clock data (din0_frm, buffer_frm) that is sent to HSDC Pro. HSDC pro would try to match the Frame clock data with Frame clock codes defined for the selected mode of the device (These codes are generated in HSDC pro based on the output format of ADC). If the codes does not match, HSDC pro will keep adjusting the bitslip of deserializers (Through config[4], config[5] registers in dumpmem_config module ) till the frame clock codes are matched. Once the frame clock codes are matched, frame_clk_en would be reset and then firmware would send actual ADC codes. If Frame clock codes are not matched even after bitslip adjustments HSDC pro throws the error "Frame clock error in Read DDR to file". Frame clock mapping Index and Channel Mapping Indexes of INI file are sent to firmware through configuration registers (frame_clk and Channel1-Channel32 in dumpmem_config module). These are used in channel_select_n_reorder module to reorder the data from deserializers based on what pins of Samtec connecter are connected to selected device. See the attachement for more info. Firmware_DLL_Design_Document0.3.docx
Takahashi,
Here is more info from our contractor regarding your issue:
He is using ADS5263, 2W_16b mode. The firmware you had sent seems to be ADC_SAMPLE_WISE.
We have a format specific firmware which supports 2W_12b, 2W_14b and 2W_16B for ADS5294. we could possibly share this firmware (//HPA/MHR/Projects/TSW1400/TSW1400_ADC_FPGA_code/FPGA Firmware/V1.11/Firmware Archive/TSW1400_ADC_ver1.11.qar) and guide him on what changes he has to make for 2W_16b of ADS5293. The changes would be in defines.vh, adcif.v.
Following are the changes needed
1. In defines.vh,
a. Comment "`define BITWISE_DDR_1W_12B" and uncomment "`define BITWISE_DDR_1W_14B". Implementation for BITWISE_DDR_1W_14B and BITWISE_DDR_1W_16B are same in adcif_formatdata.
b. Assign ADC_BM0 to ADS5263_BM0 and define ADS5263_BM0.
c. Define INTERFACE_ID as 33
2. In adcif.v,
Add a case for ADS5263_BM0 and assign pin numbers correctly for ADS5263 in order.
3. In TSW1400_IID_Lookup.csv present under HSDC Pro/1400 Details
Add a new row for Interface ID, 33 - ADS5263_2W_16B
Use the atttached updtaed INI which also has support for format specific firmware. DLL_version parameter is removed in INI sothat parameters under [ADC] section would be active.
Regards,
Jimhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/73/ADS5263_5F00_2W_5F00_16b_5F00_bytewise.iniTSW1400_ADC_ver1.11.zip
Takahasgi,
Those Time quest analyser warnings can be ignored. Firmware would still work with those.
"I couldn't get a good result with this." from the post; Does the mean you are still getting Frame clock error?
Regards,
Jim
Takahashi,
Are you still having issues with your design? Most of our firmware is done by a contractor. This is one reason why I cannot always help out customers with their issues. If you still have an issue, I can pass it on but it may take awhile before we get a response back. Try contacting an Altera rep and see if they can extend your trial period. They also have a very good support center that may be able to help with any issue's you stil may have.
Regards,
Jim