topic MC9S08AW internal clock trimming in 8-bit Microcontrollers

MC9S08AW internal clock trimming

franco — Wed, 24 May 2006 23:14:27 GMT

Ciao to every body,

May any body knows anythings about 9S08AW USBBDM trimming?:

Try this:

CW5.0 with ProcExp.

9S08AW derivative

Internal trimm initialized

Internal oscillator

FLL engaged

Bus speed 10MHz

SCI bean:

9600 baud.

what you will find is that 9600 baud has at least 20% speed error.

This is why the USBBDM (Pemicro tool) and/or CW didn't make any trimming

--> FFBE=FF....and OSCTRIM =FF.

Do you know it?

Do you have any suggestion?

Have a good day

Franco

Re: MC9S08AW internal clock trimming

peg — Thu, 25 May 2006 05:03:45 GMT

Hi,

Have you told CW to calc and programme the NVTRIM?

See Multilink CyclonePro|Advanced Programming/Debug Options

Is the option "Calculate Trim and Programme the Non Volatile Trim Register" ticked?

As for the ICGTRM register it should not be changed from reset default of $80 if the NV version is at erased state of $FF. But this is up to the user's code (or the user relying on other people's code)

Hope this helps

Regards Peg

Re: MC9S08AW internal clock trimming

franco — Thu, 25 May 2006 15:27:17 GMT

Ciao Peg,

thanks a lot for your time.

You are agree, but seams that the "command" to the BDM to make the trimming is not sent.......

I am trying to involving all "possible" player to have any possible work around.

Thanks again

Franco

Re: MC9S08AW internal clock trimming

peg — Thu, 25 May 2006 16:10:54 GMT

Ciao Franco,

I am not sure I understand your response.

Are you saying you checked what I said but it still doesn't command the thing to programme the trim?

Try this:

When the P&E script runs left click and hold on the window, this seems to halt it but not very reliably.

Can you see the PT (programme trim) command being issued?

Does it say "Success"

Regards David

Re: MC9S08AW internal clock trimming

franco — Thu, 25 May 2006 16:20:31 GMT

Ciao David,

....the "PT" command is not present in any condition in the "CW programming windows"....

I use, the customer use, CW5.0 with all the last patches installed.

If you have the "PT" command...........please try to explain the "configuration"......

Thanks again

Franco

Re: MC9S08AW internal clock trimming

peg — Thu, 25 May 2006 17:40:47 GMT

Hi again,
OK I'm just poking about in the dark here until somebody more knowledgable can assist.
I found that the setting I referred to in my first post is stored on exit of hiwave to a file in the top level of your project directory.
The file is BDM_P&E_Multilink_CyclonePro.ini
The group is [SAVESETTINGS]
DOTRIM=0 (or 1)
This reflects the setting I spoke about.
Maybe you can check to see if at least this changes with the checkbox.
After that I don't know how CW generates the script that is passed to the pemicro command line programmer. There does not seem to be a copy stored to disc.
As I have said recently in another post to Wings, I have a paid for version of this and I know how to drive that but don't understand how it is integrated into CodeWarrior.

Otherwise I don't know of any other 'configuration' that has to be done.

Regards David

Re: MC9S08AW internal clock trimming

RockyRoad — Fri, 26 May 2006 03:25:25 GMT

Franco and David -

I tried this here and I see the same thing that Franco sees. That is, FFBE is not programmed. And as further info, if you go into 'expert programming mode' (which is really just P&E's stand alone programmer) the option to trim is not there.

I can tell you how this is happening, but I can't answer why it's that way, yet.

If you look in the '9s08aw60.s8p' file, the lines that would set up performing a trim are commented out. So this is why the trim is not happening and why the PT option is not there in expert mode.

What I don't know yet is the reason behind this. I've asked the question and I'll pass on what I find out.

- Rocky

Re: MC9S08AW internal clock trimming

peg — Fri, 26 May 2006 04:16:29 GMT

Hi,

I kept forgetting to mention I was trying with GB60 presuming it would be the same! Which it SHOULD be.

Regards David

Re: MC9S08AW internal clock trimming

yb — Fri, 26 May 2006 13:52:05 GMT

Hi,

The pod just calculate and store the values into FLASH registers. You have to copy these values into RAM registers after the POR.

Regards,

Re: MC9S08AW internal clock trimming

peg — Fri, 26 May 2006 17:45:33 GMT

Hi,

OK I checked this out.

All AW .s8p files supplied with CW5 and with my genuine P&E IDE and an update set have the TRIM either commented out or not there at all.

Presumably P&E have a problem with trim calculation for this part???

Regards David

Re: MC9S08AW internal clock trimming

Encoder — Fri, 26 May 2006 22:58:37 GMT

I can add another small information piece on this matter. I do not know if pertinent...

I made only experimental sessions with DEMO9S08AW60 board and Codewarrior 3.1 with all the latest upgrades. I preferred version 3.1 instead of more recent ver. 5 (which is that supplied with the board) because of a better familiarity with this version: the newer version seams to have changed some auxiliary file like .prm etc.

I work only in Assembler: I am not familiar with C. First of all I edited the former "MC9s08aw60.inc" to a reduced format (I can't approve a 145kB initial declarations for an 8 bit processor). After this the programs work pretty well when I succeed to load them in flash. In fact this is not guaranteed: 2 out of 3 times the Codewarrior Real Time debugger fails to load the assembly code on the flash memory with the P&E debugger module.

I thought this could be related to the early version I use, instead of the newer ver. 5. The simptoms seem to indicate some difficulties to synchronize the baud rate.

In my programs I started copying the $FFBE location into ICGTRM supposing either Freescale or programmer module would have trimmed this variable. I was wrong: $FFBE was blank ($FF) and writing this value to the ICGTRM was bad. Loading default midscale value ($80) gave instead a pretty accurate result for timing.

Obviously even in a small production quantity it is impractical to trim the internal oscillator by experiments... Now I ask:

1) Is there anyone who has the same difficulties as mine to get in contact with the DEMO9S08AW60 board?

2) Is there a simple automated metode to trim the ICGTRM or the default location $FFBE during the code flashing with this board and Codewarrior?

