CC3200 LaunchPad Pins Map

[Rei Vilo 695]

Please find the pins map of the CC3200 LaunchPad.

 

Edit Sept. 08, 2014

[Thorvard 14]

Hi Rei,

 

while developing an application i took a look at the schematics of the CC3200 LP and noticed that many Pins are not connected to the booster pins and therefore not usable without modifying the Launchpad, or are already in use by system components:

 

P1.3 -> Switch3, Accelerometer INT (detachable from sensors by jumper)

P1.9 -> Yellow LED, SCL (detachable from sensors by jumper)

P1.10 -> Green LED, SDA (detachable from sensors by jumper)

P3.3 -> FTDI_TX

P3.5 + P3.6 are not connected by default

P3.9 -> Red LED

P4.1 - P4.8 are not connected by default

P4.9 -> JTAG_TDO, RS232_RX

P4.10 -> JTAG_TDI, RS232_TX

P2.2 -> JTAG_TCK

P2.8 -> SOP2

P2.9 -> FTDI_RX

P2.10 -> Switch 2

 

regards, Nick

[igor 163]

Would there be any sense in adding a short reminder to the pin map to the effect that AnalogRead pins are 1.5V only (when used as analog)?  Don't want to overload the diagram, but this seems like the sort of unexpected detail that might sabotage the unwary beginner, and therefore be worth calling attention to.  (Maybe with a brief note up next to the legend?)  Up to you if think it would add or detract from the diagram.

 

Another thing I discovered, not about Energia but noteworthy for folks using the new CC3200 - ADC inputs are measured against a 1.5V reference, the analog input buffers are only supposedly tolerant up to 1.8V.  That could be a problem if you have some 3.3V-level analog inputs.

 

This doesn't seem to apply with digital I/O mode for these pins, but as the datasheet cautions, having the digital I/O output buffers enabled & set high while the ADC mode is configured for the pin could cause the MCU to blow up its own ADC buffers.  Since Energia uses the CC3200 driverlib I assume there's no risk of that here...

 

[igor 163]

In the text about memory:

Is the amount of flash listed (8 megaBYTE) correct?  One source says 8 megaBIT.

 

Might be worth adding a footnote that programs run from RAM (images limited to 240KB).

Since the flash is not directly accessible.

Otherwise somebody not familiar with the part might think they could compare these numbers to those on other launchpads.

 

--

 

In the pin diagram, why is there a label that says "RESET" under the antenna connector?  (Lower right area of the PCB, Just above the little rocket on the PCB silkscreen).

 

--

On PIN_58, PIN_59 and PIN_60 it would make sense to have the blue analogRead() box next to all instances of the pin.

(i.e. going by black pin numbers - 2, 6, and 24 should have blue boxes by them)

The pins that are currently labeled with the blue are not even connected in default configuration (according to the schematic).

 

--

A lot of boosterpack pins are not connected to start with (as well as being duplicates of other pins).  It would be helpful to distinguish those pins in some way (e.g., put NC in the gray column, use faded versions of the colors, add an asterisk with a footnote, something)  (pins with numbers in black 33 to 40 and 24 to 26).

 

I was trying to come up with a more visual way of indicating the various connections - but it mostly winds up looking like the tangle of wires behind my computer.

 

--

 

Pins numbered in black 39 and 40 are connected to signals ANTSEL 1,2.

(chip pins 29 and 30, GPIO pins 26 and 27, which from the code of the antenna selection example looks like GPIOA3 pins 2 and 3)

This is without connecting the jumper to make them PIN_01 and PIN_02.

 

I haven't read enough to know if there are special limitations on those pins, but might at least be worth noting them as ANTSEL in gray?

 

--

Could be helpful to label PUSH1 and PUSH2 (next to the buttons) the silkscreen labels are hard to read (and do not seem to use the same name/numbering, from the schematic looks like they say SW2 and SW3).

 

--

According to the schematic a couple of the pins that are not connected to start give a choice of pins (might want to note the options)

 

number 38 can be either pin_21 or pin_61

 

number 37 can be connected to number 29, number 8, or number 30  (i.e. PIN_64, PIN_50, or PIN_62)

 

--

Thanks.  Hope this helps.

[Rei Vilo 695]

 

