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

Blackhawk emulator failing?

David Luca
Expert 2795 points

Other Parts Discussed in Thread: TMS320C6748, SYSBIOS

Hello,

I was able to debug the firmware just fine from CCS5.3.0 using our Blackhawk XDS560v2 System Trace for weeks, but it started to misbehave and I have no idea why. We are using a custom made board with TMS320C6748. The GEL file seems that is executing, firmware is loading but has problems halting the CPU and run to main code, please see the output below:

C674X_0: Output: Target Connected.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: Memory Map Cleared.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: Memory Map Setup Complete.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: KICK Unlocked.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: PSC Enable Complete.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: PLL0 init done for Core:300MHz, EMIFA:100MHz
C674X_0: Output: mDDR initialization is in progress....
C674X_0: Output: PLL1 init done for DDR:150MHz
C674X_0: Output: Using mDDR settings
C674X_0: Output: mDDR init for 150 MHz is done
C674X_0: Output: ---------------------------------------------
C674X_0: Trouble Reading Register CSR: (Error -1060 @ 0x41) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.8.0)
C674X_0: Trouble Halting Target CPU: (Error -1060 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.8.0)
C674X_0: Trouble Reading Register CSR: (Error -1060 @ 0x41) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.8.0)
C674X_0: Trouble Halting Target CPU: (Error -1060 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.8.0)

Does this mean my emulator is failing? There were no board changes and it was working fine. I tried restarting CCS, emulator, board at the same time, reduced JTAG clock settings, but nothing helps. Any idea why is this happening or what should I check? Is it a problem of the code booting from flash that cannot be interrupted by emulator?

Any suggestions are appreciated, thank you in advance,

David.

  • 0
    TI__Guru**** 171729 points

    David,

    David Luca said:

    Is it a problem of the code booting from flash that cannot be interrupted by emulator?

    The sentence above makes me believe that what is causing a system clash is double hardware initialization: when you turn on your board, the code loaded to the flash memory initializes some or all the hardware, but when you try to connect using CCS, the GEL file in your target configuration file also tries to initialize it.

    One thing you can do is either remove the GEL file from the existing configuration or create an additional target configuration that connects to the TMS320C6748 device (not the EVMC6748, which by default is pre-populated with the EVM's GEL file).

    You can also try to inspect the status of the core before connecting to it by following the procedure at the thread below:

     http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/195554/698524.aspx#698524

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 2795 points

    Hi Rafael,

    It seems this is exactly the case, because if I disable booting from flash, the emulator loads the application and runs it fine. I tried to find the GEL you mentioned, but only one available is C6748.gel in evmc6748 example folders. Our board is designed after LogicPD so it uses same mDDR. In the target configuration file it is selected TMS320C6748 not EVM. The thing is, hardware initialization wasn't changed since a few weeks ago and the debugging/booting from flash was still working fine afterwards. Seems that occasionally debugging works after board booting from flash which is even more confusing but whenever we press Pause button and then resume, we receive:

    ti.sysbios.gates.GateMutex: line 97: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
    xdc.runtime.Error.raise: terminating execution

    Best regards,

    David.

  • 0 in reply to David Luca
    Expert 2795 points

    Turns out the firmware in flash has watchdog enabled and expires in less than 100ms. Works fine now, for a few days I was very puzzled but we traced back in time where the change was made. Thank you all for your help.