IWR1843AOP: Call Stack Access

Hello.

Adam Gild said:

On another note, is there functionality available to power down or restart (power cycle) the chip in the SDK?

You cannot power cycle, but you can trigger a warm reset.

Adam Gild said:

Is there a way to access call stack information during runtime?

We are able to access the current stack pointer via the ti_sysbios_knl_Task_Stat structure, but would like the call stack information as well.

Let me look into this and provide a response by end of day tomorrow.

Sincerely,

Santosh

Hey Santosh,

Thanks for looking into this, where can I find the functionality for the warm reset trigger? 

Look forward to hearing your call stack findings too.

Thanks

Adam

Hello Adam.

Adam Gild said:

Thanks for looking into this, where can I find the functionality for the warm reset trigger? 

For SDK 3, please refer to this example in the toolbox for performing a soft reset via CLI.  There is a known errata with this method of reset which is documented in the x843 errata(check MSS #34).

Adam Gild said:

but would like the call stack information as well.

As a follow up for this, when you say call stack are you referring to the list of function calls you see when you pause the debugger?

Sincerely,

Santosh

Hey Santosh,

Yes, in essence, the call stack information we are looking for would be the last x amount of function calls at that point of the program.

Thanks for pointing me in the direction of the warm reset, I will try that method out and let you know if it works.

Thanks, Adam

Thank you for the clarification.

I am still looking into this and will provide another update by the end of the day tomorrow.

Sincerely,

Santosh

Thanks Santosh, look forward to your findings.

Hello Adam.

Apologies for the delay in response.  We are currently looking into the BIOS to see if we can find any of the call stack information.  I will provide a follow up by the end of the Friday.

Sincerely,

Santosh

Hello.

Apologies for the delay in following up.  We are continuing to look into this, but from a preliminary look it looks like you cannot access the call stack information from stack memory.  Is there a particular reason why you are looking for this information?

Sincerely,

Santosh

Hey Santosh,

We wanted this information for error logging purposes if we run into critical errors at runtime to be able to log the call stack information.

Is this confirmed now that its not possible to access that information?

Thanks a bunch,

Adam