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.

CC2640: Does the GPIO output pin follow the state of the Sensor Controller when debugging in Sensor Controller Studio?

Part Number: CC2640
Other Parts Discussed in Thread: SENSOR-CONTROLLER-STUDIO

I'm attempting to debug a task in Sensor Controller Studio.

The task is connected (it says Task Testing [connected] in the column to the left]

The initialization is run.

Then CTRL-F11 is pressed to run and debug one iteration.

The Task Debugging - Execution Code panel is open and the debugger is single-stepping and running to break-point, etc.

A breakpoint is placed at the instruction immediately following the instruction below:

                            gpioSetOutput(AUXIO_O_PERIPHERAL_GND);

0106 ---- 660e                      iobset       #(2 & 0x7), [#(IOP_AIODIO0_GPIODOUT + (2 >> 3))]

Breakpoint set here

                            fwDelayUs(100000, FW_DELAY_RANGE_100_MS);

-> 0107 ---- 7093                      ld        R7, #(((100000 * 24 ) + ((1 << 14) - 1 )) >> 14 )

The debugger runs and then stops at the instruction above^ 

Should I be able to see the GPIO pin set on the chip?

I place a scope on the GPIO pin, but it is not high.

What' am I doing wrong?

John

  • Hi John,

    Yes, you should be able to see the GPIO pin toggle.  Have you tried the SENSOR-CONTROLLER-STUDIO LED Blinker/PWM LaunchPad examples or followed the Project from Scratch SimpleLink Academy Lab?  This will help with your task properties and I/O mapping.

    Regards,
    Ryan

  • Thanks Ryan,

    I reviewed some of the Sensor Controller documents you referred to and was able to get the Sensor Controller simulator working. It now toggles the gpio outputs as it should. I don't know what the problem was on prior attempts. One thing that may have made a difference was the chip type. I was specifying a 2650 when it was failing and I switched to the 2640 and it now works. It said the 2650 code was compatible with the 2640, so it shouldn't have made a difference, however, I didn't find any other issues that would have made it fail to toggle the outputs.

    Anyway, it's working great now, so thanks.

    Regards,

    John