• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 861 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.

Compiler/CC3200-LAUNCHXL: Exit.c file pop-up when I debug the code

Yin Li
Intellectual 480 points
Part Number: CC3200-LAUNCHXL
Other Parts Discussed in Thread: CC3200

Tool/software: TI C/C++ Compiler

Hi all, 

I am using CC3200LP transfer the voltage measurement from ADC to Exosite. It works fine if ADC function is simple. However, when I added more calculations and vectors which are used to store the voltage measurement, the debugging process would stop with Exit.c file pop-up.  Does anyone know which reasons may cause Exit.c file pop-up? I attached the screenshot of that file.  . 

Is it because ADC function becomes more complex after I added some calculation and vectors? Then, the complex ADC function exceeds the memory of CC3200? 

Thanks. 

Yin 

  • 0
    TI__Guru 63006 points
    Hi Yin,

    Loader_exit can be called after SYS/BIOS has detected an error (within an Abort handler).
    Once loader_exit has been entered, try and use the stack back trace to find where it has been called from, which will hopefully identify the error which was detected by SYS/BIOS.
    It typically relates to access to an uninitialized peripheral (if you use the original linker command file, the linker will issue an error in case the code exceeds the available memory).

    Br,
    Kobi
  • 0 in reply to Kobi Leibovitch
    Intellectual 480 points

    Hi Kobi, 

    Thanks for your response. 

    Yes, I am using the original linker CMD file. Right now, my codes worked fine if I didn't add a function. If I added that function, exit.c file would pop-up. I used Memory Allocation to find that SRAM_CODE = 54.040(43%) and SRAM_DATA = 27,844(22%) without that function. However, after I added that function, SRAM_CODE = 60,786(49%) and SRAM_DATA = 27,872(22%). Does it mean that both of codes didn't exceed the available memory? 

    Meanwhile, could you give me a little tutorial about stack back trace? 

    Thanks. 

    Yin