• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 16 subscribers
  • Views 359 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

LAUNCHXL-CC26X2R1: Bootloader backdoor enable pin

CC1352P: SWRA466C: BSL Backdoor enable pins still not correct on Table 14

Omer Kilic
Prodigy 60 points
Part Number: CC1352P
Other Parts Discussed in Thread: UNIFLASH, CC2652R

Hi, a follow up to this now-locked thread: https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/871984?LAUNCHXL-CC26X2R1-Bootloader-backdoor-enable-pin

Can you please issue an update to this document so that the correct default backdoor enable pins are listed?

What is the default backdoor enable pin for CC1352P?

Thanks.

  • 0
    Prodigy 60 points

    In znp.syscfg, there is mention of CCFG.dioBootloaderBackdoor    = 15; (BTN1 on Launchpad boards?) but after a full erase, register 0x00057FD8 reads 0xC5FE0DC5 (BL_PIN_NUMBER =13). DIO_13 is also UART_TX...

    So, is it right to assume that on a "fresh" device DIO_13 is the default backdoor enable pin and on anything ZNP related it is DIO_15?

  • 0 in reply to Omer Kilic
    TI__Guru**** 317180 points

    According to "BL_CONFIGRegister(Offset= 1FD8h)[reset= C5FFFFFFh" in the default on a chip with eased flash ia that the bootloader backdoor is disabled.

    Did you do a mass erase? And did you check a device you havenæt used before?

  • 0 in reply to TER
    Prodigy 60 points

    I think I got tripped up by Uniflash here. It appears that it is unable to erase the entire flash using XDS110 (no errors) as I see the same value in that particular register ("Keep CCFG data" option is unticked). Curiously, this is only happening on CC1352P, can't replicate the same behaviour with the same XDS110 and several CC2652R boards I have on my desk...

    Switching over to J-Link, register 0x00057FD8 is indeed  0xC5FFFFFF after a mass erase:

    J-Link>mem32 0x00057FD8,1
00057FD8 = C5FE0FC5   -> ZNP firmare, BL_PIN_NUMBER = 15 as expected
J-Link>erase
Without any give address range, Erase Chip will be executed
Erasing device...
J-Link: Flash download: Total time needed: 0.693s (Prepare: 0.207s, Compare: 0.000s, Erase: 0.467s, Program: 0.000s, Verify: 0.000s, Restore: 0.018s)
Erasing done.
J-Link>mem32 0x00057FD8,1
00057FD8 = C5FFFFFF

    Re-reading SWRA466C and particularly the flowchart for BSL invocation, a blank (never programmed) device would always be entering the BSL anyway ("CCFG parameter:FLASH image valid?") so I guess there is no such things as a "factory default" BSL pin but more so using what Launchpad boards use as convention.

    Still, Table 14 on SWRA466C needs correcting as the pins used on Launchpad are DIO_13 and DIO_15 for CC26x2R and CC1352x respectively unless I am mistaken?

  • 0 in reply to Omer Kilic
    TI__Guru**** 317180 points

    I'm currently in the process of checking. Have you tested using the sblAppEx firmware and checked the DIO?