• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 1343 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.

TMS320F28335: error SC_ERR_POD_OPEN<-151> on using XDS100 emulator with CCS 3.3 v

Shailendra kumar Gupta
Prodigy 80 points

Part Number: TMS320F28335

The experimental kit was working fine till few days before and then the error "SC_ERR_POD_OPEN<-151> " started popping up each time I try to connect the board. I also tried the same with CCS 5.1and same XDS100 emulator though in vain .It looks to me a hardware problem, as sometime on shaking the cable the board gets powered and I keep it in a particular position to make it work but now nothing is happening. How could the problem be solved? I do not want to purchase a new kit due to hardware issue.

  • 0
    TI__Mastermind 45606 points

    Hi Shailendra,

    I would first check that XDS100v1 Probe is chosen in your target configurations along with TMS320F28335 for the "Board or Device" and then click "Test Connection" to see if it succeeds.

    If that doesn't fix the issue, it may be that the emulator chip needs to be reprogrammed. Please follow the instructions in the following forum post on how to do this:

    e2e.ti.com/.../21086

    Hope this helps,
    Kevin

    Edit: It would also be good to check the FTDI chip's 5V pin with a voltmeter, the connector might be worn down and need to be desoldered and replaced.

    Here is the datasheet for pins: http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT2232D.pdf

  • 0 in reply to Kevin Allen18
    Prodigy 80 points
    Thank you Kevin for your reply. Though I tried to reprogram the emulator chip using mprog application but I cannot discover the FT2232D chip through the application. I then tried on a f2812 board that I already had. I used a usb to JTAG emulator enabled with FT2232H chip. This time I could detect the device using mprog app and thus, reprogrammed it. Still I am not able to connect the f2812 board. This time the error is "Error connecting to the target: Error 0x80000200/-1135 Fatal Error during: OCS, Unrecoverable emulation error".
    And yes I checked the voltage across Vcc on both chip. The voltage are as below
    Processor Chip voltage
    f28335 FT2232D 1.3 V
    f2812 FT2232H 3.3 V
    Kindly reply.
  • 0 in reply to Shailendra kumar Gupta
    TI__Mastermind 45606 points
    Hi Shailendra,

    Please double check that you have the correct target configuration that matches your device selected and properly configured. Also, make sure the switches on the ControlCard are in the correct positions.

    Look at points 1 and 3 within the following guide for how to check both of these things:

    www.ti.com/.../sprufr5f.pdf

    From the FT2232D Datasheet it looks like VCC should be +4.35V to +5.25V. Check to make sure this is correct and that nothing appears disconnected if the first two suggestions don't work.

    Best,
    Kevin
  • 0 in reply to Kevin Allen18
    Prodigy 80 points
    Hello Kevin, as you suggested I rechecked the connection and switch and found it to be fine. Also I rechecked the Vcc pin to ground voltage and it is same as to be 1.3 V for FT2232D and 1.7 V for FT2232HL IC. What could be the problem. Again to me it seems to be hardware problem.
  • 0 in reply to Shailendra kumar Gupta
    TI__Mastermind 45606 points

    Hi Shailendra,

    How are you powering the board and connecting to the JTAG? Are both of these things occurring through a USB port, and if so, have you tried using a different cable?

    The following forum poster was having the same issue and the suggested solutions may help you:

    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    The error you are receiving is related to the Emulator, but does not seem to point to one specific solution. It could be related to emulation pins not being completely connected to the board, as suggested by a previous solution.

    Best,

    Kevin