• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 409 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Help? TI816x EVM completely stuck

Michael Dean
Prodigy 50 points
Other Parts Discussed in Thread: AM1808

Hello,    I didn't think it was possible for things to get any worse from yesterday, but they have...

I have a TI816x/389x EVM rev D (with DIMM) board.   It came with a XDS100v2.   

1) In the process of trying to build and program a u-boot (nand) for DDR2 the board will not do anything now.   Won't even boot the original CF card supplied.   Nothing prints to the console at all.   Jumpers look correct.    What could have happened where nothing will boot/print.   Can it be recovered?

2) Can't connect to target with the emulator anymore (could yesterday)  IcePick_D_0: Error connecting to the target: (Error -180) @ 0 (0x0)   What does this error mean?

3) The CF card has a CCS5 version on it that does not seem to have support for the TI816x (board that it was shipped with).   What CCS version should I use?  The only version that seems to have support for the Ti816x/xds100v2 is 5.0.1.201105110900.  All doc show the use of the xds560 emulator with this board.   Is what we were sent even a valid configuration?   Been tested?  

4) I have 2 different ezsdk versions.     ezsdk_c6a816x and ezsdk_dm816x.    Which one should I be using?    The C6a816x seems to not have the DDR3/2 issues, but does not include the host_tools dir.

5) When I could connect to the board, i could not read the the device ID of the Nand chip correctly. 

Any help would be greatly appreciated.

Thanks,  Michael

  • 0
    Intellectual 450 points

    Hi Michael,

    I know this is not much consolation for your situation...but I too just ran into this error. In my case I am using the Blackhawk USB100v2 emulator with a TI AM1808 processor.  The processor sits on a custom board which currently has nothing yet installed.  I also have this problem on a 2nd custom board where u-boot was already flashed.  I switched to the brand-new board to see if there was a hardware glitch and the new board is reacting the same way.  So ... I need the emulator to connect in order to load u-boot into NAND. Anyhow...This was working for me...and then it stopped working yesterday late afternoon.  I am trying to retrace changes that may have caused the emulator to stop connecting. I did come across  this interesting thread that I am currently evaluating as at times I was also receiving this error  IcePick_C_0: Error connecting to the target:  Cannot access register at 0x00000000

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/67844.aspx 

    Update...even before I got a chance to hit the post - it appears my problem has been solved. We were able to have our hardware guys install a wire lead to the processor reset (I am a software guy..so magically this happened). We then attempted to reset the processor while it was still powered on and now my emulator is able to connect again.  I am not sure what state it got itself in or why a hard power down on power on did not resolve the issue ..but it certainly appears the core was stuck somehow.  Perhaps you have a similar situation?

    Good luck.

  • 0 in reply to Dan Tesone
    Intellectual 450 points

    Hi Michael,

    Just an update here. Although the processor reset I mentioned above worked on one of my boards..I have 2 other custom made boards that cause the same error you mentioned where the same "fix" does not seem to apply.  This is alluding to a manufacturing issue on these 2 boards (which we need to figure out). Just wanted to let you know that hardware failure may actually be a (the) cause.

  • 0 in reply to Dan Tesone
    Prodigy 50 points

    Hi Dan,

    Thanks for the replies.    I finally gave up on the problem being a software issue and started looking at the board a little.   After a little probing with a volt meter, it seems like the power supply on the board is dead.   None of the 3.3 or CPU voltage rails are correct and the area of the board containing the power supply gets pretty hot.   Our only choice was to send the board back to be fixed.   Hopefully we won't be without it for more than a week.  Fingers crossed.

    Thanks,  Michael