• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 498 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.

RTSC apparently generating wrong cmd file

Sebastián Castillo
Prodigy 170 points
Other Parts Discussed in Thread: TMS320F28335

Hello community,

I am working with ezdsp f28335 and cssv4.1.3.00038 under Windows 7. I was following this guide:

http://rtsc.eclipse.org/docs-tip/RTSC%2BCCStudio_v4_QuickStart

but when I try to debug the project, an error is produced which says  "Data verification failed at 0x002050C0" and that i should ensure that command file matches memory map. When I open the "linker.cmd" file, I'm surprised to see that a "SRAM" block is defined at 0x200000, a memory location that according to the memory map of the device is reserved. The .text section and many others are defined in this block. I've been using the TMS320F28335 for a while now, but I am new to RTSC, so I don't know what to change in order to make this work. RTSC is version  3.16.02.32.

Any help would be appreciated.

 

  • 0
    TI__Expert 3550 points

    Hi Sebastian,

    If you are consuming RTSC content like SYS/BIOS 6.x the memory map is contributed via the RTSC platform. XDCtools 3.16.02.32 supplies one RTSC platform package - ti.platforms.control28335 . This platform refers to the device module - ti.catalog.c2800.TMS320C28335 - which in turn provides the device memory map. Reviewing this device module, I do not see any section with the name "SRAM" - that is defined for a region containing the address 0x200000. Are you using the existing RTSC platform or defining your own platform using the platform wizard? Is it possible to attach your project to this forum post so that we can take a look?

    Thanks

    Amit

     

     

  • 0 in reply to AmitMookerjee
    Prodigy 170 points

    Hi Amit,

    I've been using the platform package ti.platforms.ezdsp28335. Now I tried using the platform package ti.platforms.control28335 and the problem dissapeared. I think the platform package ezdsp28335 should be checked anyway. Thanks for your help!

    However, now I have another problem. Following the same tutorial in http://rtsc.eclipse.org/docs-tip/RTSC%2BCCStudio_v4_QuickStart, after loading the program into DSP and trying to debug, I never get the "Hello world" message on the console tab, as said there. Any suggestions?

    I have attached the current project in case someone finds it useful.

    TestRTSC.zip
  • 0 in reply to Sebastián Castillo
    TI__Expert 3550 points

    >I never get the "Hello world" message on the console tab, as said there. Any suggestions?

    Looking at your configuration file, I see that it is configured (by default) to use xdc.runtime.SysMin system services provider. This provider should flush the output buffer after program exit. In order to see output in the console as soon as System_printf is executed in your program you can use the xdc.runtime.SysStd provider.

    This maybe accomplished by adding the following lines of code to your configuration script  - hello.cfg :

    var System = xdc.useModule("xdc.runtime.System");

    System.SupportProxy = xdc.useModule("xdc.runtime.SysStd");

    To get a overview of system services provided by XDCtools you can refer to http://rtsc.eclipse.org/docs-tip/Using_xdc.runtime_System

     

    Regards

    Amit

    -----------------------------------

    Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.

     

  • 0 in reply to AmitMookerjee
    Prodigy 170 points

    I can't find that "hello.cfg" file, and if I modify "common.cfg", I get compilation errors. However, If I run the program "as is" and step into the code beyond the hello.c code, i do get the "hello world" message as you said, which is good enough for me now.

    There's nothing left to say than thank you Amit, and to remind TI developers to review the platform package ti.platforms.ezdsp28335.