RE: Tiva reset problem

Tyler Abbott

I know this is an old thread but did anyone confirm a resolution? I am experiencing the same issue and the patch doesn't work for me.

https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/399372#pi239031350=4

Any update would be greatly appreciated.

Cheers,

Tyler.

over 10 years ago

0 Amit Ashara over 10 years ago

TI__Guru**** 244440 points

Hello Tyler,

Can you please specify the following information

1. What is the Source of Reset?
2. Before the reset what is the value of RSCLKCFG register?

Regards
Amit

0 David Thompson18 over 10 years ago in reply to Amit Ashara

Prodigy 10 points

Hi Amit,

attached is our project with all registers before and after the system hang. The frequency is on the order of every 1000 resets.

Before 0x0000000B 0x03300000

After RSCLKCFG : 0x0000000B 0x13300003

Cheers,

Davehang_test.zip

0 Amit Ashara over 10 years ago in reply to David Thompson18

TI__Guru**** 244440 points

Hello Dave,

In the API SysCtlClockFreqSet please make the following modification just before the return from the function

//
// Finally change the OSCSRC back to PIOSC
//
HWREG(SYSCTL_RSCLKCFG) &= ~(SYSCTL_RSCLKCFG_OSCSRC_M);

return(ui32SysClock);

recompile driverlib.lib and use the new driverlib.lib.

After the change the RSCLKCFG should be 0x13000003 before the SysCtlReset call.

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Hello Amit,

I have applied the change and confirmed that the RSCLKCFG is 0x13000003 before the call to SysCtlReset.

Unfortunately the change has not eliminated the issue. Please let me know if you would like any additional information.

Thanks,
Tyler A.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

When the TM4C device is hung and you connect the Debugger w/o resetting the device or the CPU, what does the following registers shpw

1. CPU Register SP and PC
2. System Control Module register RSCLKCFG and MEMTIM0

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Hello Amit,

I leave the debugger attached while running the test.

The registers are as follows:

R SP 0x0000000B 0x200007D8
R PC 0x0000000B 0x00000002

R SYSCTL_SYSCTL_RSCLKCFG 0x0000000B 0x13000003
R SYSCTL_SYSCTL_MEMTIM0 0x0000000B 0x01950195

Cheers,
Tyler A.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

Thanks for the info. So it is the PC which should show the value at location 0x4 of the flash but instead has the value 0x2. Is that correct?

If yes, then can you take a snapshot of the address locations 0x0-0xFC under the failure condition.

Then using the CCS Reset Button, perform a System Reset and then take a snapshot of the address locations 0x0-0xFC.

If you now run the test code does it work till it hangs in the same manner?

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Hello Amit,

The PC register is different this time:

R SP 0x0000000B 0x200007D8
R PC 0x0000000B 0xF7FF4618

A System Reset allowed the device to continue as normal until it encountered the issue again.

I am unable to attach the memory snapshots to this reply, do I require additional privileges?

Thanks,
Tyler A.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

Please use the "Use rich formatting" link on the bottom right of the reply panel. That will allow you to attach snapshots, files, etc.

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Memory during failure memory_failure.dat

Memory after reset memory_after_system_reset.dat

Cheers,

Tyler A.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

I am not sure which TM4C129 series device you are using, but I would like to monitor the System Clock.

When the failure occurs, can you perform the following steps, by using the debugger's Register Window

1. Enable Port Q in SYSCTL.RCGCGPIO (Address 0x400FE608) by writing '1' to Bit-14
2. Write the value 0x10 to 0x40066420
3. Write the value 0x70000 to 0x4006652C
4. Write the value 0x10 to 0x4006651C
5. Write the value 0x80000005 to SYSCTL.DIVSCLK (Address 0x400FE148)

On Port PQ4 you should see a clock. If you can measure the same, please attach a Scope Snapshot with frequency measured.

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Snapshot attached.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

Maybe I am not reading it correctly, but the Frequency is not listed?

Regards
Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Sorry, missed that stat.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler,

Thank you for the data. I have attached a modified sysctl.c from TivaWare release 2.1.1.71 (and it should be fine to use in 2.1.2.111 release as the only change is to the function SysCtlClockFreqSet).

Can you please recompile the driverlib.lib and if it fails again send the clock frequency, and dump of the memory locations before and after the failure as you have done in the previous post?

1321.sysctl.c

Regards

Amit

0 Tyler Abbott over 10 years ago in reply to Amit Ashara

Prodigy 100 points

Hello Amit,

I have been running the code for more than an hour and I have not been able to reproduce the issue. Each time I reproduced the issue in the past it would manifest within 10 minutes. I will leave the unit to continue until the end of the day unless you have any other tests you wish to perform.

Thanks,

Tyler A.

0 Amit Ashara over 10 years ago in reply to Tyler Abbott

TI__Guru**** 244440 points

Hello Tyler

At this point I have no other tests planned yet. Let us wait for the test to run till end of day. If it does work, then let us run for over the weekend as well.

Regards
Amit