Menu

couldn't start nRouted

2008-08-15
2013-04-29
  • Haluk Durmus

    Haluk Durmus - 2008-08-15

    nRouted couldn't Start but the error message is "Success"

    ./nano_usb_programmer -m
    Opening programmer.
    prog_start()
    Status: B6.
    Chip ID = 8503.
    CC2430 chip found.
    Read MAC: FF:FF:FF:FF:FF:FF:FF:F1
    Closing programmer.

    dmesg:
    [10827.183722] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
    [10827.183895] /build/buildd/linux-2.6.24/drivers/usb/serial/ftdi_sio.c: Detected FT232RL
    [10827.204983] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

    nRouted.Log
    2008-08-16 09:35.09  Configuration file parsed.
    2008-08-16 09:35.09  Everything fine, nRouted version 1.0 starting using nRP version 0.
    2008-08-16 09:35.09  Closing standard file I/O
    2008-08-16 09:35.09  Starting serial server thread.
    2008-08-16 09:35.09  Serial server started, looks good.
    2008-08-16 09:35.09  Serial send buffer(s) initialized succesfully.
    2008-08-16 09:35.09  Starting serial write thread.
    2008-08-16 09:35.09  Starting TCP server thread.
    2008-08-16 09:35.09  TCP server started, looks good.
    > 2008-08-16 09:35.09  Serial port open failed with error message: Success.

    regards,
    Haluk

     
    • shelby

      shelby - 2008-08-16

      Haluk,

      Both nano_usb_programmer and nRouted are using the same serial port to communicate with your device. You can't have 2 programs using a serial port at the same time, probably what is causing the problem. When using nRouted be sure not to use *any* programs, including minicom, on the same port. You also must shut all other programs when programming.

      - Zach

       
    • Haluk Durmus

      Haluk Durmus - 2008-08-16

      Hmm...
      I always try to run one program and to same time,
      and to be sure than the serial port is not used by an other program,
      I unplug the usb cable and plug it in again and control the state of the port calling dmesg.
      There I can see that the port is disconnected and registered again correctly at port /dev/ttyUSB0.

       

Log in to post a comment.