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/F28M36H33B2: GEL: Error while executing OnTargetConnect(): Evaluation canceled

Part Number: F28M36H33B2
Other Parts Discussed in Thread: F28M36P63C2

Tool/software: Code Composer Studio

I have a newly developed PCB using the Concerto and I am trying to connect to the device for the first time, to download my code with the Spectrum Digital XDS510 emulator.  I have developed code using the ControlCard with onboard XDS100 USB emulator and programmed it successfully. Now I have setup the Target Configuration for the new hardware with the new Emulator, device and correct GEL file, found in C:\ti\ccsv6\ccs_base\emulation\gel. The "Test Connection" under Target Configuration is working and shows that there is 1 device on the JTAG chain. However, when I try to "Connect Target" it hangs on the OnTargetConnect diaglog. If I click cancel I get the following error messages:

Cortex_M3_0: GEL: Error while executing OnTargetConnect(): Evaluation canceled
Cortex_M3_0: Trouble Reading Memory Block at 0x680428 on Page 0 of Length 0x4: Error 0x80002002/-1204 Fatal Error during: Memory, Control, The DAP access, address 0x00680428, has casued a STALL. DAP transaction is aborted.
Cortex_M3_0: Error: Error 0x80002020/-1203 Fatal Error during: Execution, Control, The DAP access, address 0x41E90100, has returned a SLAVE error.

On the hardware side everything seems fine if I look at the device internal voltages (1.2V and 1.8V). The XDS reset pin toggles, meaning the device is in a continuous reset loop. According to the reference manual, this is supposed to be the case for a factory fresh device with no code in the flash or RAM, until the emulator is connected and a debug session started (6.8.4 Device Boot Sequence). However, I cannot connect to the device with the emulator to flash it.

Is there anything else I need to configure to connect to the device? Is there something wrong with the GEL file?

Thanks

  • Hi,

    >>Cortex_M3_0: Trouble Reading Memory Block at 0x680428 on Page 0 of Length 0x4:

    I can't precisely tell why the error is happening, but the address above is marked as "Reserved" in the device's memory map.

    Therefore can you try a few things?

    - Double-check your target configuration file set to the F28M36H33B2. Small differences between the devices may affect GEL functionality.

    - Can you remove the GEL files from the configuration and see if it is possible to connect to the core? Check this reference for details. This may evidence problems with the GEL file itself. 

    - The fact the OnTargetConnect procedure starts means the connection was established but the device may have gone awry during the process - perhaps being reset by an external agent such as a watchdog timer. Can you check the bootmode pins according to section 6.8.4 of the device datasheet to see if they match the information there?

    - Perhaps an update to the C2000 Device support corrects an issue specific to this device. Can you go to menu Help → Check for Updates and see if there are any available updates?

    Unfortunately I don't have the same device as you, but connecting to a blank F28M36P63C2 is successful. I am using CCSv7, however. 

    Hope this helps,

    Rafael

  • Thanks Rafael

    I also suspected a GEL file problem, but I have tried all your suggestions and it still does not want to connect. However, we also had a Blackhawk USB560 Emulator lying around and when I connected that up, and only changed the Emulator in the Target Configuration file, everything was working fine! I am now able to connect and flash the device successfully with the USB560. I know my XDS510 is not faulty and I have also tested it with another XDS510 which also does not want to connect. I would still like to get the XDS510 working though. Why would the Blackhawk USB560 work but not the XDS510?

  • Hi,

    Thank you for reporting back the details. I can't necessarily point to a specific root cause for this, but history shows that a few details that may be influencing your ability to connect are:
    - Ground loops. The XDS510USB is USB powered, while the USB560 may or may not be (depends on your model). If both your PC and your target board do not have isolated power supplies, the XDS510USB may be closing a ground loop from the USB port of your PC all through the target board, while the USB560 may have some isolation between the USB and the JTAG. That or the power supply of your USB560 is diverting part of the ground loop current through its own power supply.
    - Differences in design. The XDS510USB and the USB560 have different designs with different JTAG line drivers and, possibly, some isolation between the USB and the JTAG ports. The line drivers can also have marginal differences in strength which cause integrity issues in the JTAG communications.
    - Differences in target board design. The same idea as above, but this time with the target board. Specific routing or pull ups/pull downs that can marginally affect the integrity of JTAG communications.

    All in all, I would double-check the circuitry and compare with section 7.1 of the reference below:
    processors.wiki.ti.com/.../XDS_Target_Connection_Guide

    Hope this helps,
    Rafael
  • My target device is powered through an isolated DC-DC converter, so ground loops should not be a problem. I have however managed to get it working. I found another post with a similar problem and apparently the "Extended IcePick Router support" checkbox in the configuration file should be checked. When I did that the XDS510 connected and is working fine now. What exactly is Extended IcePick Router support? Thanks.
  • Hi,

    Thank you for reporting back your findings. Unfortunately I don't know what is this option as this is directly provided by Spectrum Digital. In any case, i am glad it worked for you.

    Regards,
    Rafael