CC2652R7: serial upgrade problem

Hi Jason,

I apologize that my prior E2E support was insufficient to address your issue, I will attempt to loop in a developer who knows more about this bootloader example and can help further assist.  Meanwhile, you can try to use Flash Programmer 2 or Uniflash in bootloader mode as well.

Regards,
Ryan

Hi Ryan,

Are there any updates to your site?

Is it because CC265R1 and CC2652R7 have different check ID so sblAppEx cannot be used on R7?

Do you have any experience supporting other teams upgrading FW on CC2652R7 via sblAppEx?

Can you share your experience if there is an example?

Thanks,

Jason

hi Jason,

Do you use cc13xx-sbl code in Linux host ? For sblAppEx , it runs on Windows environment.

Hi Jerry, 

Yes, we have ported sbl code in Linux host.

We wonder if sblAppEx can support CC2652R7 FW upgrade?

If supported, do files Sbl_device_cc2652.h / Sbltool.h need to be modified for CC2652R7?

Thanks,

Jason.

Forward:

==================================================================================

Hi Jerry

Currently, I found the error occurred in “flash size” check, I’ve listed sample code for your check and confirm.

These define with("##WNC##") as below list were work with CC2652R1, but, I want to know if these define keep working in CC2652R7?

Btw, in attached initial flow in main function (“connect”), currently, we can running success with “initcommunication” for com port detect and “readDeviceid” catch device ID, but, error occurred in “readFlashSize”, So, I think it might be related with “SBL_CC2652_FLASH_SIZE_CFG” setting, so, that’s why I need your support to check those ("##WNC##") setting for CC2652R7.

Thank you

Danny

(sample “sbltool.c” source)

-----------------------------------------------------------------------------------------------------

.....

if((retCode = readFlashSize(sbl_device, &tmp)) != SBL_SUCCESS) {

                   return retCode;

          }

.....

uint32_t readFlashSize(SBL_DEVICE *sbl_device, uint32_t *pui32FlashSize)

{

          uint32_t retCode = SBL_SUCCESS;

          uint32_t addr = SBL_CC2652_FLASH_SIZE_CFG;   //##WNC##

          uint32_t value = 0;

          //

          // Read CC2652 DIECFG0 (contains FLASH size information)

.....

In the “sbl_device_cc2652.h”, I’ve been mailed in previous mail…..

//##WNC##

#define SBL_CC2650_MAX_BYTES_PER_TRANSFER   252

#define SBL_CC2650_MAX_MEMREAD_WORDS        63

#define SBL_CC2652_PAGE_ERASE_SIZE          8192

#define SBL_CC2652_FLASH_SIZE_CFG           0x4003002C

#define SBL_CC2652_RAM_SIZE_CFG             0x40082250

#define SBL_CC2652_FLASH_START_ADDRESS      0x00000000

#define SBL_CC2652_BL_CONFIG_PAGE_OFFSET    0x1FDB

//##WNC##

-----------------------------------------------------------------------------------------------------

Hi Jason, Jerry,

Thank you for helping clarify that the tool being used is the Linux cc13xx-sbl and not Windows sblAppEx.  This helps clear the inconsistencies I've been observing between the description provided and the behavior I've observed while evaluating sblAppEx, which I have confirmed works for the CC2652R7 device.

C:\Users\a0274016\Documents\Connectivity\sblAppEx_1_03_00_00\bin>.exe
+-------------------------------------------------------------
| Serial Bootloader Library Example Application
+-------------------------------------------------------------

+-------------------------------------------------------------
| COM ports:
+-------------------------------------------------------------
|Idx    | Description
| 0     | Intel(R) Active Management Technology - SOL (COM3)
| 1     | XDS110 Class Application/User UART (COM6)
| 2     | XDS110 Class Auxiliary Data Port (COM7)
+-------------------------------------------------------------

Select COM port index: 1
+-------------------------------------------------------------
| Supported devices:
+-------------------------------------------------------------
|Idx    | Device
|  0    | CC2538
|  1    | CC13x0/CC26x0
|  2    | CC2640R2
|  3    | CC13x2/CC26x2
+-------------------------------------------------------------
Select target device: 3

Connecting (COM6 @ 230400 baud) ...
100% (624.00ms)
Erasing flash ...
100% (5279.00ms)
Writing flash ...
100% (200345.00ms)
Calculating CRC on device ...
100% (386.00ms)
Comparing CRC ...
OK
Resetting device ...
OK

Is the TI-15.4-STACK-GATEWAY-LINUX-SDK v4.40 being used for the Linux machine being used?  I can notify the correct tools owner to further investigate.

Regards,
Ryan

Hi Ryan,

Yes, the refer code, cc13xx-sbl is from  TI-15.4-STACK-GATEWAY-LINUX-SDK, but I am not sure which SDK they based. Could you have someone to clarify the correct flash size definition for CC2652R7 ?

Thank you.

I already have verified that CC2652_FLASH_SIZE_CFG is still 0x4003002C which works for programming my LP-CC2652R7 when using the default sblAppEx.

Regards,
Ryan

Jerry,

I will be helping you here.

I am confused, is the customer using a linux port of sblAppEx or using the cc13xx-sbl from the linux SDK?

If so, where exactly is the code getting hung and not working?

Thanks,

AB

It would be kind of them to post the root issue and accepted workaround for others in the community to benefit from their efforts.

Regards,
Ryan