• Locked Locked
  • Replies 10 replies
  • Subscribers 56 subscribers
  • Views 868 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.

CCS6 locks up

Bob D.
Expert 2430 points


Ive just migrated from CCS5 to CCS6 and it's day one for me and CCS6 is locking up whenever I try to access memory. I'm using the ICEV2 board with the USB emulator. I have both the ARM core and both PRU's enabled. When I try to switch from looking at the PRU memory to ARM memory, CCS6 hangs up so I have to end the program with task manager.  This is not acceptable behavior! I did not have this problem with CCS5.

I tried attaching the debug log from the crash event but I got a file size error message from E2E.

  • Guru 192875 points

    Hi Bob,

    Can you try installing CCSv6.1 again? Uninstall and remove the previous folders completely.

    Regards,
    Gautam

  • in reply to Gautam Iyer
    Expert 2430 points
    Hi Gautam, Spent the last hour uninstalling and reinstalling CCS6. Started it up and same exact problem. Locks up when I go to enter a value in the disassembly window. Very repeatable.
  • in reply to Bob D.
    Expert 2430 points

    Any update on this? I'm kind of stuck waiting for your response. Just to be clear, the program hang occurs when I put in a value into the disassembly window to see the PRU code at 0x4a300000. (I can view that section of memory just fine in the memory window.)

  • in reply to Bob D.
    TI__Guru**** 171254 points
    Bob,

    Since you are having a CCS freeze when trying to access a specific address or address range, I wonder if the CCS debugger is locked waiting for a JTAG operation to complete (which can stem from the JTAG debugger, the core or a peripheral or bus). To double check this, you can try to force a catastrophic failure and see if you can recover CCS control. By catastrophic failure I mean unplugging the USB cable or turning off the board.

    If that is the case, then the issue is either with the address (invalid or perhaps it became misconfigured), another core protecting the given memory region or a failure on how the JTAG debugger itself is accessing the device. For this last possibility I would need to reproduce this locally, but unfortunately I am a bit backed up at this time due to an internal office move.

    Please let me know what are your findings.

    Regards,
    Rafael
  • in reply to desouza
    Expert 2430 points
    Hi Rafael, Unplugging the USB cable during the locked up state does not restore control. CCS6 stays locked up.
  • in reply to Bob D.
    TI__Guru**** 469061 points

    Hi Bob,

    I tried to reproduce the issue on a similar target and was not successful (I experienced no hang). What exact CCSv6 version are you using? And what debug connection?

    Also just to confirm, your test case is:

    -connect to the ARM and both PRU

    -select PRU as the debug context and view PRU memory

    -select ARM as debug context and view address 0x4a300000 in the disassembly window

    Thanks

    ki

  • in reply to Ki
    Expert 2430 points

    Hi Ki,

    CCS Version: 6.1.0.00104

    The steps that I use:

    1) Connect to ARM, PRU0, PRU1 (all CPU's suspended)

    2)View Memory window -> PRU_Device_Memory address 0

    3)Switch to Disassembly window -> type in address 0  (can be any address)

    CCS locks up as soon as 0 is typed in the disassembly window address box.

    Thanks,

    Bob

  • in reply to Bob D.
    TI__Guru**** 469061 points

    Thanks Bob. I tried those steps but still do not see the hang. I am using a slightly different target however so that could be the reason. What debug connection are you using?

    Could you generate a debug server log and attach it to this thread?

    zip the log first before attaching. While the logs themselves can be quite large, it compresses really well.

    Thanks

    ki

  • in reply to Ki
    Expert 2430 points

    CCSLogFile.zipHi Ki, Here is the log file following a crash.

  • in reply to Bob D.
    TI__Guru**** 469061 points
    Thanks.
    Can you also generate a hang dump file? Basically when CCS hangs, let it stay hung for at least 15 seconds. CCS will then generate a hang dump file. You can then use the CCS support dialog to get a zip of all the various diagnostic logs, including the dump files.
    processors.wiki.ti.com/.../Troubleshooting_CCSv6

    Thanks
    ki