Problem sending chars

RE: Problem sending chars

ryerye120 — Tue, 14 Apr 2020 17:24:17 GMT

That may have something to do with how the CDC ACM example processes received chars from the keyboard. So depending on when you print you may only get one character at a time. How are you triggering the transmissions? Do you have an example that allows for typing in one terminal and transmitting that to another?

RE: Problem sending chars

Pinout_1 — Tue, 14 Apr 2020 15:15:50 GMT

Thanks ryerye120, according to your suggestion, I made a few changes in my code, now I'm able to see strings. But now I have other problem - I can see only one string. For example when I declare a string in the Tx side, I get H word in the Rx side. Maybe it is CDC ACM problem?

RE: Problem sending chars

ryerye120 — Fri, 10 Apr 2020 16:26:17 GMT

In the end, you're just sending and receiving bits. So what are you sending and how are you casting on the RX side? It looks like you're printing them as 'unsigned longs'. Try sending a string and printing it with %s.

On the Tx side you can make a test string like this:

#define TEST_STRING "comes_from_tx"
static uint8_t       m_tx_buf[] = TEST_STRING;

and then on the rx side you can debug with NRF log:

NRF_LOG_INFO(" Transfer completed. Received: %s",(uint32_t)m_rx_buf);