Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > Help me!
2024-07-28 23:56
JackAsser

Registered: Jun 2002
Posts: 2038
Help me!

So I'm coding some EasyFlash stuff so most often the kernel is swapped in ($01 = #$37).

Take a look at the following chis (VICE cpu history): https://i.postimg.cc/sg9xL7xV/temp-Image-Gb-W5z-N.avif

I'm putting a CR to $ffd2 and all goes well until it hits $ed41 where the CPU fetches a JAM-instruction. How's that even possible?! The ROM can't be altered. Comparing to ROM-listings it should do a JSR $EE97 there.

There is a SEI just infront if that matters.

(Only tested in HEAD VICE and some older version like 3.6 and 3.8). Could it be an emulation bug?

((Nevermind the .arbX label, it's just my loaded labels from the assembler. In the ROM it's just BIT $94)).

It happens VERY seldom.
 
... 15 posts hidden. Click here to view all posts....
 
2024-07-29 21:37
chatGPZ

Registered: Dec 2001
Posts: 11443
Indeed traps are implemented via JAM ... should probably say so in the history/disassembly. Another of those thousand things... :)
2024-07-29 23:11
JackAsser

Registered: Jun 2002
Posts: 2038
Quote: Indeed traps are implemented via JAM ... should probably say so in the history/disassembly. Another of those thousand things... :)

Yep, so I figured deep down the rabbit hole. :D

VDT are very useful for debugging in my case. Getting a quick stdout log to a file is VERY helpful via device #4. Single step in the debugger is too low level, and simple $d020/$d021 writes are not enough in this case. I need a proper history of events (30+ cooperative threads running wild).

Anyways, VICE works fine. I need to submit a patch for a proper fflush() on each $ffd2 though. Currently on my mac it's line buffered which is a bit annoying.
2024-07-30 00:41
Count Zero

Registered: Jan 2003
Posts: 1945
Salvation!
Now you just need to tease us harder on the next print-on-virtual-paper RPG you seem to be working on, JA!
2024-07-30 01:08
Fungus

Registered: Sep 2002
Posts: 706
What even are virtual device traps?
2024-07-30 02:26
Krill

Registered: Apr 2002
Posts: 3005
Quoting JackAsser
I need to submit a patch for a proper fflush() on each $ffd2 though. Currently on my mac it's line buffered which is a bit annoying.
Line-buffered output is a good thing.

Maybe you just want a way to issue a flush from a guest-side KERNAL call? =)
2024-07-30 03:14
Martin Piper

Registered: Nov 2007
Posts: 727
Quote: Quoting JackAsser
I need to submit a patch for a proper fflush() on each $ffd2 though. Currently on my mac it's line buffered which is a bit annoying.
Line-buffered output is a good thing.

Maybe you just want a way to issue a flush from a guest-side KERNAL call? =)


Not when single step debugging and the output has been triggered, and you're watching the debug log file in an external editor. In those situations the external editor visible log file won't reflect the most recent events until they are flushed, which can be several C64 logging calls behind.
2024-07-30 04:08
Krill

Registered: Apr 2002
Posts: 3005
Quoting Martin Piper
Not when single step debugging [...]
... earlier ...
Quoting JackAsser
Single step in the debugger is too low level
So then, a way to enable/disable buffering via KERNAL call?
2024-07-30 08:20
JackAsser

Registered: Jun 2002
Posts: 2038
Quote: What even are virtual device traps?

A way for VICE to intercept standard kernel I/O-calls and execute them immediatly instead of doing the full emulation of the $dd00-dance.
2024-07-30 08:22
JackAsser

Registered: Jun 2002
Posts: 2038
Quote: A way for VICE to intercept standard kernel I/O-calls and execute them immediatly instead of doing the full emulation of the $dd00-dance.

So basically, by attaching a raw printer that emits to a file and the do an open 1,4,7 you’ll get an easy debug print interface via $ffd2.
2024-07-30 09:33
JackAsser

Registered: Jun 2002
Posts: 2038
Quote: Quoting Martin Piper
Not when single step debugging [...]
... earlier ...
Quoting JackAsser
Single step in the debugger is too low level
So then, a way to enable/disable buffering via KERNAL call?


Imo it shouldn’t be line buffered at all - ever. When you send a character to a printer connected to a c64, that character is printed directly. And so should it behave when emulated to a file also.

Maybe a toggle switch in the VICE-settings.
Previous - 1 | 2 | 3 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Mike
zscs
Guests online: 182
Top Demos
1 Next Level  (9.7)
2 Codeboys & Endians  (9.7)
3 13:37  (9.7)
4 Coma Light 13  (9.6)
5 Mojo  (9.6)
6 Edge of Disgrace  (9.6)
7 Uncensored  (9.6)
8 What Is The Matrix 2  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Nine  (9.7)
2 Trippy Tea  (9.7)
3 Layers  (9.6)
4 Party Elk 2  (9.6)
5 Cubic Dream  (9.6)
6 Copper Booze  (9.6)
7 The Boiling Bar  (9.5)
8 Libertongo  (9.5)
9 Ten  (9.5)
10 Dawnfall V1.1  (9.5)
Top Groups
1 Oxyron  (9.3)
2 Booze Design  (9.3)
3 Performers  (9.3)
4 Censor Design  (9.2)
5 Crest  (9.2)
Top Diskmag Editors
1 Magic  (10)
2 Jazzcat  (9.5)
3 Newscopy  (9.2)
4 hedning  (9.2)
5 Elwix  (9.1)

Home - Disclaimer
Copyright © No Name 2001-2025
Page generated in: 0.061 sec.