• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 596 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.

TMS570LC4357: TMS570LS3137 to TMS570LC4357 backward/upward compatible?

Manny Salazar
Prodigy 290 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMS570LS3137,

Hello,

We're using several TMS570LS/LC devices and need to understand the following due to our software team has a concern the difference in ARM cores shall cause software maintenance issues.

Questions -

1. Is there a whitepaper which describes if the Software can be backward or upward compatible between the LS and LC series ?

2. Is the a QFP version of LC series on the way or sampling ?

-- In project 2 we cannot use the BGA version as we are using thick copper layers and we cannot have such fine pitch BGA .

 

Project 1: We're using TMS570LS3137 in QFP Package - ARM Core R4F, 160MHz max

Project 2: : Now-Using TMS570LS3137 in BGA Package  ARM Core R4F, 180 MHz max - But would like to upgrade to TMS570LC4357  , BGA Package , ARM Core R5F, 300 MHz Max.

  • 0
    Expert 1810 points

    I thing, that you can do it. But only almost! TMS570LC4357 can be configured in same pinout as TMS570LS3137. It is not optimal (ethernet pins) but is is possible.

    But there are some more or less significant differences:

    * TMS570LC4357 need better power supply lines than TMS570LS3137. For example there is sharp edge current peak on MCU wake up from sleep. 

    * Do you use EMIF? TMS570LS3137 can run up to 180MHz/2=90MHz bus. TMS570LC4357 can run up to 300MHz/2/2=75MHz only. Theoretically up to 110MHz, but not with 300MHz CPU clock.

    * some peripherials are extended, but usually backward compatible (for ex SPI on 3137 is replaced by MibSPI on 4357)

    * There is lot of differences on SW. Boot code is different. SW must divide internal RAM to shared (non-cacheable) and non-shared (cacheable) part. Any memory with EMAC or DMA access need to be "shared". EMAC driver need modification for 4357 bug (see errata). Lot of differences, but it is possible to have only one SW with conditional sections (problem with safety certification rules, but it can be solved).

    * many other details