• Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 1386 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.

Detecting Target and Loading binary file using scripts

Vinay Kumar37373
Intellectual 315 points
Other Parts Discussed in Thread: OMAP3530

Hi all,

 

Iam using beagle board as my target board and connecting to CCS4 with XDS510PPPlus emulator. here I used some example scritps given in C:\Program Files\Texas Instruments\ccsv4\scripting\examples\ folder , for connecting  and loading  program directly to target with the scripts. I used the loadti.bat  for this automation and  I got good result when i placed the target configuration as simulator as shown below:

 

loadti.bat -c simulator.ccxml C64x.out

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

START: 14:56:47 GMT+0530 (GMT+05:30)

Configuring Debug Server for specified target...
Done
WARNING: Unlicensed
An error occured attempting to acquire a license for this product.
TARGET: C64x+ CPU Cycle Accurate Simulator, Little Endian_0
Connecting to target...
testEnv.outFiles: TI_64x.out
Loading TI_64x.out
Done
Target running...
Interrupt to abort . . .

helloworld
**********NORMAL COMPLETION: 5120 cycles

END: 14:56:49 GMT+0530 (GMT+05:30)

 

similarly I did with the Hardware target configuration file (attached in Zip file naming New target configuration.ccxml ), selecting OMAP3530 proceesor and placing appropriate gel files, and run the command shown below:

loadti.bat -c NewTargetConfiguration.ccxml C64x.out, but here it shown following error:

SEVERE: C64XP_0: Error connecting to the target: Error 0x80000244/-1178 Fatal Error during: Register, Initialization, OCS, The target does not have a CPU clock

and I searched for the error cause it may be due to gel files said in some related posts:

so, any one suggest me and help me in this regard to solve the problem.

 

Thanks in advance,

Vinay.

loadti.zip
  • TI__Expert 8055 points

    Vinay,

    When you boot BeagleBoard, the 64x+ is held in reset by the Arm.  Before CCS or DSS can connect to the 64x+ , it has to be brought out of reset.  There are a few ways that you can handle this.  You can do the memory writes on the ARM that will remove the 64x+ from reset via the ARM Gel File's OnTargetConnect function.  This would require modification of the script that you are running to first open and connect to the ARM to allow the Gel file to execute.  You could also just connect to the ARM with DSS and do the writes directly from the DSS script.  A 3rd option is to flash some code that will remove the 64x+ from reset that the ARM will boot.  In this manner, once the boot code has been executed, you should be able to run this script without modification.

    Regards,

    Dan

  • in reply to DanRinkes
    Intellectual 315 points

    Hi Dan,

     

    thanks for ur reply, I tried with your suggestion, making ARM Gel file OnTargetConnect function to bring 64x+ out of reset by calling some IVA2.2 start up function and used loadti.bat batch file, but it shown same output as I mentioned in previous post.

    one thing I need to inform that Iam facing the problem even to load ARM Binary file to CortexA8 target also. so I need to do anything that avoid errors with in scripts or at gel files. suggest me.

     

    Thanks,

    Vinay.

  • in reply to Vinay Kumar37373
    TI__Expert 8055 points

    Wat kind of error are you getting when you load the ARM .out file?  Are you sure the DSP is out of reset when you execute the ARM Gel function?  The error message that you are getting clearly indicates that the  DSP is still in reset.

    Regards,
    Dan

  • in reply to DanRinkes
    Intellectual 315 points

    Hi Dan,

    when I load ARM.out file the error is:

    SEVERE: C64XP_0: Error connecting to the target: Error 0x80000244/-1178 Fatal Error during: Register, Initialization, OCS, The target does not have a CPU clock

    > Yes I am sure that DSP is out of reset after executing gel function.

    Here I have an doubt that why DSP C64XP_0 target error is coming when I tried to connect to ARM target?

    what will happens if DSP is still in reset condition?

     

    Thanks,

    Vinay.

     

  • in reply to Vinay Kumar37373
    TI__Expert 8055 points

    Vinay,

     

    Yes, that is odd that you get a C64x message when loading the ARM.  Are you sure you clicked on the ARM device within the debug window?  (grasping at straws here). If the DSP is still in reset, then you expect to get the no target clock message.

    Regards,
    Dan

     

  • in reply to DanRinkes
    Intellectual 640 points

    Dan,

    I have the same error message but I think my DSP is still in reset.  The detail setup is described in the link below. 

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/537/t/311654.aspx

    You mentioned that there are 3 methods to debug the DSP side; could you give me the step by step on one method to get the DSP side debug started.

    Regards,

    Sy