• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 63 subscribers
  • Views 1254 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

[ UCD3138 ] Question about the "Memory Debugger" of Fusion tool

Snaku Lee
Prodigy 60 points
Other Parts Discussed in Thread: UCD3138A64

Hi,

I am using UCD3138A64 with CCS6.1, last week I created a new 'configuration' of my project. I named the new configuration as 'Stand_Alone', and I put output files (i.e. .map, .pp, .out) to 'Stand_Alone' sub-folder, after the .x0 image file load to UCD3138A64, I change Fusion memory debugger tool map file to 'Stand_Alone' sub-folder, but I can't see "RAM" information of the memory debugger tool, "Registers" still work but nothing in the "RAM" page. What are the necessary files for the memory debugger tool in the 'RAM' page? only .map and .pp files?

Regards,

Snaku

  • 0
    TI__Expert 4970 points

    Snaku,

    Can you try again without copying the .map, .pp, and .out files to a stand alone folder, but leave them, and point the GUI to that location?

    Are you certain that you declared the variables as global variables in the appropriate header files? eg. if you want a RAM variable to show up in the GUI, it must be a global variable. To make the variable a global variable, you can declare it along with the others in variables.h

    Let me know if this helps. Thanks!

    Regards,

    Brandon Vonk

  • 0 in reply to Brandon Vonk
    Prodigy 60 points

    Hi Brandon,

    I delete the configuration and change back to original one (its named 'UCD3138A64'), then I download the .x0 file and change 'Memory Debugger' tool's map back to the 'UCD3138A64' folder, but the result is worse, I miss all pages contain of 'Memory Debugger' tool. Nothing in the 'Registers', 'RAM', 'DFlash' and 'PFlash' pages.

    And I am sure those global variables are define in the variables.h file, and I can access those global variables before I create the new configuration.

    May I send you my project files to your email?

    PS. The version number of my Fusion tool is v2.0.50[2015-06-12].

    Thank you,

    Snaku

  • 0 in reply to Brandon Vonk
    Prodigy 60 points

    Hi Brandon,

    I roll back my code to make the 'Memory Debugger' can use the 'RAM' page, then add my code step by step, and I find the 'RAM' become empty when I include my 'sys_cfg.h' header file. This file just define some number and string, it should not effect the RAM debugger function. I copy the output folder which contain .map and .pp files before and after I include 'sys_cfg.h' file.

    • UCD3138A64_ram_ok : the RAM debugger is work on this folder
    • UCD3138A64_ram_ng : the RAM debugger become empty after I add my sys_cfg.h file.

    [sys_cfg.h]

    #ifndef DEF_SYS_CFG_H
    #define DEF_SYS_CFG_H

    #define DEF_UART_DEBUG /**< remark it can disable UART debug message */
    /*#define DEF_STAND_ALONE *< test application code without FBL, this is define in CCS project file */

    #define APP_VERSION "0.0.1"
    #define APP_TITLE "UCD3138A64_APP"

    #define SREC_DATA_LEN_MAX 32U /* s-record max data length */
    #define SRAM_START_ADDR 0x0006A000UL /* SRAM start address */

    #endif

    --

    Regards,
    SnakuUCD3138A64_RAM_DBG.zip

  • 0 in reply to Snaku Lee
    TI__Expert 4040 points

    Hello Snaku,

    The memory debugger does not support .pp files that have the /* comment style.  So I see that your *.h file has /* so if you can change it to // you should be able to see your variables.

    Amiel

  • 0 in reply to Amiel Hussain
    Prodigy 60 points

    Hi Amiel,

    After I remove the multi-line comment (i.e. /**/) of my sys_cfg.h, I can see RAM items of memory debugger, thanks for your help.

    But other files still have the multi-line comment in .pp files, the memory debugger still works, so I think multi-line comment is not the only issue for RAM debugger.

    One more thing is MISRA-C2 doesn't allow single line comment.

    Regards,

    Snaku