• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 88 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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:

CC2340R2: Triggerring bootloader

CC2340R2: Cannot trig bootloader

Fred P
Expert 2215 points
Part Number: CC2340R2
Other Parts Discussed in Thread: CC2340R5, SYSCONFIG

Tool/software:

Hello,

I have programmed successfully my application and a CCFG file through the bootloader using sblApp tool.

The application runs but I cannot trig the bootloader anymore using DIO pin. 

The application starts right out of reset while DIO21 is low.

Below is the start (bootloader config) of CCFG file I have programmed using sblApp tool.

Any clue?

Regards

  • 0
    TI__Guru**** 216717 points

    Hello Fred,

    The first four bytes (0xFFFFFFFF) indicate that XCFG_BC_PBLDR_UNDEF is used (Default FCFG bootloader).  Thus the following bytes (0x03 indicates enabled bootloader and pin entry, 0x015 indicates DIO21) are not used.  From the TRM:

    This should still be valid for a DIO21 low bootloader pin entry, and I've confirmed that such a similar setup works for my CC2340R5 device.  What SimpleLink F3 SDK are you using and how did you generate the CCFG settings?  Typically this is accomplished through the SysConfig Device Configuration.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 2215 points

    Hi Ryan,

    Sysconfig generated the CCFG sector ( like your screenshot).

    After build, I split the CCFG sector and the application code from the binary file using:

    ${CG_TOOL_ROOT}/bin/tiarmobjcopy.exe "${BuildArtifactFilePath}" --only-section .ccfg --output-target binary "${BuildArtifactFileBaseName}_ccfg.bin"
    ${CG_TOOL_ROOT}/bin/tiarmobjcopy.exe "${BuildArtifactFilePath}" --remove-section .ccfg --output-target binary "${BuildArtifactFileBaseName}_app.bin"

    I then feed the 2 files to the sblApp tool.

    I am using SDK 8.10.01.02 .

    I don't see how the final CCFG file content vs device behavior would relate to the SDK version.

    If you cannot replicate that behavior on R5 using the same CCFG bootloader sector as mine, could it be R2 specific?

    Speaking of the first four bytes, Sysconfig, SDK, TRM and all other things in the universe, you may find my other post interesting, here: e2e.ti.com/.../cc2340r2-sysconfig-bootloader-configuration-problem

    Thanks for your support

  • 0 in reply to Fred P
    Expert 2215 points

    It turns out that there was a glitch on DIO21 after releasing the reset pin.

    Glitch solved, bootloader invoked.

    Case closed.

    Sorry for all of that....

    Thank you for your support.