Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple errors in the built-in ET-3400 ROM image #12

Open
ricknun opened this issue May 16, 2022 · 0 comments
Open

Multiple errors in the built-in ET-3400 ROM image #12

ricknun opened this issue May 16, 2022 · 0 comments

Comments

@ricknun
Copy link

ricknun commented May 16, 2022

Your source file "monitor.bin" has these differences from the ET-3400 ROM, using FC00 as its start address.

addr  HK    Error   Heathkit source code notes
====  ====  ======  ==================================
FC48  E2    F2      BKSET  LDX  #BKTBL-2
                                 ^^^^^ wrong

FD5A  FD    F7      .byte  HEXA,LTRC,LTRC,LTRA+$80
                                          ^^^^ wrong

FDF6  20    7F      INC1  LDAB  #TIME  VIOLATION COUNT
                                 ^^^^ wrong

FDFF  20    7F      INC3  LDAB  #TIME TIME UNTIL PAROLE
                                 ^^^^ wrong

FF81  12    10      OPTAB .word $9C00,...
FF84- 6410  0000    ^^ Opcode Table   ^^^ errors
FF85                   !!!!!!!!!!!!
FF94- 100C  0000
FF95

Details: Thinking about the "v0.2 Beta: Breakpoints don't seem to work at all" issue and ET-3400 ROM image error I stumbled on there, I exported the entire ROM image from the .exe file and compared it with the Heathkit original. This issue lists all errors found. For interest I traced them back into the Heathkit source code. I am curious, what generated monitor.bin and the errors?

For ET-3400 code development I am now using a hacked version of et3400.exe 0.2 Beta, with the built-in ET-3400 ROM image replaced by the original Heathkit ROM + the OUTCH fix + my Sample1B program in the 34 unused bytes near the end of the ROM. I used program XVI to edit the .exe file. I prefer your emulator to the others discussed on groups.io because of its disassembly pane, Save RAM (to a .s19 file), and user COMMENT/DATA labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant