last version of M16C/62 serial monitor

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
After Renesas merging, do someone know were to find the latest version of
M16C/62 serial monitor ?
Seems that Renesas site has an older one.

And... speaking of serial monitor: do anybody know if is already possible to
use the 4 address match units in the new 62P to handle 4 breakpoints ?
This is the reason I'm searching for the latest version...

Previously used sites such as
http://www.infomicom.mesc.co.jp/M16C/sw/library/monitor/emoni.htm#62

now redirect to Renesas.

The last version I have is:

; FILENAME: mon_m16c.a30
; Ver      : 2.02.02
; CPU      : M16C/6x

On Renesas site I can find only "6mo_srcj.zip", that contains 2.02, but the
source is much worse than the latest I have.
Seems that the version revision is completely out of sync.
The 2.02.02 sources are much better parameterized, and well written.

The 2.02.02 shows this history:

; History  : 2001.09.14 First Version for M32C by Noguti   *
;          : 2001.10.10 Change for M16C/62 by Sakata       *
;          : 2001.10.19 Arrange for M16C/62 by K.Tanimoto  *
;          : 2002.03.27 Modified to support various        *
;          :              processors by FLA (EDEC)         *
;          : 2002.05.15 Version 2.00.03                    *
;                       Support M16C/62P TS2 by osamura    *
;          : 2002.06.27 Version 2.00.04                    *
;                       Support UART0 or UART1             *
;          : 2002.07.29 Version 2.00.05                    *
;                       Support UART2 for M16C/6N0/6NA     *
;                       DOES NOT WORK ON M16C/62           *
;          : 2002.08.22 Version 2.00.06                    *
;                       Support PCLKR div1 for M16C/6N0/6NA*
;          : 2002.11.05 Version 2.00.07                    *
;                       Modified behaviour after restart   *
;                       Restart of KD30 is possible without*
;                         reset of target system.          *
;                       Reset on target system is possible *
;                         without restart of KD30.         *
;          : 2002.11.06 Version 2.00.08                    *
;                       Add support for M16C/6N4 and 6N5   *
;                         with PLL and without PLL         *
;          : 2003.02.24 Version 2.02.01                    *
;                       Synchronised with version 2.02     *
;                       INFOMICOM homepage. Small change   *
;                       in routine for setting breakpoints *
;          : 2003.04.10 Version 2.02.02                    *
;                       Added support for M30262F6 and     *
;                       M30262F8.                          *

---------------------------------

This, instead, is the history taken from Renesas site file:

; History : 2001.9.14 Fist Version for M32C by Noguti  *
;   : 2001.10.10 Change for M16C/62 by Sakata  *
;   : 2001.10.19 Arrange for M16C/62 by K.tanimoto *
;   : 2002.5.16 Modify for M16C/62 by osamura  *
; RCS ID : $Id: mon_uart.a30,v 1.10 2001/10/25 11:52:29  *
;  NAME    : tanimoto Exp tanimoto $      *















Re: last version of M16C/62 serial monitor
I answer to myself...

Quoted text here. Click to load it
to

After some googlin' around, I found the site:

http://www.m16c.de

this has a 2.02.05, that seems newer, and says it supports the 4 breakpoints
of 62P.

Now the question is... do KD30  3.20 release 1B supports 4 breaks also ?
I have no samples to try...



Re: last version of M16C/62 serial monitor


Quoted text here. Click to load it

Hi Antonio,
 
 I quit using the KD30 debugger because it's too slow and yet
 every once in a while it hangs and stop the microcontroller.
 I use instead Microsoft Visual C to debug my code: if the application
 has some hardware dependancies I write a Visual C version
 of those functions.

 ciao
 Enrico

Re: last version of M16C/62 serial monitor
Enrico,

when using the KD30/ ROM monitor you have to reenable interrupts in all ISR.
(asm "FSET I")
Else the ROM monitor will hang occasionally.

It is one of the topics in the monitor usage precautions issued by Renesas
(previously Mitsubishi)

regards
/jan


snipped-for-privacy@fatti.com...
Quoted text here. Click to load it
breakpoints



Site Timeline