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.

AWR1642: Hardware trigger is working on Rev. A, but is not on Rev. B with same setup

Part Number: AWR1642

Hello everyone, 

I'm using the AWR1642BOOST Rev. A and Rev B in combination with the DCA1000. The software trigger works fine on bothe revisions. Now, I basically want to use the hardware trigger to obtain the data, which once worked for both revisions. Of course I exactly use the same setup.

Right now, just Rev. A is delivering data from the hardware trigger. I flashed the "xwr16xx_mmw_demo.bin" from mmWave SDK version 2 to the Rev. B as descripted in the corresponding user guide, which makes the mmWave Demo Visualizer work, but the hardware trigger does not work. On the other hand I never flashed anything to the Rev. A, which probably makes the hardware trigger work.Surprisingly the Demo Visualizer does not work here. Unfortunately I do not know, which binary is flashed to Rev. A. Could you tell me which binary should be flashed to use the hardware trigger? Maybe even that is a totally wrong reasoning, but it's the only change I remember. What else could cause this behavior? 

Best regards

Max