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.

CCS/CCSTUDIO: Building the same project gives different output

Part Number: CCSTUDIO


Tool/software: Code Composer Studio

Hello

I built the same project using two pc, but the two output files are different, and also .map files are different

Computer A is running win7 and CCS8.3.1
Computer B is running win10 and CCS8.3.1

I zip the project on ComputerA , copy to computerB and use "import CCS project" on ComputerB

I triple check that CCS version are the same, all libraries are the same, compiler is the same, platform is the same.

In the map file
- the ENTRY POINT SYMBOL is different
- the amount of used MSMCSRAM is different
- the length of the .text section is different
- input section have different origin address
- output section have different address

As result, the exe from computerA boots correctly from flash (on EVMK2H), the exe from computerB doesnt
Both version run correctly using JTAG

obviously I was expected to have the same .out using 2 computers.

Am I missing something?

Regards

Fabio

  • I do not know what has happened.  But I know a method to help you narrow down the cause of the problem.

    The article Find Source of Code Size Increase shows how to determine which functions have increased in code size the most.  Follow the same method, except that you are interested in any function with a different size.  Focus your investigation on those functions.  I do not know what you will find.  But, whatever it is, it is likely to lead you to the root cause of the problem.

    Please let us know what you find.

    Thanks and regards,

    -George

  • Hi

    using utility 'ofd6x.exe' I found size differences in function such as

    pciev0_write_accr_reg 108 88 20
    pciev0_write_ackFreq_reg 120 116 4
    pciev0_write_capPtr_reg 32 24 8
    pciev0_write_cfgTrans_reg 96 84 12
    pciev0_write_cmdStatus_reg 120 108 12
    pciev0_write_corErrMask_reg 140 116 24
    pciev0_write_corErr_reg 140 116 24
    pciev0_write_devStatCtrl_reg 316 252 64
    pciev0_write_deviceCap_reg 160 136 24

    Using utility winmerge I found that a lot of .se66 files inside directory 'C:\ti\pdk_k2hk_4_0_15' are different . For example

    File \pdk_k2hk_4_0_15\packages\ti\drv\srio\lib\k2h\c66\obj\src\srio_drv.se66, line 130

    COMPUTER_A , line 130

    ; gSrioDriverVersionStr[33] @ 264
    .bits 0x4a,8
    ; gSrioDriverVersionStr[34] @ 272
    .bits 0x75,8
    ; gSrioDriverVersionStr[35] @ 280
    .bits 0x6e,8
    ; gSrioDriverVersionStr[36] @ 288
    .bits 0x20,8
    ; gSrioDriverVersionStr[37] @ 296
    .bits 0x20,8


    COMPUTER_B, line 130

    ; gSrioDriverVersionStr[33] @ 264
    .bits 0x4d,8
    ; gSrioDriverVersionStr[34] @ 272
    .bits 0x61,8
    ; gSrioDriverVersionStr[35] @ 280
    .bits 0x72,8
    ; gSrioDriverVersionStr[36] @ 288
    .bits 0x20,8
    ; gSrioDriverVersionStr[37] @ 296
    .bits 0x31,8

    It seems to me that SRIO DRIVER version is different

    The same happens with
    file '\pdk_k2hk_4_0_15\packages\ti\drv\cppi\lib\c66\obj\src\cppi_drv.se66'
    file '\pdk_k2hk_4_0_15\\packages\ti\drv\hyplnk\lib\c66\obj\src\hyplnk.se66'

    see following figure, how many .se66



    Anyway, I copied 'C:\ti\pdk_k2hk_4_0_15' from ComputerA to ComputerB, and now output files and map files are equal.

    But really I dont understand why pdk directories are different.

    Sounds like TEXAS released two different 'pdk_k2hk_4_0_15' ???

    Regards 

    Fabio

  • Fabio,

    I don't think we published two versions of pdk_k2hk_4_0_15. The latest is here:  

    it should be PDK 4.0.16. The previous one should be here: 

    This is the PDK 4.0.15 you are using. It looks that on both PCs you downloaded the PRSDK installer but the contents are different. Do you still have both installer and the MD5 the same?

    f5da1df3d4086226eb750589e9f4925a  Processor-SDK_RTOS_K2HK_Manifest.html
    dab6c2fc7c8cf668132dedb9591e0dbf  software_manifest_linux.txt
    904ddb14f10c60a74e0c6a1fa367990c  software_manifest_windows.txt
    bac1824d50d135c1a65e4030e800b866  ti-processor-sdk-rtos-k2hk-evm-06.01.00.08-Linux-x86-Install.bin
    5521c707c25c67c3dd15e70210d359ad  ti-processor-sdk-rtos-k2hk-evm-06.01.00.08-Windows-x86-Install.exe

    I am not sure what happened and glad you copied over and resolved the issue anyway.

    Regards, Eric 

  • Hi, I found the same installer on both pc and md5 is the same

    I dont know what happened, anyway problem solved.

    Thank you