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.

AFE5832: MED1426

Part Number: AFE5832
Other Parts Discussed in Thread: TIDA-010057

We finally have our own SWAROOP board in hand (took a while to get the components !), as well as the TIDA-010057 power supply (MED1427).
However I am having trouble performing the tests described in the SWAROOP user guide.

1) We checked all the power rails: very nice and clean (with 5V on the Green-Power J1-39 pin).
2) We check the SF3 and programed it with the supplied example code (swaroop_v0.1.img).... we programed via RAM as R21 is in, preventing EEPROM reload)
3) We programed the JTAG (FPGA) EEPROM via Vivado with "Swaroop_june.bit" successfully
4) We run HSDC, and select the board.,
5) We select the ADC (AFE5832LPTX), and it launches the AFE5832LPTX 3LVL EVM software.
6) We press "DUT HW Reset", "Initialize Device" and "FPGA reset", and the scripts appear to load.
7) We set the TX channels to 32, and RX channels to 32

But with Trigger Capture both "on" or "off", we cannot get a sync pulse on TP1 (which we should according to the "manual").

What have we missed?
Am I supposed to "Download firmware" in the HSDC software?
Also It appears to write to the FPGA, but when reading it appears non-responsive.
Possibly I am just missing a setting somewhere......

Is there another testing manual I have missed?
How long does the Register Map Configuration take to be read (in full) normally?

  • Hi Philippe,

    Thanks for reaching out.

    Firstly could you clarify are you using TIDA-010057 or MED1427 board (both of them are different boards). TIDA-010057 is switching supply which generates required rails from USB. MED 1427 LDO based board which needs external power supplies.

    Looking at your observations, I don't see any clear indication what is being missed. Let me check with my team members on this and I will get back to you soon.

    Thanks & regards,
    Abhishek

  • Ouch.... not the MED1427....sorry, I meant the MED1426 (SWAROOP board)
    We are using the TIDA-010057 to power the MED1426 board..... (sorry I stated the MED1427, which is an alternative supply for the MED1426)
    The power supply board works very well (all power rails are perfect).... with the interesting exception being that a Lenovo PC made the HV components overheat due to insufficient current supply (i.e. the Lenovo appears to throttle the USB power to 250mA.... as do a few other PC's in conflict to the USB specification).
    We were surprised by the overheating, which also pulled the 5V rail down to 4V, but did not trip the USB port.... thus took a while to debug.
    This power test was without the MED1427 board attached. So the power supply appears to be quite power hungry, which was in conflict to the current consumption measurements performed by TI.

  • Hi Philippe,

    Thanks for the clarification.

    I see you are discussing this issue with Shabbir on our internal group. Lets continue there only, and we can further discuss on to resolve your issue. 

    I am also not sure what is missing, your settings and observations are looking okay to me. Not sure why the capture isn't happening. 

    Regarding power consumption, something must be consuming more current than anticipated. Do you know what is overheating?

    While testing the board, since there are so many different components which are not really essential (such as INAs for measurement, clocks for sync etc) which may be damaged and takes huge amount of current. So to isolate them, I used to take a thermal image of the board to identify if any unnecessary device is getting overheated and just remove them.

    Also, the HV circuit take large amount of current while start up. May be you can try doing the tests without HV in the picture. See if anything changes.  You can remove the 0 ohm supplying 5V input to the HV circuit. I think it is R54.

    I am closing this thread and we can continue on mail.

    Thanks & regards,

    Abhishek