• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 509 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.

ERROR: cannot access file all.x64P (in the WINCE6.0)

xu haiyang
Prodigy 120 points
hi, I want to run the apps of audio_copy of the codec_engine_2_24_01, and I find that dsplinkk.dll, cmemk.dll, lpmdrv.dll and timm.dll has insert into the NK.bin. When I run the app_remote_wince.exe, the info of the GT as follows: @56,913,000us: [+0 T:0x053f0016 S:0x0004fad8] CE - rserverOpen('all.x64P'), count = 0 @56,927,000us: [+0 T:0x053f0016 S:0x0004faa8] OP - Processor_create> Enter(imageName='all.x64P', linkCfg='(null)', attrs=0x4faec) @56,951,000us: [+7 T:0x053f0016 S:0x0004faa8] OP - Processor_create> ERROR: cannot access file all.x64P @56,969,000us: [+6 T:0x053f0016 S:0x0004fad8] CE - rserverOpen: can't start 'all.x64P'; Processor_create failed @56,989,000us: [+0 T:0x053f0016 S:0x0004fad8] CE - rserverOpen('all.x64P'): 0x0 done. @57,017,000us: [+0 T:0x053f0016 S:0x0004faf0] CS - Server_disconnectTrace('0x51c80', 0x0) @57,033,000us: [+0 T:0x053f0016 S:0x0004faf0] CS - Server_connectTrace> return(0) ....... @57,115,000us: [+1 T:0x053f0016 S:0x0004fb60] ZZ - error: can't open engine At first, I assume that it is the attribute of the all.x64P, so I change the project.bib to the follows, but it does not works too. So I am confused by the errors. FILES ; Name Path Memory Type ; -------------- --------------------------------------------- ----------- ;-- by sea ------------------------------------------------------------------ app_remote_wince.exe $(_FLATRELEASEDIR)\app_remote_wince.exe NK U all.x64P $(_FLATRELEASEDIR)\all.x64P NK U in.dat $(_FLATRELEASEDIR)\in.dat NK U ;----------------------------------------------------------------------------- If anyone account for this problem, do me a favor please! Thanks a !lot
  • 0
    TI__Mastermind 22760 points

    Did you export the file using the remote file viewer? You can do this in Platform Builder by selecting the Menu:

        Target --> Remote Tools --> File Viewer

    In the remote file viewer,  select:

        File --> Export File

    and browse to the directory where you have the all.x64P file.

    Regards,

        Janet

  • 0 in reply to janet
    Prodigy 120 points
    hi, janet Thanks for your reply, I have solved this problem, but the reason isn't what you apply. I just add the sentence "myEngine.server = "windows\\\\all.x64P";" to the remote.cfg, and it's OK! But I don't figure out the problem. Can you give me some inspiration.
  • 0 in reply to xu haiyang
    TI__Mastermind 22760 points

    Hi Xu,

    Maybe in your case, the all.x64P is built into your image, and is sitting in the Windows directory. So when you changed "myEngine.server" to "windows\\\\all.x64P", you gave the correct full path to the server.  If you were to import the file using the remote file viewer at the root of the WinCE file system, then setting "myEngine.server" to just "all.x64P" would be sufficient for the file to be found.

    Regards,

        Janet

  • 0 in reply to janet
    TI__Genius 9185 points

    xu haiyang: Is your issue resolved? If so, could you please select the "Verify Answer" button for the relevant answer post. Thanks.

     

     

     

  • 0 in reply to Jatin Jain
    Prodigy 120 points

    hi,Jatin Jain,

          Thanks for reminding me. I am so sorry for that.