CC2640R2F: TI flash tool allow to flash CC2640,CC2620, CC13252P and CC1310F128

chandra n

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640, CC2620, UNIFLASH

i have written a code for CC2640R2F, but when I select any other Target Device(correct device is CC2640R2F) such as CC2640,CC2620, CC13252P and CC1310F128,
the TI flash tool firmware downloading prompt is also “success”.

TI flash tool is allowing them to flash all the above devices which are my main concern

over 2 years ago

0 Jan over 2 years ago

TI__Mastermind 42320 points

Hi,

Can you specify which flashing tool you are using? Is this occurring in flash programmer 2 or in Uniflash?

Best Regards,

Jan

0 chandra n over 2 years ago in reply to Jan

Prodigy 41 points

this is occuring in programmer 2.

0 Jan over 2 years ago in reply to chandra n

TI__Mastermind 42320 points

Hi,

That is strange. I would expect the device to be identified or at the very least the ID to be displayed. Can you specify how you are connected to your device? Is your device on a custom board or a launchpad?

Best Regards,

Jan

0 chandra n over 2 years ago in reply to Jan

Prodigy 41 points

My device is connected to a custom board.

0 Jan over 2 years ago in reply to chandra n

TI__Mastermind 42320 points

Hi,

Got it. Are you using an XDS110 to connect your board to your PC? Can you share a picture of the setup?

Best Regards,

Jan

0 chandra n over 2 years ago in reply to Jan

Prodigy 41 points

Hi Jan,
i am using my BLE module supplier board to flash, i don have the details on that. My question is how does the setup matter if the tool allows flashing any other controller?

0 Jan over 2 years ago in reply to chandra n

TI__Mastermind 42320 points

Hi,

The main reason I ask is because when connecting to Flash Programmer 2, the device should be identified in the connected devices section as shown below:

I am able to see the behavior that you are referencing, being able to flash a board with another board's image, however one should not do this. One should only flash an image of the same board than the board identified.

Best Regards,

Jan

0 chandra n over 2 years ago in reply to Jan

Prodigy 41 points

Hi Jan,

pls check the below image of our connected device:

0 Jan over 2 years ago in reply to chandra n

TI__Mastermind 42320 points

Hi,

That looks good. I would make sure that you always flash an image that was compiled for the device that is identified in Flash Programmer 2.

Best Regards,

Jan

0 chandra n over 2 years ago in reply to Jan

Prodigy 41 points

okay thanks. By When you can provide the solution?

0 Jan over 2 years ago in reply to chandra n

TI__Mastermind 42320 points

Hi,

From a JTAG perspective, we are simply writing bytes to the flash of the connected device. So from a flash writing perspective, the operation is executing properly. It is the responsibility of the process that is performing the flashing (manual by a single person or automated using scripts) to ensure the image provided is compiled for the connected device. The flash programmer 2 tool does not extract any information from the hex file to verify the device type.

You can create some scripts using Uniflash Commandline to check the device type connected before flashing it with a known image if desired.

Best Regards,

Jan

Bluetooth®︎

Bluetooth forum

CC2640R2F: TI flash tool allow to flash CC2640,CC2620, CC13252P and CC1310F128