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

TMS320F28386D: about CMD Tool error in sysconfig

Ben Qin
Intellectual 2690 points
Part Number: TMS320F28386D
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE, TMS320F28379D

Hi Team,

There's an issue from the customer need your help:

As show in picture one, GSRAM all is controlled by CPU1.

In picture two combined GS9-15 RAM to GSRAMB and it has generate CMD file in the right side of picture.

In picture three if I allocate GSRAMB to data section, it will shows the error 'The memcfg module is needed on CPU1 to assign GSRAM', and it will shows whichever section I allocate. Is this a bug?

I use the latest C2000Ware and sysconfig.

Could you help check this case?

Thanks & Regards,

Ben

  • 0
    TI__Mastermind 32565 points

    I believe it is a bug. I am able to reproduce the issue. I will file a ticket to get this fixed in the next C2000ware release.

    Thanks,

    Veena

  • 0 in reply to Veena Kamath
    Intellectual 902 points

    I see this bug too.

    Can you please provide link to the ticket in jira?

    I can add that is seems to be correlated with using memory combinations, ion my small example i just added all gs ram sectors to a combination named RAM_GS. And i got the error as described by Ben (exept i saw it on bss section).

    I fiddled around with it, an found if I removed one sector from this combination, and then select the build-in symbol RAMGS15 that now shows on the pulldown list. The error goes away.

    resulting in this cmd file

    #ifdef CMD_SIMPLE

MEMORY
{

    RAM_M                     : origin = 0x000123, length = 0x0006D5
    CLATOCPU_MSGRAM           : origin = 0x001480, length = 0x000080
    CPUTOCLA_MSGRAM           : origin = 0x001500, length = 0x000080
    RAM_LS                    : origin = 0x008000, length = 0x003000
    RAM_D                     : origin = 0x00B000, length = 0x001000
    RAM_GS                    : origin = 0x00C000, length = 0x00F000
    RAMGS15                   : origin = 0x01B000, length = 0x000FF8
    CPU2TOCPU1RAM             : origin = 0x03F800, length = 0x000400
    CPU1TOCPU2RAM             : origin = 0x03FC00, length = 0x000400
    FLASH                     : origin = 0x080000, length = 0x03FFF0
    RESET                     : origin = 0x3FFFC0, length = 0x000002
}


SECTIONS
{
    //
    // C28x Sections
    //
    .reset               : >  RESET, TYPE = DSECT /* not used, */
    codestart            : >  0x080000
    .text                : >  FLASH,
                              ALIGN(8)
    .cinit               : >  FLASH,
                              ALIGN(8)
    .stack               : >  RAM_M
    .init_array          : >  FLASH,
                              ALIGN(8)
    .bss                 : >  RAMGS15
    MSGRAM_CPU1_TO_CPU2 : > CPU1TOCPU2RAM, type=NOINIT
    MSGRAM_CPU2_TO_CPU1 : > CPU2TOCPU1RAM, type=NOINIT

}

#endif

    NB: I can confirm same error/bahaviour for data section, as in Ben's example.

    EDIT: forgot to mention i see it on TMS320F28379D