Bye, Encoder

Re: MC9S08AW internal clock trimming

RockyRoad — Sat, 27 May 2006 01:32:35 GMT

Encoder -

Other 08 and S08 parts with trimmable internal oscillators do automatically perform a trim calculation and store the value into a flash location during programming with CodeWarrior and the P&E Multlink or Cyclone Pro. The value in flash then must be copied to the trim register by the user's software during initalization.

We are trying to track down why this has been disabled for the 9S08QW60. I'll let everyone know when I get an answer to this.

- Rocky

Re: MC9S08AW internal clock trimming

peg — Sun, 28 May 2006 08:17:48 GMT

Hi all,

This exposes a minor bug in CW.

When you can't do a trim calc the option to select whether to do so or not should be greyed out.

Refer also to this tread:

http://forums.freescale.com/freescale/board/message?board.id=CWCOMM&message.id=855

The option is still available on a MON08 interface where there is definately no support for trim calibration!

Regards David

Re: MC9S08AW internal clock trimming

yb — Mon, 29 May 2006 13:41:23 GMT

Hi,

>Other 08 and S08 parts with trimmable internal oscillators do automatically

>perform a trim calculation and store the value into a flash location during

>programming with CodeWarrior and the P&E Multlink or Cyclone Pro

No, look at the window in this jpg file (CW5.0 / MultinlinCyclonePro / Advanced Programming - debug options

Regards,

Re: MC9S08AW internal clock trimming

franco — Mon, 29 May 2006 14:34:16 GMT

Ciao Rocky,

thanks a lot for your time.

I hope you find the "solution" asap.

Have a good day and week

Franco

Re: MC9S08AW internal clock trimming

peg — Thu, 01 Jun 2006 04:49:15 GMT

Hi franco,

Here's the official "solution" straight from the horses mouth, Mark Cukier of P&E Microsystems:

"For the intial release of these algorithms, we commented out the trim. However, individual users are free to uncomment the trim lines (the three commented lines) to enable trim for their systems."

Didn't really get an answer as to why, but anyway.....

Regards Peg

Re: MC9S08AW internal clock trimming

RockyRoad — Tue, 06 Jun 2006 03:58:24 GMT

Sorry that this has taken so long. In addition to what peg forwarded on from P&E, I just got word that they have now tested the routines that were commented out and they work correctly on the AW60.

We still don't have an answer to the 'why' question. No one that I've talked to here or at P&E knows any reason that they should have been left commented out in the release version of the file.

- Rocky

Re: MC9S08AW internal clock trimming

seanmac — Fri, 08 Jun 2007 17:11:32 GMT

Download and install the latest service packs from Freescale. This issue appears to have been sorted out.

http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=0127260061788213CF

or use the "Codewarrior Updater"

Cheers

Sean

Re: MC9S08AW internal clock trimming

jingbo — Fri, 30 Jan 2009 04:37:24 GMT

Hi Guys,

I was trying to post a new thread but saw this one already about clock trimming, still couldn't find a close match to what I was looking for.

I am using a S08QE64 which has a ICS instead of a ICG like the S08AW.

Basically I need to get a uS timer interrupt. I do not have any external clock sources. I do not have any idea about clock trimming but somehow think it can help. Can anyone give me a laymans idea about what trimming is actually and how can I use it?

I read thru the QE128RM and QE128RUG but still can't make out anything about trimming teh internal clock.

thnks

Re: MC9S08AW internal clock trimming

peg — Fri, 30 Jan 2009 04:57:19 GMT

Hello and welcome to the fora, jingbo

OK here goes...

These devices have an internal clock source. They way they make it, it is very difficult for them to make it accurate. So they provide a method to trim it. This allows the user to adjust the trim value to get the clock running at very close to the intended rate. It also now opens up the possibility to use the trim value to run at "custom" frequencies as long as they are within the scope of the trim register for a broad range of devices and operating conditions (temperature).

Note that this clock is then used as the main clock for the CPU and there are then selectable dividers that can be applied to this to provide different frequency clocks to different peripherals in the device. The timers then have the ability to select their modulo. With all this adjustment (including additional software methods) you should be able to produce and delays/frequencies that you desire.

Message Edited by peg on 2009-01-30 08:02 AM