• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 55 subscribers
  • Views 1469 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.

problem in loaing a .out file using command line options

chandrakala madhira
Prodigy 110 points

Hi

how to load a .out file in CCS4.0 without having a project or workspace created. I have a .out file which is generated using makefiles, and now i want to run the .out file.  Is there any command to do that.

Thanks in advance

  • 0
    TI__Guru**** 482841 points

    You can right-click on your target configuration file in the Target Configurations view and launch a debug session for it without a project. This video has an example of creating a target configuration file and launching a debug session for it.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    Thank you very much ki.

    By doing this iam able to launch the debugger session, but not able to run the .out file, which i have generated using makefiles. can you please provide any information on this.

    Thank you

    Chandrakala

  • 0 in reply to chandrakala madhira
    Prodigy 110 points

    ki,

    Iam able to run my .out file by launching debugger session.

    Thanks

    Chandrakala

  • 0 in reply to chandrakala madhira
    Prodigy 30 points

    Hi,

    please tell me how to run .out file without using debugger. My CCS crashes every time I try to run the debugger :(

    Any suggestions ?

  • 0 in reply to Deyan Vitanov
    TI__Guru**** 482841 points

    Hi Deyan,

    Deyan Vitanov said:
    please tell me how to run .out file without using debugger.

    Are you looking for a way to run your program outside CCS?

    Deyan Vitanov said:
    My CCS crashes every time I try to run the debugger

    If you can provide the information as requested in this post, we can try an investigate the crash.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points

    Here is the information:

    Host: Windows 7 64bit Professional

    IDE Version: Version: 4.1.1.00014

    LOG:

    Fullscreen 5238.hs_err_pid3184.log Download 
    #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  Internal Error (0xe06d7363), pid=3184, tid=3108
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_14-b03 mixed mode)
# Problematic frame:
# C  [KERNELBASE.dll+0xb727]
#

---------------  T H R E A D  ---------------

Current thread (0x4933bef8):  JavaThread "pool-2-thread-1" [_thread_in_native, id=3108]

siginfo: ExceptionCode=0xe06d7363, ExceptionInformation=0x19930520 0x4b42ecb8 0x4aabbcc0 

Registers:
EAX=0x4b42ebc4, EBX=0x71e8334a, ECX=0x00000003, EDX=0x00000000
ESP=0x4b42ebc4, EBP=0x4b42ec14, ESI=0x4b42ee5c, EDI=0x4a7945e0
EIP=0x7707b727, EFLAGS=0x00000212

Top of Stack: (sp=0x4b42ebc4)
0x4b42ebc4:   e06d7363 00000001 00000000 7707b727
0x4b42ebd4:   00000003 19930520 4b42ecb8 4aabbcc0
0x4b42ebe4:   0000006f 6f8b3958 0000006e 4a7945e0
0x4b42ebf4:   4b42ecc4 71e8334a 4aade968 6f8b49ea
0x4b42ec04:   4b42ec9c 00000000 ffffffff 4b42ecb8
0x4b42ec14:   4b42ec4c 71e58e89 e06d7363 00000001
0x4b42ec24:   00000003 4b42ec40 e06d7363 00000001
0x4b42ec34:   00000000 00000000 00000003 19930520 

Instructions: (pc=0x7707b727)
0x7707b717:   0c eb 03 89 45 c0 8d 45 b0 50 ff 15 6c 11 07 77
0x7707b727:   c9 c2 10 00 cc cc cc cc cc 8b ff 55 8b ec 56 8b 


Stack: [0x4b3f0000,0x4b430000),  sp=0x4b42ebc4,  free space=250k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [KERNELBASE.dll+0xb727]
C  [MSVCR80.dll+0x28e89]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Ljava/lang/Object;Ljava/lang/String;[Ljava/lang/Object;Ljava/lang/String;)Ljava/lang/Object;+0
j  org.mozilla.xpcom.internal.XPCOMJavaProxy$3.call()Ljava/lang/Object;+16
j  java.util.concurrent.FutureTask$Sync.innerRun()V+22
j  java.util.concurrent.FutureTask.run()V+4
j  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Ljava/util/concurrent/ScheduledThreadPoolExecutor$ScheduledFutureTask;)V+1
j  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run()V+15
j  java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Ljava/lang/Runnable;)V+43
j  java.util.concurrent.ThreadPoolExecutor$Worker.run()V+28
j  java.lang.Thread.run()V+11
v  ~StubRoutines::call_stub

