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

Troubles to connect to the board

Robert Smith
Intellectual 640 points

I work with DM642 based custom board and CCS 3.3 with Blackhawk USB560 JTAG emulator. I always have troubles to connect to the board.

If I turn board on and try to connect to it, the CCS always(!!!) displays the following error message:

Error connecting to the target:
Error 0x80000240/-1156
Fatal Error during: Initialization, OCS,
Invalid data was scanned by the emulation controller.
Verify the board setup to make sure the scan chain is properly
defined.
If the setup is correct, then RESET EMULATOR.  This will disconnect each
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.


Sequence ID: 0
Error Code: -1156
Error Class: 0x80000240

Board Name: Blackhawk USB560bp - DM640,1,2,3 Emulator
Cpu Name: TMS320C6400_0

Abort:        Close Code Composer Studio.
Retry:        Try to connect to the target again.
Cancel:        Remain disconnected from the target
Diagnostic:    Run diagnostic utility.

In order to connect to board I have to reset board and quickly(!!!) reconnect. Only after these manipulations I successfully connect to board.

Can anyone explain this strange behavior?

Thank

  • 0
    TI__Guru* 84110 points

    Robert,

    It would be easy to blame the old version of CCS you are using, but do make sure you have the latest patch release of it. If my memory is right, there was an SR12 or SR13 service release. And make sure your BlackHawk drivers are up-to-date for the version of CCS 3.3/SRnn that you have.

    The "no boot" boot mode is the most reliable one for use with emulation, and the host boot modes can have problems with emulation depending on what the state of the host boot process is. This is my first guess for what the problem is, meaning the solution would be to select "no boot" or EMIF boot. But you might already be doing that.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 640 points

    Thank you for your reply. I worked on another project for 4 months, now I am returning to my old problems.

    Could you explain, what do you mean by "no boot" boot mode and EMIF boot?

    One more thing I notice in relation to this JTAG connectivity problem. If I erase executable image from flash (Flash mapped via EMIF), then I don't have described JTAG connectivity problem. So the problem happens only when I try to connect to board via JTAG while DSP loaded and executes image from flash.

    Could you comment

    Thanks

  • 0 in reply to Robert Smith
    TI__Guru* 84110 points

    Robert,

    Please see the datasheet and find Section 2.4 Bootmodes. There is a bullet for "EMIF boot" and a bullet for "no boot".

    You did not say in your first post which boot mode you were using. The recommendation to use "no boot" was made to help you prove to yourself whether the problem is with JTAG connectivity or not. JTAG connectivity is simply a symptom of another problem in most cases.

    Your experiment with erasing the executable image from flash was a good one. It has the same effect as above, and proves that the problem is not JTAG connectivity but something wrong with the contents of your executable image.

    Specifically, did you erase the entire contents of the flash, or did you leave the 1KB portion that is initially copied by the internal bootloader?

    A common method to debug this type of problem is to replace the executable code (not the 1KB secondary bootloader) with a small test program as simple as a B $ instruction followed by 7 NOPs. If you can get CCS control after booting with that code, then your secondary bootloader is working okay and your problem is in the executable code; if you cannot get CCS control in this case, then you will need to look at the 1KB secondary bootloader code.

    For more advice on boot debug, please go to the TI Wiki Pages and search for "Debugging Boot Issues" (quotes or not, okay).

    Regards,
    RandyP