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.

TIDM-TM4C129POEAUDIO: Down during operation

Part Number: TIDM-TM4C129POEAUDIO
Other Parts Discussed in Thread: TIDM-TM4C129POE

Hello?
I have three TIDM-TM4C129POE modules.
I am testing by connecting an audio output(eg mp3) to the input of each module
and connecting an amplifier to each output.
The connection (CALL-RECEIVE) works well.
However, after operating normally for several seconds, several minutes,
or several hours, one module stops (system down).
Only one module is stopped. Stopped modules do nothing.
No audio output, no LED blinking, no touch screen input, etc. all do not work.

Version of program and source file in use:
TivaWare_C_Series-2.2.0.295
CCS version 6/9/10
opus version 1.1.2 / 1.1.5 / 1.2.1 / 1.3.1

Even if all CCS versions and all opus versions are combined and compiled, the result is the same.
The same goes for testing by changing modules.
It is being used without modifying the contents of the source file.

I don't know what the problem is.

  • Hi,

    sh l said:
    However, after operating normally for several seconds, several minutes,
    or several hours, one module stops (system down).
    Only one module is stopped. Stopped modules do nothing.
    No audio output, no LED blinking, no touch screen input, etc. all do not work.

    I have never worked with this reference design. It may take a while to understand what is going on. 

    - Is is true only one specific module not working, but the other two are always working. Suppose we name them module A, B and C. Is it always the module C?. What I want to know if it is sometime module A or sometime module B that stops working.

    - Suppose module C will always stop after a while. Can you confirm if the problem can be repeated if the other two modules (A and B) are never used and connected?

     - On the problem module, can you find out what is going on using the debugger? Is the processor getting a fault? If the board seems dead, then it is possible that the processor is trapped in some type of fault. 

      - Can you run another program such as enet_io example and does it also stop after a while? I'm just curious if the problem is hardware related as you said the other two identical boards running the same application all seem to run fine.