---------------  P R O C E S S  ---------------

Java Threads: ( => current thread )
  0x49437cc8 JavaThread "Worker-12" [_thread_blocked, id=2712]
  0x49437520 JavaThread "Worker-11" [_thread_blocked, id=1396]
  0x4933cb38 JavaThread "polling thread" daemon [_thread_blocked, id=1392]
=>0x4933bef8 JavaThread "pool-2-thread-1" [_thread_in_native, id=3108]
  0x4926ad38 JavaThread "Worker-10" [_thread_blocked, id=2452]
  0x4926a718 JavaThread "Worker-6" [_thread_blocked, id=684]
  0x45f37940 JavaThread "StandardManager[/help]" daemon [_thread_blocked, id=2692]
  0x45f377b8 JavaThread "TP-Monitor" daemon [_thread_blocked, id=396]
  0x45f37630 JavaThread "TP-Processor4" daemon [_thread_blocked, id=1764]
  0x45f374a8 JavaThread "TP-Processor3" daemon [_thread_blocked, id=3452]
  0x45f37320 JavaThread "TP-Processor2" daemon [_thread_in_native, id=3216]
  0x45f37198 JavaThread "TP-Processor1" daemon [_thread_blocked, id=3584]
  0x45f36d00 JavaThread "StandardManager[]" daemon [_thread_blocked, id=1660]
  0x45f36868 JavaThread "org.eclipse.jface.text.reconciler.MonoReconciler" daemon [_thread_blocked, id=1692]
  0x44b78340 JavaThread "Start Level Event Dispatcher" daemon [_thread_blocked, id=3432]
  0x44b7e5d0 JavaThread "Framework Event Dispatcher" daemon [_thread_blocked, id=3044]
  0x44b29810 JavaThread "traceMsgQueueThread" daemon [_thread_blocked, id=952]
  0x44b043a0 JavaThread "State Data Manager" daemon [_thread_blocked, id=2408]
  0x44576fb0 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=2828]
  0x003dba58 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2520]
  0x44576e28 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1656]
  0x003db070 JavaThread "Finalizer" daemon [_thread_blocked, id=3052]
  0x003d9298 JavaThread "Reference Handler" daemon [_thread_blocked, id=3368]
  0x0060b438 JavaThread "main" [_thread_in_Java, id=2044]

Other Threads:
  0x003d5298 VMThread [id=3872]
  0x0060fbc0 WatcherThread [id=2232]

VM state:not at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread: None

Heap
 def new generation   total 18240K, used 7419K [0x04020000, 0x053e0000, 0x06780000)
  eden space 16256K,  39% used [0x04020000, 0x04674580, 0x05000000)
  from space 1984K,  47% used [0x051f0000, 0x052da800, 0x053e0000)
  to   space 1984K,   0% used [0x05000000, 0x05000000, 0x051f0000)
 tenured generation   total 241984K, used 54681K [0x06780000, 0x153d0000, 0x24020000)
   the space 241984K,  22% used [0x06780000, 0x09ce6678, 0x09ce6800, 0x153d0000)
 compacting perm gen  total 45824K, used 45813K [0x24020000, 0x26ce0000, 0x44020000)
   the space 45824K,  99% used [0x24020000, 0x26cdd4c0, 0x26cdd600, 0x26ce0000)
No shared spaces configured.

