CCS/CC2650: CODE OR HEX FILE CAN NOT LOAD TO CC2650

I suggest you to refer to processors.wiki.ti.com/.../CC26xx_HW_Troubleshooting to do HW trouble shooting first.

In addition to the troubleshooting tips, the DevPack Debugger (CC-DEVPACK-DEBUG) is not recommended for debug/program of CC26xx custom boards. I suggest using a compatible debugger listed in the Tools wiki page (link on BLE Wiki), such as the LAUNCHXL-CC2650 LaunchPad and a 10-pin JTAG cable.

Best wishes

thank  you for your reply

but i want to know what is the difference between these debugger

i gone through the schematic of both have similar except 2 buffers used for debug line in lunchpad.

why can't i use CC-DEVPACK-DEBUG please explain technically

thank you.

I think it's because the connector of cc-devpack-Debugger is specifically designed for CC2650STK and it would be easier for you to use XDS110 Debugger of LAUNCHXL-CC2650.

for connection i made a wiring from the CC-DEVPACK-DEBUG according to schematic of cc-devpak-debug provided by TI

here is

i can read the mac address of the target device i.e mac of cc2650

 

 

and when i try to upload one of the hex file which is not going through

please look at the below image for the error what i get in flash program 2

 

 

please tell me what exactly is happening and revert back to me

thank you

Hi,

I have used CC-DEVPACK-DEBUG to debug and flash hex file to our custom CC2640R2 board. The CC-DEVPACK-DEBUG is wired to our custom CC2640R2 board.

If your CC-DEVPACK-DEBUG wiring to your custom CC2650 board is correct, then maybe there is a problem with the custom CC2650 board.

- kel

I agree with Markel. There's no reason that you cannot use cc-DevPack-Debugger

okay ,

this is my custom cc2650 schematic and please find  out  and let me know where i made a mistake.

 

 

you mean we can also use CC-DEVPACK-DEBUG to flash cc2650 and debug the device.

if the custom board design is wrong, then how it can be identified in flash program 2...?

thank you

keerthi kumar said:

you mean we can also use CC-DEVPACK-DEBUG to flash cc2650 and debug the device.

Yes, I use CC-DEVPACK-DEBUG wired to my custom CC2640R2 board for CCS/IAR debug and flashing using SmartRF Flash Programmer 2, so should work same for CC2650.

keerthi kumar said:

if the custom board design is wrong, then how it can be identified in flash program 2...?

The SmartRF Flash Programmer 2 output log can provide some slight clue to what causes the problem.

Is your custom CC2650 board design based from CC2650 Launchpad? If yes, is there any component that is different from CC2650 Launchpad?

You also need to check everything that is needed to make your custom CC2650 board work, that includes power supply, crystal frequency, and others.

- kel

there is no difference .. the design is purely based on cc2650 launchpad..
we can see the device detection in smartRF flash program 2 , it erases the 2650 flash and its only get failed to write the new flash .
why..??

Hello,

You mention that the design is "purely based on cc2650 launchpad" however you are using a 5x5 vs the 7x7 on the LaunchPad. Also, from your schematic, it looks like you placed load caps on the 24 MHz xosc. Please review the HW Troubleshooting tips on the BLE wiki and report your findings. You may also have a layout or assembly issue that is preventing proper operation.

Please perform the check items and report your findings.

Best wishes