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.

ADS54J66EVM: Synchronize two ADS54J66EVM

Part Number: ADS54J66EVM
Other Parts Discussed in Thread: ADC12J4000, ADS54J66, LMK04828

HI,

I have two ADS54J66EVM boards and two TSW14J56 boards. Can I synchronize ADS54J66s on two ADS54J66EVM boards?

I notice that in tidu851 the way of synchronziation of two ADCs(ADC12J4000) is described. But I still have some questions about that:

(1)  In tidu851, the chain of "trigger in" on board is TMST+(boardA)  ——>R18(boardA)——>SYNC_P(boardA)——>FPGA(master)——>SYNC_N(boardA)——>TMST-(boardA)——>TMST+(boardB)——>R18(boardB)——>SYNC_P(boardB)——>FPGA(slave)——>SYNC_N(boardB)——>TMST-(boardB,named as " Trigger out"). What is "trigger out" for on TMST- of board B?Why is it connected by a SMA cabel? It seems that someone will use this singal?  

(2) The "trigger in" is internally connected to FPGA by pin G12 of FMC, which is Net SYNCbABP on board ADS54J66EVM. So if I want to synchronize two ADS54J66s, should I cut the microstip line of net SYNCbABp and SYNCABm,then put coaxial pigtails on them? And then connect all of them as described on tidu851?  

(3) I think the firmware will be changed if I use synchronization_2x_demo.exe to synchronize two ADS54J66s instead of two ADC12J4000s. So do you have that firmware based on ADS54J66? If not , do you have other ideas about synchronizing two ADS54J66EVMs based on two TSW54J66EVMs?

Best Regards

                        

  • User,

    Yes, you can synchronize both boards. You will need to modify both ADC boards to allow you to use the OSC input on the LMK's so you an operate them in 1 loop 0-delay mode (see the LMK04828 data sheet for more info regarding this). For this, do the following:

    Install R60, R61, C92

    Remove R62, C169, JP2, C80

    Replace C82 with a 0 ohm resistor and R77 with a 0.1uF capacitor.

    Provide the required SYSREF frequency that is synchronized to J12 of both EVM's. Once the system is up and running, verify both LMK's are synchronized by monitoring R30 of both boards.

    To setup for triggering both boards, see section 3.1.3.3 of the HSDC Pro GUI User's Guide from the link below. You will have an option to either use a software trigger or hardware trigger.

    Regards,

    Jim

    txn.box.com/.../yggz55vq0ah0n8dlcrlbml1gveoeeuqj

    5165.ADS54J66_ADS58J63_ADS58J66-SCH_A.pdf

     

      

  • Hi, JIm

    I followed the procedure of the user's guide of HSDU and I have one question.

    With both enables selected, the capture button changes from "Capture" to "Generate Trigger" as  described at the guide.

    When ADS54J66_LMF_4421 is used as a config file in HSDC,click on the "Generate Tigger" button,  the signal at TRIG OUT A will be low-high-low,as shown in Figure1.

    Even if J13(TRIG IN) and J7(TRIG OUT A) was not connected by SMA cable, based on configuration  above, data was still captured. “No trigger occurred”was not reported,but it should be  reported.

    At section 3.1.3.3, it says that:

    “To use this rising edge to trigger the same TSW14xxx, the user must connect a cable from the  SMA labeled as“EXT_TRG_INPUT” SMA (J11) on the TSW1400 ("TRIG_IN", SMA J13 on the TSW14J5x)  

    to one of the SYNC (TRG_OUT) SMA's. Without this connection, the GUI will never detect a  trigger and will report “No trigger occurred” a short time after the user has clicked on the  "Generate Trigger" button.”

    Is it normal? If it isn't, what else should I do?

    When ADS54J66_LMF_4421_mode7 is used as a config file, the signal at TRIG OUT A will be low-high,as shown in Figure2 and later “No trigger occurred”will be reported. No data will be  

    captured while under normal condition(no trigger mode selected) data can be received.

    When configure different ini file, the signal at TRIG OUT A will be different?

    Best regards

  • Hi Jim

    I delete "Sysref Based Master Slave Trigger = 1" in ADS54J66_LMF_4421.ini. Then it behaves the same as mode 7 described above.

    But why it will report "No trigger occurred" since I alread connect J13 and J7 on the same TSW14J56 board? However the slave TSW14J56 already can capture data as the same as described on section 3.1.3.4.4 of HSDU user's guide.

    Best regards.

  • User,

    Do you plan on using the software trigger option or an external trigger? If you use the software trigger option, one TSW145J56 has to be setup in master mode and the other in slave mode. I suggest you start with internal trigger mode first and just use one setup and get this working. After this, add the second setup as a slave and get both setups to trigger. Then if you need to use an external trigger, go back to the master board and set it up in slave mode as well.

    All three SYNC outputs are the same signal and anyone can be used.

    Regards,

    Jim

  • User,

    Are you saying the trigger works with the comment removed from the ini file but not when it is present? is this just when using one setup?

    Regards,

    Jim 

  • User,

    The trigger function was never added to the firmware that is used by this ini file. We are looking into adding this feature.

    Regards,

    Jim