Altirra Debug Console Question

[TGB1718]

When I use the debugger in Altirra, whenever I access D1: or D2: I get a stream of messages (100's) in the Console (see below)

This obviously gets in the way of normal monitoring, is there a way to turn this off ?

It never used to do this, I think I may have accidentally turned it on, but for the life of me

I can't see where to turn it off

 

DISKEMU: Stepper phases now: 2C
FDC: Physical track is now 4.5
DISKEMU: Stepper phases now: 34
FDC: Physical track is now 5.0
DISKEMU: Stepper phases now: 38
FDC: Physical track is now 5.5
DISKEMU: Stepper phases now: 1C
 

[Rybags]

I can't see any debug command that would generate that - do you have a specific drive defined in devices?

This is below SIO or serial tracing, it's as if it's showing the actual drive firmware's stepping commands.  1050 and I think 810 do 2 step phase changes to move 1 track.

[+DjayBee]

This looks like logs from Full Disk Emulation.

[Rybags]

Agreed - I can't seem to find a 1050 firmware here so can't recreate the situation properly.

[TGB1718]

2 hours ago, Rybags said:

do you have a specific drive defined in devices?

I have the drives mapped as 1050 with USD, same as my real setup, I'll try digging a bit deeper to see if I can find how to turn it off

[Rybags]

Maybe try in the debugger:

 

.traceser off

.tracesio off

 

Actually, I thought these options weren't persistent.  Generally debugger stuff like breakpoints only exist for the duration of the Altirra run.

Edited May 17 by Rybags

[TGB1718]

11 minutes ago, Rybags said:

Maybe try in the debugger:

 

.traceser off

.tracesio off

Many, Many thanks, that fixed it, like you, I didn't think commands existed after shutting it down 👍👍👍

[phaeron]

"lfd fdc" and "lfd diskemu" to turn off these logging channels.

 

[TGB1718]

How do you get Altirra to keep these settings ?

 

Every time I use the debugger I find I'm still getting tons of these messages, I have to manually turn these messages off

then next day it's back, I've tried Save State and Quick Save State, but it's always the same when I restart.

 

I'm running in Registry mode and have tried switching to Portable mode, but it still does this, is there a way to make

Altirra save the current debugger settings (in fact all settings as a lot of the time it removes attached drives between sessions too)

 

FDC: Physical track is now 18.0
DISKEMU: Stepper phases now: 2C
FDC: Physical track is now 18.5
DISKEMU: Stepper phases now: 34
FDC: Physical track is now 19.0
DISKEMU: Stepper phases now: 38
FDC: Physical track is now 19.5
DISKEMU: Stepper phases now: 34
FDC: Physical track is now 19.0
DISKEMU: Stepper phases now: 38
FDC: Physical track is now 19.5
DISKEMU: Stepper phases now: 1C
FDC: Physical track is now 20.0
DISKEMU: Stepper phases now: 2C
FDC: Physical track is now 20.5
DISKEMU: Stepper phases now: 1C
FDC: Physical track is now 20.0
DISKEMU: Stepper phases now: 3C
 

[phaeron]

Altirra saves most non-debugger settings by default, but be aware that if you open more than one copy of the program at a time, they may stomp on each other when saving settings. This is worse in portable mode than in registry mode.

 

You can place commands in a file called startup.atdbg next to the program executable to auto-run those commands when the debugger initializes.

 

[TGB1718]

7 hours ago, phaeron said:

Altirra saves most non-debugger settings by default, but be aware that if you open more than one copy of the program at a time, they may stomp on each other when saving settings.

No, I never run more than one copy at a time, learnt the problems associated with that many years ago

 

7 hours ago, phaeron said:

You can place commands in a file called startup.atdbg next to the program executable to auto-run those commands when the debugger initializes.

Thanks, I'll try that today, I just ran Altirra and it's still outputting those drive commands, so before I switch them off manually, I'll create this file

and run it again 👍

[TGB1718]

8 hours ago, phaeron said:

You can place commands in a file called startup.atdbg next to the program executable to auto-run those commands when the debugger initializes.

Thanks again that worked a treat, been annoying me for ages. One thing though, I couldn't find any reference to using

that file in any documentation.

 

I still think the main problem is that Altirra is not saving those settings on exit regardless of registry or portable mode, I remember

turning those settings on a long time ago to debug a disk based program and obviously it saved that, but won't save the turn off, strange 

[+DjayBee]

6 hours ago, TGB1718 said:

turning those settings on a long time ago to debug a disk based program and obviously it saved that, but won't save the turn off, strange

Did you check whether you have full disk emulation activated for a drive?

 

My Altirra never shows these logs with standard disk emulation but always shows them with full disk emulation.
(Both certainly unless I change it explicitly.)

[TGB1718]

42 minutes ago, DjayBee said:

Did you check whether you have full disk emulation activated for a drive?

Yes I have it emulating D1: and D2: as USD drives, same as my real hardware, I'll have a play tomorrow and see if that also fixes it.