Search found 10 matches

Go to advanced search

by mhavoc
Tue Jun 09, 2020 2:26 am
Forum: MAME Discussion
Topic: trace syntax
Replies: 1
Views: 1098

Re: trace syntax

Following up on my own post after a few days of trial an error, reading the source and reading the syntax of other debug commands.... Firstly, the <action> can be anything that is a valid debug command. Looking under the 'Expressions' section... it talks about data memory notation... there are a few...
by mhavoc
Fri Jun 05, 2020 5:12 pm
Forum: MAME Discussion
Topic: trace syntax
Replies: 1
Views: 1098

trace syntax

Hi all... Im attempting to do some debugging that is pretty complex. I have my normal trace command of trace mytrace.txt,0,logerror,{tracelog "A=%02X X=%02X Y=%02X ",a,x,y} (PS: Im targeting the 6502). There are several RAM variables that I would love to be able to capture in the trace too...
by mhavoc
Sat Dec 01, 2018 5:21 pm
Forum: MAME Discussion
Topic: Issue compiling on VS2017
Replies: 3
Views: 2137

Re: Issue compiling on VS2017

..and one final post here.... I was able to uninstall my VS 2018 15.8+ (no reboot required!)... and then install the 15.7.6 version from this page. https://docs.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 The process took 3+ hours, but I am now able to compil...
by mhavoc
Sat Dec 01, 2018 6:27 am
Forum: MAME Discussion
Topic: Issue compiling on VS2017
Replies: 3
Views: 2137

Re: Issue compiling on VS2017

So, I just found this mentioning that the newer versions have this issue while the older version of VS2017 do not. https://developercommunity.visualstudio.com/content/problem/345010/internal-compiler-error-with-mame-emulator-devdele.html I will look into downgrading my VS2017, but I was wondering if...
by mhavoc
Fri Nov 30, 2018 9:47 pm
Forum: MAME Discussion
Topic: Issue compiling on VS2017
Replies: 3
Views: 2137

Re: Issue compiling on VS2017

Okay, so apparently I was not running a very recent update of VS 2017... I just updated to VS 2017 15.9.3.. However, still won't compile... *although* the errors are a tad different here, so maybe I need to tweak some solution or project settings? 1>c:\svn\git\xxx.mame\src\emu\devdelegate.h(103): er...
by mhavoc
Fri Nov 30, 2018 9:01 pm
Forum: MAME Discussion
Topic: Issue compiling on VS2017
Replies: 3
Views: 2137

Issue compiling on VS2017

Hi Folks... My mame source is compiling fine using MINGW64, but Mame64.exe is crashing when I try to run my new driver. So, I figured I would build in VS2017 in order to have better debugging tools... I ran... [MINGW64] make vs2017 SUBTARGET=mhavoc SOURCES=src\mame\drivers\mhavoc.cpp PYTHON_EXECUTAB...
by mhavoc
Sat Aug 18, 2018 5:23 pm
Forum: MAME Discussion
Topic: Logging a memory write?
Replies: 1
Views: 1548

Re: Logging a memory write?

... and of course after posting.. I figured it out..

wpset 0295,1,w,1,{logerror "ID: %02X",wpdata: g}

Worked like a charm.. nice job devs!!!
by mhavoc
Sat Aug 18, 2018 5:10 pm
Forum: MAME Discussion
Topic: Logging a memory write?
Replies: 1
Views: 1548

Logging a memory write?

Hiya.. I need to dump to the log anytime a byte is written to a specific RAM location. From want I can tell, I can't seem to do this from the debugger as the only way to do it is to set a watchpoint along with a logerror action.. however, that also stops execution in the debugger each time, which is...
by mhavoc
Fri May 25, 2018 1:48 pm
Forum: MAME Discussion
Topic: ROM Filename Case in driver
Replies: 4
Views: 7527

Re: ROM Filename Case in driver

Cool, thanks for the info on the inner-workings of MAME appreciate it.. I will go with lowercase for now.

You are correct.. I don't have a .1L and a 1I location (luckily).
by mhavoc
Fri May 25, 2018 12:04 am
Forum: MAME Discussion
Topic: ROM Filename Case in driver
Replies: 4
Views: 7527

ROM Filename Case in driver

I couldn't find a answer to this doing a search... should I distribute ROM's in Lower Case, Upper Case or doesn't it matter? the ROM extensions are going to be the PCB location and they are much easier to read in Upper case.... .1L vs .1l for example. I didn't know if this was breaking some conventi...

Go to advanced search