Hi Rei,

 

while developing an application i took a look at the schematics of the CC3200 LP and noticed that many Pins are not connected to the booster pins and therefore not usable without modifying the Launchpad, or are already in use by system components:

 

P1.3 -> Switch3, Accelerometer INT (detachable from sensors by jumper)

P1.9 -> Yellow LED, SCL (detachable from sensors by jumper)

P1.10 -> Green LED, SDA (detachable from sensors by jumper)

P3.3 -> FTDI_TX

P3.5 + P3.6 are not connected by default

P3.9 -> Red LED

P4.1 - P4.8 are not connected by default

P4.9 -> JTAG_TDO, RS232_RX

P4.10 -> JTAG_TDI, RS232_TX

P2.2 -> JTAG_TCK

P2.8 -> SOP2

P2.9 -> FTDI_RX

P2.10 -> Switch 2

 

regards, Nick

 

 

Thank you for your comments.

 

The next release of the pins map uses light colour for not connected pins.

 

Most of the hardware connections are in grey.

 

Labels are from Energia, e.g. SW3 is PUSH1 according to pins_energia.h

[Rei Vilo 695]

Would there be any sense in adding a short reminder to the pin map to the effect that AnalogRead pins are 1.5V only (when used as analog)?  Don't want to overload the diagram, but this seems like the sort of unexpected detail that might sabotage the unwary beginner, and therefore be worth calling attention to.  (Maybe with a brief note up next to the legend?)  Up to you if think it would add or detract from the diagram.

 

Good catch and good idea. I've added a warning.

 

Chapter 3.2 Drive Strength and Reset States for Analog-Digital Multiplexed Pins in SWAS032E

[Rei Vilo 695]

In the text about memory:

Is the amount of flash listed (8 megaBYTE) correct?  One source says 8 megaBIT.

 

Might be worth adding a footnote that programs run from RAM (images limited to 240KB).

Since the flash is not directly accessible.

Otherwise somebody not familiar with the part might think they could compare these numbers to those on other launchpads.

 

Fixed. 1 MBytes. Added comment Storage in Flash, execution in SRAM

 

 

In the pin diagram, why is there a label that says "RESET" under the antenna connector?  (Lower right area of the PCB, Just above the little rocket on the PCB silkscreen).

 

 

Removed. Label from another LaunchPad!

 

 

On PIN_58, PIN_59 and PIN_60 it would make sense to have the blue analogRead() box next to all instances of the pin.

(i.e. going by black pin numbers - 2, 6, and 24 should have blue boxes by them)

The pins that are currently labeled with the blue are not even connected in default configuration (according to the schematic).

 

 

Done, with faded colours.

 

 

A lot of boosterpack pins are not connected to start with (as well as being duplicates of other pins).  It would be helpful to distinguish those pins in some way (e.g., put NC in the gray column, use faded versions of the colors, add an asterisk with a footnote, something)  (pins with numbers in black 33 to 40 and 24 to 26).

 

I was trying to come up with a more visual way of indicating the various connections - but it mostly winds up looking like the tangle of wires behind my computer.

 

 

Done, with faded colours. The 0? shunts are difficult to remove and place.

 

 

Pins numbered in black 39 and 40 are connected to signals ANTSEL 1,2.

(chip pins 29 and 30, GPIO pins 26 and 27, which from the code of the antenna selection example looks like GPIOA3 pins 2 and 3)

This is without connecting the jumper to make them PIN_01 and PIN_02.

 

I haven't read enough to know if there are special limitations on those pins, but might at least be worth noting them as ANTSEL in gray?

 

 

I'm not sure to understand. 

 

 

Could be helpful to label PUSH1 and PUSH2 (next to the buttons) the silkscreen labels are hard to read (and do not seem to use the same name/numbering, from the schematic looks like they say SW2 and SW3).

 

 

Done. Labels are from Energia, e.g. SW3 is PUSH1 according to pins_energia.h

 

 

According to the schematic a couple of the pins that are not connected to start give a choice of pins (might want to note the options)

 

number 38 can be either pin_21 or pin_61

 

number 37 can be connected to number 29, number 8, or number 30  (i.e. PIN_64, PIN_50, or PIN_62)

 

 

