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.

LAUNCHXL2-RM57L: Connection Problem

Part Number: LAUNCHXL2-RM57L
Other Parts Discussed in Thread: RM57L843, HALCOGEN, TPS2553

Hello everybody,

I have been doing my project on Launchpad RM57L843. I have followed the following steps to perform UART operation and send ADC values through USB jumpers:

  1. Program the Launchpad according to the example given in Halcogen for ADC.
  2. Applied the signals to the relevant pins defined in Halcogen.
  3. After one minute, red LED of current limiting turns on and after ten seconds of that LED glowing everything turned off and died

After debugging, I came to find out that even on disconnecting C2 from OSCOUT and KELVIN_GND both pins are still shorted, and 3.3V and GND are also shorted.

Can anyone please help me?

Please respond as soon as possible.

Regards,

  • Hi Ali Zain,
    Any component that is powered by +3V3 power supply could cause short circuit between +3V3 and GND. LED9 is ON when TPS2553 nFAULT pin is asserted (during overcurrent, overtemperature, or reverse-voltage conditions).
    The only way to understand what is damaged is to isolate different groups that is powerd by +3V3 and observe when short circuit will be solved. Please, start with ICs. Passives are not often causing short circuit.
    Any suggestion from somebody will be a hit as the board is not in his hands.

    Best regards,
    Miro
  • I have the board in my hands, but I am not able to debug it.

    You, yourself, said to make another post and now you are saying that the board is not in my hands?

    What is your problem?
  • Hi Ali Zain,
    I think there is some misunderstanding. Sorry for that.
    I never proposed to you opening a new thread.
    Also what I am saying in previous post was: .."Any suggestion from somebody will be a hit as the board is not in his hands.".. What I meant is that the only one who can examine the board is you, because the board is in your hands and any suggestion from somebody else will be a hit. Also I proposed to you a way how to proceed with board examination (both here and in the other thread).
    I hope all misunderstandings are cleared!

    Best regards,
    Miro
  • You said that "the board is not in his hands".
    Whose hands?

    Oh well, forget it.
    Anyways thanks for the help and clearing the misunderstanding.

    Regards,
  • You said :"You can create a new post with a step by step description of what you have done and what you have observed."
    So I did.
  • Hello Ali Zain,
    Please take a look at your previous thread: e2e.ti.com/.../731788

    Community member Tomasz Kocon was the one who said: .."You can create a new post with a step by step description of what you have done and what you have observed."..

    Best regards,
    Miro
  • Hello Ali,

    I did my best to help you.
    However, as I have expressed, I have never were a h/w guy.
    When you came with your issue we have seen seen your LP with all possible connectors already soldered on.
    Did you tried some examples, tests before soldering?

    I am asking about this because we are dealing with ESD sensitive devices.
    I would remember forever that case:
    30-60 minutes before a storm, open window and no ionizer working around my desk.
    I have damaged 20 from 80 prototype devices.

    In my opinion, the best option for you is to buy a new LP and to start with some testing before soldering.
  • It is alright.

    Thanks for your help.

    Regards,

  • Sorry for the misunderstanding and thanks for all the help.
    I am going to disconnect one terminal of all the components connected between 3.3V and GND to debug this board.
    I cannot think of any other way of correcting this problem.

    Regards,

  • Hi Ali Zain,
    Sorry, there is no precise answer for such problems. Just start with ICs and regulators.

    Best regards,
    Miro

  • Its ok.
    I will try my best to identify the faulty component and replace it.

    Thanks for your help.
    Regards,