• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 2391 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Error "sys_reset failed" using PurePath Wireless Commander

Torje Nikolai Thorsen
Intellectual 520 points

Hi,

I am trying to run some RF tests using the Wireless Commander.

When I try any of the default example tests included in the config folder I get an error message saying "sys_reset failed".

I manage to define the tester, load the tester firmware to the tester board and load the test and application firmware to the DUT boards. It is only the RF test stages in the test routine that fail. Furthermore, when I try to get chip or device info in the Device Manager i also get an error message telling there is a communication failure. Please see the attached screenshots below.

Does anybody have an idea why this happens?

Best regards,
Torje

  • 0
    Intellectual 520 points
    Hi again,

    Can anybody at TI please have a look at this?

    Best regards,
    Torje
  • 0 in reply to Torje Nikolai Thorsen
    Intellectual 520 points
    Dear TI,

    Could you please have look at my question or forward me to someone who can answer this?

    I have batch of PPW boards with bad performance, and I need this tool to find the root cause of my problem. I am running out of time .

    Best regards,
    Torje
  • 0
    Prodigy 110 points
    I have been having the same problem and i am truly lost especially whn it is crucial for us to check the RF tests
  • 0 in reply to Segala Yohann
    TI__Expert 3240 points
    Hi,

    Some quetsions:
    Are you using your own hardware or one of the DKs?
    Have you built you own production test image for your specific configuration?
    Can you program the device correctly with an application and connect to a network etc?

    Regards,
    Johan
  • 0 in reply to Johan Gustafsson
    Intellectual 520 points

    Hello Johan,

    Thanks a lot for your response.

    I am only using hardware from the development kit. I am using the default configurations contained in the "config" folder, and the associated test images.

    Both PurePath boards are working perfectly when programmed using the PurePath Wireless Configurator. It is only when I try to run the tests in PurePath Wireless Commander that I get this unexpected behavior.

    Regards,
    Torje

  • 0 in reply to Torje Nikolai Thorsen
    TI__Expert 3240 points
    Hi Torje,

    I have tried to forceing this behavior using my hardware but I have not been able to do so.
    Can you run the SYS_RESET() command from the "Command and Monitoring" panel successfully?

    Regards,
    Johan
  • 0 in reply to Johan Gustafsson
    Intellectual 520 points
    Hi Johann,

    First, concerning your question: I'm not sure if I can run the SYS_RESET() command successfully from the "Command and Monitoring" panel. I don't get any error message when typing it and clicking run. But I don't know if the command is executed, because nothing happens. For the record, I can also type any other, random word, for example DALAHEST(), and I get exactly the same behavior: nothing happens and I get no error message. So I really don't know...

    But I have some new information. The tests actually worked fine for a good while this morning. The problem seems to be intermittent. Sometimes it works, sometimes not. The symptoms are often different. Sometimes one of the debuggers are marked as "not available", sometimes it seems to be available but does not respond (blink) to the "identify" function, sometimes the "get device ID" function does not work, and sometimes it does. When I first posted my question I did not manage to run the tests at all, but today it sometimes works.

    Do you think the problem could be USB/PC or debugger related? I run the latest version of the PurePath Wireless Commander software (version 1.0.0 - Build ID 36940). There has been only one release of this software, hasn't it? I'm running it on a Windows XP SP3 computer.

    Thank you for your help.

    Regards,
    Torje
  • 0 in reply to Torje Nikolai Thorsen
    TI__Expert 3240 points
    Hi,

    Yes, now it really sounds like a HW issue. Very hard to say where to find the root cause. The version of commander you have is the latest one.

    To test the sys_reset() command, you can e.g. have a link up and running. Then its easy to see if the device resets.
    DALAHEST() should give you the response "Script execution failed ..." in commander.

    Regards,
    Johan