Hi Mark,
Have you submitted a trouble ticket?
That would probably be the best way to go.

Which version od the ZDSII are you using?
You might try recompile all before you use the interactive debugger (just in case).
I would also be curious about the location - if you set a breakpoint at the beginning, does that make a different?
Do you have WDT enabled?

I have a couple of open tickets regarding my Z80 to eZ80 conversion study.
462 - using ZDSII to debug Z80 project [2011-02-08 13:02:01] [OPEN]
439 - eZ80 Mixed Mode ADL support within ZDS2 [2011-01-28 05:01:16] [OPEN]

We use 5.1.1. I've tried 4.11.0 just to see . . .

Ticket 462 has a small example attached.

I will ask our support people to understand what is going on.
In the meantime, I remember running into something similar when I first went to Windows 7.

Are you using the Smart cable? If so, which one and what hardware version and what software version?
Are you using Windows 7 or XP? 64 or 32 bit?

I'm using Windows XP 32-bit. I use the smart cable. I've been using this environment daily for over 2 years, sometimes with 3 smart cables active at once. I use the eZ80 acclaim ZDS version 5.1.1 with my eZ80 projects and the Encore ZDS version 4.11.0 with my z8 projects.

Recently, I was asked to explore the options for porting Z80/Z180 assembly code to the eZ80 platform. I figured I would create a simple example Z80 project to explore the requirements for initializing an eZ80 in ADL=0 mode. As the first phase, I sought to initialize the vector table, stack pointer and clear the RAM. Next, I plan to create a loop after the initialization and make sure the vector table is configured properly by testing with Timer 0 and Timer 1. After that, I expect to be able to use this core as a starting point for the porting of a Z80 system.

Is there an example 'ADL mode 0' project anywhere that I can download for the eZ80 development kit ? I could use something that is proven as a baseline.

HACK-RTOS for eZ80 uses the ADL-0 mode. See the _core.asm file. It starts in ADL-1 mode, copies its memory segments in RAM then switches to ADL-0 and continues in this mode.

Thank you,

I'll give that a look now