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.

cc2650 bootloader not responding

Other Parts Discussed in Thread: CC2650, CC2650STK

I'm trying to access the bootloader using cc2650 + devpack by editing the CCFG and setting the flash image as invalid. According to http://www.ti.com/lit/an/swra466a/swra466a.pdf that should cause the device to enter the bootloader and it should respond to commands if BL is enabled (it is). Unfortunately, after sending 0x55 0x55 I never get a response from the device. I've tried wiring the UART pins from the devpack to another MCU and sending commands from there as well as sending the commands directly from my PC but I'm unable to get any sort of response either way. 

  • Hello,

    A couple questions so that I can best help you debug the issue you are seeing:

    1. Please confirm what evaluation board you are using and how you are connecting it to the PC/MCU (wiring diagram or schematic would be best)
    2. Can you provide details about your changes to the CCFG, I understand you are invalidating the flash, but I would like to know exactly how you are doing so
    3. Alternatively can you try to modify the CCFG to enable to BL backdoor and set the pin to the required level and see if this warrants a response from the BL
    4. Can you provide a logic trace of the above tests?
  • 1. I'm using the cc2650STK + Devpack, connected directly to PC via Micro USB cable. Also have another cc2650STK wired to another MCU using pins 10/12 (UART_TX and UART_RX) on the devpack. I know my pins are correct because I've used the same setup in the past to send commands to the 2650 and get responses, and I'm able to do so now if I flash a valid .bin file.

    2. In startup_files/ccfg.c I have SET_CCFG_IMAGE_VALID_CONF_IMAGE_VALID set to 1.

    3. Unfortunately I'm working remotely today so I'm not able to do that at the moment, which is why I'm invalidating the image instead.

    4. Not sure what you mean.
  • Hello,

    1) I think this may be your issue. Section 8.2.2 of the Technical Reference Manual (table 8-2) shows that the ROM bootloader uses DIO_2 and DIO_3 as the UART transport pins for the 7x7 package. However, the sensortag will use DIO_28 and DIO_29 as the UART pins. If you can route the UART backchannel of the devpack debugger to these pins I would expect you to see a response.

    2) This sounds correct

    3) Okay, lets probe along option #1 for now

    4) I mean using a logic analyzer to capture the state of the pins during the BL transfer.
  • So I've changed BOARD_UART_RX and BOARD_UART_TX to use DIO2 and DIO3 respectively but I'm still not getting a response. Just to confirm, should the red LED be on after setting the image to invalid/in BL? I can't find anything regarding it in the bootloader docs (swra466a.pdf/swcu117f.pdf) so I just want to make sure I'm actually in the bootloader.
  • I guess I'll just assume the cc2650STK isn't able to access the bootloader without a devpack then.
  • Hello,

    I wouldn't agree that the sensortag development kit cannot access the bootloader without a depack. I believe that there may still be a small issue in your setup.

    Changing the pinout in the board file will only affect the way the SensorTag sample app assigns and uses the UART pins. However, in order to access the bootloader you will need to physically change your wiring to the STK in order to access the device.

    Can you provide a wiring diagram or a brief description of how you are connecting to the device?
  • hello jc12321,
    I'm also using the cc2650STK + Devpack. My cc2650 bootloader not responding. Could you help me?