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.

Debug Error: No source available for "0x3ffe9a"

Other Parts Discussed in Thread: CONTROLSUITE

Hi, 

 I am trying to connect my experimenter kit with CCS5.3.00009.  I build was successfully completed. But i am trying to debug my source code i am getting this error.

 No source available for "0x3ffe9a"  

Screen shot for that is:

Please help me to resolve this error.

Thanks in advance!!!

Thirumoorthy.R

  • This is normal.  The address is in the boot ROM, and the source code for the boot ROM is not in your project, right?  Hence, no source available message.  This also happens with library functions.  Just hit RUN in the debugger.  The code will execute.

    Regards,

    David

  • I have got a similar error. I am running an example from the controlSUITE on a LaunchPadXL with an 28027F.

    ERROR: No source available for "0x3ff5f5". See screen dump. (Error occurs in this case after 19867 interrupts)

    The program works fine for hours and sometimes the error happens regularly. Simply pressing the run button in the debugger does not work unfortunately. Any idea?

    Regards,

  • Bart Roodenburg said:
    Simply pressing the run button in the debugger does not work unfortunately.

    What happens if you press the RUN button in this instance?

    Regards,

    Gautam

  • The debugger starts properly and after a certain time (minutes) the error, shown in the screen-shot above, occurs. If I press the "green play button" again the screen flashes and the debugger stops immediately. (Play button becomes/stays green).  It seems to happen more frequent when running on the external XTAL. So I have checked the divided XCLKOUT on GPIO-18 on the oscilloscope and it looks in both situations the same.

    Regards, Bart

  • Bart,

    Address location 0x3FF5F7 corresponds to SelectMode_Boot.obj in BOOT ROM.

    I believe you would need to investigate why your PC reached boot rom in the 1st place. Did a watchdog, NMI watchdog (or) BOR reset which might have cause the PC to reach boot rom.

    Regards,

    Manoj