Unexpected behavior in kl25z TPM.

Mockingbird · ‎03-21-2018

I am programming a kl25z on a Freescale FRDM-KL25Z board using assembly language. My IDE is CodeWarrior 10.7. My program is a simple LED-blink program. I use the TPM output compare interrupt to schedule the blinks.

The program works correctly when I connect TPM to the FLL. The program fails to work when I connect TPM to MCGIRCLK. The only differences between the two versions of the program are in SIM_SOPT2 TPMSRC (which selects the TPM clock) and in TPM0_SC PS (the TPM clock prescaler).

When I write corresponding C-programs with help of the Processor Expert, the C- program works both when TPM is connected to FLL and when TPM is connected to MCGIRCLK.

Why won't my assembly-language program work with TPM connected to MCGIRCLK?

mjbcswitzerland · ‎03-22-2018

Timothy

Load the code that works, let if run, then pause it and do a screen shot of all relevant registers.

Then load your code and do the same.

You should be able to see a difference in a register somewhere showing what is missing to get it working the same way.

Regards

Mark

元の投稿で解決策を見る

mjbcswitzerland · ‎03-21-2018

Hi Timothy

You probably need to enable the MCGIRCLK clock gate with IRCLKEN in register MCG_C1.
To get 4MHz MCGIRCLK remove its divider to get 4MHz clock (MCG_S = 0) and select 4MHz instead of 32kHz with IRCS in register MCG_C2.

Regards

Mark

Build with: CW10.x, KDS, MCUXpresso, IAR, Keil, Greenhills, Crossworks, CooCox, Atollic, S32 Design Studio, GNU Make and Visual Studio

HW timers: http://www.utasker.com/docs/uTasker/uTaskerHWTimers.PDF

Free Open Source solution: https://github.com/uTasker/uTasker-Kinetis
Working project in 15 minutes video: https://youtu.be/K8ScSgpgQ6M

For better, faster, cheaper product developments consider the uTasker developer's version, professional Kinetis support, one-on-one training and complete fast-track project solutions to set you apart from the herd : http://www.utasker.com/support.html

Mockingbird · ‎03-22-2018

The code I attached shows that IRCLKEN is already set. The debugger confirms this.

mjbcswitzerland · ‎03-22-2018

Timothy

Load the code that works, let if run, then pause it and do a screen shot of all relevant registers.

Then load your code and do the same.

You should be able to see a difference in a register somewhere showing what is missing to get it working the same way.

Regards

Mark

Mockingbird · ‎03-22-2018

Thanks, that helped. It turns out the instruction to set IRCLKEN wasn't written correctly; I wasn't taking proper account of the little-endian architecture.