• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 239 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.

AM3359 / CCSv5 connect

Tom Smith
Expert 2930 points
Other Parts Discussed in Thread: AM3359

Customer issue;

I have a custom AM3359 based board in hand.
Presently, I can connect to the AM3359 via CCSv5, so the processor is running…but the microSD based application may not.
I’m following TIs AM335X board bring up guide and would like to verify the processor PC… (where the code is running).
Do I need a TI hardware debugger in conjunction with CCSv5 or can I get a disassembly window using just CCSv5?

-Tom-

  • 0
    TI__Expert 8275 points

    Hi Tom,

     

    If you are on a custom board and can verify that you have a host machine connected to the AM3359 by using the CCS software, then it sounds to me like there is a XDS100 in the picture. If that is the case then no, you would not need any additional hardware for the disassembly information that you are looking for. However, if you are simply recognizing the AM3359 is connected by the host OS, then that may be a different story.

     

    Can you confirm if, like our EVMs and beaglebone examples, there is an XDS100 on the custom board?

     

    -Colin

  • 0 in reply to Colin Callaghan
    Expert 2930 points

    Colin,

    Customer response;

    I do not have a physical XDS100v2 debugger installed, but I do support a 20P header for one.
    CCSv5 is configured for an XDS100v2.


    Apparently, I need a JTAG debugger to get a disassembly window using CCSv5. Is a TDMSEMU100V2U-20T JTAG debugger adequate for an AM3359?


    Presently, I am connecting to the AM3359 JTAG using CCSv5 via a 2 Port Ethernet Hub and an FT2232H path.
    I’m confident I have a JTAG connection because of the work I had to do to configure the FT2232H SEEPROM to get the test connection to pass.
    The Hub->FD2232/AM3359 path seems only partially functional, due to observing the Port_#0002.Hub_#0004 Generic USB Hub power tab. The driver is happy, but it lists a USB composite at 500mA, per SEEPROM data and an unknown device, not an unknown USB device as I might expect. In addition, a Windows device manager message “unknown device at Port_#0002.Hub_#0009” also shows up in the list which isn’t normal.


    I’m starting to think I have a problem with my path from the hub to the AM3359. Supposedly it has passed the TDR testing for a 90 Ohm diff path, but it is longer than the one to the FT2232H. Maybe it is just the AM3359 is not running properly yet. I’ll bet the AM3359 needs to be running in order to be recognized as at least an “unknown USB device”.


    Maybe I have a problem with half of the USB2412 hub? If half is working, I would think the other half would also.
    Since it apparently shows up as an unknown device instead of an unknown USB device,


    is there any chance I’m still having a Windows driver/vender ID/SN USB config issue concerning the AM3359 USB0 port?

    -Tom-

  • 0 in reply to Tom Smith
    TI__Genius 13045 points

    Tom,

    You need an emulator (stand alone or embedded) connected to JTAG port on target device to perform assembly language debug (Disassembly Window).  Here is overview of the interface: http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide.  If customer has emulator connected and is still having problems here is debug guide: http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems.

    Regards.