Grazing through the datasheets (my first time looking at them from an application POV) gave me an overview of what the ICs could be doing in Run's design.
NOTE: To mark/highlight the datasheet, mark out only those things which answer "What can be done" and not "How it can be done"- cause the later always follows the former and is always almost never going to be memorized.
Getting an overview of all the chips except the ADCs (since I havent really been with an ADC before), I think I should be diving into programming one chip just to get the hang of the USB FX3 interface.
Run's old is available to work on. He has suggested to try and program the DDS using the USB3.0 because one can directly pick out the output of the DDS without connecting the input signal.
He says there might be some error in the amplitude of the DDS output, but the frequency should manifest the functionality of the firmware interface.
NOTE: To mark/highlight the datasheet, mark out only those things which answer "What can be done" and not "How it can be done"- cause the later always follows the former and is always almost never going to be memorized.
Getting an overview of all the chips except the ADCs (since I havent really been with an ADC before), I think I should be diving into programming one chip just to get the hang of the USB FX3 interface.
Run's old is available to work on. He has suggested to try and program the DDS using the USB3.0 because one can directly pick out the output of the DDS without connecting the input signal.
He says there might be some error in the amplitude of the DDS output, but the frequency should manifest the functionality of the firmware interface.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.