CC2652R: Basic Display/UART Function Standalone board

Matt Gaidica1

Part Number: CC2652R
Other Parts Discussed in Thread: SYSCONFIG

I want to use DIO_2 and DIO_3 for UART on a standalone board. This is my configuration in SysConfig and code. When I put Tx on a scope I don't see anything—am I missing something simple here? These lines don't need a pull-up or something do they?

#include <ti/display/Display.h>
...

Display_Handle dispHandle = NULL;

dispHandle = Display_open(Display_Type_ANY, NULL);

while(1) {
	Display_printf(dispHandle, 0, 0, "abc");
}

over 5 years ago

0 YiKai Chen over 5 years ago

Guru 735705 points

I suggest you to try uartecho example.

0 Ryan Brown1 over 5 years ago

TI__Guru**** 223727 points

Hi Matt,

Beyond YK's advice, please refer to the Custom Hardware section of the BLE5-Stack User's Guide and the display example.

Regards,
Ryan

0 Matt Gaidica1 over 5 years ago in reply to Ryan Brown1

Expert 1540 points

Despite copying the Display/UART settings from display.syscfg, I still can't get the XDS UART to work when I plug the code into simple_peripheral. The precompiler flags don't seem to matter. This is my code after SimplePeripheral_init().

GPIO_init();

	Display_init();
	Display_Params params;
	Display_Params_init(&params);
	params.lineClearMode = DISPLAY_CLEAR_BOTH;
	Display_Handle hSerial = Display_open(Display_Type_UART, &params);
	if (hSerial == NULL) {
		while (1) {
		}
	}

Which reaches the NULL loop. The display.c example works.

0 Ryan Brown1 over 5 years ago in reply to Matt Gaidica1

TI__Guru**** 223727 points

The Simple Peripheral project already uses the Display TI Driver for its two-button menu, see simple_peripheral.c and two_btn_menu.c for more information. You would need to use/modify this existing module or remove/replace it from the application. https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/creating-a-custom-bluetooth-low-energy-application-cc13x2_26x2.html?highlight=display#remove-the-two-buttons-menu-and-display

Regards,
Ryan

0 Matt Gaidica1 over 5 years ago in reply to Ryan Brown1

Expert 1540 points

Thanks, I followed a lot of those steps to remove the menu a while back as well as the NPI folder. Now that I've added it back, dpi_tl.c tosses an undefined error for "CONFIG_PIN_BTN1" (and BTN2) since those are not defined in my GPIO. It's here, I guess I'm trying to workaround without modifying SDK source files.

static PIN_Config npiHandshakePinsCfg[] =
{
    MRDY_PIN | PIN_GPIO_OUTPUT_DIS | PIN_INPUT_EN | PIN_PULLUP,
    SRDY_PIN | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MAX,
    PIN_TERMINATE
};

0 Ryan Brown1 over 5 years ago in reply to Matt Gaidica1

TI__Guru**** 223727 points

So have you removed all instances of CONFIG_PIN_BTN1 from board_key.c, simple_peripheral.c, and simple_peripheral.syscfg? What is its relation to the npiHandshakePinsCfg?

Regards,
Ryan

0 Matt Gaidica1 over 5 years ago in reply to Ryan Brown1

Expert 1540 points

Yes. But in npi_config.h there is still this block looking for CONFIG_PIN_BTN1:

#if (NPI_FLOW_CTRL == 1)
  #ifdef NPI_USE_SPI
    //NOTE: Board_SPI1 SPI module must be used for NPI.
    #define MRDY_PIN CONFIG_PIN_BTN1
    #define SRDY_PIN CONFIG_PIN_BTN2
  #elif defined(NPI_USE_UART)
    #define MRDY_PIN CONFIG_PIN_BTN1
    #define SRDY_PIN CONFIG_PIN_BTN2
  #endif
  #define SRDY_ENABLE()                   PIN_setOutputValue(hNpiHandshakePins, SRDY_PIN, 0) /* RTS low */
  #define SRDY_DISABLE()                  PIN_setOutputValue(hNpiHandshakePins, SRDY_PIN, 1) /* RTS high */
#else
  #define SRDY_ENABLE()
  #define SRDY_DISABLE()
#endif // NPI_FLOW_CTRL = 1

Do I need to use the NPI or is it possible to just run XDS UART?

0 Ryan Brown1 over 5 years ago in reply to Matt Gaidica1

TI__Guru**** 223727 points

If you do not require a Network Processor Interface then you can/should just enable UART functionality. Furthermore, you could not use MRDY_PIN/SRDY_PIN by setting NPI_FLOW_CONTROL to 0.

Regards,
Ryan

0 Matt Gaidica1 over 5 years ago in reply to Ryan Brown1

Expert 1540 points

Great. I guess I should have just gone with standalone UART from the start, for some reason I recall XDS not showing up under hardware in SysConfig UART, but I must have looked over it or something. Binary is much better for me anyways. For reference, NPI folder can be excluded from build and those header files can be removed (or #define PTM_MODE 1).

Thanks for leading the horse (or donkey ) to water.

Bluetooth®︎

Bluetooth forum

CC2652R: Basic Display/UART Function Standalone board