azya52 / brickemupy Goto Github PK

Jump to the middle of the instruction, most likely there is a jump to 0x50D (one bit difference).

4FF:    ja1 50C                         ;8D0C
...
50B:    mov R1R0, 0x14                  ;5401
50D:    inc [R1R0]                      ;0C

Just need to click on main.py

Run it in a cmd is a no no. My bad.

how to build E23PlusMarkII96in1.asm to E23PlusMarkII96in1.bin ?

Какой файл надо открыть чтобы запустить эмулятор? При открытии py файлов появляется коандная строка и потом пропадает

No sounds still. I'm still testing on this Nobara OS.

I will try the Fedora OS out next. The one from the Rawhide 40. Just to test out to see the same issues are there.

Windows 11 Home no issue at all. :)

As I was reading through your article, I noticed that you had a picture of multiple generations of the brick game MCU. Have you been able to translate those yet, or are they still in progress?

I have an E-9999 BB-664 model, and I was wondering if you happened to have one of those. I don't have the necessary equipment (microscope) to be able to do the ROM extraction myself, so I was hoping you would have one.

BrickEmuPy seems to max out a single thread, even with the debugger hidden.

Is the debugger the cause of this or is the emulation in general causing the "high" usage?

Is it real Emulator?
where i can get die shots/reverse information/discussion threads etc?

Hi,

Haze is currently adding the emulation of the same device to Mame. I see that you've done a beautiful svg for the device, would you agree that we use it in Mame too?

Best regards,

Olivier Galibert

Shooting games, for example, 6 are reset to the main screen if you play them a little

1. This looks wrong because the high nibble of the second byte is not used, so it should be zero:

1C2:    mov R3R2, 0x08                  ;6840

2. There are two ways the code gets to CF5.

First:

C4E:    call 858                        ;F858
C50:    jnc C54                         ;CC54
C52:    jmp CF5                         ;ECF5

Second:

CCA:    mov R1R0, 0x93                  ;5309
...
CD2:    dec R1                          ;13
...
CDC:    jz A, CF5                       ;B4F5

On the first path, calling 858 returns R1R0 = 0x39, on the second path R1R0 = 0x83.

I think there is a typo in the address for jumping from C52.

CF5:    inc R0                          ;10
CF6:    mov A, [R1R0]                   ;04

It could also be a bug in the ROM code.