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.

ZNP and znp-host-framework by "UART without Power Management" mode

Other Parts Discussed in Thread: CC2630

Hi, all,

we use znp and znp-host-framework develop our appilication. Znp runs on cc2630, and znp-host-framework runs on an host processor which has Ubuntu OS. The communicates interface between them is from UART. And we'd like to use "UART without Power Management" mode which requires only two wires(RX/TX).

But during our test, I always failed to acess CC2630. It always feed back folow message, which seems CC2630 didn't response to host app.:

# /opt/cmdLine.bin /dev/ttyS1 
Do you wish to start/join a new network? (y/n)
y
rpcSendFrame: SRSP Error - CMD0: 0x21 CMD1: 0x09
network start failed
Network Error


rpcSendFrame: SRSP Error - CMD0: 0x21 CMD1: 0x04
rpcSendFrame: SRSP Error - CMD0: 0x21 CMD1: 0x09
Enter CMD

I'm confusing about it because when I did the same test from USB-to-Serial interface, it could connect successful.

Failed case :        【CC2630 Serial(RX/TX)】    <--->    【Host CPU Serial(TX/RX)】

Success case:     【CC2630 Serial(RX/TX)-To-USB】    <--->    【Host CPU (USB driver, /dev/ttyUSB0)】

The difference between them is USB-To-Serial switch chip. But the Uart interface is same RX/TX wires.

Is there any points I didn't understand correctly? Very appreciate for your any advice.  

  • What's your host CPU?
  • For Succcess case upon, I used Intel x86 notebook as Host CPU side which was installed Ubuntu 12.04 64bit OS. The CC2650DK (1pcs SmartRF06 and 1pcs CC2650EM ) was programmed with ZNP image as ZNP side. The Host CPU connected with the USB interface on SmartRF06 board by USB cable.
    For Failed case upon, I used Cavium 64bit CPU board as Host CPU side. Because there is one UART jumper can be used for my testdirectly . The Linux OS on it is big endian.
  • I suggest you to use oscilloscope to check TX/RX signal on failure case.
  • Yes, thanks for your advice. The problem was resolved just now. The main reason is mismatch of UART flow control.
    When in USB-To-UART case, it was hid because by switch chip. But in UART case, it exposed. Logged here and hope useful for others.
  • You are welcome and it's good to know it works now.