CCS/LAUNCHXL-CC2650: Connecting Educational Boosterpack MK II with CC2650 LaunchPad

Great I'll give that a shot. I saw that I could use the MSP432 SDK but since I didn't need all the other capabilities of the booster pack I figured I could just use the display drivers given for my board. Since that obviously didn't work, I'll try looking at that thanks.

I tried looking at the MSP432 example. Seems like there are LcdDrivers (Crystalfontz128x128_ST7735.h) and ti/grlib/grlib.h drivers. How do I adapt these drivers to work with my board, either the CC2650 or CC26x2 launchpads? I see that there are defines for these pins, but I'm not sure how these relate to my board(s):

// Ports from MSP432 connected to LCD
#define LCD_SCK_PORT          GPIO_PORT_P1
#define LCD_SCK_PIN_FUNCTION  GPIO_PRIMARY_MODULE_FUNCTION
#define LCD_MOSI_PORT         GPIO_PORT_P1
#define LCD_MOSI_PIN_FUNCTION GPIO_PRIMARY_MODULE_FUNCTION
#define LCD_RST_PORT          GPIO_PORT_P5
#define LCD_CS_PORT           GPIO_PORT_P5
#define LCD_DC_PORT           GPIO_PORT_P3

// Pins from MSP432 connected to LCD
#define LCD_SCK_PIN           GPIO_PIN5
#define LCD_MOSI_PIN          GPIO_PIN6
#define LCD_RST_PIN           GPIO_PIN7
#define LCD_CS_PIN            GPIO_PIN0
#define LCD_DC_PIN            GPIO_PIN7

Bharathi,

There already exists an LCD Display handle configured in the Board file for the CC26x2 LaunchPads. Checkout CC26X2R1_LAUNCHXL.c in the SimpleLink SDK. You can reconfigure the LCD CS, POWER and Enable pins to the corresponding pin on the BoosterPack.

So I found this in CC26X2R1_LAUNCHXL.c:

const DisplaySharp_HWAttrsV1 displaySharpHWattrs = {
.spiIndex = CC26X2R1_LAUNCHXL_SPI0,
.csPin = CC26X2R1_LAUNCHXL_GPIO_LCD_CS,
.powerPin = CC26X2R1_LAUNCHXL_GPIO_LCD_POWER,
.enablePin = CC26X2R1_LAUNCHXL_GPIO_LCD_ENABLE,
.pixelWidth = BOARD_DISPLAY_SHARP_SIZE,
.pixelHeight = BOARD_DISPLAY_SHARP_SIZE,
.displayBuf = sharpDisplayBuf,
};


Is this what I need to change? If so, what are the corresponding values for the Boosterpack then? I'm struggling to find that info. I'm also unsure what CS, POWER, and ENABLE refer to.

You need to find out which pins on the BoosterPack is the CS, Power and Enable pins. Then, you need to see which pins this matches on the LaunchPad.

Yes I understand that. I just can't seem to find on any documentation which pins are the CS, Power and Enable pins. Once I figure out those pins, I can figure out which of those correspond to the LaunchPad.

The PIN layout of the BoosterPack is documented in the User's Guide: www.ti.com/.../slau599a
Then, simply see where a given PIN matches on the LaunchPad. That is the DIO you want to use in your board file.

I've looked over the document, but I am still struggling to identify which pins correspond to ENABLE and POWER. The diagram 2.1.1 on page 5 seems relevant. But it doesn't point to which pins are power and enable. I also don't understand what power and enable are, could these be mapped to any GPIO pins on the launchpad. 

I do see the SPI and CS on the diagram, so that's a start. Looks like SPI is pin 7 and CS seems to be pin 13. Can you please confirm this?

Thanks,

Bharathi

I'm getting:

LCD SPI clock: DIO10
LCD SPI chip select: DIO13
LCD SPI MOSI: DIO9
LCD reset pin: DIO17
LCD backlight: DIO6

It seems like the LCD display is powered by the attached LaunchPad via the 3v3 and 5v pins, so there is no need to use a Power pin. In addition, the LCD also seems to be always enabled, so need for the Enable pin as well.

Have you taken a look at the LcdDriver as supplied by the MSP432 SDK?

Great thank you. Are these the pin configurations for the booster board or the launchpad?

I took a look at the LcdDriver on MSP432 SDK. It used the Crystalfontz128x128_ST7735.h and the ti/grlib.grlib.h drivers. I was unsure how to adapt these drivers with my launchpad. Is it just a matter of changing those pins as we discussed?

That is for the LaunchPad.

The Crystalfontz128x128_ST7735.h/c files can probably be left untouched. It looks like you need to implement the HAL files for the CC2650. That is, the HAL_MSP_* files must be re-implemented for CC2650.

Hey,

I've actually been busy working on another project, so I haven't been able to test this. I'll keep you updated as things develop though.