SebRmv

That was the Scatbox that prevented me from using the JagGD... Thanks to @SainT for his help

Thanks to @Zerosquare, I have now an original BIOS. When I boot the JagGD, I get the RetroHQ logo and that's it, nothing more. What should I do?

Congratulations guys! This looks really cool

Thanks! It is an M serie. Actually the simpler would be that I flash my EPROM. My modded jag has actually a switch to select between 4 roms: Stubulator 93, Stubulator 94, BJL and JagOS. I guess I could replace one of these with the original BIOS (maybe JagOS?). I believe I flashed this EPROM myself, but I don't have the hardware anymore to do that.

Ok, thanks. Too bad I haven't kept the original BIOS on this modded Jag...

Hello, I just received my Jaguar GameDrive. My first impression was that it really looks good and was impatient to test it. Unfortunately, I cannot manage to use it right now. So I have a few questions. First, I use a BJL modded Atari Jaguar. When I press B, I got sometimes the RetroHQ logo, and sometimes a blackscreen. When I get the RetroHQ, it seems just stuck afterwards. I tried with and without a SD card plugged in the slot. (also, I am not sure the SD card is plugged correctly as it seems there is a spring mechanism) I don't get the screen with the QR code and the instructions to flash the latest firmware (as it is explained in the manual) Are there any specific instructions to follow? Is it supposed to work with a BJL modded Jaguar or should I get my hands on a "normal" Jaguar? Many thanks, Seb

Use the Makefile to build... make build and make run (you have also make help )

Looks great! Congratulations!

You can use that by enabling WSL2 extensions. I tried it with ubuntu on WSL2 and it worked (well, except jcp, but you can use native windows jcp)

Thanks! Actually, since this is my first Python program, there may be some bugs. So if you notice regression, please tell me.

Finally got time to work a bit on the Jaguar Image Converter in Python. This should work reasonably well now. I have not ported all the options that were in the ocaml version (dithering/rotation/cut/...) I'd be happy to get feedback on it (as well as on the Docker environment). Cheers Seb

LOL And thanks, now I can assemble AW

Where should I report bugs? ;;; address register = base of var array VARREG equ 2 .macro emitInstr ;; \1 = instruction move.w \1,(a1)+ .endm .macro emitTgtMem ;; \1 = opcode ;; \2 = variable number (will be multiplied by 2) ;; \3 = address register number add.w \2,\2 beq.s .opt\~ emitInstr #(\1)|(%101<<6)|((\3)<<9) bra.s .done\~ .opt\~: emitInstr #(\1)|(%010<<6)|((\3)<<9) .done\~: .endm ;; emit "move.w #YYyy,xx(Var)" emitTgtMem (%0011<<12)|(%111100),d0,VARREG This one produces a segmentation fault.

Hey, thanks! Also to mention I am working on building a docker environment (based on archlinux) that configures everything. It is ongoing work but this works reasonably well, even on WSL2 (I still need to adapt to use rmac instead of madmac) Repo is here: https://github.com/theRemovers/jagdev I am also working on translating my Jaguar Image Converter in Python, because it is too difficult to maintain the build with ocamlimages.

Yes, with the patch to rmac, no need to modify rmvlib

@ggnI think it is time that I use a more modern tool than MadMac I will report issues if I found any, be reassured It would be great if the patch is integrated to rmac github repo. By doing so, I will be able to officially switch to rmac all my projects.

I applied the patch and it seems to work! Thanks I need to test, test and test now

Ok, many thanks! Will try that edit: just tried, display.s still fails to be assembled (not tried the other files, but I guess it's the same issue)

I think one problem in my code is the use of '*' to refer to current PC, as for instance in the following code: .org G_RAM padding_nop (G_RAM+$10-*) where padding_nop is a macro defined as follows: .macro padding_nop .print "adding ",\1/2," padding nop" .rept (\1 / 2) nop .endr .endm What should I use instead of '*' ?

Hello, I am trying to switch to rmac for building The Removers Library. I get the following errors when compiling display.s: display.s 192: Error: illegal relative address display.s 192: Error: mis-nested .endr First, I believe the line numbers are wrongly reported, because on line 192 stands a local label definition: .gpu_display_from_cpu_it: Secondly, the second error message seems to indicate a problem with a rept/endr. Is there a way to adapt code that was accepted by MadMac? How can I track more precisely the origin of the error? Many thanks! Seb

Thank you so much for your detailed answer I need to read and digest this now

Hello, I'd like to add support for rotary controller in the Removers library. However, right now, I have not a clear understanding on how to read data from joypad, interpret them, and report them. Is there some reference documentation about that? And/or even better some available code to do that? Thank you, Seb

Removers extensions to JCP published here: https://github.com/theRemovers/skunk_jcp

Sorry, I will publish source of rmvjcp Done: https://github.com/theRemovers/skunk_jcp/

Oh, I think I never saw that (or at least do not remember). Yes, I should publish source of rmvjcp, let me do some cleanup in my files, before.