CYBLE343072-02 issues getting testPUARTDiver working using ModusToolBox

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
JohnKir
Level 1
Level 1
First question asked Welcome!

I have the pins configured as:

#include "cycfg_pins.h"

const wiced_platform_gpio_t platform_gpio_pins[] =
{
[PLATFORM_GPIO_0] = {WICED_P10, uart_1_cts_0_TRIGGER_IN},
[PLATFORM_GPIO_1] = {WICED_P11, uart_1_rts_0_TRIGGER_IN},
[PLATFORM_GPIO_2] = {WICED_P29, uart_1_rxd_0_TRIGGER_IN},
[PLATFORM_GPIO_3] = {WICED_P32, uart_1_txd_0_TRIGGER_IN},
};

 

I am seeing the data being sent, but nothing on the CTS line.

 

Started with the empty_wiced_bt.c Empty_BDSDK_App for the part CYBLE343072-02

void testPUARTDriver(void)
{
uint8_t readbyte;
uint8_t loopCtrl = 1;
char printBuffer[50];
//Pins for PUART should be configured from wiced_platform_pin_config.c

wiced_hal_puart_init();

wiced_hal_puart_flow_off(); //turn off flow control
wiced_hal_puart_enable_tx();
wiced_hal_puart_enable_rx();


while(loopCtrl)
{while(wiced_hal_puart_read(&readbyte))
{
wiced_hal_puart_write(readbyte);
if(readbyte == 'S')
{
wiced_hal_puart_print("\nYou typed 'S'.");
sprintf(printBuffer, "\nThis message sprintf'ed here.");
wiced_hal_puart_print(printBuffer);
}
if(readbyte == 'E') // End.
{
loopCtrl = 0;
}
}
}
}

0 Likes
1 Solution
Owen_Zhang123
Moderator
Moderator
Moderator
5 questions asked 500 solutions authored 250 sign-ins

The CTS pin is pulled by the peer device which indicates it can receive data or not.

View solution in original post

0 Likes
1 Reply
Owen_Zhang123
Moderator
Moderator
Moderator
5 questions asked 500 solutions authored 250 sign-ins

The CTS pin is pulled by the peer device which indicates it can receive data or not.

0 Likes