• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 57 subscribers
  • Views 1785 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.

GUI Composer Issue

Max Liao
Prodigy 60 points
Other Parts Discussed in Thread: TMS320F28335, CONTROLSUITE

GUI Composer Issue

When I test the GUI Composer function On CCS5.3, I encounter a problem.

When I run an application in CCS Debug and use GUI Composer (Preview Mode) to obeserve a global variable named "value".
The application will always be stopped.And the console window has following message:

CortexR4: Trouble Reading Memory Block at 0x800151c on Page 0 of Length 0x2: (Error -1170 @ 0x0) Unable to access the DAP. 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.0.872.0) 

Attach is the project.

System Setup:
Host OS: Windows XP Professional, Service Pack 3
CCS Version: 5.3.0.00090
Hercules Sefaty MCU Developemnt Kit (RM42 MCU)
Texas Instruments XDS100V2 USB Emulator

  • 0
    TI__Intellectual 1115 points

    Hi Max,

    I have moved your question to the Code Composer Forum Support who should be able to help you with this issue.

    Best regards,

    Paul

  • 0
    TI__Genius 16520 points

    Hi Max,

    Without GUI Composer open, but with the expression view open, do you get the error message or not? You might have to hit the refresh button in the Expression view.

    Patrick

  • 0 in reply to Patrick Chuong
    Prodigy 60 points
    Hi Patrick,
    This issue has been fixed when I enable the option to "Halt the target before any debugger access".

    Thanks
    Max
  • 0 in reply to Max Liao
    TI__Genius 15710 points

    Hi Max, 

    Please keep in mind that this particular option will temporarily halt the processor while memory access is made. You would need to determine whether your application/system can handle these processing interruptions. Interrupts will get dropped when CPU is halted. 

    Unfortunately, RM42 does not support non-intrusive memory access while processor is running like RM48 or RM46 do.

    Martin

  • 0 in reply to MartinS
    TI__Intellectual 1785 points

    As Martin mentioned, RM42 does not support real time accesses via JTAG. We will be introducing UART based transport in CCSv5.5 (Sept, 2013). This transport, along with a monitor running on the target, will allow for real time accesses for such devices. 

    Raj

  • 0 in reply to Patrick Chuong
    Prodigy 70 points

    Dear Patrick

    I also have some question about GUI composer.

    My target is TMS320F28335. I use CCS5.4. the emulator is XDS100V2. I want to observe 8 variables during the debug process. So I try the GUI composer. I use the “Scalarlinegraph” widget. First I try display only one variable. I utilize a project designed by TI, provided in controlsuite.

    ti\controlSUITE\development_kits\HVMotorCtrl+PfcKit_v2.1\HVACI_Sensorless_2833x

     

    In this project I bind a global variable rg1.Out to value0 of the scalarlinegraph. This variable is expected to generate a ramp. I set the Buffer Length to 200. However when I run the project, the graph always has some glitch, which should not appear.

     

     When I change to another computer, the OS of which is WIN7, it is even worse. There is no ramp curve at all.

    I feel confused. I don’t know how to solve such problem.

     

    Could I trouble you give me some documents that show how to use linegraph widget? I search on the internet, but I can’t find one suitable. 

  • 0 in reply to xin qi68742
    TI__Genius 16520 points

    Hi Xin,

    It is most likely that the target variable is updating faster than the Scalar graph's update rate. You can change the update interval to a smaller number by creating a textbox widget and bind it to this variable $refresh_interval. The default is to update the widget once for every 1000ms.

    Regards,
    Patrick

  • 0 in reply to Patrick Chuong
    Prodigy 70 points

    Hi,Patrick

    Really thank you. I will have a try. thank you.