CC1310: CC1310F32 DEVICE ACCESS ACCESS FAILED : XBAL : TARGET CONNECT FAILED

Ajit Chaudhari27

Prodigy 170 points

Part Number: CC1310
Other Parts Discussed in Thread: UNIFLASH

hi,

CC1310F32 connect successfully with SmartRF Studio 7 and Flash Programmer 2.

Program burn into cc1310 successfully by using Flash Programmer 2.

After program burn device not detect in SmartRF Studio 7 and Flash Programmer 2 for reprogramming.

In Flash Programmer 2 shows Unknown.

device cc1310 detect only once after programming it is not detect, is this problem because of hardware or flash programmer?

plz help me to solve this issue.

over 8 years ago

0 TER over 8 years ago

TI__Guru**** 317180 points

If you overwrite the CCFG area of the flash you can end up bricking the device. Have you set correct flash size in your program? If you use a F128 image on a F32 device you can risk this.

0 Ajit Chaudhari27 over 8 years ago in reply to TER

Prodigy 170 points

I use CC1310F32

i defined below in program .cmd file

#define FLASH_BASE 0x0
#define FLASH_SIZE 0x8000
#define RAM_BASE 0x20000000
#define RAM_SIZE 0x4000

Is this correct?

0 FredG over 8 years ago in reply to Ajit Chaudhari27

TI__Expert 6540 points

Hi, yes that looks correct. I compared it to a cmd file I have for a F32 project:

/* The starting address of the application.  Normally the interrupt vectors  */
/* must be located at the beginning of the application.                      */
#define FLASH_BASE              0x0
#define FLASH_SIZE              0x8000
#define RAM_BASE                0x20000000
#define RAM_SIZE                0x4000
#define GPRAM_BASE              0x11000000
#define GPRAM_SIZE              0x2000

0 Ajit Chaudhari27 over 8 years ago in reply to FredG

Prodigy 170 points

if size defined is correct then why device is not detect after program burn.

0 Ajit Chaudhari27 over 8 years ago in reply to Ajit Chaudhari27

Prodigy 170 points

if device is bricking then how to recover it?

0 FredG over 8 years ago in reply to Ajit Chaudhari27

TI__Expert 6540 points

If bricked: mass erase option in Flash Programmer 2 - but that does not work if your device shows up as unknown.
So what kind of HW are you testing on? Custom?

0 Ajit Chaudhari27 over 8 years ago in reply to FredG

Prodigy 170 points

HW is custom designed.

0 TER over 8 years ago in reply to Ajit Chaudhari27

TI__Guru**** 317180 points

Do you have a board you haven't tried to flash? If yes, could you post a screenshot of the flash programmer GUI when you have connected to the board (before flashing it)?

0 Ajit Chaudhari27 over 8 years ago in reply to TER

Prodigy 170 points

see below screen shot

0 Ajit Chaudhari27 over 8 years ago in reply to Ajit Chaudhari27

Prodigy 170 points

0 FredG over 8 years ago in reply to Ajit Chaudhari27

TI__Expert 6540 points

Ok, have you programmed more devices with this code or just this one?
Is it possible for you to make a generic project which reproduces the error?

0 Ajit Chaudhari27 over 8 years ago in reply to FredG

Prodigy 170 points

I programmed 4 devices using Flash Programmer 2 and it fails.

i tried 5th device programmed using Uniflash with same program file and it's working fine.

0 FredG over 8 years ago in reply to Ajit Chaudhari27

TI__Expert 6540 points

Hi, ok that I have not heard about before.
I tested programming the EM with the F32 code with both applications and they both worked as expected.
So I am not able to reproduce what you are seeing on your side. But I will forward your case to our tools department to get a statement.

0 TIABO over 8 years ago in reply to Ajit Chaudhari27

TI__Genius 12900 points

Ajit,

Can you share the output file you are using to program the CC1310F32? It makes it easier for us to reproduce.

TIABO

0 Ajit Chaudhari27 over 8 years ago in reply to TIABO

Prodigy 170 points

see attached output file.

rfPacketTx_CC1310_LAUNCHXL_tirtos_ccs.rar

0 Ajit Chaudhari27 over 8 years ago in reply to Ajit Chaudhari27

Prodigy 170 points