Dynamic libraries:
0x00400000 - 0x0040d000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\javaw.exe
0x77bc0000 - 0x77d40000 	C:\Windows\SysWOW64\ntdll.dll
0x76d20000 - 0x76e20000 	C:\Windows\syswow64\kernel32.dll
0x77070000 - 0x770b6000 	C:\Windows\syswow64\KERNELBASE.dll
0x76500000 - 0x765a0000 	C:\Windows\syswow64\ADVAPI32.dll
0x76e20000 - 0x76ecc000 	C:\Windows\syswow64\msvcrt.dll
0x773c0000 - 0x773d9000 	C:\Windows\SysWOW64\sechost.dll
0x76920000 - 0x76a10000 	C:\Windows\syswow64\RPCRT4.dll
0x75730000 - 0x75790000 	C:\Windows\syswow64\SspiCli.dll
0x75720000 - 0x7572c000 	C:\Windows\syswow64\CRYPTBASE.dll
0x773e0000 - 0x774e0000 	C:\Windows\syswow64\USER32.dll
0x75790000 - 0x75820000 	C:\Windows\syswow64\GDI32.dll
0x76bd0000 - 0x76bda000 	C:\Windows\syswow64\LPK.dll
0x77320000 - 0x773bd000 	C:\Windows\syswow64\USP10.dll
0x77170000 - 0x771d0000 	C:\Windows\system32\IMM32.DLL
0x771d0000 - 0x7729c000 	C:\Windows\syswow64\MSCTF.dll
0x6d640000 - 0x6d7de000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\client\jvm.dll
0x732e0000 - 0x73312000 	C:\Windows\system32\WINMM.dll
0x730a0000 - 0x730eb000 	C:\Windows\system32\apphelp.dll
0x6d290000 - 0x6d298000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\hpi.dll
0x77b90000 - 0x77b95000 	C:\Windows\syswow64\PSAPI.DLL
0x6d610000 - 0x6d61c000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\verify.dll
0x6d310000 - 0x6d32d000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\java.dll
0x6d630000 - 0x6d63f000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\zip.dll
0x6d4d0000 - 0x6d4e3000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\net.dll
0x77030000 - 0x77065000 	C:\Windows\syswow64\WS2_32.dll
0x76a30000 - 0x76a36000 	C:\Windows\syswow64\NSI.dll
0x73dc0000 - 0x73dfc000 	C:\Windows\system32\mswsock.dll
0x74bc0000 - 0x74bc6000 	C:\Windows\System32\wship6.dll
0x6d4f0000 - 0x6d4f9000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\nio.dll
0x6d1f0000 - 0x6d203000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\deploy.dll
0x76a40000 - 0x76b34000 	C:\Windows\syswow64\WININET.dll
0x75850000 - 0x758a7000 	C:\Windows\syswow64\SHLWAPI.dll
0x76a20000 - 0x76a23000 	C:\Windows\syswow64\Normaliz.dll
0x76be0000 - 0x76d15000 	C:\Windows\syswow64\urlmon.dll
0x76ed0000 - 0x7702c000 	C:\Windows\syswow64\ole32.dll
0x770e0000 - 0x7716f000 	C:\Windows\syswow64\OLEAUT32.dll
0x765a0000 - 0x766bc000 	C:\Windows\syswow64\CRYPT32.dll
0x76a10000 - 0x76a1c000 	C:\Windows\syswow64\MSASN1.dll
0x76720000 - 0x76919000 	C:\Windows\syswow64\iertutil.dll
0x758b0000 - 0x764f9000 	C:\Windows\syswow64\SHELL32.dll
0x75600000 - 0x7560b000 	C:\Windows\system32\profapi.dll
0x6d5c0000 - 0x6d5e5000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\RegUtils.dll
0x75640000 - 0x75649000 	C:\Windows\system32\VERSION.dll
0x6fc60000 - 0x6fea0000 	C:\Windows\system32\msi.dll
0x73f30000 - 0x740ce000 	C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.dll
0x74d30000 - 0x74d74000 	C:\Windows\system32\dnsapi.DLL
0x73eb0000 - 0x73ecc000 	C:\Windows\system32\iphlpapi.DLL
0x755c0000 - 0x755c7000 	C:\Windows\system32\WINNSI.DLL
0x74cd0000 - 0x74d22000 	C:\Windows\system32\RASAPI32.dll
0x74cb0000 - 0x74cc5000 	C:\Windows\system32\rasman.dll
0x74ca0000 - 0x74cad000 	C:\Windows\system32\rtutils.dll
0x74c90000 - 0x74c96000 	C:\Windows\system32\sensapi.dll
0x45800000 - 0x45852000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.osgi\bundles\221\1\.cp\swt-win32-3232.dll
0x772a0000 - 0x7731b000 	C:\Windows\syswow64\comdlg32.dll
0x72760000 - 0x72781000 	C:\Windows\system32\MSVFW32.dll
0x73130000 - 0x731b0000 	C:\Windows\system32\uxtheme.dll
0x732c0000 - 0x732d3000 	C:\Windows\system32\dwmapi.dll
0x45990000 - 0x45998000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.osgi\bundles\173\1\.cp\os\win32\x86\localfile_1_0_0.dll
0x459a0000 - 0x459a8000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.osgi\bundles\177\1\.cp\os\win32\x86\win32refresh.dll
0x730f0000 - 0x7312c000 	C:\Windows\system32\oleacc.dll
0x466e0000 - 0x466f3000 	C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.osgi\bundles\221\1\.cp\swt-gdip-win32-3232.dll
0x72990000 - 0x72b20000 	C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_72fc7cbf861225ca\gdiplus.dll
0x73e60000 - 0x73e76000 	C:\Windows\system32\CRYPTSP.dll
0x73e20000 - 0x73e5b000 	C:\Windows\system32\rsaenh.dll
0x73e10000 - 0x73e1e000 	C:\Windows\system32\RpcRtRemote.dll
0x76b40000 - 0x76bc3000 	C:\Windows\syswow64\CLBCatQ.DLL
0x728c0000 - 0x728ee000 	C:\Windows\system32\mlang.dll
0x71010000 - 0x71a8c000 	C:\Windows\SysWOW64\ieframe.dll
0x73ed0000 - 0x73f2f000 	C:\Windows\system32\SXS.DLL
0x73db0000 - 0x73db5000 	C:\Windows\System32\wshtcpip.dll
0x74c20000 - 0x74c30000 	C:\Windows\system32\NLAapi.dll
0x74bb0000 - 0x74bb6000 	C:\Windows\system32\rasadhlp.dll
0x74c00000 - 0x74c08000 	C:\Windows\System32\winrnr.dll
0x74bf0000 - 0x74c00000 	C:\Windows\system32\napinsp.dll
0x74bd0000 - 0x74be2000 	C:\Windows\system32\pnrpnsp.dll
0x74b70000 - 0x74ba8000 	C:\Windows\System32\fwpuclnt.dll
0x7c000000 - 0x7c054000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\msvcr70.dll
0x7c080000 - 0x7c0f7000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\msvcp70.dll
0x7c140000 - 0x7c23d000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\mfc70.dll
0x48700000 - 0x48711000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\cToolsIF.dll
0x48880000 - 0x488e8000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\ctools.dll
0x48ae0000 - 0x48cd2000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\xerces-c_2_5_0.dll
0x71e30000 - 0x71ecb000 	C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll
0x488f0000 - 0x48906000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\JTrace.dll
0x48910000 - 0x4891f000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\TraceFactory.dll
0x48940000 - 0x48982000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\ICECD.dll
0x48ce0000 - 0x48d01000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\icestorm21.dll
0x48d10000 - 0x48d2f000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\iceutil21.dll
0x48d30000 - 0x48e0c000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\ice21.dll
0x48e10000 - 0x48e2c000 	C:\Program Files (x86)\Texas Instruments\ccsv4\emulation\analysis\bin\LIBBZ2.dll
0x73290000 - 0x73295000 	C:\Windows\system32\msimg32.dll
0x6e1b0000 - 0x6e763000 	C:\Windows\SysWOW64\mshtml.dll
0x74b30000 - 0x74b5a000 	C:\Windows\SysWOW64\msls31.dll
0x72750000 - 0x7275b000 	C:\Windows\system32\msimtf.dll
0x48e50000 - 0x48e57000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\bin\win32\LibraryLoader.dll
0x6f8b0000 - 0x6f937000 	C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCP80.dll
0x4a7e0000 - 0x4a843000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\CCReg.dll
0x4a860000 - 0x4a8b1000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\Logger.dll
0x4a8d0000 - 0x4a963000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\rtdx.dll
0x4a970000 - 0x4ab0b000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\setup_parser.dll
0x4ab20000 - 0x4ab2b000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\jtagdata.dll
0x4ab30000 - 0x4ab3e000 	C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin\ti_targetdb_parser.dll
0x4ab50000 - 0x4ab57000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\javaxpcomglue.dll
0x4ab60000 - 0x4ab88000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\nspr4.dll
0x73e00000 - 0x73e07000 	C:\Windows\system32\WSOCK32.dll
0x4ab90000 - 0x4ab97000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\plc4.dll
0x4aba0000 - 0x4aba6000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\plds4.dll
0x4abb0000 - 0x4ac22000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\js3250.dll
0x4ac30000 - 0x4b314000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\xul.dll
0x731d0000 - 0x73221000 	C:\Windows\system32\WINSPOOL.DRV
0x71f30000 - 0x71f96000 	C:\Windows\system32\MSVCP60.dll
0x4b320000 - 0x4b326000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\xpcom.dll
0x6f7f0000 - 0x6f8a2000 	C:\Windows\SysWow64\jscript.dll
0x731b0000 - 0x731bb000 	C:\Windows\system32\ImgUtil.dll
0x72740000 - 0x7274e000 	C:\Windows\SysWOW64\pngfilt.dll
0x73230000 - 0x73251000 	C:\Windows\system32\ntmarta.dll
0x77540000 - 0x77585000 	C:\Windows\syswow64\WLDAP32.dll
0x77590000 - 0x7772d000 	C:\Windows\syswow64\SETUPAPI.dll
0x75820000 - 0x75847000 	C:\Windows\syswow64\CFGMGR32.dll
0x770c0000 - 0x770d2000 	C:\Windows\syswow64\DEVOBJ.dll
0x72470000 - 0x72565000 	C:\Windows\system32\propsys.dll
0x4bd80000 - 0x4bf1f000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32\components\mdex.dll
0x73330000 - 0x73341000 	C:\Windows\system32\NETAPI32.dll
0x73da0000 - 0x73da9000 	C:\Windows\system32\netutils.dll
0x73350000 - 0x73369000 	C:\Windows\system32\srvcli.dll
0x73320000 - 0x7332f000 	C:\Windows\system32\wkscli.dll
0x4bf30000 - 0x4c1ad000 	C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\license\mdexutil.dll

