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.

TMDSCSK388: DM388 Part with manufacture defective

Part Number: TMDSCSK388
Other Parts Discussed in Thread: DM388

Hello,

I am working on a project and I have purchased the TMDSCSK388 and TMDSCSKCC as a bundle. I followed all of the directions to fully implement them.

The boards will not talk to a computer over ethernet or USB. We have tried 3 different computers with Putty and the other program listed in the manual and no luck. I believe the board has a manufacture defect. I received this response from Billy Owens at TI. "I apologize about the slight delay to this. It looks like this ticket got flagged as silicon quality issue by keyword and it was just reassigned out of that workload." He said to post on this forum to receive the help I need. Please let me know what you guys can do. I have a very strict development timeline for this product and I will have to go another route if it is not resolved as soon as possible! 

Order #: 1729444

  • Hi,

    Have you tried to run the demo that comes on the SD card?

    It is possible that the SD card is corrupted.

    The first step to debug your board is to create a new SD card. There are instructions provided in the User's Guide

    thank you
    Cesar
  • Hi Cesar,

    I looked at the SD card and it shows the files on a laptop so I do not believe it is corrupted. If its a new product why would the SD card be corrupted? Is the board tested before its shipped? Also, what is the "silicon issue" that Billy Owens mentioned?

    I have waited 5 days for a response on this. I need to return this and get my money back. If I order another one how do I make sure this will not happen again?

    Best,
    Matt
  • I understand,

    Do you see any debug logs?

    Any leds blinking?

    Thank you
    Cesar
  • I just wanted to chime in and explain that my first email to you was explaining that your ticket was flagged as a quality silicon issue, and went to that team’s workload before being reassigned to my team. I was not explaining that you had a silicon issue, just that the system flagged it as that initially. I’m sorry about that confusion.

    -Billy
  • I will debug the SD card before COB. I will let you know what the outcome is today.
  • Ok Billy. Sorry about that I did not know what you meant. Now I see.
  • Hi Cesar,

    There are LEDs blinking on the large main board. This was a week ago and I do not have the board in front of me but I will in the next 1-2 hours and I can tell you exactly what is going on. No LEDs on the Ethernet what so ever though. Only LEDs on the board main. What LEDs should I be looking for after the new SD card is made ?

    Best,
    Matt
  • Hello Cesar,

    We are working through the issues now. I think we are on to something but I will give you more details Monday morning.

    Best,
    Matt
  • Hello,

      Working with the DM388 board, the sd card has the files and I copied all the files and reformated and put them back. The issue is I can't build the files again which I believe to be the issue, this is due to the fact that while all guides mention the IPNC_RDK_3.9.1.tar.gz file there is no available download for these files. Currently the device will write to the serial terminal repeatedly every few minutes "CCCCC" which is indicative of attempting to boot from UART. Not sure what to do without being able to rebuild it from the binaries.

    Please advise.

    Thank you,

  • Hello,

    Working with the DM388 board, the sd card has the files and I copied all the files and reformated and put them back. The issue is I can’t build the files again which I believe to be the issue, this is due to the fact that while all guides mention the IPNC_RDK_3.9.1.tar.gz file there is no available download for these files. Currently the device will write to the serial terminal repeatedly every few minutes “CCCCC” which is indicative of attempting to boot from UART. Not sure what to do without being able to rebuild it from the binaries.

    Please advise.

    Thank you

  •  Using a new sd card but same files that were on the previous one has no provided this error which repeats constantly:

    U-Boot SPL 2016.05-00004-g63acf8c-dirty (Feb 13 2017 - 17:24:46)
    Trying to boot from MMC2

    After a few minutes it ended up trying to boot the kernel but reached a kernel panic

    PLEASE ADVISE

  • The tar.gz file is included in this installer. Please use a Linux PC to install it.

    www.ti.com/.../ipnc-rdk-csk

    Thank you
    Cesar
  • Updated fixed kernel panic, was a file copy issue. Now the issue is the board constantly boots running through available access points and repeatedly doing the same loading seen in the first screenshot. Was able to get to the linux prompt but unreliably it will crash by rebooting to the boot menu prompt. Issuing the boot command just reiterates through the boot loop, where occasionally you are able to boot into the linux prompt.

    Not sure what is causing this unreliable booting as no clear errors are being displayed. The usecase script floods the screen's output which may be partially the issue.

  • Hi,

    I would need some more information?

    Are you able to see the Camera input on the PC GUI?

    Thank you

    Cesar

  • What information? 

    No we are not? Are you talking about inside the command window? That's all we have to work with so far. That is the only way we can talk to the camera. 

  • Are you able to stream the demo on Web Browser as described in the User's Guide?

    Thank you

    Cesar

    http://processors.wiki.ti.com/index.php/IPNC_RDK_DM38x_,_DM8127#Streaming_Demo_on_Web_Browser.28IE.29

  • Hi Cesar,

    No we are not able to stream the demo. We deleted the usecase.sh file and that stopped the system from crashing. Now we need help with a new file that will allow us to use the camera but does not try to automatically start the system. Essentially, there is a file that is crashing the system that is uploaded on that usecase.sh file. We need to know what that is, so we can delete it and get this up and running. 

    The use case file provided that implements the UI, causes the device to reboot constantly. I can send you the entire putty log as well if you can provide me with an email address. The file is not able to be attached to this forum.  

    Thank you for your continued support, hopefully we can have an answer by EOB today! 

    Best,

    Matt