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

Connection problem with an ARM 9 board with CodeComposer

Laurent Martin
Prodigy 20 points

Other Parts Discussed in Thread: CODECOMPOSER, OMAP-L137

Hy, verybody,

I'm new recent user of CodeComposer V3.3.38.2, and I don't succeed to connect to my board...

I have each time following error :

Error connecting to the target:
Error 0x80000220/-2062
Fatal Error during: Execution, OCS,
Cannot halt the processor


Sequence ID: 0
Error Code: -2062
Error Class: 0x80000220
I/O Port = 240

Board Name: ARM9 JTAGjet Emulator
Cpu Name: ARM9_0

I have check emulator and it seems OK... I really don't understand how to debug/solve this problem.

Is there anybody who can hep me please?

Laurent

  • 0
    TI__Mastermind 30805 points

    It looks like that you posted on the wrong forum. You should have used:
    TI Home     > TI E2E Community > Support > Development Tools > Code Composer Studio

     

    Regarding your question since you do not specify what devide you use it makes it difficult to make precisely. A couple of suggestions:

    - Some ARM9 devices such as OMAP-L137 require to use CCS 3.30 SR12.1 (ie 3.3.82.13).
    - Ensure that you installed the according CCS driver of TI compatible JTAG emulator you want to use. Double check with the emulator provider to be sure which dirver to use with which CCS version.
    - Most of the time you can select from CCS setup a pre-made configuration.
    - If possible try with a development board that is know to be working to check the CCS setup and see if you can debug. Then you can try with a custom board.
    - For ARM9 emulation you might require adaptive clocking (more information are provided at the Twiki page referenced below).

    For customer board some debugging might be needed to identify if the JTAG interface on the board is functional. Typically the device need to be powered and booted. Note as well that some bootmode (like HPI boot, emulation boot, ..etc) might make it easier to connect to CCS.

    Here is a good starting point for troubleshooting:
           http://wiki.davincidsp.com/index.php/Debugging_JTAG_Connectivity_Problems

    All CCS 3.30 topics are listed here:
            http://wiki.davincidsp.com/index.php/Category:Code_Composer_Studio_v3

    Some more literature about JTAG and emulation that you can find on the TI web and that could help. It does not refer to ARM9 but still it can be useful
        C6000 Boot Mode and Emulation Reset (spra978)
        C6000: Board Design for JTAG  (SPRA584C)
        Emulation Fundamentals for TI 's DSP Solutions (SPRA439B)
        C6000 DSP Designing for JTAG Emulation Reference Guide (SPRU641)

    Ant.

     

  • 0 in reply to AnBer
    Prodigy 20 points

    Thanks alot for your so quick answer!

    I have check my emulator (JTAGjet of Signum) and it is OK (check done by DiagTool of Signum which succeed to dialog with emulator).

    I have check that it is the good driver and it's OK too. CCS is weel configured to use this driver, see following jpeg of my screen :

    Normally I used good GEL file as shown below :

     And when I try to connect to the board I have this pop-up :

    It seems that the micro is not seen as power ON. I have try with other configurations of micro-switch just near micro but it is always same error.

    Do you have an idea to explain this message?

    Laurent

  • 0 in reply to Laurent Martin
    TI__Mastermind 30805 points

    - It seems that you try to emulate a DM644x. Have you tried to select DM644x rather than creating a ARM9 config by hand?
    The point is that there is not only a ARM9 in the JTAG chain, there is as well a C64x+. It is easier to select a DM644x device from the list as it will configure the JTAG chain accordingly.

    - Is the Signum emulator supporting adaptive clocking? If not check the link I refer to in the last post.

    - Sometimes ago I managed to connect to both ARM9 and C64x+ of the  DM6446 EVM using a BH 560 LAN emulator. Here is what I used and I was able to open both C64x+ and ARM CCS windows as well as connect to the target:
    1) HW/boot config:
    a) For the ARM CPU there are no problem to debug whatever the bootmode is:
     - If AEMIF boot is used (ie RBL boots UBL that boots U-BOOT). The UBL does the PLL, DDR, pin mux ..etc set up so no need of GEL.
     - If UART bootmode is used then the GEL file is needed.

    b) C64x+:
    One potential problem is that the C64x+ need to be POWERED and OUT of RESET (via a given bootmode).
    This might be handled by U-boot already in the recent DVSDK versions (ie ARM power DSP an dput it out of RESET).

    Still to connect more reliabily to the C64x+ CPU I would advise to use the following setup:
     - C64xx self boot
     - UART boot mode    In this case the C64x+ self boots which does POWER the CPU + put it out of RESET
    All this is setup via the DM6446 switch S3.

    2) CCS setup:
    a) Most of the emulator do provide some predifined configuration for DM6446.
    I used for example the following:
     Blackhawk LAN560   - DM6446 Emulator
     Blackhawk USB560m  - DM6446 Emulator

    b) I used the GEL file from Spectrum Digital:
    The ARM gel file takes care of all the system level inits (PLL, PINUMX, DDR2, ..etc):
         http://c6000.spectrumdigital.com/davincievm/revf/