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

TMS320F28027: chip execution speed

Cherry Zhou
Mastermind 22235 points
Part Number: TMS320F28027
Other Parts Discussed in Thread: C2000WARE

Hi team,

Here's re few questions from the customer may need your help:

1) The 74HC595D chip is driven with normal IO, and the manual States that the maximum clock rate is shorter than the time to execute an instruction. No delay is used in the customer's program and the drive signal output from the 74HC595 was found to be good. Clock is 60 MHz. DSP/DSC is a multi-level pipeline instruction which is faster, right? But now there's no problem. Is there anything wrong or any configuration need to be modified? 

2) The program starts with MemCopy&RamfuncsLoadStart,&RamfuncsLoadEnd,&RamfuncsRunStart

Does this statement indicate that the program is executing in RAM? What should the customer do if they want code in a while loop to execute in RAM? 

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Guru** 115881 points

    Hi Cherry,

    I am not very clear on the problem statement but to answer your 2nd query - You really need to look at the project setting (like linker cmd file) to know which part of the application is getting copied into RAM and which one is running from flash. There is not enough RAM on device to copy everything from flash to RAM. In general time critical code (like ISR) is copied into RAM and executed.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Mastermind 22235 points

    Hi Vivek Singh,

    Thanks for your help.

    Please let me clarify the Q1: regarding the IO port the customer has referenced the code of link here, and remove the delay. 

    Generally DSC 60 MHz, running a simple IO should be mostly run with a single instruction of 16.6 ns. And the 595 is slower than that. Why is the output driven by the 595 correct without a delay?

    Could you help give an example of code downloading in flash and running in RAM or CMD configuration? Is the #pragma code_section simply moving the function to RAM for execution?

    Customer's code was downloaded to flash (power-cycle to run), what if they want code sections or functions to execute in RAM?

    Thanks and regards,

    Cherry

  • +1 in reply to Cherry Zhou
    TI__Guru** 115881 points

    Hi Cherry,

    All examples in C2000Ware have flash build configuration where code gets loaded into flash and then part of the code (the flash configuration) is copied into RAM and then executed from RAM. Please take a look at these exmaples.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Guru** 115881 points

    Let us know if you have any further query on this topic.