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.

CCS/TMDSEMU110-U: Problems with AM4377

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: AM4377, TMDSIDK437X, AM4379

Tool/software: Code Composer Studio

Hello,

I am having problems getting the xds110 to work correctly with the AM4377. The jtag scan complete with no failures or skips, however when I try using the XDS110 to flash the program onto the board the chip seems to come up badly. Output from the uart shows that the program is getting loaded however parts of the chip dont seem to respond. The internal EEPROM often shows unreadable. Often when this happens the board will partially reset and try booting from sd card or lock up. Debugging has had its own issues as well, please see the mention of that below.

I have asked a previous question (here) about debugging on the AM4377 with the xds110 and I believe they might be related. Unfortunately a bug ticket was made but then closed without a fix.

I have Tried this same thing with a spectrum digital xds200 and had no issues with the exact same target configuration. Is there some other board start up configuration that might be causing me an issue?  





Versions:
CCS - 10.1
TI Emulators - 9.2

  • Hello Hayden,

    I looked at the details of that bug ID in the other thread you referenced. It was closed because the engineers could not reproduce the issue with newer silicon revision. What revision are you using? What is exactly printed/stamped on the package? For example, I can reproduce the issue on my AM437x IDK. The packaging has: XAM437XAZDN

    Thanks

    ki

  • I have tested this with two different boards with 2 different  AM437x chips. Both have had the same behavior for me. 1 is a custom board and the other is a dev board from TI , the TMDSIDK437X . 


    Custom board: AM4377BZDND100

    TMDSIDK437X: AM4379BZDNA100

    I believe this means both chips are using silicon rev 1.2 .

    -Hayden

  • Thanks. I know that the engineers tried to reproduce with an AM4379 silicon rev 1.4a and were not able to reproduce. 

    I will investigate to see if the silicon revision is the issue.

    ki

  • I have reopened this bug with the engineers. We hope to be able to find a workaround for affected versions. I will keep you posted of any progress

  • Just a quick update, this is still under investigation. Interestingly, I was not able to reproduce the issue on a Windows 7 PC. But I can reproduce it on Windows 10 and on my Ubuntu 18.04 laptop.

  • I tested both boards on a ubuntu 20.04 laptop and found the same issue as well. I do not have any machines with windows 7 on them, so unfortunately I was not able to duplicate those results.