• Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 852 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.

I am trying to debug Hello World program of NDK for my evm8148 and I am getting this error. Can anyone help me out??

Touseef
Intellectual 280 points
Other Parts Discussed in Thread: SYSBIOS

I am using CCS 6.1, XDC 3.25.0.48 ,ndk_2_24_03_35 and nsp_1_10_03_15 

This is the error I am getting 

Description Resource Path Location Type
template generation of 'C:\Users\touseef.elahi\workspace_v6_1\ndk_evm6748_elf_helloWorld/src/sysbios/makefile' failed: InternalError: XDC runtime error: ti.sysbios.family.c64p.EventCombiner/common$: no property named 'outPolicy' .xdchelp /ndk_evm6748_elf_helloWorld line 667 C/C++ Problem

  • Intellectual 280 points
    I have changed the XDS, now I am getting these errors...

    Description Resource Path Location Type
    #10010 errors encountered during linking; ndk_evm6748_elf_helloWorld C/C++ Problem
    <a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain ndk_evm6748_elf_helloWorld C/C++ Problem
    unresolved symbol NDK_recvncfree, first referenced in ./udpHello.obj ndk_evm6748_elf_helloWorld C/C++ Problem
    unresolved symbol NDK_recvncfrom, first referenced in ./udpHello.obj ndk_evm6748_elf_helloWorld C/C++ Problem
    unresolved symbol NDK_sendto, first referenced in ./udpHello.obj ndk_evm6748_elf_helloWorld C/C++ Problem
    unresolved symbol NDK_setsockopt, first referenced in ./udpHello.obj ndk_evm6748_elf_helloWorld C/C++ Problem
    unresolved symbol NIMUDeviceTable, first referenced in C:\ti\tirtos_c6000_2_00_01_23\products\ndk_2_23_01_01\packages\ti\ndk\stack\lib\stk6.ae674<nimu.oe674> ndk_evm6748_elf_helloWorld C/C++ Problem
    Build variable 'NDK_INSTALL_DIR' cannot be resolved. ndk_evm6748_elf_helloWorld properties Problems
    Invalid project path: Include path not found (\packages\ti\ndk\inc). ndk_evm6748_elf_helloWorld pathentry Path Entry Problem
    Invalid project path: Include path not found (\packages\ti\ndk\inc\tools). ndk_evm6748_elf_helloWorld pathentry Path Entry Problem
  • Intellectual 280 points
    Now Build done, I am getting this error. I am using TI XDS100v2 USB Debug probe

    Error connecting to the target:
    (Error -1180 @ 0x0)
    Device is held in reset. Take the device out of reset, and retry the operation.
    (Emulation package 6.0.14.5)

    and I get this error when I restart the EVM

    Error connecting to the target:
    (Error -6310) PRSC module failed to read a register.
    (Emulation package 6.0.14.5)
  • in reply to Touseef
    TI__Guru**** 173310 points

    Touseef said:
    Error connecting to the target:
    (Error -1180 @ 0x0)
    Device is held in reset. Take the device out of reset, and retry the operation.
    (Emulation package 6.0.14.5)

    Sorry about the delayed reply, this post seems to have fallen through the cracks.

    If you are still experiencing connection issues, I would suggest taking a look at this wiki page first. If that still does not help, please post to the DM814x device forum so the experts there can provide additional comments.

  • in reply to Touseef
    Prodigy 225 points

    I used the exact same USB (TI XDS100v2 USB Debug probe).  I found the easiest way to reset this error is to unplug the probe, reset the development board, and plug the probe back.

    Usually what caused the error was a bad executable causing a crash (I was working with a test tool called IBM - RTRT at the time which creates a wrapper to facilitate code coverage for safety-critical flight code).

    I would suggest resetting the development board as stated above but then try running a simple hello world' program to see if you can connect to the target and get something up and running again.  Once you know you are good with a simple program you will know the issue has something to do with the image and not the CCS configuration.  Then it's up to some reading and engineering to solve what could be happening.

    Hope the information above provides the necessary steps to rest the development board & probe and the simple 'hello world' gives you some confidence that the problem is not in the software configuration (linker cmd file, target config ccxml, etc) but rather in the executable.