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.

CCS/CC3220SF-LAUNCHXL: GPIO_write not working with P59 / GPIO_04

Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: SYSCONFIG, CC3220SF, OPA4342

Tool/software: Code Composer Studio

I'm trying to integrate some hardware pins 21 through 26 on the +5v side.  The small test hardware is just a quick pin setup with some LED's and one test switch.

Right now, I'm just trying to enabled one of the LEDs through code and aws_iot.syscfg window.

I enabeld one like the following screenshot.

I see the generated code and I'm using the code, must like the standard LED on/off code base.  That code for the Red LED is working fine, but I can't seem to find the issue why the LED (from an external board soldered up) isn't working.

And in my code, I'm calling two functions and it doesn't appear to light up.

        GPIO_write(CONFIG_GPIO_LED_0, CONFIG_GPIO_LED_ON);


        GPIO_write(CONFIG_GPIO_FM_LFT_DN, CONFIG_GPIO_LED_ON);

But the standard (CONFIG_GPIO_LED_0  - on board) LED is working fine.

Is there something I'm missing that needs to be configured?

I'm even setting the following, but I'm not sure if it's even required, but I did notice the CONFIG_GPIO_LED_0 is configured the same way in some of the sample code.

    GPIO_setConfig(CONFIG_GPIO_FM_LFT_DN, GPIO_CFG_OUT_STD | GPIO_CFG_OUT_LOW);

I'm mostly using the publish / subscribe example application along with the out of box sampleAny  application integrated together. I'm also using the AWS IoT plugin codebase as well.

Any help would greatly be appreciated as I'm really stuck on this one, and somewhat new to TI hardware.

  • To add to this, the external hardware is using the 5v line, some resistors and some other piece of hardware, to power the LEDs from the incoming lines.  I have 3 LED's.  One is attached to P57, Another P58, and another to P59.

    I think the configuration is right on the SysConfig panel, but I really don't know.  The hardware guy says that I may not have to point to P59

    For now, I just configured the P59 option until I get one of them working.

    Also, within the SysConfig editor and the GPIO Pin drop down, I don't even see a P47/23 option. I'm wondering how to utilize that Pin now?  I see a lock / unlock option on that field, but not sure exactly how to work this.

  • Hi,

    As to be honest I don't understand what you have done at software side. Please wait for someone else which maybe understand your needs. But I want to say few comment related to hardware:

    • CC3220 does not have TTL tolerant GPIO pins. That means +5V at I/O pins may to damage CC3220 chip. Please do not use GPIO pins from CC3220 for direct driving 5V circuits. You should to use voltage level shifter.
    • It seem that you are using CC3220SF LaunchPad. At this LaunchPad are pins 58, 59, 60 intended for using with ADC. From this reason are connected to buffer OPA4342 (voltage follower). If you want to use this pins as GPIO, you need to do hardware modification of you LaunchPad. Please see this thread.
    • Pin P57 is as default connected to UART. In case you want this pins use as GPIO you need to disconnect UART at jumper J6 (change position to BP connector 1+2).
    • Pin P47 is a VDD_ANA2 pin. It is one of powering pins of CC3220SF and from this reason it cannot be used as GPIO.
    • Pin P23 is used for a connection of fast clock 40MHz XTAL.

    Please study schematic for your LaunchPad to discovery how is connected and which pins you can use.

    Jan

  • Thanks for the response.  I talked to our hardware guy and we are using VL shifters to power the LED's.  We ended up working around some of the shared Pins and only using some of the Pins (like 18, 21, and 61 for outputs, and 62 for input). The only one we've seen some subtle issues with is Pin 21 as it seems shared so when we flash the device OR reset the board, the LED will turn on (within our external connected test board).  Not major for now, but it seems we found some solutions to the problem.

  • Hi,

    behaviour which you see during reset at pin SOP2 pin (pin 21) is normal and expected. There you should see short scanning pulse after reset (moment when state of SOP2 pin is scanned).

    Jan