hc908qb8 problem with CodeWarrior.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

hc908qb8 problem with CodeWarrior.

2,298 Views
Yaroo
Contributor I
Hello.

I've got problem with debugging my program in CodeWarrior 5.0. I'm initializing the KBIPR - keyboard polarity register, pins KBI3, KBI1 and KBI0 are rising edge sensitive.
I've experienced strange behavior of the simulator. It says that im attempting to write an unimplemented memory at address 0x001C. According to datasheet the KBIPR register occupies this location.
Futhermore, I've searched all files with "qb8" phrase and found that me and the datasheet are right - my register is at the address 0x001C.
So where's the bug? Is there a file containing MCU's memory mapping (register mapping) I've missed in my searches? How to fix this?

Thanks.
Labels (1)
0 Kudos
8 Replies

596 Views
peg
Senior Contributor IV
Hi,
True-Time Simulator 6.1 (Part of CW5.1) appears not to support this register.
 
To confirm this in your copy:
Run simulator for the QB8
Open HC08FCS menu
Choose View Register Files...
Then select KBD
Here I only see:
1A KBSCR and
1B KBIER
 
This is why it does not work. It will require an update from P&E via CW/Freescale
 
0 Kudos

596 Views
Yaroo
Contributor I
Hello.

I've received replay from Technical Support:

"Thanks a lot for this report,
In fact this is a known issue we already reported to the engineering team of P&E which implemented the simulation module (bug: 4034).
They informed us that they corrected this problem, so the fix will be available with our next HC08 CD release.

Currently we do not have any information about this new coming update, but we will inform you as soon as we have more detail"

So... so far I've got to comment the line with KBIPR during simulation, and uncomment when programming the chip.

Thank You for Your interest.
Best wishes!
0 Kudos

596 Views
jamesmorales
Contributor I
that thing you wrote you did...about comment the line to simulate and then burn the device with that line on....your device will be programmed but it want work fine...it will have problems with that interruption
thats the problem
0 Kudos

596 Views
bigmac
Specialist III
Hello,
 
This does raise the issue of Freescale publishing a list of known bugs associated with their software products.
 
It is deemed appropriate for Freescale to provide details of any known hardware problems, within the various Mask Set Errata documents.  So why not for the Code Warrior products?
 
The fact that third parties may supply some of the software modules within the Freescale package is quite irrelevant to the reporting, and the provision of a work-around solution until the problem can be fixed by Freescale, or the third party.
 
What do others think?
 
Regards,
Mac
 
0 Kudos

596 Views
peg
Senior Contributor IV
Hi Mac,
 
I totally agree!
The list obviously already exists, complete with little numbers allocated to the problem.
However it remains to be seen whether they are game enough to release this given the seemingly high level of issues.
 
As to this issue and ones like it, I have noticed that many files to support different members of the same family are simply renamed versions of other members. This is what I believe is more than likely what has happened here, another similar device does not have this register.
 
The details that I pointed out can probably be filled in by anyone adding to the 08QB_kbd.reg file.
However I doubt that the improvement would go beyond this.
I imagine the real support is within ics08dll_ics08qbz_v110.dll
If this is the case then this would support my assumption above as the "mistake" or "bug" is unlikely to have occurred in the same area in two places.
 
0 Kudos

596 Views
YeOldeBDM
Contributor III
Start the simulator and then simulator->configure.
 
See if the memory address you are trying to use is properly defined in the configuration. 
 
I can't find any good documentation on the simulator->configure window, so if anyhow has any, please respond.
0 Kudos

596 Views
jamesmorales
Contributor I
hi...i want to know if you could fix the problem you mentioned?, if yes i would thank you send me that information
0 Kudos

596 Views
bigmac
Specialist III
Hello,
 
I have been able to replicate your problem.  The KBIPR register is correctly defined within the header file for the QB8 device (otherwise it would not compile), but the register location is not recognised during debug.  This would appear to be a problem with full chip simulation for the QB8.
 
I guess you will need to get a definitive answer from Freescale (via a service request).  Let us know the results of any request you make.
 
Regards,
Mac
 
0 Kudos