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.

DSS in JUNIT problems

Other Parts Discussed in Thread: TMS570LS1227

Hi,

I have two questions:

1. JUnit won't stop at breakpoints, here are my java codes:

long breakPoint = debugSession.symbol.getAddress("main");

System.out.println("breakPoint :" + breakPoint);

int brkInstall = debugSession.breakpoint.add(breakPoint);

2. debugSession.memory.loadProgram always erase the entire FLASH memory. Is it possible to configure it only erase necessary flash?

My CCS version is: 5.3.0.00090 with JUNIT 4.11, JAVA version 1.7.0_25.

 

Thanks

Jun

 

  • Hi Jun,

    Jun Xu said:

    1. JUnit won't stop at breakpoints, here are my java codes:

    long breakPoint = debugSession.symbol.getAddress("main");

    System.out.println("breakPoint :" + breakPoint);

    int brkInstall = debugSession.breakpoint.add(breakPoint);

    Your usage of the API looks correct. Where is this breakpoint being set? In flash?

    What device are you using?

    Jun Xu said:
    2. debugSession.memory.loadProgram always erase the entire FLASH memory. Is it possible to configure it only erase necessary flash?

    Yes. Please see the DSS API doc, specifically the Flash section. There are a list of APIs and an example:

    <CCS INSTALL DIR>/ccsv5/ccs_base/scripting/docs/DS_API/com/ti/debug/engine/scripting/Flash.html

    Thanks

    ki

  • Hi Ki,

    The API getAddress("main") returns a correct address which is exactlly same in the map file.

    The breakpoint is In Flash. My device is TMS570LS1227.

    I have tried this http://stackoverflow.com/questions/1370868/eclipse-debugger-doesnt-stop-at-breakpoint but it won't work.

    Thanks

    Jun

  • Check the following:

    -your application actually makes it to 'main'

    -you have a hardware breakpoint available to use (there are limited number of HW breakpoints available)

    -you are using a correct debugger memory map, usually defined by a startup GEL file.

    Thanks

    ki