Okay dear friends, here are some results:
6 brand new chips from the box, programmed with the same USBSPYDE08 device showed some nice expected results when looking at the FLASH memory map after entering debug memory addresses $3FFA and $3FFB :
Chip # 1 = 61 01
Chip # 2 = 5C 01
Chip # 3 = 64 00
Chip # 4 = 5A 00
Chip # 5 = 6C 00
Chip # 6 = 5D 00
The same chips have been re-checked without programming (just verifying) and the same exact values are still there in FLASH.
So the clock is being correctly trimmed ( hope so ) and the FLASH memory is being correctly programmed as seen.
After this I am copying a portion of the wizard's generated code in assembler. Highlighted in green, I can see that the code is initializing the trimming registers. Do you agree that this is the correct code to do this ? I believe yes.
If this is OK, the only thing that may be causing the failure is that this code is not being excecuted, but I discard this possibility. Many things are working fine in the chip, MTIM, modulo counter value, etc. Besides this I could alter the divisor and I can see the frequency change.
40: ** ==============================
41: ** Method : MCU_init (bean MC9RS08KA2_6)
43: ** Description :
44: ** Device initialization code for selected peripherals.
45: ** ==============================
46: */
47: void MCU_init(void)
48: {
*** EVALUATION ***
49: /* ### MC9RS08KA2_6 "Cpu" init code ... */
50: /* PE initialization code after reset */
51: /* Common initialization of the write once registers */
52: /* SOPT: COPE=0,COPT=1,STOPE=0,BKGDPE=0,RSTPE=0 */
53: SOPT = 0x40;
0000 3e001f MOV #%HIGH_6_13(_SOPT),PAGESEL
0003 3e4000 MOV #64,%MAP_ADDR_6(_SOPT)
54: /* SPMSC1: LVDF=0,LVDACK=0,LVDIE=0,LVDRE=1,LVDSE=1,LVDE=1,BGBE=1 */
55: SPMSC1 = 0x1D;
0006 3e1d00 MOV #29,%MAP_ADDR_6(_SPMSC1)
56: /* System clock initialization */
57: ICSTRM = *(unsigned char* __paged)CONVERT_TO_PAGED(0x3FFA); /* Initialize ICSTRM register from a non volatile memory */
0009 3eff1f MOV #255,PAGESEL
000c 4efa00 MOV 250,_ICSTRM
58: ICSSC = *(unsigned char* __paged)CONVERT_TO_PAGED(0x3FFB); /* Initialize ICSSC register from a non volatile memory */
000f 4efb00 MOV 251,_ICSSC
59: /* ICSC1: CLKS=0,IREFSTEN=0 */
60: ICSC1 = 0x00; /* Initialization of the ICS control register 1 */
etc, etc, etc, ....
0012 80 CLR _ICSC1
002f be RTS
/-----------------------------------------------------------/
Really lost and confused ...
Thank you so much dear Mac for your kind reply.
Just to order a little this conversation just in the case some more friends are reading out there:
1. I've been using my DEMOQE board to program many chips with accurate timing tasks, such as QE128, QE8, QG8, and the like. Never had a problem. The PC, the CodeWarrior IDE, the calibration and programming tasks work perfectly well.
2. the USBSPYDER08 we bought here was intended just for KA2 chips. The tool programs the FLASH and verifies correctly. It fails to obtain the calibration values needed to be written in FLASH at locations $3FFA and $3FFB.
3. I am completely aware that the FLASHing process and the calibration process are completely separated issues. In fact, FLASHing is not the problem.
4. I understand that there may be some "typical" ranged, values for trimming, being $80 right in the middle of the scale, and that is not likely to trim with $00 or $FF. But IMHO $A0 could be a good value for a lot of chips of the same production mask. Writing this value "by hand" forcing a constant into the register, works and places the clock in the desired value. So all chips are working and accept calibration. The calibration tool should find this value correctly, as I do it by hand.
5. this tool USBSPYDER08 has apparently been discontinued and I couldn't find any support for it, no drivers downloads, no mentions in the manufacturers website Softec Microsystems http://www.softecmicro.com/ which is now SMH Technologies. Not even at the Freescale site http://www.freescale.com/webapp/search/Serp.jsp?qt=USBSPYDER08&Go=%C2%A0&QueryText=USBSPYDER08&baseU...
6. please note this: the same DEMOQE board that I successfully use with the other chips, communicates perfectly with CW IDE and its Hiware software tool. Further more, it recognizes the 9RS08Kxx derivatives. Also fails to calculate de trimming values for the KA2 and throws the same bogus results the USBSPYDER08 finds.
7. same hardware and software fail to calibrate on different PC's
9. Question 1: could Softec Microsystems have released a tool not matching Freescale CodeWarrior's IDE ?
10. Question 2: what are you guy using to RELIABLY program a KA2 chip ? P&E ? Please enlighten me about this because I am about to buy a 3rd tool to get the job done and avoid making my friend here and myself loose their time 
I will very much appreciate any idea to solve the problem, specially from Softec Microsystems.
Dear Jim, thank you for your opinion.
When I bought the five units DEMOQE for my lab about 3 years ago, nobody told me that the 6 pins BDM connector provided on the boards were a bonus. I don't know any document explainig this point I don't see the point in restricting this posibility. In the other hand, clearly the reason is that P&E wants to sell BDM cables, but I find this policy tricky. We have discussed this point some time ago in a different post. I have longly paid this cable by buying 5 units DEMOQE
The guys at support@softecmicro.com ( Softec Microsystems ) are not replying to my request for the USBSPYDER08 device. I will never buy anything from them in the future because in my opinion support is everything after sales. So far, I am not having support of any kind. The device bought from an authorized Freescale dealer has been discontinued and all information related to it, dissapeared. It is noticeable that the corporate mailer rejects all of my support request messages posted at their website (qota exceeded). I can provide the copies of these messages.
Instead, I received an extremely fast response from P&E Micro. They explained that the DEMOQE board is not intended for programming any other chip different from a QE128 with the same pin count as the one that comes provided with the board. However, they said that if my instalation and Codewarrior IDE is able to program almost any derivative 9S08 as I'd been doing for the last 3 years, there is a detail to be considered in the case of KA2: the trimming frequency, which is by default ~39 Khz as shown in the Hiwave screen at the moment of programming, should be custom set at 31,25 KHz ( something I didn't imagined or considered ). When I tryied this option, I couldn't FLASH the part because of a software restriction or bug related to the connection between the Codewarrior IDE and the DEMOQE board, specifically for the KAx derivatives. But to my surprise, the log file ( the screen showing all commands ) showed that the calculation of the trimming value was finally correct with $A6. So, if the DEMOQE board could have FLASHed the part, my problem should had been finally solved.
The USBSPYDER08 could never calculate the correct value, so it is perfectly normal that the part is incorrectly calibrated.
Finally, there is no solution for my problem with the elements I have handy. I am now buying a MULTILINK UNIVERSAL BDM device from P&E Micro. I believe that this tool allows programming and calibration of the complete family of derivatives.
Kind regards