VM Arguments:
jvm_args: -Xms256m -Xmx512m -XX:MaxPermSize=512m -DXPCOM.RUNTIME=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32 -Dxpcom.bridge.executeOnDedicatedThread=yes -Dorg.eclipse.swt.browser.XULRunnerPath=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32 -Dosgi.instance.area.default=file:/C:/Users/flashman/Documents/workspace/
java_command: C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\startup.jar -os win32 -ws win32 -arch x86 -launcher C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\eclipse.exe -name Eclipse -showsplash 600 -exitdata 40c_cc -vm C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\javaw.exe -vmargs -Xms256m -Xmx512m -XX:MaxPermSize=512m -DXPCOM.RUNTIME=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32 -Dxpcom.bridge.executeOnDedicatedThread=yes -Dorg.eclipse.swt.browser.XULRunnerPath=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32 -Dosgi.instance.area.default=file:/C:/Users/flashman/Documents/workspace/ -jar C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\startup.jar
Launcher Type: SUN_STANDARD

Environment Variables:
PATH=C:\Program Files (x86)\Texas Instruments\ccsv4\common\bin;C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif;C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\slicense;C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\..\common\bin;C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\..\common\uscif;C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\..\DebugServer\license;C:/Program Files/Texas Instruments/xdctools_3_16_02_32;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\system32\wbem;C:\Windows\system32\windowspowershell\v1.0\;c:\program files (x86)\ati technologies\ati.ace\core-static;C:\Program Files (x86)\MATLAB71\bin\win32;;c:\mspgcc\bin;C:/Program Files/Texas Instruments/xdctools_3_16_02_32;C:\Sun\SDK\bin;C:\Program Files (x86)\OpenVPN\bin
USERNAME=flashman
OS=Windows_NT
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 26 Stepping 5, GenuineIntel



