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.

CC2640: Firmware upgrade over UART

Part Number: CC2640


Hi,
     I am using CC2640R2F lauchpad. In that i want to flash a hex file using a python script which I downloaded  from github.com/.../cc2538-bsl. I installed python ,python-magic. Using this script firmware upgrade is working over Launchpad's builtin UART to USB converter. But If I use an external UART to USB converter, I am getting ACK/NACK error. What could be the issue? Can anyone please update on this. Any quick response will be greatly appreciated.

  • Hi Paul,

    I have not worked with this script before, but looking at it it seems to always be selecting the first available serial port it finds.
    Are you having the LP connected to the computer while trying the external UART to USB converter?
    If this is the case. have you verified that the correct serial port is getting opened when you run the script with the external UART to USB converter?
  • Hi M-W,
    Thanks for the quick response. Iam connecting launchpad USB to another pc for power only. Is any thing to takecare while communicating controller UART pins via USB converter. With the external uart to usb converter only /dev/ttyUSB0 is opened in my case and Ia m selecting that. Actually while using internal usb converter communication is success via /dev/ttyACM0 - USB debugger UART -controller UART via that script .In this type I programmed several times. But If I connect ext UART and controller UART ( debugger portion is not here) no acknowledgement from the device. Is any s/w portion required for this because of the absense of debugger?
  • Hi Binchu,

    I'm afraid I don't think I can help you much more then this as I'm not familiar with this script and it is not something released by TI. You could try to reach out to the creator of the script and see if he has any pointers for you.

    You can try removing the debugger jumpers, only leaving the jumpers needed to power the chip and see if this makes any difference. Also, if possible, try another USB -> Serial converter. You can also try checking the communication with e.g. a logic analyzer to see what is differs between the two communication attempts. 

    Good luck with getting this to work!

  • HI M-W,
    Thanks for the quick response. That was my boards issue. When I replaced USB ->Serial converter as you suggested it works. Thanks for your support.