Hi TIABO,

Have you checked attached output file.

0 TIABO over 8 years ago in reply to Ajit Chaudhari27

TI__Genius 12900 points

Ajit,

I converted the provided .out file to a binary file. Then I programmed the .out file onto a CC1310F128 (on purpose) and read back the flash content into a binary file. Comparing the two binary files show that they are identical for the first 32KB. Next step will be to program your .out file to a CC1310F32 to see if that is any different.

TIABO

0 TIABO over 8 years ago in reply to TIABO

TI__Genius 12900 points

Ajit, I'm unable to reproduce what you are seeing. Programming the .out file you provided works fine using SmartRF Flash Programmer 2 v1.7.5. The flash content I read back from the device is identical to what is expected (compared to a binary generated from the .out file). This does not appear to be an issue with SmartRF Flash Programmer 2.

What you can try is to turn off the "Disconnect frafter action finished" setting found under the Tools icon. Then you can (a) erase/program/verify the image onto your device, (b) read back the entire flash content (without resetting first), and (c) verify that the binary content you read from SmartRF Flash Programmer 2 matches the binary content you read from Uniflash.

TIABO

0 Ajit Chaudhari27 over 8 years ago in reply to TIABO

Prodigy 170 points

hi TIABO,

Thanks for testing .out file using SmartRF Flash Programmer 2 and Uniflash.
But i can't go with SmartRF Flash Programmer 2 because i bricked 6 devices while doing program.
so it's better for me to go with Uniflash.

One thing i am not getting,
why device bricked while doing the program?
why ccfg contains change allowed while doing program?

0 TIABO over 8 years ago in reply to Ajit Chaudhari27

TI__Genius 12900 points

Ajit,

I cannot explain why you see this using SmartRF Flash Programmer 2 since we're not seeing it on our side. That's why I asked you the above question to program the device in Srfprog2 *without* disconnecting afterwards. If you follow the above steps, you should be able to do "mass erase" immediately after without bricking the device.

I'm not sure what your mean with your second question, can you clarify?

TIABO

0 Ajit Chaudhari27 over 8 years ago in reply to TIABO

Prodigy 170 points

Hi,

Device(F32) flash with wrong out file(F128) the ccfg contains get change and device bricked, after that it shows wrong device name or unknown device. Is it correct?

if yes then why it is allowed?

if i am going in wrong way then please let me know.

0 TIABO over 8 years ago in reply to Ajit Chaudhari27

TI__Genius 12900 points

The placement of the CCFG struct you have in your project is essential. If you write 00s to the CCFG area, you will lock down the device. It will not be possible to unlock it. This is a security feature with the device.

I agree that you should not be allowed to program an F128 .out file into an F32 device in srfprog2. We will add a check for this so that you will not be allowed in the future.

If using Uniflash is a suitable workaround for you, I would recommend that you use that tool moving forward.

TIABO

0 Kian over 8 years ago in reply to TIABO

Expert 1595 points

Hi all,

I am having a similar problem. I made a customed PCB for the CC1310F32 and got some free samples from TI. I soldered the CC1310F32 onto the PCB and checked all my connections. I am using a CC1310 Launchpad to program my customed board using 5 pins ( 3.3V, GND, RESET, TMS and TCK).

When I start Flash Programmer 2, its shows XDC110, XDS-L400A327 (Unknown).

I tried to CC26XX/CC13XX Force Mass Erase, but got the following error in the status window:

>Initiate access to target: XDS-L400A327.

>Create XBAL object failed: Target connect failed

>Failed to create device object.

Can someone advise what could be wrong??

0 TER over 8 years ago in reply to Kian

TI__Guru**** 317180 points

Kian: Have you set Flash Programmer 2 to use CJTAG? If yes it sounds like it's something wrong with either the board or the connection. To start with it could be useful to see a picture how you have connected together your board with the LP.

0 Kian over 8 years ago in reply to TER

Expert 1595 points

Thanks TER. I found the problem. It was a indeed a connection problem. A loose wire was giving the problem. I how have another problem but i will start another thread as it a different problem from this original thread.

Sub-1 GHz

Sub-1 GHz forum

CC1310: CC1310F32 DEVICE ACCESS ACCESS FAILED : XBAL : TARGET CONNECT FAILED