CC2340R5: Flashing via jlink is failing

Hello Rasikraj,

1) Is this one of your own examples? Just as a test we can see if the .hex file from SDK load correctly: C:\ti\simplelink_lowpower_f3_sdk_8_10_00_55\examples\rtos\LP_EM_CC2340R5\ble5stack\hexfiles

2) The error here is that the project generated a .out file instead of a .hex file, in order to generate a .hex file we need to add some "post build steps" to the project to create the .hex file when building. Specifically add the following text to the post build steps "${CG_TOOL_ROOT}/bin/tiarmobjcopy -O ihex ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.hex"

Thanks,
Alex F

Hello Alex,

1.Yes, error when .hex file from SDK is used.

However, if same .hex file is loaded using jlink then it is success and software runs correctly. (Can see device is advertising e.g.)

2. To load device via jlink, we need to have below post build commands right?

I had added post build commands as described, however when loaded the generated .hex file, I get below error.

Even below SDK example is having same issue.

Data file contains 4 memory ranges:
#0: 0x00000000 - 0x00027715 (161558 Bytes)
#1: 0x00027718 - 0x0002AD12 (13819 Bytes)
#2: 0x0002AD14 - 0x0002B123 (1040 Bytes)
#3: 0x4E020000 - 0x4E0207FF (2 KB)
Connecting to J-Link...
Bank selection: BankAddr=0x00000000 Enabled
Bank selection: BankAddr=0x4E020000 Enabled
Loader selection: BankAddr=0x00000000 Loader=Default
Loader selection: BankAddr=0x4E020000 Loader=Default
Connecting to target...
Downloading...
ERROR: Could not download file.
Done.

However, if I use hex converter utility (.bin format is generated), then this file can be loaded successfully in jlink but not sure software is running.

Secondly, how I can debug the software in CCS when using jlink?

When tried to debug, I get below error in CCS.

Regards.

Rasikraj.

Hello Rasikraj,

Thank you for the extra information. Did you already follow the TI Code Composer Studio - SEGGER Wiki? Also you should be able to set your debugger to SEGGER in CCS: 

Thanks,
Alex F

Hello Alex,

Yes as I mentioned, I am following descriptions for using jlink.

Also, SEGGER Jlink is selected already as debugger connection.

I am not able to download the code via CCS and no debugging possible as well. I am having latest CCS version installed.

Regards,

Rasikraj,

Hello Rasikraj,

I believe one issue we might have here is related to the CCFG CRC section not being populated (which could explain some projects working and some not) a related E2E about this: (11) LP-EM-CC2340R5: How to download bin file to cc2345 use jlink? - Bluetooth forum - Bluetooth®︎ - TI E2E support forums and (11) CC2340R5: CCFG area programming failure using J-Flash - Bluetooth forum - Bluetooth®︎ - TI E2E support forums

Looking at the error message this seems to related to the connection, will check with my HW apps team member who has more experience with the Segger to see if they have any tips on addressing this error. 

Thanks,
Alex F

Hello Alex,

I think CCFG CRC are now correctly populated for me.

I had to swap below post build command sequence and then I could now flash and run our custom application successfully.

However, downloading and debugging with CCS has still the same issue.

Regards.

Rasikraj.

Hello Rasikraj,

I have reached out to our HW team member who has more experience with JLINK to see if they can help resolve this issue, currently awaiting on their response feedback.

Thank you,
Alex F

Hello Rasikraj,

Still awaiting on feedback from the HW team, sorry for the delay.

Thanks,
Aelx F

Hello Rasikraj,

I met with my HW team member, and they indicated to me that the error in this image:

Was resolved in CCS 12.7, are you on an older version of CCS? 

Thanks,
Alex F

Hello Alex,

Probably you have not noticed the attachments correctly.

I am using most recent versions already.

Regards.

Rasikraj.

Hello Rasikraj,

Sorry for missing that information! I also wanted to ask what version Segger device you have? The HW team member had indicated to me that older versions of the Segger debugger could have issues. Additionally, our HW team member noticed that there is an issue that even after the Segger connects the CCFG CRC field is not filled correctly and produces an error.s

Thanks,
Alex F

Hello Alex,

The installed version of Segger is-

Also, as mentioned earlier, CCFGC CRC field should be NOT an issue now. 

Because same HEX generated out of post build commands can be successfully flashed using J Flash Lite and it runs as well.

Regards.

Rasikraj.

Hello Rasikraj,

Rasikraj Deshmukh said:

The installed version of Segger is-

-Sorry, I mean what is the actual physical device being used here (the Segger board). 

Thanks,
Alex F

Hello Alex,

It is J-Link plus, Version 11.0  from the week 42 in year 21.

Regards,

Rasikraj.

Hello Rasikraj,

In my previous conversation with our HW team member, they noted that there was an issue that older Segger devices could have issues with the CC2340R5, I have sent the information in your reply above to our HW team member to see if your version may be impacted by this. 

Thanks,
Alex F

Hello Rasikraj,

I checked with the HW team member, and your device is not an "older Segger device" I mentioned above, so the Segger device should support TI devices without issue. Can you post an image of your physical setup with the Segger device and TI device (with connections shown) if possible?

Thanks,
Alex F