LP-CC2652RB: LP-CC2652RB

Hi Shruti,

I have not experienced a similar issue.  Did you erase all memory before programming the off-chip BIM hex file with Uniflash or Flash Programmer 2?  And have you disconnected the device from other software programs before starting the debug session?  CCS Cloud is not recommended for debugging.  Are you using CCS or IAR, and which version?

Regards,
Ryan

HI Rayan,

Ryan Brown1 said:

I have not experienced a similar issue.  Did you erase all memory before programming the off-chip BIM hex file with Uniflash or Flash Programmer 2

Yes I have erased entire flash and loading the image through Uniflash

I have only this program running in this software. 

I am using downloaded CCS -  Version: 10.3.0.00007 

H Rayan,

I tried debugging the issue and came on the following conclusion:

I tried to remove the GEL files as said in this thread https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/808058/ccs-cc2640r2f-unable-to-access-the-dap The DAP issue is not seen now.

Observation at BIOS_Start :

1. The code is getting stuck and below message is received

Can't find a source file at "../rom_temp/rom/fw//src/hapi.c"
Locate the file or edit the source lookup path to include its location.

Attaching Assembly code

2. The values written to the flash memory through uniflash tool is overwritten at this point with some new value. 

Values loaded in memory from Uniflash

Values in memory after BIOS_Start

The lower bytes you've noted are for the OAD Image Header and Application Interrupt Vectors, please see the BLE5-Stack User's Guide -> Flash Layout for Off-Chip OAD information.  These are not a concern from the Uniflash session which programs the BIM starting at 0x50000.  Does the program operate as expected if you do not attempt a debug session?  What happens for instance if you use Uniflash to program both the BIM hex and Application's *_oad.bin output file?  Do you have any different LaunchPad versions (i.e. LAUNCHXL-CC26X2R1) to test?  Have you changed any CCS Debug Configuration settings?

Regards,
Ryan

>> Does the program operate as expected if you do not attempt a debug session? What happens for instance if you use Uniflash to program both the BIM hex and Application's *_oad.bin output file?

I tried to download the program into flash, but I am not able to discover the device in my phone. 

>> Do you have any different LaunchPad versions (i.e. LAUNCHXL-CC26X2R1) to test?  

No I have only CC2652RB with me

>> Have you changed any CCS Debug Configuration settings?

No changes made in the Debug configurations. 

I tried reducing the JTAG TCLK frequency from 5.5 MHz to 2.5 MHz, but it did not make any difference, reverted the change and also I noticed ENABLE_BOOTLOADER was was disabled in the sysconfig, which I enabled 

Shruti,

Please closely follow the BLE Enhanced OAD SimpleLink Academy Lab and project_zero or simple_peripheral_oad_offchip READMEs.  Confirm the default UART peripheral through a terminal program or state the specific issues you encounter during this process.

Regards,
Ryan

Hi Rayan,

I tried using the suggested simple peripheral OAD on-chip as well as off-chip(just to ensure I am not missing out any part). After loading the images, I is said to observe the display on console for the Resolvable Private Address (RPA) but I cannot find any display. 

While I tried to check using BTool, I get an error device connection timeout. Attaching the screenshot. 

PS: It is possible to schedule a call to resolve this issue faster?

Yes

I accidently pressed the issue is resolved but it is not resolved

Hey Shruti,

You mention the projects you built imported from resource explorer (project zero and simple_peripheral) fail to run. Do I understand correctly?

Can you try to install the full SDK from here: SIMPLELINK-CC13X2-26X2-SDK Software development kit (SDK) | TI.com? And import the project from the install package? Are you using the CCS Cloud IDE, or an installed version? If so, can you verify the CCS version you are using, along with the TI Compiler version?

The SDK installation contains prebuilt hex files located in examples\rtos\LP_CC2652RB\ble5stack\hexfiles. Can you try one of these to see if the device functions? I would try simple_peripheral or even project_zero to start.

Hi Ammar,

The Bluetooth projects fail to run as in when I try to load the simple link or project zero program by debug mode (BIM already present in the flash), Sometimes it shows unable to access DAP while the other times it goes in infinite loop in the simplePeripheral_init function.

I have installed the latest version of SDK 5_10_00_48 and I am importing the project from the installed SDK, not from the resource explorer

CCS version 10.3.0

TI emulator version 9.3.0.00042 

Hey Shruti,

If you can flash/debug any project (does not have to be a Bluetooth stack project), this would help rule out an issue with the hardware itself. You can also try flashing the prebuilt hex files in the SDK with Uniflash. Please verify you have all the jumpers populated on the LaunchPad.

Hi, 

I tried loading uart_echo example using uniflash and the output was printed on the terminal as expected. So this verifies the hardware probe is connected as required. 

While I use BLE preloaded hex files, I cannot see any prints on the terminal (terminal is blank). Is there any setting on the sysconfig I am missing?

Hey Shruti,

I've reached out to a colleague for some advice. In the meantime, can you confirm you are using a Launchpad and not custom hardware? I tried this on my end and did not see issues.

Hi Ammar,

I am using the Launchpad and not a custom hardware.