• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 689 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.

CCS/LAUNCHXL2-RM57L: Stop in dataentry due to local string definition, data write fault

DavidRojas
Intellectual 280 points

Part Number: LAUNCHXL2-RM57L
Other Parts Discussed in Thread: HALCOGEN

Tool/software: Code Composer Studio

Hi,

Currently, I try to develop an application on Hercules RM57L. In a specific routine of the application, it stays in dataentry in HL_sys_intvecs.asm.

During debugging the routine goes to HL_sys_intvecs.asm during TL string definition. As follow: 

Strangely, when I see the string variable during debugging before the definition, it has the values of a locally defined string in another function in the same .c file. '3208' value, 

A revision in CP15 registers DFSR, DFAR, and IFAR relates that that error occurs due to a write error, and the status register indicates that it is related to a background fault. Finally, the data fault address means that 0x07FFF9B0 is the address where data fault originated. I saw along with all variable addresses in the function and another variable address in other functions, but I can't find this fault address related to another variable. 

How can I fix this issue ?? 

Thanks for your attention. 

  • 0
    Intellectual 680 points

    David,

    You probably have too much stuff on stack and caused a stack OV. As you noticed the data fault address is an invalid mem location, below stack space.

    What is your stack size? do you need to allocate all those variables on the stack? If you do, increase your (user) stack size, else place the variables in data space.

    Joe Josn

  • 0 in reply to Joe Josn
    TI__Guru**** 200676 points

    Hello David,

    All the local variable (including pointer variables) are stored in stack. The default stack side of HALCoGen generated code is 0x800. As Joe said you may not have enough stack for your local variables, function arguments, and function return address. Please try big stack size,or declare fftinpu[] and fftouput[] as global variables.