• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 428 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.

Stellaris M4F pin to pin table ?

Ryan(FAE) Lin
Prodigy 65 points


Hi All

A quick question , does anybody have the pin to pin table of Stellaris M4F ? ( 110 , 120 ... series )

I would like to know whether i can develop using like 110 series and shift to 120 series when production.

Thanks for help !!

  • 0
    Prodigy 40 points

    I believe you can...

    From page 41 on the LM4F110  "Stellaris LM4F microcontrollers consist of fifteen pin-compatible series of devices." There is also a table listing them.

    Best of luck!

  • 0 in reply to Nathan Poland
    Guru 47900 points

    @Nathan - resourceful, helpful - hereby memorialized.

    Paints perchance bigger picture - if these 2 MCU families were "designed" w/such overlap:

    a) that is big/valued Selling Point - deserves better than "passing glance" at/around pg 41..

    b) if this was by "intent" - has such intent continued throughout this enlarging M4 spectrum?  Again - Mkt Dept not exactly, "Shouting from rooftops..."

    c) beyond simple, "pin compatibility" - functional comparisons may prove of even higher value.  (i.e. presence/number of key peripherals {i.e. PWM Generators - for one})  Sadly many note that device selected for lunchlaunchpad is "stripped down" version - PWM Generators not included - that lunchlaunch...

  • 0 in reply to cb1
    Guru 58965 points

    On the other hand, if they make different chips 100% totally "compatible", what is the point of calling them as different chips? 

  • 0 in reply to old_cow_yellow
    Guru 47900 points

    @OCY:

    This reporter has never argued/pushed for "100% compatible!"

    Clearly your smart, sufficiently experienced to know that Memory (Flash & SRAM, EEPROM), MCU Speed, Temp Range all classically vary - across vendor's line-up.

    (one may suspect past few OCY comments result from this reporter's (yet unanswered) post in response to "road rarely travelled...")

  • 0 in reply to cb1
    TI__Prodigy 65 points

    Hi All

    Thanks all you guys

    the reason that i mean compatible is focusing on "don't have to change hardware / schematic".

    which means pin out will not be changed.

    and about page 41 table , it help me a lot

    Thanks !!

  • 0 in reply to Ryan(FAE) Lin
    Guru 47900 points

    Ryan(FAE) Lin said:
    don't have to change hardware / schematic

    Ryan - while that has some appeal - is it not unduly "restrictive?"  Pin for pin may suggest - but does not insure - a peripheral-capability match.  And is not the ability to bring full (or at minimum high) capability one of the key appeal-points of ARM?  Trading capability for compatibility - may not always be wise...

    Fifteen, twenty years past - such goal was far more valid.  Today's rich schematic/pcb packages - and your clever "re-use" of prior, schematic/pcb "puzzle pieces" - enables fast/eased "purpose optimized, design/built" boards.  And quick-turn, discount pcb houses abound.

    There's yet another method (used by our firm - and the original LMI LM3S introduction demo) - creation of unique, individual MCU "daughter boards" - which plug-in to a larger "mother board."  All key MCU support components (i.e. xtal, caps, LDO treatment, reset etc.) reside on such daughter board - daughter board is designed to accommodate & throughput (GPIO) the largest candidate MCU.  

    This method significantly reduces the design effort, size and thus cost of the MCU-specific board - greatly aids design choice/flexibility - but is inefficient for volume production.   Remains a very effective means to "eval" a variety of MCUs - accommodating (pardon) eased eval of multi-vendors.  (especially important in light of recent "diplomacy-lite" M3 NRND pronouncements - high from the "mount.")