• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 298 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.

Compiler/CC1352R: _system_pre_init seems not to be called

Erwin Ahlers
Intellectual 570 points
Part Number: CC1352R

Tool/software: TI C/C++ Compiler

Hello,

I would like to check the contents of a gloabal variable that was set before a reset happened. This check should be coded inside the _system_pre_init function as this is called before all the variables are set to zero.

So I implemented a function like

int _system_pre_init(void)
{
    MyTestVar++;
    return 1;
}

and wanted to put a breakpoint inside it. The whole stuff compiled but I was not able to set a breakpoint in this function. I was always shown as disabled. According documentation the general initialization should be skipped when I return 0. So I tried it but can't observe and difference. I also trie to switch a LED, which is connected to a processor pin, but couldn't see it.

So it seems that this function is not called. How can that be?

My problem would also be solved when it would be possible to define a global variable that is not initialized to any value at startup. I thought by defining a dedicated RAM section in the linker file would enable this, but also no success. I thought just -bss sections are initialized. Is there a possibility to define a global variable that is not initialized at startup?

Regards
Erwin

  • 0
    TI__Guru**** 244300 points

    I'm confident that the _system_pre_init function you supply is in the program.  While debugging in CCS, search for it by name in the Disassembly view.  To set a breakpoint, double-click on an address.  If that doesn't work, then you may have run out of hardware breakpoints.  Please see this discussion of breakpoints for more on that issue.

    Erwin Ahlers said:
    My problem would also be solved when it would be possible to define a global variable that is not initialized to any value at startup.

    Please consider using the NOINIT pragma.  For details, please search the TI ARM compiler manual for the sub-chapter titled The NOINIT and PERSISTENT Pragmas.

    Please let me know if one of these suggestions resolves the problem.

    Thanks and regards,

    -George

  • 0
    Guru 92251 points

    Erwin Ahlers said:
    My problem would also be solved when it would be possible to define a global variable that is not initialized to any value at startup. I thought by defining a dedicated RAM section in the linker file would enable this, but also no success.

    Previous threads have noted that the cc1352 doesn't allow SRAM to be preserved across a reset, e.g. see Compiler/LPSTK-CC1352R: #pragma NOINIT

  • 0 in reply to Chester Gillon
    Intellectual 570 points

    Then _system_pre_init is of no use for me.

    Thanks