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.
Tool/software: Code Composer Studio
From the picture , I define the value of variables in the 'Variables.h' ? Is right way to define the variables in the 'Variables.h'?
If variables.h is not the right location to define the follow variables , Where I can define them , and the difference about the location ?
By memory debug I find the value of variable is " -1 " , is wrong . as follow ,
This is just a matter of naming convention, order and project structure.
You could probably place your #define in variable.h and things will still work just fine.
But in the project system_dfines.h is named like that to indicate that it contains many #defines. This way the search and readability of the program will be better and easier.
In the same fashion variables.h name indicates that this file contains declaration of generic variables.
Regards,
Please make sure that you are pointing the memory debugger to the right directory where the .map and .pp files reside.
The memory debugger parser uses these files to extract the name and location of the variables.
This can be done through the file menu in the memory debugger:
Choose the "Select Folder Containing the Map/PP files" and browse to get to the right directory.
Regards,
Can you provide a specific example that you have problem with?
It is hard to address this in a generic way. We may need your code to reproduce the problem.
I have seen cases where the memory debugger parser of .pp and .map file can not parse the variable information due to comments embedded in the code.
Try to remove the//comments around the specific variable that does not show up properly in the memory debugger.
Does this happen only under certain noise levels or switching/load conditions? Why do you think this is noise related?
Understood, I was not aware that this problem is an intermittent one.
Is this happening only when the power supply output is running? Is the probability load dependent?
You may wrap the PMBus interface ribbon cable around a ferrite core and see if it helps.
You should also look at the PMBus commands log in the GUI and see if any commands get Nack-ed.
Please be so kind as to set the status of this post to resolved, and open a new post with your new question.