• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 361 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.

ARM9_0: Can't Run Target CPU

Michelle Lopez
Intellectual 650 points

Other Parts Discussed in Thread: OMAPL138

Hello all,

I have been trying to run the IPC example found in StarterWare for the OmapL138 but am encountering problems. I was able to load both binaries into the ARM and the DSP and was able to group the cores. I have a problem when I try to run the cores grouped. First i got a message that it was having an internal error (2030) and it could access some registers.

Some weeks before, a coworker was having trouble with somthing alike when tryng to enable the kick registers and he used the boo.asm file and the gpio handling was able to work correctly. So, I tried on incuding the boot.asm file into my IPC ARM project to see if this was resolved  but now I get the message:  ARM9_0: Can't Run Target CPU.

You can view my other thread posted in the StarterWare forum: http://e2e.ti.com/support/embedded/starterware/f/790/p/214190/756821.aspx

Please let me know of any suggestions.

Thanks,

Michelle

 

 

 

 

 

 

  • 0
    TI__Guru** 116780 points

    Hi Michelle,

    I need some more details of your setup and procedure.

    • Are you using the GEL files on the ARM and the DSP when you connect to the target? OMAPL138 is ARM boot device so connect first to the ARM and then to the DSP.
    • IPC lite example expects ARM code to run first and then the DSP is this the sequence you followed.:http://processors.wiki.ti.com/index.php/StarterWare_01.10.01.01_User_Guide#Example_application
    • Go to View -> Disaasembly and let us know when load code do you see the Program counter(PC) at main, please report the location of the PC on ARM and DSP.
    • Have you set the device switches to emulation boot mode? If not, can you set them in emulation boot mode and try this again.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 650 points

    Hi Rahul,

    The problem was that I was grouping the cores and running them at the same time instead of running the ARM fisrt and then the DSP as you suggested in your reply. Yet, I am still encountering a problem in  the output. in the example folder in the StarterWare folder theres a readme file with an expected ouptut.

    It states:

    Expected output
    ---------------------
    UART serial console:
    ARM IPC ready
    ARM: event received 1
    ARM: event received 4
    ARM: event received 10
    ARM: event received 40
    ARM: event received 100
    ARM: event received 400
    ARM: event received 1000
    ARM: event received 4000
    ARM: event received 10000
    ARM: event received 40000
    arm done - total events received 10

    CCSv5 CIO console:
    [C674X_0] DSP IPC ready
    [C674X_0] Event received 2
    [C674X_0] Event received 8
    [C674X_0] Event received 20
    [C674X_0] Event received 80
    [C674X_0] Event received 200
    [C674X_0] Event received 800
    [C674X_0] Event received 2000
    [C674X_0] Event received 8000
    [C674X_0] Event received 20000
    [C674X_0] Event received 80000
    [C674X_0] dsp: done - total event received 10

    Yet this doesn't make much sense since in the code the only lines that generate an ouptu to Uart are: ARM IPC ready(as well as the DSP) and [C674X_0] dsp: done - total event received 10 (as well as this line in the ARM) I dont know if this should be addressed to the StarterWare folks but have not gotten too much support from that thread. Please let me know of any advice.

    Thanks,

    Michelle