• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 96 subscribers
  • Views 318 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.

Endiness question on DM6437

Anonymous
Anonymous
Other Parts Discussed in Thread: TMS320DM6437

Hi All,


I would like to ask a question on endianess.

Although TMS320DM6437 supports only little endian, specified on page 1 of SPRS345d TMS320DM6437 Digital Media Processor, why in simulator I was still able to choose:

  1. "big" in Project Settings->Device Endianess
  2. "Big Endian" DM6437 Device Accurate Clock Cycle Simulator in Target configuration->Texas Instruments Simulator

?

                                

               

Sincerely,
Zheng

  • 0
    TI__Genius 14405 points

    Zheng,

    As far as I know, for the public, DM6437 only supports little endian mode.

    Which CCS are you using? I will pass on this message and get it cleared.

  • Anonymous
    0 Anonymous in reply to Paul.Yin

    Dear Paul,

    I am using CCS 4.1.2.00027.

     

    Zheng

  • Anonymous
    0 Anonymous in reply to Paul.Yin

    Dear Paul,

    When you say "for the public", do you mean that DM6437 actually has the hardware capability to support big endian, but the way to make it work is not released in its public documents?

     

    Zheng

  • 0 in reply to Anonymous
    TI__Genius 14405 points

    Zheng,

    Please don't get hang up on this.

    Just checked with the CCS team. They mentioned the "new project" window is very generic, you choose whatever you plan to create. The other items are not refined or filtered when you choose the device name. I.e., because TI has both little endian and big endian devices, it doesn't automatically get filtered just because you selected a little endian device (dm6437). This feature will make a good update to the software though, I agree.

  • Anonymous
    0 Anonymous in reply to Paul.Yin

    Dear Paul,

    I still haven't fully understood it. Does this basically mean:

    In the ideal way, once the chip type (say 6437) is selected it, the select option will automatically be updated and depending on the type of the chip:

    1. If the chip supportsonly little endian, the window will give you only little endian without another option, i.e., you have NO drop down menu.
    2. If the chip supportsonly big endian, the window will give you only big endian without another option and you also have no drop down menu.
    3. Only when the chip supports both little and big endian will there be a drop down menu for you to choose from.

    In reality, CCS just didn't make it to the ideal way.

     

    Is this what the designers actually meant? But if this is true, isn't it possible for someone to get big endian configured in CCS for a little endian chip? And will he be able to load the code, in particular, multi-byte data into the chip, and run the code without any error?

     

     

    Zheng

     

  • 0 in reply to Anonymous
    TI__Genius 14405 points

    Hi Zheng,

    Zheng Zhao said:
    In the ideal way, once the chip type (say 6437) is selected it

    1-3 are what I meant, but I won't call it the "ideal way", it is only what I wish to see if I were using it -- personal preference only.

     

    Zheng Zhao said:

    Is this what the designers actually meant? But if this is true, isn't it possible for someone to get big endian configured in CCS for a little endian chip? And will he be able to load the code, in particular, multi-byte data into the chip, and run the code without any error?


    I am not too sure what will happen in this case. This is unsupported usage according to the datasheet, so you shouldn't even consider it.

  • Anonymous
    0 Anonymous in reply to Paul.Yin

    Dear Paul,

    Got it, thanks.

     

    Zheng