TMS320F28377D: Application problem.

Hello,

Is the only difference between these two projects contained within the .cmd file you have sent? I see that you've modified where the .econst memory section is stored in Flash memory, but this should not impact the behavior of the motor. What exactly is your question? Are you trying to resolve the discrepancy between these two .cmd files?

Kind regards,

Skyler

Hi Skyler,

The "normal program" on the left side of the figure can load the rated load of the motor to 150%, while the "abnormal program" on the right side fails when loaded to around 70%.

Help analyze the reason, thank you!

Hi Reed,

Does .econst have to be stored in FLASHI as well? If the only difference between the software on the two projects is the location of the .econst memory section in Flash, I suggest changing the .cmd file of the "abnormal program" to match the "normal program". I don't expect this to affect the behavior you are highlighting, but that could rule out the software as the root cause of the issue.

If the issue persists after modifying the .cmd file to match the "normal program", I suggest checking the .map file of both programs and verifying that there is no overlap or unintended behavior as a result of storing the .econst section in FLASHI.

Kind regards,

Skyler

map-20240521.zip

Hi Skyler,

The attachment contents a normal map file and a abnormal one, Could you please help us to analyze the abnormal one,thanks a lot.

Best regards，

Lei Wang

Hi Lei,

I think the filenames you sent may have been swapped. The abnormal MAP.map doesn't include FLASHI, but normal MAP.map does (the opposite of what is indicated in the screenshots and the previously attached .cmd files). Besides that, both of them look correct and I don't see any issues with them. 

Were you able to verify that the "abnormal" program behaved like the "normal" program once the .cmd files were edited to be the same?

Kind regards,

Skyler

Hi Skyler,

1.  I think the filenames you sent may have been swapped

-----Yes,sorry, the two file names are swapped as you said.

2.  Difference between two map

The address of some const  are difference,and the running result is normal and abnormal.

3.Were you able to verify that the "abnormal" program behaved like the "normal" program once the .cmd files were edited to be the same?

-----For the abnormal program,we just modify the cmd(add FLAHSI to econst area), if we modify the cmd file to the normal(delete FLASHI) ,the result is good. 

Best regards，

Lei Wang

Hello,

Are you able to determine the function/line of the software that causes the motor to fail at 70% load in the abnormal project? Without any context of the motor failure, it is difficult to pinpoint the reason why the difference in linker .cmd files would cause this behavior. Is the source code referencing a location in memory that is being modified by the abnormal .cmd file? The map file indicates that the normal project stores data in FLASHJ, FLASHK, FLASHL, FLASHM, and FLASHN, while the abnormal only stores data in FLASHI and FLASHJ. Is there a place in the source code that depends directly on some data being stored in the FLASHJ, FLASHK, FLASHL, FLASHM, or FLASHN sections? What is indicating that there is a motor failure?

Kind regards,

Skyler

Hi Skyler,

We have attempted to identify the function code that caused the problem, but were unable to locate it. 

 Additionally, Is there any difference in code execution between EABI compilation and COFF compilation?

Best regards，

Lei Wang