• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 346 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.

SDK 1.0.0.9 : Project Ecat_appl

Bindu Ganesh
Expert 2220 points
Other Parts Discussed in Thread: SYSBIOS

SDK 1.0.0.9 Ecat_appl , Application to run in debug mode

First thing we are trying to Run the project ecat_appl in debug mode on ICE Board,  project located at ti\am335x_sysbios_ind_sdk_1.0.0.9\sdk\protocols\ethercat_slave

For your information we have already  worked on SDK 1.0.0.4 and SDK 1.0.0.8 and were succesfully able to run the ecat_appl project in debug mode on ICE board

Below is the steps carried out on SDK 1.0.0.9

1) As it is mentioned in userguide to downlaod Slave Stack Code SSC 5.10 from ETG and Place the *.c and *.h files of SSC to C:\ti\am335x_sysbios_ind_sdk_1.0.0.9\sdk\protocols\ethercat_slave\ecat_appl\EcatStack.

2) Define 2 macros in ecat_def...things are taken care here

3)To run the application in Debug mode, Using CCS v5.2 we need to pass a command in Post-build-steps as below

 "${IA_SDK_HOME}/tools/post_build/post_build.bat" "${CCS_INSTALL_ROOT}" "${CG_TOOL_ROOT}" "${PWD}" "${ProjName}" "${IA_SDK_HOME}/tools/sdk_image" "1" "1" "0x80000000" "0x80000000"

4) Now was able to successfully buit the ecat_appl and *.out created in debug folder

5) Now at this time when we tried to run the application in debug mode, by laoding the *.out file on ICE Board,

It pops up no source available at 0x8...... (this 32bit address is not constant).failed to run the application in debug mode here

earlier observation with SDK 1.0.0.4 and SDK 1.0.0.8 was that the cursor was pointing tiesappl.c main function, but it is not the behaviour in SDK 1.0.0.9?

did not missed out any steps to run the application in debug mode, because previously have followed the same procedure for SDK 1.0.0.4 and 1.0.0.8 and was succeeded

Hope this information, helps you to figure out the solution. I guess Some settings need to be taken care in CCS Post-build steps .

Thanks,

Bindu

  • 0
    Expert 2380 points

    Bindu,

    Have you made any change(s) to the project settings or source code or cfg ? If yes, Can you try the sdk ecat_appl  AS IS ? This application in sdk is well tested.


    Once the .out file is loaded, if execution doesn;t stop at common_main, suspend the execution  and do a restart. This should ideally bring you back to common_main.

    Let me know the results.

    Regareds,

    Shahid

  • 0 in reply to Shahid AC
    Expert 2220 points

    Shahid,

    Did not make any changes, just run the SDK 1.0.0.9 set up and copied the SSC to Ether stack and built, it generated the .out file

    Tried with the mentioned procedure, but did not work in debug mode

    Instead a message "No source available for "_c_int00() at ox80000000" appears

    Regards,

    Bindu

  • 0 in reply to Bindu Ganesh
    Expert 2380 points

    I see.  What did you do next? Did you resume execution after coming to 0x80000000 ? what was the behavior ?I believe this  a CCS related issue.

    Just to ensure that, can you flash ecat_appl_SPI.bin and see if the application is running ?

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Expert 2220 points

    Shahid,

    1) What did you do next? Did you resume execution after coming to 0x80000000 ?

          Since Resume was disable, we could not resume.

    2) Behaviour is not constant,

    Some times the exection is pointed to main, simply by loading .out file ( without suspend and restart), but the propability of this condition is very less.

    and was able to communicate with twincat .

    3) Some times when we do suspend, the exection is pointing to "ti_sysbios_family_arm_exe_exception_excHandler Data ASM_I"

    will try to flash the ecat_appl and let you know the result.

    Regards,

    Bindu

  • 0 in reply to Bindu Ganesh
    Expert 2380 points

    Alright. Thanks.

    One thing, are you executing GEL init script before loading .out file ?

    Before loading the .out file, it is good to make  that the GEL initialization script is executed and before executing GEL init script, make sure that CPU is reset.

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Expert 2220 points

    Shahid,

    CPU Reset , before loading GEL init script, Solved the issue.

    Thanks,

    Bindu