• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 510 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.

CCS/TMS320C5517: Can't find source file "...src\C55\rfft64.s" when simulating the tdu test package (VoLIB)

user5926475
Intellectual 270 points

Part Number: TMS320C5517

Tool/software: Code Composer Studio

Hi,

I simulate the VoLIB tdu test project "test_rel_C5510_C55L_COFF" following the "TDU_Test.chm"  the Unit Test Procedures:

1 Open CCS( version 5.5.0.00077),

2 Import Existing  CCS/CCE  Eclipse Project test_rel_C5510_C55L_COFF  in   packages\ti\mas\tdu\test

3 Bulid All the project  to target: test_rel_C5510_C55L_COFF.out

4 Open C55xx Rev3.0 CPU Functional Simulator to debug and load the test_rel_C5510_C55L_COFF.out

5 In the tdusim.c, I step run to the " do_while" loop (  line 1795 to 1801):


  do {
    generate_tone_frame (&tduSim.txSGN, tduSim.frame_size, tx_in_frame);
    if (tduSim.options.overwrite_scr) {
      overwriteScratchBuffers ();
    }
    tduSendIn (tduInst, tx_in_frame, tdu_TX_ONLY);
  } while (!tduSim.txSGN.fileCLOSE);

when  looping 26 times, A message " Can't find a source file at "M:\TI_MAS_VOLIB_2_1_0_1_bldforge\dsps_gtmas\ti\mas\tdu/src\c55\rfft64.s" " will appear in tduSendIn  and  simulating halt.

I don't know what is wrong,

The VoLIB package is "ti_mas_volib_2_1_0_1_C55_cpu3_Win32.exe". With the same package the ecu simulating is ok.


Best Regard,

Dudechao

  • 0
    TI__Guru**** 484151 points

    Hello,

    user5926475 said:
    when  looping 26 times, A message " Can't find a source file at "M:\TI_MAS_VOLIB_2_1_0_1_bldforge\dsps_gtmas\ti\mas\tdu/src\c55\rfft64.s" " will appear in tduSendIn  and  simulating halt.

    I can't the halt, but I can explain the error message:

    https://e2e.ti.com/support/tools/ccs/f/81/t/738885?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

    user5926475 said:
    The VoLIB package is "ti_mas_volib_2_1_0_1_C55_cpu3_Win32.exe". With the same package the ecu simulating is ok.

    I'm not sure I understand what is happening. You said that when you use the above package, that it works fine. But based on the error message, that same version of the package (VOLIB 2.1.0.1) is being used. Where did you get the package when you get the error?

    Thanks

    ki 

  • 0 in reply to Ki
    Intellectual 270 points

    Hello Ki,

    Can  the message be ignored in normal run? It is harmless, only appar in debug when no  source found?

    I also simulate the tdu test in package "ti_mas_volib_2_1_0_1_C55_Win32.exe", the same  message appears as it does in the  package "ti_mas_volib_2_1_0_1_C55_cpu3_Win32.exe".

    "The VoLIB package is "ti_mas_volib_2_1_0_1_C55_cpu3_Win32.exe". With the same package the ecu simulating is ok.", I mean that in the same package, the ecu test simulating is fine, but the TDU test appear this message. the ecu and the tdu are two different components in the same packages(VOLIB2.1.0.1).

    Best Regards,

    Dudechao

  • 0 in reply to user5926475
    TI__Guru**** 484151 points

    user5926475 said:
    Can  the message be ignored in normal run? It is harmless, only appar in debug when no  source found?

    Basically yes. It does not impact application execution or performance.

    user5926475 said:
    "The VoLIB package is "ti_mas_volib_2_1_0_1_C55_cpu3_Win32.exe". With the same package the ecu simulating is ok.", I mean that in the same package, the ecu test simulating is fine, but the TDU test appear this message. the ecu and the tdu are two different components in the same packages(VOLIB2.1.0.1).

    I will need to bring this thread to the attention of the device experts.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 484151 points

    Ki said:
    I will need to bring this thread to the attention of the device experts.

    Before I do that, I just want to confirm if the TDU test does not run as expected. The message itself is not to be concerned about. 

  • 0 in reply to Ki
    Intellectual 270 points

    Hello Ki,

    It take me a long time to run to the end with all the breakpoints assumed, and get the result file "testrep.txt", I attach it here and it seem right.

    Best Regards,

    Dudechao

    testrep.txt

  • 0 in reply to user5926475
    TI__Guru**** 484151 points

    user5926475 said:
    It take me a long time to run to the end with all the breakpoints assumed, and get the result file "testrep.txt", I attach it here and it seem right.

    Ok, then the issue was just the warning about the source file lookup (which can be ignored).

    I think we can close this thread.

    Thanks

    ki