• Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 765 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.

Executing AXF generated by ARM DS-5 using TI USB Onboard Emulator

Barath Ramesh
Intellectual 360 points


Hi,

I compiled a simple hello world code using DS-5 for Cortex-A15 in TCI6638. The scatter file I used is as shown below:

;**************************************************
; Copyright (c) 2011 ARM Ltd.  All rights reserved.
;**************************************************

; Scatter-file for RAM based example on OMAP4430

; This scatter-file places application code, data, stack and heap at suitable addresses in the memory map.

; OMAP4430 has 56kB of internal RAM, which this scatter-file uses.
      
SDRAM 0x0C000000 0xE000 ;Placing code and data in MSMC RAM
{    
    APP_CODE +0
    {
        * (+RO, +RW, +ZI)
    }
                                            
    ARM_LIB_STACKHEAP  0x0C001000 EMPTY  0x00001000 ; Application heap and stack
    { }
}

When I dump the AXF using CCS the processor does not come out of running state for me to execute the code (the play button is disabled and the processor status is running). Am I doing something wrong?

Thank you in advance.

regards,

Barath Ramesh

  • TI__Guru**** 171309 points

    Barath,

    CCS supports .axf file formats (I just tested with a Cortex M4 part as I don't have the device you are using), thus the issue may be somewhere else.

    Assuming the memory configuration in the scatter file is correct, it seems that either the hardware is not properly configured and the initialization is hang at some point (check GEL files, any necessary jumpers or dip switches), or the initialization code itself has issues. You can always halt the processor and see where it stopped (maybe in an exception, in invalid memory, etc.).

    Also, you can disable the Run to main() option enabled by default and step through your initialization code to see where it halts. For that, check:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/186694/681141.aspx#681141 

    Hope this helps,

    Rafael