Topic
33 replies Latest Post - ‏2014-03-01T10:58:05Z by SahilKulkarni
SystemAdmin
SystemAdmin
2260 Posts
ACCEPTED ANSWER

Pinned topic TDP development

‏2013-04-06T18:55:27Z |
Hi , I'm very new with TDP. The development environment is High-performance Embedded Workshop(HEW) and the CPU is SH7211. From where should i start to develop the TDP.
  • richard.france
    richard.france
    811 Posts
    ACCEPTED ANSWER

    Re: TDP development

    ‏2013-04-22T15:07:20Z  in response to SystemAdmin

    I have made a similar TDP few times ago for TestRT v8.0.0.3. and HEW 4

    Here you are

    read carefully all comments to understand how it works

    Attachments

    • 35BX
      35BX
      9 Posts
      ACCEPTED ANSWER

      Re: TDP development

      ‏2013-05-03T21:05:23Z  in response to richard.france

      Hi Richard,
      Many thanks to you for reply.

      But i want to ask about an other thing. HEW doesn't support some standard c library wich implement some functions required for TPD's library settings(atexit, getenv...). Must i write this functions???

      • richard.france
        richard.france
        811 Posts
        ACCEPTED ANSWER

        Re: TDP development

        ‏2013-05-06T09:03:47Z  in response to 35BX

        As you can see into the attached TDP those function qre set to NONE because they are not available on the target.

        Doing so the TestRT runtime change its behaviour to do the job without those functions.

        Note the attached TDP is a TDP for HEW (from renesas) with RX600 processors

        • 35BX
          35BX
          9 Posts
          ACCEPTED ANSWER

          Re: TDP development

          ‏2013-05-07T21:40:07Z  in response to richard.france

          Please can you help me with this error while linking .obj files (i didn't inderstand where this symbol come from):

           

           

          Linking .\HITACHI\Test.exe...
           optlnk  -message -nooptimize -noprelink -list -DAta_stuff     C:\Users\sh\HITACHI\TTest.obj C:\Users\sh\HITACHI\MonFichier.obj HITACHI\TP.obj -output=".\HITACHI\Test.exe"
           
          Optimizing Linkage Editor V.9.02.00.000
          Copyright (C) 1989,2003 Renesas Technology Corp. and Renesas Solutions Corp.
          All rights reserved.
          License has expired. Maximum link size limited to 256KB code+data.
           
          ** L2310 (E) Undefined external symbol "__stod_a" referenced in "HITACHI\TP.obj"
           
          Optimizing Linkage Editor Abort
          Failed

           

  • 35BX
    35BX
    9 Posts
    ACCEPTED ANSWER

    Re: TDP development

    ‏2013-05-15T17:28:48Z  in response to SystemAdmin

    Please richard can you answer me for this questions ? 

     1) why did you put the priv_exit() in the IntPRG function and priv_close() also ?

    2) when i execute the application it launch Hew and  the command line window  shows :

     

    >ow C:\\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace.hws NOTSILENT
    >FL C:\\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace\\SimDebug_SH2A-FPU_Func\\RTRT_Workspace.abs
    Batch file C:\Users\ME\AppData\Local\Temp\cmd.001 aborted on line 1
    Invalid command
    >

    and when i close it RTRT give :

     

    \\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace.hdc" 

     

    Executable terminated with error code 1.
    Splitting 'HITACHI\\Test.spt' traces file...
    Split unneeded
    No trace HITACHI\\Test.spt generated.
    No RIO instruction found.
    Postprocessing...
    No TIO instruction found.
    Unable to copy "HITACHI\TTest.rio": No such file or directory at C:\PROGRA~1\Rational\TESTRE~1\lib\scripts\Tools.pl line 68.

     

     

    • richard.france
      richard.france
      811 Posts
      ACCEPTED ANSWER

      Re: TDP development

      ‏2013-05-16T12:56:19Z  in response to 35BX

      Hi 35BX,

      unfortunately I am not a Renesas HEW specialist; I only based this TDP on the renesas example.

      1) So I did not put the RTRT runtime code TP.c in a special segment. I only used the link file as is, from the provided HEW example.

      and I do not think it is in the PIntPRG segment . my linker file tell me it is part of the "P" SECTION.

      So if you think it would be better to change it, because your project use a different one, or any other reason, Do it.

      what is important is the debugger have access to those method to put a break point on them.

       

      2) here is the build log when I rebuild the add example using the RenesasRX TDP:

      I hope it will help you to compare with your environment and understand where is your issue

      C:\Program Files\IBM\TestRealTime\bin\intel\win32\utags -sspgtags .\add.ptu

      Preprocessing PTU test script file...
      C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\attolpreproC "C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\add.ptu"      "crenesasRX\Tadd.c"      -studio_log="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\intermediates_files91813665.log" -STD_DEFINE="C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1\ana\atus_c.def" -RENAME=stubs_rename.opt -TSF="crenesasRX\add.tsf" -incl="c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include","crenesasRX" -NOSIMULATION -FAST
      TestRT-I-STARTEXEC,  IBM(R) Rational(R) Test RealTime C Test Script Compiler 8.0.0.4.101.013
      TestRT-I-COPYRIGHT,  (C) Copyright IBM Corp. 1992-2011 All Rights Reserved. All rights reserved.
      TestRT-I-ENDNOENWR,  End of execution with 0 error and 0 warning
      crenesasRX\Tadd.c: Preprocessing...
      ccrx.exe -lang=c    -include=c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include,crenesasRX -output=prep="crenesasRX\Tadd_aug.i" "crenesasRX\Tadd.c"
      RX Family C/C++ Compile Driver V.1.02.00.000
      RX Family C/C++ Compiler V.1.02.00.000
      RX Family Assembler V.1.02.00.000
      Optimizing Linkage Editor V.10.02.00.000
      Copyright (C) 2008 (2009 - 2011) Renesas Electronics Corporation and
      Renesas Solutions Corp.
      Copyright (C) 1999 Hitachi, Ltd.
      All rights reserved.
      Tadd.c:
      C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\attolccp "crenesasRX\Tadd_aug.i" "crenesasRX\Tadd_aug.c" atus_c.def atl.opp  -exfile="crenesasRX\Tadd.c" -noinstrdir="C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1" -proc=ret -block=logical -trace   -studio_log="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\intermediates_files91813665.log"
      ---
      crenesasRX\Tadd_aug.c: Compiling...
      ccrx.exe -lang=c  -cpu=rx600 -patch=rx610 -save_acc -nologo  -include=c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include,crenesasRX -output=obj="crenesasRX\Tadd.obj" "crenesasRX\Tadd_aug.c"
      ---

      add.c: Preprocessing...
      ccrx.exe -lang=c    -include=c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include -output=prep="crenesasRX\add.i" "C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\add.c"
      RX Family C/C++ Compile Driver V.1.02.00.000
      RX Family C/C++ Compiler V.1.02.00.000
      RX Family Assembler V.1.02.00.000
      Optimizing Linkage Editor V.10.02.00.000
      Copyright (C) 2008 (2009 - 2011) Renesas Electronics Corporation and
      Renesas Solutions Corp.
      Copyright (C) 1999 Hitachi, Ltd.
      All rights reserved.
      add.c:
      add.c: Instrumenting using TDP "C RENESAS RX" in "C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1"...
      C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\attolccp "crenesasRX\add.i" "crenesasRX\add_aug.c" atus_c.def atl.opp  -noinstrdir="C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1" -proc=ret -block=logical -trace   -studio_log="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\intermediates_files91813659.log"
      ---
      add.c: Compiling...
      ccrx.exe -lang=c  -cpu=rx600 -patch=rx610 -save_acc -nologo  -include=c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include -output=obj="crenesasRX\add.obj" "crenesasRX\add_aug.c"
      ---

      Result buffer size reduced to 256 chars
      Compiling C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1\lib\TP.c using crenesasRX/products.h containing C/C++ TDP Library settings...
      ccrx.exe -lang=c  -cpu=rx600 -patch=rx610 -save_acc -nologo   -include=crenesasRX,C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1\lib,c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include -output=obj="crenesasRX\TP.obj" "C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1\lib\TP.c"
      Need startup file startup.c
      Compiling startup file C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1/lib/startup.c
      ccrx.exe -lang=c  -cpu=rx600 -patch=rx610 -save_acc -nologo   -include=c:\crossenv\renesas\hew\tools\renesas\RX\1_2_0\include -output=obj="crenesasRX/startup.obj" "C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1/lib/startup.c"
      ---
      Linking .\crenesasRX\add.abs...
      LnkSpawn.exe  -subcommand=tmp.hlk
      ---
      Software license problem:
          Duration of Trial License of UNKNOWN is exhausted. (37)
      Maximum link size limited to 128KB code+data.

      Optimizing Linkage Editor Completed
      mapFile is .\crenesasRX\add.map
      #Time:Thu May 16 14:06:09 2013

      Executing .\crenesasRX\add.abs  ...
      Renesas Debugger Workspace for Test RealTime is C:\PROGRA~1\IBM\TESTRE~2\targets\CRENES~1/RWorkSpace,  execution Target is SimDebug_RX600
      C:\WINDOWS\system32\cmd.exe /c start /w c:\crossenv\renesas\Hew\HEW2.exe "ow C:\\PROGRA~1\\IBM\\TESTRE~2\\targets\\CRENES~1\\RWorkSpace\\RTRT.hws" "FL C:\\PROGRA~1\\IBM\\TESTRE~2\\targets\\CRENES~1\\RWorkSpace\\RTRT\\SimDebug_RX600\\RTRT.abs" "SU C:\\PROGRA~1\\IBM\\TESTRE~2\\targets\\CRENES~1\\RWorkSpace\\RTRT.hdc"
      Splitting 'crenesasRX\\add.spt' traces file...
      ---
      On the fly split done.
      Postprocessing...
      "C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\attolcov" "C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\ADD.C.fdc" "C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\crenesasRX\add.tio" -su=c -output="add.atc.txt" -cio="crenesasRX\atu.cio"
      C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\attolpostpro "crenesasRX\Tadd" "crenesasRX\Tadd.rod"   -studio_log="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\intermediates_files91813624.log" -cio="crenesasRX\atu.cio" -VA=EVAL
      TestRT-I-STARTEXEC,  IBM(R) Rational(R) Test RealTime C and Ada Test Report Generator 8.0.0.4.101.013
      TestRT-I-COPYRIGHT,  (C) Copyright IBM Corp. 1992-2011 All Rights Reserved. All rights reserved.
      TestRT-I-ENDNOENWR,  End of execution with 0 error and 0 warning
      C:\PROGRA~1\IBM\TESTRE~2\bin\intel\win32\rod2xrd -s500 "-hadd.summary.txt" "-lC:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\intermediates_files91813624.log" "-ocrenesasRX\add.xrd" "crenesasRX\Tadd.rod"
      #Time:Thu May 16 14:06:42 2013

      Done

       

      Here is the begin of the map file showing the link command:

      -subcommand=tmp.hlk
      noprelink
      rom D=R,D_1=R_1,D_2=R_2
      nomessage
      list ".\crenesasRX\add.map"
      nooptimize
      -start=B_1,R_1,B_2,R_2,B,R,SU,SI/01000,PResetPRG/0FFFF8000,C_1,C_2,C,L,C$*,D_1,D_2,D,P,PIntPRG,W*/0FFFF8100,FIXEDVECT/0FFFFFFD0
      nologo
      -input="crenesasRX/startup.obj"
      -input="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\crenesasRX\Tadd.obj"
      -input="C:\Program Files\IBM\TestRealTime\examples\TDP\tutorial\crenesasRX\add.obj"
      -input="crenesasRX\TP.obj"
      -library="RX_DSP_RTRT.lib"
      -output=.\crenesasRX\add.abs
      end
       

       

      I hope this helps you.

      tell me if you thing we have to make some modification to this TDP.

      • 35BX
        35BX
        9 Posts
        ACCEPTED ANSWER

        Re: TDP development

        ‏2013-05-18T15:46:32Z  in response to richard.france

         

        Thanks a lot for your reply it was section adresses issue, 
         
        Now the .spt file is generated in the workspace file but it is not copied on the TestRT .spt file , it gives the following perl script error while opening $out : 
         
        No such file or directory 
         
        Note : i'm using TestRT V7.0.0.0

        -------------------

         
        Optimizing Linkage Editor Completed
         
        Optimizing Linkage Editor V.9.02.00.000
        Copyright (C) 1989,2003 Renesas Technology Corp. and Renesas Solutions Corp.
        All rights reserved.
        mapFile is .\HITACHI\add.map
        Executing .\HITACHI\add.abs...
        Renesas Debugger Workspace for Test RealTime is C:\PROGRA~1\Rational\TESTRE~1\targets\HITACHI/RTRT_Workspace,  execution Target is SimDebug_SH2A-FPU_Func
        C:\Windows\system32\cmd.exe /c start /w  C:\Renesas\Hew_001\HEW2.exe "ow C:\\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace.hws" "FL C:\\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace\\SimDebug_SH2A-FPU_Func\\RTRT_Workspace.abs" "SU C:\\PROGRA~1\\Rational\\TESTRE~1\\targets\\HITACHI\\RTRT_Workspace\\RTRT_Workspace.hdc" 
        Splitting 'HITACHI\\add.spt' traces file...
        Split unneeded
        No trace HITACHI\\add.spt generated.
        No RIO instruction found.
        Postprocessing...
        No TIO instruction found.
        Unable to copy "HITACHI\Tadd.rio": No such file or directory at C:\PROGRA~1\Rational\TESTRE~1\lib\scripts\Tools.pl line 68.

         

        Updated on 2013-05-19T19:59:30Z at 2013-05-19T19:59:30Z by 35BX
        • richard.france
          richard.france
          811 Posts
          ACCEPTED ANSWER

          Re: TDP development

          ‏2013-05-21T07:16:42Z  in response to 35BX

          in the execution function some print would help to understand what happend after the execution ....

          make sure the RTRT_Workspace.abs exist before starting exec. then check existance of  RTRT.spt file after execution.

          In my TDP the line "bp _priv_writeln "Output" rtrt.spt _atl_buffer 1 256 A" into hdc file means the rtrt.spt file will be generated into the curent directory of execution which must be the dir specified by the basic settings RTRTRENESASWORKSPACE key.

          Since you have not the same TDP as me could you send me yours as I could have a look at your issue with a reference to your execution function and basic settings.

          • 35BX
            35BX
            9 Posts
            ACCEPTED ANSWER

            Re: TDP development

            ‏2013-05-21T07:51:59Z  in response to richard.france

            Also in my TDP the line "BP _priv_writeln "Output" RTRT_Workspace.spt  _atl_buffer 1 512 A " into hdc file generate RTRT_Workspace.spt  into the  directory specified by RTRT_Workspace key  equivalent to yours RTRTRENESASWORKSPACE key.

            But when it has to filter the data and output it in the $out file i found that it's not writable and when i try to change it with chmod it doesn't change any thing.

            Attachments

            • richard.france
              richard.france
              811 Posts
              ACCEPTED ANSWER

              Re: TDP development

              ‏2013-05-21T09:08:49Z  in response to 35BX

              Your TDP exec function looks good except that you should not check the write access of $out like this because this file is supposed to not exist before the execution.

              $out is the result file generated by the execution function.

              Note Windows 7 turn off write access to all file installed into the ProgramFile.

              So Since your TDP write tmp file into TDP subdirectories,  if your OS is Windows 7, I strongly suggest to save&Generate your TDP into a separate directory where you are sure you will have write access, then do the same for your example.

              once done Studio will be able to see TDP generated ouside TestRT install thanks to the studio preferences > project > TDP

              • 35BX
                35BX
                9 Posts
                ACCEPTED ANSWER

                Re: TDP development

                ‏2013-05-21T10:36:17Z  in response to richard.france

                I did change the directory of the project and  the TDP, but TestRT always create $out file in a non writable mode so it will not be generated by the execution function. 

                Updated on 2013-05-21T10:43:19Z at 2013-05-21T10:43:19Z by 35BX
                • richard.france
                  richard.france
                  811 Posts
                  ACCEPTED ANSWER

                  Re: TDP development

                  ‏2013-05-21T21:37:12Z  in response to 35BX

                  No. TestRT does not write the file it expect to be wrote by the execution. from studio click on the clean button to remove all previously built files. then make sure there is no .spt file. remove them manually if any.

                  From the TDP execution function, you can write to an other file than $out (">$out.tmp" for example)

                  then after the filtering execute the instruction copy("$out.tmp", $out);

                  once the execution finished you will be able to check manually the content of $out.tmp and $out

                  since there are no reason studio write or read $out.tmp if you have not this file created that means your host make the issue.

                  Note your TDP Basic setting ENV_PATH must not contains '%' char this may disturb the file management of windows

                  in addition your rar file included too many .spt file so difficult to know which one was the good one. nevertheless I had a look and it seemed strange: "tdp end" token should be the last line of the file. That'a was not the case.

                   

                  • 35BX
                    35BX
                    9 Posts
                    ACCEPTED ANSWER

                    Re: TDP development

                    ‏2013-05-28T10:23:28Z  in response to richard.france
                    Please Richard can you help me with this : 
                     
                    when compiling my test script it give the folllowing error : 
                     
                    C:\PROGRA~1\Rational\TESTRE~1\targets\HITACHI\lib\priv.h(253) : C2118 (E) Prototype mismatch "_atl_error_dump"
                    C:\PROGRA~1\Rational\TESTRE~1\targets\HITACHI\lib\image.h(119) : C2118 (E) Prototype mismatch "_atl_add_error"
                     
                     
                    i found that a const used in the prototype of this functions cause this error
                     
                    i want to know how to move this const from the TDP
                     
                     
                    Also, the test script stub functions which is in the same source file (i've used atu_stub_function_name) in their service. But when linking file it gives the following error : 
                     
                     
                    ** L2300 (E) Duplicate symbol "_FHC1" in "C:\Users\ME\test_project\stub_proj\HITACHI\TTest.obj"
                     
                    NOTE : FHC1 is declared in the source file and it's stubed in another service into the test script 
                     
                     
                    • richard.france
                      richard.france
                      811 Posts
                      ACCEPTED ANSWER

                      Re: TDP development

                      ‏2013-05-28T18:10:58Z  in response to 35BX

                      about the const the best way is to add the const into the libray code body. This is what has been done in later releases

                      about stub: you must include the file under test into the PTU file if you want to stub a fonction existing into the code under test.

                      Doing so you must not compil the code under test because it is part of the test driver object.

                      Look at the StubC example (2 nodes stubbing and not stubbing a fonction from code under test)

                       

                      all of those issues have been fixed in the following releases.

                      So I would suggest to move to the latest release (8.0.0.4) that also offer other fonctionalities and a new Eclipse UI.

                      • 35BX
                        35BX
                        9 Posts
                        ACCEPTED ANSWER

                        Re: TDP development

                        ‏2013-05-28T20:53:53Z  in response to richard.france

                        i didn't understand how to add the const into th library code 

                        now making the test pass i have,every time the TDP updated, to manually remove this const  from priv.h and image.h when compiling the .ptu file and later from rtbuffer.c when compiling TP.c

                        • richard.france
                          richard.france
                          811 Posts
                          ACCEPTED ANSWER

                          Re: TDP development

                          ‏2013-05-29T08:40:42Z  in response to 35BX

                          here is the methode body header for the 8.0.0.4 release

                          in rtbuffer.c

                          _ATL_C_GLOBALFCT void _atl_add_error
                          #if !RTRT_KR
                          ( const char *errcode,const char *msg )
                          ........

                          _ATL_C_GLOBALFCT void _atl_error_dump
                          #if !RTRT_KR
                          ( const char icode )
                          ..........

                          into priv.h

                          _ATL_EXTERN_C void _atl_error_dump
                          #if !RTRT_KR
                          ( const char error )
                          .....

                          into image.h

                          _ATL_EXTERN_C ATL_TP_PROTO_PREFIX void _atl_add_error
                          #if !RTRT_KR
                          ( const char *errcode,const char *msg )
                          .............

                          To fix your issue you have to modify your TestRT_Installation/targets/xml/c/lib/rtbuffer.c and other files as shown above then save your TDP.

                          • 35BX
                            35BX
                            9 Posts
                            ACCEPTED ANSWER

                            Re: TDP development

                            ‏2013-05-29T09:23:44Z  in response to richard.france

                            thanks Richard for the reply 

                            Can you tell me  how to use clock target from the simulator for clock interface since sys/time.h is not available in the environment ?

                            Updated on 2013-05-29T09:31:24Z at 2013-05-29T09:31:24Z by 35BX
                            • richard.france
                              richard.france
                              811 Posts
                              ACCEPTED ANSWER

                              Re: TDP development

                              ‏2013-05-30T17:08:46Z  in response to 35BX

                              unfortunately not.

                              I am a TestRT specialist but not a specialist for your target.

                              So I suggest to ask your simulator provider or read the simulator documentation to find how you can get any tick or cycle counter from register or variable.

                              Once you have that info then I could help you on how to use it in the TDP.

                              • This reply was deleted by 35BX 2013-06-06T11:03:15Z.
                              • Deepanjan89
                                Deepanjan89
                                5 Posts
                                ACCEPTED ANSWER

                                Re: TDP development

                                ‏2013-06-25T09:24:41Z  in response to richard.france

                                Hi,

                                I am trying to make a TDP for the softune compiler.can anyone help me with the base TDP i should take for that??

                                I am using RTRT version 7.0.5

                                 

                                Updated on 2013-06-25T09:26:08Z at 2013-06-25T09:26:08Z by Deepanjan89
                                • richard.france
                                  richard.france
                                  811 Posts
                                  ACCEPTED ANSWER

                                  Re: TDP development

                                  ‏2013-06-26T07:44:15Z  in response to Deepanjan89

                                  here is a TDP made for suftune environment.

                                  It may not be complete, but it could be a base.

                                  Attachments

                                  • Deepanjan89
                                    Deepanjan89
                                    5 Posts
                                    ACCEPTED ANSWER

                                    Re: TDP development

                                    ‏2013-06-26T10:02:39Z  in response to richard.france

                                    Thanks Richard.

                                    I have some queries..What is the difference if we test in simulator and if we test on target.

                                    And we are making the tdp for the simulator for that what changes we may require can you tell..

                                     

                                  • This reply was deleted by SahilKulkarni 2014-01-27T12:41:13Z.
                                    • richard.france
                                      richard.france
                                      811 Posts
                                      ACCEPTED ANSWER

                                      Re: TDP development

                                      ‏2013-12-30T12:49:03Z  in response to SahilKulkarni

                                      if you are using studio to build the TTest.obj I suggest to enable the verbose mode in order to get the compilation command used to compile TTest.c

                                      and compare it with your compilation command used in command prompt.

                                      verbose mode can be activated as studio edit menu > preferences > project > verbose output

                                      so missing flags/option can be added into the node settings>build> compilation

                                      • This reply was deleted by SahilKulkarni 2014-01-27T12:38:55Z.
                                      • This reply was deleted by SahilKulkarni 2014-01-27T12:41:03Z.
                                        • richard.france
                                          richard.france
                                          811 Posts
                                          ACCEPTED ANSWER

                                          Re: TDP development

                                          ‏2013-12-31T16:33:54Z  in response to SahilKulkarni

                                          After a quick look at your build log, It seems to me your preprocessing command is too similar to your compilation command and let me think your preprocessing function does not do the right job.

                                          preprocessing means the .i file is the expension of your source file and all includes in 1 file (the .i file) where all macro defines have been replaced by their values.

                                          So check your .i file and make sure you have the source file content and #line in it.

                                          if not read the compiler documentation to find how to make the preprocessing step properly.

                                           

                                          • This reply was deleted by SahilKulkarni 2014-01-27T12:39:06Z.
                              • This reply was deleted by SahilKulkarni 2014-01-27T12:40:57Z.
                                • richard.france
                                  richard.france
                                  811 Posts
                                  ACCEPTED ANSWER

                                  Re: TDP development

                                  ‏2013-12-30T13:08:57Z  in response to SahilKulkarni

                                  I am not familiar with CubeSuite but I guess you should have a documentationthat tell you how to start it using a script that load the code on the target set breakpoints dump data and run the application.

                                  here is an example of TDP that have been done for Renesas RX600 simulator where the HEW is used to debug the code on a RX simulator.

                                  Attachments

                                  • This reply was deleted by SahilKulkarni 2014-01-27T12:40:52Z.
                                    • richard.france
                                      richard.france
                                      811 Posts
                                      ACCEPTED ANSWER

                                      Re: TDP development

                                      ‏2014-01-02T17:07:19Z  in response to SahilKulkarni

                                      The TDP I have provided is for TestRT verion 7.5.0.3 and newer.

                                      TestRT is compatible with all development environment because it generate a standard C code that can be compiled by any compiler.

                                      The adaptation to the user environment is then done by the TDP.

                                      did you check the .i file to make sure this is a preprocessed file ?

                                      can you attach that file D:\TDP\Configuration1\Report\add_aug.c to let me have a look at ?

                                      • This reply was deleted by SahilKulkarni 2014-01-27T12:40:42Z.
                                        • This reply was deleted by SahilKulkarni 2014-01-27T12:40:36Z.
                                        • richard.france
                                          richard.france
                                          811 Posts
                                          ACCEPTED ANSWER

                                          Re: TDP development

                                          ‏2014-01-02T23:21:15Z  in response to SahilKulkarni

                                          I have no idea why your .i file are correct in a location and not in an other location. may be you should restart with a new simple project !!!

                                          nevertheless I can tell you why you have the content of the add.c into the TTest.i

                                          This is because you have the line

                                          #include "add.c" into the PTU file. So I suggest to remove this line from the PTU anyway, and replace by th eline:

                                          #extern int add(int,int);

                                          about the undefined symbol _main, did you try to remove the _ before the main into the startup source file ?

                                          unfortunately I have not this file SO I cannot have better idea about that

                                          • This reply was deleted by SahilKulkarni 2014-01-27T12:39:51Z.
                                          • This reply was deleted by SahilKulkarni 2014-01-27T12:40:26Z.
                                          • SahilKulkarni
                                            SahilKulkarni
                                            6 Posts
                                            ACCEPTED ANSWER

                                            Re: TDP development

                                            ‏2014-01-27T12:48:16Z  in response to richard.france

                                            Hello Richard,

                                            Please help me in Report generation currently I am able to generate Test Result Report but Code Coverage Report is not getting generated. I suspect this is because of the following line in log

                                            exfile="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c

                                            In Log I have observed that -EXFILE option is specified for TTest.c  file. Documentation says that  -EXFILE explicitly specifies the files that are to be excluded from the instrumentation.

                                            So may be because of this code coverage report is not generated so please let me know how to disable or change this option.  

                                            • richard.france
                                              richard.france
                                              811 Posts
                                              ACCEPTED ANSWER

                                              Re: TDP development

                                              ‏2014-01-27T15:18:24Z  in response to SahilKulkarni

                                              TTest.c is always to be excluded from instrumentation because this is the generated Test driver (PTU) code.

                                              even if you #include "mysourceCode.c" into the PTU the #line xx or # xx directives found in the .i file allow to know what part of the code is comming from the source code under test or the test driver itself

                                              check the .i file provide the #line xx or # xx directive.

                                              Q1 Is your code under test part of the PTU ? if yes through #include, or directly using a # at the begin of each line of code ?

                                              please provide the complete build log

                                              • SahilKulkarni
                                                SahilKulkarni
                                                6 Posts
                                                ACCEPTED ANSWER

                                                Re: TDP development

                                                ‏2014-01-28T13:10:06Z  in response to richard.france

                                                Hello Richard,

                                                I have verified the .i file it contains  # line Line_No "Include file Name" in it. Also the .ptu file contains ##include SourceFile.c but still the Coverage Report is not generated also there are warnings like NO FDC generated and for #pragma attol ato_stub "Unrecognized #pragma" how to remove these warnings also find the build log for reference.

                                                 

                                                C:\Program Files\Rational\TestRealTime\bin\intel\win32\utags -sspgtags .\Os_Task.ptu
                                                Preprocessing PTU test script file...
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\attolpreproC "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\Os_Task.ptu"      "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c"      -studio_log="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\intermediates_files444245907.log" -STD_DEFINE="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\ana\atus_c.def" -RENAME=stubs_rename.opt -incl="D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc","D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc","D:\Bangalore\OS\Branches\Generic\RH850_Types\inc","D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc","D:\Bangalore\OS\Branches\OS\Common\ssc\inc","D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc","D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg","..\..\..\..\..\..\Common\ssc\src","D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib","D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report" -family=nominal -service=ActivateTask -NOSIMULATION -FAST
                                                TestRT-I-STARTEXEC,  IBM(R) Rational(R) Test RealTime C Test Script Compiler 7.5.0.0.276.008
                                                TestRT-I-COPYRIGHT,  (C) Copyright IBM Corp. 1992-2008 All Rights Reserved. All rights reserved.
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c: Preprocessing...
                                                ccrh.exe -Xcommon=v850e3v5 -Xpreprocess=line  -c   -I"D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\Generic\RH850_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\OS\Common\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg" -I"..\..\..\..\..\..\Common\ssc\src" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c" > atltmp.i
                                                TestRT-I-ENDNOENWR,  End of execution with 0 error and 0 warning
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(88):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(166):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(244):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(341):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(461):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(554):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(696):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(826):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(960):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1089):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1166):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1244):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1323):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1403):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1483):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(1694):W0520161:Unrecognized #pragma
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(311):W0520177:Function "_atcc_ptr" was declared but never referenced
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c(315):W0520177:Function "_atcc_str" was declared but never referenced
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32/fixlines atltmp.i D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest_aug.i
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\attolcc1 "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest_aug.i" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest_aug.c" atct.def  -exfile="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.c" -noinstrdir="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP" @stubs_rename.opt -proc=ret -call -block=logical -cond=modified -compact   -studio_log="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\intermediates_files444245907.log"
                                                ---
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest_aug.c: Compiling...
                                                ccrh.exe -c -Xcommon=v850e3v5 -Xpreprocess=line -Xcommon=v850e3v5 -g -Xreserve_r2 -Xcheck_div_ov=1 -Xuse_fmaf -Xunordered_cmpf -Xdiv   -I"D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\Generic\RH850_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\OS\Common\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg" -I"..\..\..\..\..\..\Common\ssc\src" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest_aug.c" -o"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.obj"
                                                TestRT attolcc1 - INFO: No branches of requested coverage types can be found in file TTEST_AUG.I; no FDC generated
                                                ---
                                                Os_Task.c: Preprocessing...
                                                ccrh.exe -Xcommon=v850e3v5 -Xpreprocess=line  -c   -I"D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\Generic\RH850_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\OS\Common\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg" -I"..\..\..\..\..\..\Common\ssc\src" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" "D:\Bangalore\OS\Branches\OS\Common\ssc\src\Os_Task.c" > atltmp.i
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32/fixlines atltmp.i D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Os_Task.i
                                                Os_Task.c: Instrumenting using TDP "C Renesas" in "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP"...
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\attolcc1 "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Os_Task.i" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Os_Task_aug.c" atct.def  -noinstrdir="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP" -proc=ret -call -block=logical -cond=modified -compact   -studio_log="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\intermediates_files444245905.log"
                                                ---
                                                Os_Task.c: Compiling...
                                                ccrh.exe -c -Xcommon=v850e3v5 -Xpreprocess=line -Xcommon=v850e3v5 -g -Xreserve_r2 -Xcheck_div_ov=1 -Xuse_fmaf -Xunordered_cmpf -Xdiv   -I"D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\Generic\RH850_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\OS\Common\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg" -I"..\..\..\..\..\..\Common\ssc\src" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Os_Task_aug.c" -o"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Os_Task.obj"
                                                TestRT attolcc1 - INFO: No branches of requested coverage types can be found in file OS_TASK.I; no FDC generated
                                                ---
                                                Compiling D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib\TP.c using D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report/products.h containing C/C++ TDP Library settings...
                                                ccrh.exe -c -Xcommon=v850e3v5 -Xpreprocess=line -Xcommon=v850e3v5 -g -Xreserve_r2 -Xcheck_div_ov=1 -Xuse_fmaf -Xunordered_cmpf -Xdiv    -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" -I"D:\Bangalore\OS\Branches\Generic\AUTOSAR_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Compiler_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\Generic\RH850_Types\inc" -I"D:\Bangalore\OS\Branches\Generic\Startup_Files_Renesas_CubeSuite\inc" -I"D:\Bangalore\OS\Branches\OS\Common\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\ssc\inc" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Cfg" -I"..\..\..\..\..\..\Common\ssc\src" -I"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib\TP.c" -o"D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TP.obj"
                                                D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\Renesas_TDP\lib\atu.c(1749):W0520550:Variable "stop_time" was set but never used
                                                Linking ..\..\Report\Test.abs...
                                                ---
                                                rlink.exe -start=.const,.data,.text/00010000,RESET,VECT/01000000,.EIINTTBL.const/00101000,.data.R,.bss,.stack.bss/FEDF4000 -rom=.data=.data.R -list=add.map  "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Obj\Startup.obj" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\TTest.obj" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TP.obj" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Obj\Vecttbl.obj" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Obj\Appl_Common_Defs.obj" -library=""C:\CC-RH_V1.00.01\V1.00.01\lib\v850e3v5\libc.lib"" -library=""C:\CC-RH_V1.00.01\V1.00.01\lib\v850e3v5\libm.lib"" -library=""C:\CC-RH_V1.00.01\V1.00.01\lib\v850e3v5\libmf.lib"" -library=""C:\CC-RH_V1.00.01\V1.00.01\lib\v850e3v5\libsetjmp.lib""  -output="..\..\Report\Test.abs"

                                                Renesas Optimizing Linker W1.00.00  [12 Dec 2012]
                                                   Copyright (C) 2011, 2012 Renesas Electronics Corporation

                                                W0561100:Cannot find ".EIINTTBL.const" specified in option "start"

                                                Renesas Optimizing Linker Completed
                                                Executing ..\..\Report\Test.abs...
                                                Debugger started flashing : ..\..\Report\Test.abs
                                                C:\CubeSuite+\CubeSuiteW+.exe  /ps "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\TDP\ExecutionScript.py"
                                                Executable terminated with error code 255.
                                                Splitting 'D:\\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Test.spt' traces file...
                                                Traces file successfully split.
                                                Postprocessing...
                                                "C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\attolcov"  "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Test.tio" -su=c -output="Test.atc.txt" -cio="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\atu.cio"
                                                status 255
                                                ---
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\attolpostpro "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.rod"   -studio_log="D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\intermediates_files444245830.log" -VA=EVAL
                                                TestRT attolcov - FATAL ERROR: There is nothing to report ... report is empty
                                                TestRT-I-STARTEXEC,  IBM(R) Rational(R) Test RealTime C and Ada Test Report Generator 7.5.0.0.276.008
                                                TestRT-I-COPYRIGHT,  (C) Copyright IBM Corp. 1992-2008 All Rights Reserved. All rights reserved.
                                                C:\PROGRA~1\Rational\TESTRE~1\bin\intel\win32\rod2xrd -g  -s500 "-hTest.summary.txt" "-lD:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Procedure\Task\intermediates_files444245830.log" "-oD:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\Test.xrd" "D:\Bangalore\OS\Branches\OS\PortSpecific\RH850Renesas\UnitTesting\Configuration1\Report\TTest.rod"
                                                TestRT-W-EXE_ABORT,  FATAL SHUTDOWN DURING EXECUTION
                                                TestRT-W-TEST_ERRO,  Unit Test Report Generator execution completed with incorrect tests
                                                TestRT-I-ENDNOEWAR,  End of execution with 2 warning(s)

                                                Done

                                              • SahilKulkarni
                                                SahilKulkarni
                                                6 Posts
                                                ACCEPTED ANSWER

                                                Re: TDP development

                                                ‏2014-02-20T07:10:06Z  in response to richard.france

                                                 Hello Richard, 

                                                1. For copying atl_buffer we  have used API debugger.Upload.Binary(fileName, address1, address2, force = False) but as address1 and address2 will be dynamic for atl_buffer depending upon number of test cases so how to handle this situation in TDP or in debugger ?
                                                2. When priv_exit function is getting called from RTRT then control from debugger is not going where I have written this function, I have written this function inside pythonScript.py file so how RTRT will come to know where is priv_exit function is implemented? 

                                                Attachments

                                                • richard.france
                                                  richard.france
                                                  811 Posts
                                                  ACCEPTED ANSWER

                                                  Re: TDP development

                                                  ‏2014-02-20T07:58:35Z  in response to SahilKulkarni

                                                  Sometimes we are facing to debugger that cannot use application symbols.

                                                  If this is your case

                                                  the link step must generate the map file then the execution step should read that map file du get the address of the symbols priv_writeln, priv_close, atl_buffer

                                                  then the execution step replace the keyword __PRIV_WRITELN__ by the address of this symbol,

                                                  __EXEFILE__ by the executable (.abs), and so on.

                                                  That require to have a debugger script template in the TDP that will be copied locally and modified as show above.

                                                  all of those modifications are done in perl into the execution function of the TDP.

                                                  • SahilKulkarni
                                                    SahilKulkarni
                                                    6 Posts
                                                    ACCEPTED ANSWER

                                                    Re: TDP development

                                                    ‏2014-02-21T05:51:21Z  in response to richard.france

                                                    Hello Richard,

                                                     

                                                    Thanks for Reply.

                                                    As in Cubesuite debugger i have to create the project then load that project then have to connect to the emulator and then flash the executable but all these steps are done using Debugger provided Python API's,

                                                    So as I do not have Debugger script such as *.cmm file so how to copy atl_buffer?

                                                  • SahilKulkarni
                                                    SahilKulkarni
                                                    6 Posts
                                                    ACCEPTED ANSWER

                                                    Re: TDP development

                                                    ‏2014-03-01T10:58:05Z  in response to richard.france

                                                    Hello Richard,

                                                    Now I am able to pass 1 test case. Test case report is getting generated. Also while code coverage report generation I am getting following 2 errors

                                                    Error thrown during execution: "a composition of conditions reached with an unexpected input vector, contact your vendor" logged in traces file Test.tio
                                                    Error thrown during execution: "a source object was not linked with the right runtime object (check instrumentation mode)" logged in traces file Test.tio

                                                    Also I have tried following solution but it does not work

                                                    In the section:
                                                    Library Settings ->
                                                       For runtime analysis features ->
                                                          Initialized global variable support and checks ->
                                                             RTRT_VARIABLE_INIT_SUPPORTED
                                                    Untick  RTRT_RAM_CLEAN
                                                    Tick     RTRT_RAM_SET_RANDOMLY

                                                    so please help me.