---------------  S Y S T E M  ---------------

OS: Windows NT 6.1 Build 7600 

CPU:total 8 (cores per cpu 8, threads per core 2) family 6 model 10 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, ht

Memory: 4k page, physical 4194303k(4192020k free), swap 4194303k(4194303k free)

vm_info: Java HotSpot(TM) Client VM (1.5.0_14-b03) for windows-x86, built on Oct  5 2007 01:21:52 by "java_re" with MS VC++ 6.0

    PROJECT SOURCE: 7532.TRF7960_demo.rar

    If there is any way to tell me how to start this executable .out file, I'll be glad :)

    10x

  • 0 in reply to Ki
    Prodigy 50 points

    Did You try with loadti?

    http://tiexpressdsp.com/index.php/Loadti

  • 0 in reply to andreiltd
    Prodigy 30 points

    ***** DSS Generic Loader *****

    START: 00:15:44 GMT+0200 (EET)

    Configuring Debug Server for specified target...
    Done
    #
    # An unexpected error has been detected by HotSpot Virtual Machine:
    #
    #  Internal Error (0xe06d7363), pid=1680, tid=2332
    #
    # Java VM: Java HotSpot(TM) Client VM (1.5.0_14-b03 mixed mode)
    # Problematic frame:
    # C  [KERNELBASE.dll+0xb727]
    #
    # An error report file with more information is saved as hs_err_pid1680.log
    #
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    #

     

    I'm almost sure that is some configuration issue...

    I'm not so familiar with all this ccs project configurations

  • 0 in reply to Deyan Vitanov
    Prodigy 85 points

    Hello Deyan,

    I am seeing a similar crash (same condition, same java stack trace in the log) on a Windows XP system when trying to start the debugger as a non-admin user, even though the user has full control on the whole CCS v4 tree. However, the jvm no longer crashes when I add the user to the Administrators group.

    I hope this problem can be fixed soon because working with admin privileges is only a temporary workaround for me.

    Robin

     

  • 0 in reply to Rob'in
    Intellectual 670 points

    Hi,

    I have also found this problem, but I'm already an Administrator.

    loadti.bat -c="c:/temp/C28027_XDS100.ccxml" c:/temp/a.out"

    ***** DSS Generic Loader *****

    START: 17:31:39 GMT+0100 (BST)

    Configuring Debug Server for specified target...
    Done
    #
    # An unexpected error has been detected by HotSpot Virtual Machine:
    #
    #  Internal Error (0xe06d7363), pid=2516, tid=2488
    #
    # Java VM: Java HotSpot(TM) Client VM (1.5.0_14-b03 mixed mode)
    # Problematic frame:
    # C  [kernel32.dll+0x1eb33]
    #
    # An error report file with more information is saved as hs_err_pid2516.log
    #
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    #

    C:\Program Files\Texas Instruments\ccsv4\scripting\examples\loadti>

    I've attached a log of the java dump as well.

    My PC is running windows XP and I'm developing a stand along application for the piccolo A USB stick.

    I've un-installed all java JDKs and JRE, CCS4 and re-installed CCS4, but that didn't work.

    I have another PC (that's got a lot less apps installed) with the same version of CCS4, test code, etc which works fine. So I know it's not my test code, hardware or target file.

    I'm guessing it's some interaction between CCS4 and some software on my PC. I thought the Loadit.bat set up every path possible so it should pull in the correct jar files.

    I've also attached the pass/fail files output with the environment variables just before calling the java command line, but they both look pretty much the same.

     

    cheers Chris

    errorlog_pass_fail.zip