• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 85 subscribers
  • Views 1241 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.

CCS/TMS320F280049: Target Configuration File: Explanation of Target scan format OSCANx?

StephanS
Genius 4087 points
Part Number: TMS320F280049


Tool/software: Code Composer Studio

Hi,

I cannot find an explanation regarding the Target scan format in the Target Configuration File when using cJTAG.

What do the different OSCANx values mean?

Background: Sometimes, the cJTAG connection to our own board is instable. We have reduced the JTAG TCLK frequency, but would like to get an optimal configuration (stable, but as fast as possible).

  • 0
    Genius 4087 points

    The instable connection is reset after 1..10 min runtime with the error

    C28xx_CPU1: JTAG Communication Error: (Error -1135 @ 0x86A3C) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002)

  • 0 in reply to StephanS
    TI__Genius 15385 points

    Hi Stephan - Let me get back to you on this issue by end of this week, need to talk to experts.

    Best Regards,

    Nirav

  • 0 in reply to Nirav Ginwala
    TI__Guru**** 472081 points

    Hi Stephan,

    I don't know much about it myself, hence I contacted engineering for more details. Below is their response:

    OSCAN# are defined capabilities. So you could refer to that spec for additional details. The high level summary is that OSCAN is an advanced scan format that enables different levels of optimization.  OSCAN0 and OSCAN1 are mandatory (as is MSCAN), all others (OSCAN2-5) are optional.  For those listed as “Adaptive”, RTCK (return clock) is sent back—this is generally only required in special cases (e.g. for devices that have an ARM9 core).   I would generally recommend using MSCAN or OSCAN1. 


    Hope this helps

    ki

  • 0 in reply to Ki
    Genius 4087 points

    Hi Ki,

    thanks for the info.

    What do the different OSCAN settings mean regarding robustness and speed?
    Are they target or debugger capabilities?

    For 280049 and XDS110, I only get OSCAN1+2, OSCAN2 as default (when switching to 2-Pin cJTAG) - not the recommended OSCAN1. The "mandatory" MSCAN is not even offered as setting.

    For 280049 and XDS200, I get MSCAN and OSCAN0..5, OSCAN0 as default - not the recommended OSCAN1.

    Regards,
    Stephan



  • 0 in reply to StephanS
    TI__Guru**** 472081 points

    Stephan,

    I found this summary:

    MSCAN format - do it all, don't optimise
    OSCAN0 format - is adaptive, no escapes
    OSCAN1 format - non adaptive, no escapes
    OSCAN2 format - fast non-scan, no escapes
    OSCAN4 format - is adaptive, fast scan
    OSCAN5 format - non adaptive, fast scan

    The availability of the OScan formats vary per target and JTAG debug probe. 

    For more details on the Optimized Scan (OScan) formats, please refer to IEEE 1149.7 level T4 specification.

  • 0 in reply to Ki
    Genius 4087 points

    Okay, thanks.