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.

CCS/LAUNCHXL-F280049C: How to emulate / test the boot sequence

Part Number: LAUNCHXL-F280049C


Tool/software: Code Composer Studio

Back ground:

We have GPIO24, which is one of the default boot selection inputs, in use for SPI B which then interferes with the boot process.

I want to use just GPIO 32 select between Flash and SCI/Wait bootmodes.

I think I should do this by  setting following

BOOTPIN_CONFIG = 0x5AFFFF20
BOOTDEF.BOOTDEF0 = 1 , wait SCI (when GPIO32 = 0, S2 on BOOSTXL on ie switch in the '0' position)
BOOTDEF.BOOTDEF1 = 3 , boot from Flash (when GPIO32 = 1, S2 on BOOSTXL off ie switch in the '1' position)

Is that correct?

What is the canonical way to program these OTP locations ( would prefer it that so that whenever

anyone pulls the project from GIT and just loads/runs the code in CCS the BOOTPIN and friends

will be set correctly as this will be our workflow for months to come.

Before programming the OTP locations I want to ensure everything is correct.

I think I should be able to emulate this by setting memory as follows:


0x0000 0D00: 5AFFFF20 FFFF0301 FFFFFFFF  (copy pasted from the Memory Browser in 32 Bit Hex  - TI Style)

Is this correct?

But how do I test this, exact steps would be great as although I've been through the One Day Workshop 

for F280049 not everything clicked and matched what  see in my CCS.

For example Reset Emulator is grayed out always. When I select Run/Reset/CPU nothing happens. Mostly I seem to be stuck at PC= 3FB02A

  • The boot pin config and boot def you mentioned seems to be correct.

    For loading them to OTP you can create a simple project with 3 variables which are directed to required address in OTP.

    Once you compile and load the project to CCS, the flash plugin will program these value into OTP.