• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 127 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHCC3220MODASF: Pin Mismatch Between CC3220MODASM2MONR Chip and Launchpad

Maximillian Gomer
Prodigy 55 points
Part Number: LAUNCHCC3220MODASF
Other Parts Discussed in Thread: CC3220SF, , SYSCONFIG

Hi there, I've got a question about the pin mappings of the LAUNCHCC3220MODASF versus the pin mappings of the CC3220MODASM2MONR chip. I bought the standalone chip for a custom PCB, and also purchased the Launchpad that was listed as the development/evaluation board for this chip. Code Composer Studio recognizes the Launchpad as the CC3220SF, which is a different Launchpad model. The pin mappings for the Launchpad appear to match the pin mappings of the CC3220SF though, and I'm able to program the Launchpad without issue. The concern lies with flashing a program that runs on the Launchpad onto the CC3220MODASM2MONR chip. For example, a basic blinking LED program using GPIO_06 on the Launchpad uses pin 61, but on the standalone chip, GPIO_06 is pin 51 and pin 61 is a thermal ground pad.

How can I remedy this pin mismatching so I can flash programs that run on the Launchpad to the standalone chip without issue?

  • 0
    TI__Expert 5430 points

    Hi  Maximillian,

    The CC3220MODAS should be quite similar to the LAUNCHCC3220MODASF, although the CC3220MODAS will be missing the external 1MB execution flash that the launchpad has.  Let me ask one of our experts on the pin mismatching issue, and get back to you later today.

    Best Regards,

    Jessica M. Torres

  • +1 in reply to Jessica M. Torres
    Guru 73315 points

    Hi Maximillian,

    TI manufacture two types of packages for CC32xx devices. QFN and MOD package. MOD package contains inside CC32xx QFN chip and some other components (SPI flash, XTAL, RF filter). Software configuration inside code is related to QFN (because exact same QFN is inside module). Pins numbering of QFN and MOD are not same. How pins from internal QFN are mapped to pins of MOD package you find at MOD datasheet.

    Difference between S and SF devices is internal 1MB (execution flash). In real world it means that SF devices allow to execute bigger code.

    Jan

  • 0 in reply to Jan D
    Prodigy 55 points

    Oh I see, thank you, that clarifies things a little. If I understand correctly, then Code Composer Studio is correctly identifying the LAUNCHCC3220MODASF launchpad as a CC3220SF device because the CC3220MODASF packaged chip on the launchpad contains the CC3220SF QFN chip?

    So, when writing code for the standalone CC3220MODASM2MONR chip, is it correct to assume that I'm actually programming the internal CC32xx QFN chip and using the QFN's defined pin numbers for software functions, like GPIO toggling? For example, if I want to toggle GPIO_06 on the MOD chip, I use the QFN's defined pin (61) for GPIO_06 in the sysconfig and not the MOD's defined pin (51). Then on the hardware side, once the program is flashed to the MOD chip, I should expect the MOD package's GPIO_06 at pin 51 to be toggled. Is this correct?

  • 0 in reply to Maximillian Gomer
    Guru 73315 points

    Hi,

    Yes, your understanding is correct.

    Jan