• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2906 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.

Fatal Error during:initialization, OCS, Control

Calum Mackinnon
Genius 4155 points
Other Parts Discussed in Thread: OMAPL138

My customer has an OMAPL138 board from LogicPD and is getting the following error. I've sent them the gel files form logicpd to try as they were using there own. I've also asked them to check they have the OMAP SOM and not the 6748 SOM plugged in. However if that does not work what else should we check for?

They have CCS V4.1.2

I never use ARM before. I have no idea why it failed. The memory space is defined in the gel file:

    /* Shared RAM */

    GEL_MapAddStr( 0x80000000, 0, 0x00020000, "R|W|AS4", 0 );   // Shared RAM

Do you have any suggestion?

 

  • 0
    TI__Guru**** 474481 points

    Hi,

    Looks like they are having issues connecting to the target. First off, what emulator are they using? In the screenshot it says XDS100v2. But many people get confused and think that the onboard emulation on the L138 board is an XDS100v2 when it is indeed an XDS100v1. Are they using the onboard (plugging a USB cable directly to the mini-USB port on the board) or are they using an external emulator (connected to the JTAG header)?

    If they are indeed using an XDS100v2, I would suggest upgrading to the latest v4 (v4.2.4). v4.1.2 is pretty old and many bug fixes have been made since then.

    Finally, they can do some JTAG connectivity tests:

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    Hope this helps

    ki

  • 0 in reply to Ki
    Genius 4155 points

    Thanks Ki,

    Below is an update. Do you have any comments on what they are asking?

    Cheers

    Calum

    We struggled a little with the evaluation board.  The eval board documentation only indicates to use the null modem connection with the OMAP processor.  We didn’t bother with it as we know this would prevent any debugging, and would only allow loading the code.Then we tried using the spectrum digital XDS560R emulator but we found out that it is incompatible with the latest version of Code Composer v4.2.x.Then we found some documentation on-line about the eval board indicating that a XDS100v2 emulator circuit is located on the board and can allow direct PC connection with a mini-USB cable.  That’s what Yadong is using for now.

    I’d like to get your opinion on how to proceed with the emulator next for target hardware debugging?

    There is a XDS100 JTAG emulator cable compatible with latest version of CCS 4.2.x and quite affordable ~$100, but I’m suspecting that it has limited debug capabilities.

    Then yesterday we found on-line the spectrum digital XDS560v2 JTAG emulator for $1200, compatible with CCS 4.2.x and which we believe it is an advanced emulator with true real-time debug capabilities.  This seems to be the option to select for our long term need.

    Please let me know if we understand this correctly.

     

     

  • 0 in reply to Calum Mackinnon
    TI__Guru**** 474481 points

    Calum Mackinnon said:
    hen we found some documentation on-line about the eval board indicating that a XDS100v2 emulator circuit is located on the board and can allow direct PC connection with a mini-USB cable.

    Where did they find this documentation? As far as I know, the emulation logic on the evm is an XDS100v1. I can't find any documentation that definitively states that it is an XDS100v2. Since XDS100v1 does not support ARM, they need an XDS100v2

    Calum Mackinnon said:
    There is a XDS100 JTAG emulator cable compatible with latest version of CCS 4.2.x and quite affordable ~$100, but I’m suspecting that it has limited debug capabilities.

    The main limitation is speed. Program download times and data transfers between host and PC are slow (this will make CCS debugging appear more sluggish too). Otherwise the rest of the debug capability is mostly there. If you can deal with the slow speed, it should be adequate.

    Calum Mackinnon said:
    Then yesterday we found on-line the spectrum digital XDS560v2 JTAG emulator for $1200, compatible with CCS 4.2.x and which we believe it is an advanced emulator with true real-time debug capabilities.  This seems to be the option to select for our long term need.

    XDS560v2 is recommended if it is in your budget. You get a better performing emulator, true. But for basic debug, an XDS100v2 is not a bad choice. Many people have used an XDS100v2 for their entire development.

    Thanks

    ki