The 0? shunts are difficult to remove and place.

 

 

Thanks.  Hope this helps.

 

 

Thank you very much for the detailed comments. It helps me a lot!

[igor 163]

On PIN_58, PIN_59 and PIN_60 it would make sense to have the blue analogRead() box next to all instances of the pin.

(i.e. going by black pin numbers - 2, 6, and 24 should have blue boxes by them)

The pins that are currently labeled with the blue are not even connected in default configuration (according to the schematic).

Just fading the color doesn't totally fix these pins. Should also add non-faded blue boxes next to the versions of these pins which are connected to start with. (Since those pins are capable of analog read). e.g. there should be a blue box that says PIN_58 next to the pin with the black number 2 in the left hand column. Similarly for pins 6 and 24.

 

Thanks.

[igor 163]

Pins numbered in black 39 and 40 are connected to signals ANTSEL 1,2.

(chip pins 29 and 30, GPIO pins 26 and 27, which from the code of the antenna selection example looks like GPIOA3 pins 2 and 3)

 

This is without connecting the jumper to make them PIN_01 and PIN_02.

 

I haven't read enough to know if there are special limitations on those pins, but might at least be worth noting them as ANTSEL in gray?

I'm not sure to understand.

I will try to explain what I meant - but since I haven't studied the data sheet in full detail I am not sure of all the ramifications/limitations/etc.

Unlike some of the other faded pins (which are not connected at all), pins 39 and 40 are connected to pins on the CPU. They are just connected to pins with special functions.

The pins they are connected to are listed with the names ANTSEL1 and ANTSEL2.

They are controlled by GPIO26 and GPIO27.

 

There is a note saying they are "Connected to enable pin of RF switch. Other usage not recommended."

swru367a, table 16-5

 

One can see code that uses these pins in the antenna selection example in the CC3200 SDK.

From the documentation for that example (picture of antenna booster pack board) it looks like those pins have special functions with that board.

 

So it looks to me like these pins are connected, but have special functions, and although they can be controlled by GPIO, this is not recommended. Which could be useful to know if one was designing an antenna boosterpack, or using the antenna boosterpack with other boosterpacks. (i.e. one should use extra caution with pins 39 and 40 to make sure don't have conflicting signals.)

 

So I was suggesting that the gray colored column labels for pins numbered in black 39 and 40 contain the text ANTSEL1 and ANTSEL2 (Right now I don't have the schematic to say which one was 1 and which one was 2).

That would give the reminder that these are connected to something on the board/do have special functions, and then the interested user can look up ANTSEL in the documentation to figure out what it means for their application.

 

Sorry if that is too long-winded of an explanation, but hope it is clearer.

 

Thanks.

[Rei Vilo 695]

@@igor

 

Thank you so much for the clear explanation and the pointers to the documentation. 

 

There are so many documents and so many pages about the CC3200 it is difficult to read them all.

 

I've updated the pins map accordingly: revision is now 1.0.

 

Compared with other LaunchPads, the CC3200 is quite different. I don't understand why so many pins aren't connected

[Rei Vilo 695]

Just fading the color doesn't totally fix these pins. Should also add non-faded blue boxes next to the versions of these pins which are connected to start with. (Since those pins are capable of analog read). e.g. there should be a blue box that says PIN_58 next to the pin with the black number 2 in the left hand column. Similarly for pins 6 and 24.

 

Thanks.

 

Thank you for the explanation. 

 

Same comments about the CC3200 available pins and documentation as in the previous post.

[radiator 0]

>>Compared with other LaunchPads, the CC3200 is quite different. I don't understand why so many pins aren't connected

[servette 0]

Would it be useful to include a note that the jumper shown between P58 and VCC apparently puts the network processor into Access Point mode when using the board's wireless networking capabilities (for example, that's the jumper configuration used when running the demo code right out of the box)?

 

See http://e2e.ti.com/support/wireless_connectivity/f/968/t/358291.aspx

[Rei Vilo 695]

@@servette

 

I don't know whether the P58-VCC short for access-point mode is hardware or software.

[Thorvard 14]

@@servette

 

I don't know whether the P58-VCC short for access-point mode is hardware or software.

 

Its software, i've analysed the out of the box demo shortly after release of the LP.