• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 1422 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.

CMD File

Abhijit Kelkar
Intellectual 855 points
Other Parts Discussed in Thread: F28M35H52C, CONTROLSUITE

Hi..Mark,

I am directly referring you as you answered my last two queries.

I have updated Control Suit to 2.8.4 today and I was using USB related projects. USB_HOST_MSC_M3. I tried to run it th' RAM so I made similar build configuration. I tried with generic RAM cmd file as well as device f28m35h52c specific cmd file.in both files there was compilation error (line 39: error:C2 memory range overlaps existing memory range RESETISR in cmd file.)  so started checking cause of error. Please check memory definition mark in RED .

It is showing clear overlapping of memory areas. Is this some error? Do I need to run USB related programs only from Flash ? Please let me know 

Best Regards

Abhijit Kelkar

MEMORY

{

C0 (RWX) : origin = 0x20000000, length = 0x2000

C1 (RWX) : origin = 0x20002000, length = 0x2000

BOOT_RSVD (RX) : origin = 0x20004000, length = 0x0900

RESETISR (RWX) : origin = 0x20004FF8, length = 0x0008

INTVECS (RWX) : origin = 0x20005000, length = 0x01B0

C2 (RWX) : origin = 0x20004900, length = 0x1700

C3 (RWX) : origin = 0x20006000, length = 0x2000

S0 (RWX) : origin = 0x20008000, length = 0x2000

S1 (RWX) : origin = 0x2000A000, length = 0x2000

S2 (RWX) : origin = 0x2000C000, length = 0x2000

S3 (RWX) : origin = 0x2000E000, length = 0x2000

S4 (RWX) : origin = 0x20010000, length = 0x2000

S5 (RWX) : origin = 0x20012000, length = 0x2000

S6 (RWX) : origin = 0x20014000, length = 0x2000

S7 (RWX) : origin = 0x20016000, length = 0x2000

CTOMRAM (RX) : origin = 0x2007F000, length = 0x0800

MTOCRAM (RWX) : origin = 0x2007F800, length = 0x0800

}

  • 0
    TI__Mastermind 22025 points

    Abhijit,

    It sounds to me like you are trying to add a linker command file to the example project in controlSUITE.  Is that correct?  The projects already have linker command files defined, so adding an additional linker command file with cause the memory overlaps you are seeing.  Try running the project as it came originally, it should work.

    Also of note, all of the USB examples may be run from RAM with some tweaking, but not all of the USB examples include a RAM build configuration.  The reason for this is that we use the generic linker command files on all the examples and the generic linker command files only define the RAM that is available on the smallest concerto part.  The larger USB examples won't fit in this smaller memory space so we only use the generic flash linker command file (which defines much more code space) for these examples.  If you wish to run from RAM, include the linker command file of your choice and start modifying the cmd file until you can get the code to fit.

    Regards,

    Trey

  • 0
    TI__Expert 3520 points

    Hi Abhijit,

    No need to directly refer to me as there are plenty of  more knowledgeable experts on the C2000 line of devices who browse this forum!  It's just been a coincidence I have answered your posts thus far.

    The memory configuration you show above is an error with the C2 RAM section.  To fix the issue replace the RED highlighted lines (including INTVECS) with the following lines instead:

        BOOT_RSVD (RX)   : origin = 0x20004000, length = 0x0900
        C2_1 (RWX)       : origin = 0x20004900, length = 0x06F8
        RESETISR (RWX)   : origin = 0x20004FF8, length = 0x0008
        INTVECS (RWX)    : origin = 0x20005000, length = 0x01B0
        C2_2 (RWX)       : origin = 0x200051B0, length = 0x0E50

    This should fix the compilation error you were receiving earlier and allow you to compile the project.  Note that you also need to change all references to C2 in the SECTIONS area to instead read C2_1 | C2_2.

    Best Regards,

    Mark-

  • 0 in reply to Trey German289
    Intellectual 855 points

    Trey,

    thanks for your reply. I was not trying to add  a linker command file to example. Particular example is active Flash type and I wanted make it active RAM type so I was trying to use RAM linker command file by changing build options. The overlap caused because of incorrect definition of memory area in supplied cmd file. When I made small change, it assembled. 

    Yes you are right, when I tried to build in Active Ram mode it was not fitting because of RAM space limitation.

    But I am finding a problem when running code from flash, USB device is not recognised . It is same USB memory& USB Cable received with KIt.

    regards

    Abhijit

  • 0 in reply to Mark Swanson
    Intellectual 855 points

    Hi.. Mark,

    thanks for reply.

    I already made those changes and tried but USB MSC project can not fit in RAM because of size. I just want to show error in file to get in corrected in next version.

    Similarly while running from Flash, USB Memory is not getting recognised by Kit. I am using Cable/Memory every thing supplied with Kit.

    Best Regards

    Abhijit

  • 0 in reply to Abhijit Kelkar
    TI__Mastermind 22025 points

    Abhijit,

    This example does in fact work, but I think you may be confused about how it works.  The USB_Host_MSC example turns the Concerto into a USB host such that a USB Flash drive may be plugged into the controlCard directly.  On the PC you should connect to the XDS100's serial port and open up a serial terminal with hyperterminal or Putty (settings are 115200 8n1).  Then you will be able to navigate the flash drive through the serial terminal.

    Regards,

    Trey

  • 0 in reply to Trey German289
    Intellectual 855 points

    Trey,

    I have already followed procedure of connecting th' Hyperterminal. After running the USB_MSC program I got following message.

    I checked USB memory by connecting to Laptop and it works fine but it is not recognised by Concerto Kit. Same memory if connected to Stelaris Kit,immedietly gives list of files on display.

    Is this software probelm or I need to do some thing?

    As in v110 during debug it was giving error as nothing to do and it was not even pointing to Main after jumping from cint0.

    This problem is not showing in V120.

    I am mainly concentrating on USB as we are already using F2812 in our system and we looking to Concerto because of its communication modules like USB, Ethernet etc.  

    Abhijit

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

    Unknown device connected.
    UNKNOWN>
    Unknown device disconnected.
    NODEV>
    Unknown device connected.
    UNKNOWN>
    Unknown device disconnected.
    NODEV> help

    Available commands
    ------------------
    help : Display list of commands
    h    : alias for help
    ?    : alias for help
    ls   : Display list of files
    chdir: Change directory
    cd   : alias for chdir
    pwd  : Show current working directory
    cat  : Show contents of a text file
    NODEV>
    Unknown device connected.
    UNKNOWN>
    Unknown device disconnected.
    NODEV> ls
    Command returned error code FR_NOT_READY

  • 0 in reply to Abhijit Kelkar
    TI__Mastermind 22025 points

    Abhijit,

    So you were able to get it working with the v120 files?

    v120 should work for you.  v110 there was a bug with DMA that was preventing the application from executing correctly, so if you were using that before I would expect the behavior you posted above.  In v120 we disabled DMA and are using CPU transfers instead.

    Trey

  • 0 in reply to Trey German289
    Intellectual 855 points

    Trey,

    No I was not able to get working with V120 files.

    I could go one step forward by using V120 files. With V120 files at least project got compiled and run in debug mode.

    But... It is not recognizing USB device. I have pasted Hyper temninal response in my earlier post.

    Secondely I checked even USB _Host_Mouse project but again same problem. Mouse is not getting connected.

    Could there be  any board version related issue or Have I to do any alteration in PCB hardware like jumper setting for USB to work?

    regards

    abhijit

  • 0 in reply to Abhijit Kelkar
    TI__Mastermind 22025 points

    Abhijit,

    Do you have both of the USB jumpers placed on the board?  They are near the right side of the bank of jumpers (jumper 30 and 31) and should be in the up (BC) position.

    Trey

  • 0 in reply to Trey German289
    Intellectual 855 points

    Trey,

    Yes it worked after inserting Jumper30&31. Do you have such document which will give details of particular jumpers to be used for particular applications? If so please let me know.

    thanks & regards

    Abhijit

  • 0 in reply to Abhijit Kelkar
    TI__Mastermind 22025 points

    Yes, but the document is very well hidden within controlSUITE (not sure why?!!?).  Take a look here:

    C:\TI\controlSUITE\development_kits\~ExperimentersKits\F28M35xx_InfoSheet.pdf

    There is a table on the last page with jumper settings.

    Trey