Date: Thu, 06 Jan 2005 13:50:57 -0800 
From: "Taft, John" <John.Taft@renesas.com> Subject: RE: QzROM Support Tool Update To: Chad Solomon <csolomon@sc3.com>, 
        "Tyagi, Ritesh" <Ritesh.Tyagi@renesas.com> Cc: "Logan, Don" <Don.Logan@renesas.com>, 
        "Belanger, Andre - SCC" <abelanger@sc3.com> Thread-topic: QzROM Support Tool Update Thread-index: AcTzTFalwr/dkvXiT3u7MMgyAzoUHgA6Xjfg X-MS-Has-Attach: yes 
X-MS-TNEF-Correlator: 
X-MFData: [v2.3 t10,560034] 




Hi All,
I took the starter kit’s AD_CONV sample C code and made it into a full-blown IAR C project, with outputs for several debuggers and a release version too.
 
Here is a IAR project for the AD_CONV sample.
I’ve added several targets:
-Release        (download hex file to MCU with FoUSB) -KD38 Debug  (output works with KD38)
-PD38 Debug  (output works with PD38 and PD38simulator) -PDB38M Debug (output works with PDB38M on the T-PAC emulator) -C-SPY Simulator (output works with C-SPY) I tested all the targets on the PD38simulator, except the KD38 target, because it required the interrupt vectors to be at 3FDC, rather than at FFDC.
So the KD38 Debug output has not been tested at all.  I am guessing I got it right, and only looked at the map file for verification.
For all the targets above,  the code & data memory sections are located exactly where they should be in the microcontroller, except for KD38 Debug, where the locations conform to the requirements of KD38.
 
I tried it on the starter kit and it works, though I don’t see any pot connected to P20 (AN0) input, to adjust.  P20 floats, so you see different readings of “Read_Data”.  If you connect the GND testpoint to the P20 header location, then Read_Data gets a 0, as expected.

Let me know if you have any questions.
 
 
If you use PD38simulator, then select the attached sfr file for debugging 37544.
 
Best Regards,
John Taft
Renesas Technology America, Inc.
16515 CR 327
Buena Vista, Colorado 81211
phone: 303-588-0524
fax: 928-447-3685
email: mailto:John.Taft@renesas.com
Renesas web site
 
 