CCFG table burning in the CC1352

Shir Adar

Hi,

I have an open issue related to the burning of the ccfg table in the CC1352.

When I perform ccfg burning table, a hard fault appears. My tests show that hard fault appears ONLY when the device is clean, by clean I meant that the internal and the external flash are earesed

and the bootloader , application bootloader (consist ccfg params) and application are reburned.

I noticed that adding delay (at least 5 milisecond) after the function that execute the ccfg burning process resolved the problem and no hard fault accours.

In case of updating the ccfg without cleaning the device - there is no hard fault. for example, calling the burning function through test mode or reburning just the application bootloader and app.

I try to figure out why this hard fault appears and why I need this delay to resolved it. any ideas?

Thanks!

over 5 years ago

0 IUsedToBeARealPerson (M-W) over 5 years ago

TI__Guru 58425 points

Hi Shir,

Could you elaborate on what you are doing in terms of software. Are you "burning" from the device or using the debugger/bootloader interface?

0 Shir Adar over 5 years ago in reply to IUsedToBeARealPerson (M-W)

Prodigy 60 points

Release version by bootloader interface

0 IUsedToBeARealPerson (M-W) over 5 years ago in reply to Shir Adar

TI__Guru 58425 points

Hi Shir,

I would really need you to elaborate more on what you are doing in terms of programming, steps and all.

0 Shir Adar over 5 years ago in reply to IUsedToBeARealPerson (M-W)

Prodigy 60 points

Step 1: using JTAG in order to completely erase the internal (include ccfg) and external flash.

Step 2: load a release version through UART.

Step 3: the program checks if ccfg should be written from defaults - in this case, the ccfg was erased in step 1 so ccfg must be written.

Step 4: after written the ccfg the program executes soft reset.

Step 5: on startup, the program fails and a hard fault occurs.

0 Shir Adar over 5 years ago in reply to Shir Adar

Prodigy 60 points

addition for step 5, when the program fails the system commits hard reset, the hard fault occurs and the program keeps on running as it should.

0 IUsedToBeARealPerson (M-W) over 5 years ago in reply to Shir Adar

TI__Guru 58425 points

Hi Shir,

What is the cause of the hard fault you are seeing in step 5 (after "soft" reset)? It would be good to know why you would be seeing an exception here (and which exception you see) as a soft reset on these devices typically is routed to perform a full device reset (equal to a pin reset).

Processors

Processors forum

CCFG table burning in the CC1352