swapd0

The Jaguar memory map is 8MB of RAM, 6MB of cartridge and 2MB for ROM/IO.

I'm fixing/updating the code/assets to some changes that I've made to my libraries. Also I've done some testing in NTSC mode and it looks ok, but I need to do more testing on later levels.

A couple of month of further development to include a cache on DSP, GPU, OP & blitter, include a few extras (like RGB transparency), and you'll have an awesome console. No need for a 68020 or a R3000.

I doubt that the 68000 has some bus issues because it's the more stable/reliable/tested processor in the Jaguar but it has also the lowest priority, so if you hit the bus very hard with all other processors it won't have free bus cycles for him.

Anyway you still have 2MB RAM and all OP objects must be at first 8MB address space, with or without JagSD you only have main RAM there.

I think that you can fit all jaguar library into a 2GB SD... maybe 4GB if you include CD images.

So... you should give preference to EU users... 😁

You have to read the main memory before a write or the data won't be written. IIRC from DOOM source code.

"Maybe" (for sure) I did bad soldering, it takes me 10 to 40 minutes to do a soldering so I'm not very good at it. Tested with Super Burn Out and it works. This is wrong. Yes, it works. I've used that point.

Also the left point above R140 shares the same line.

I can't make the connection but I've realised that the each pin of the resistor are connected to that points, can I use these points to connect the switch? I've already removed the resistor.

I can't understand it, it doesn't matter if they are connected or not but I always get a NTSC Jaguar (VIDTYPE != 0 always)

Found, at the left side there's a row of soldering. The top one and the fourth starting at the bottom are the left and the right side of that resistor.

Is there place on the PCB except the R140 edges to test if you are in PAL or NTSC mode? I've done the mod but I'm always in NTSC mode, not sure what I've done wrong.

OMG, do you mean that the Jaguar has hardware bugs? 😂

This is a hardware constraint or it can be lowered by software?, maybe it can be nice to have 1 cycle access time and put textures there instead of RAM.

How it's that possible? The 68000 can address 16MB and you need to reserve some address for cartridge and devices. If it's some kind of bank switching the limit can be much higher.

It must work, having an offset to each row it's a good solution.

IIRC it's a skunk-board-only-rom.

At leas has a better/bigger homebrew community.

IMHO Rick Dangerous 2 it's a better game, at least I played it a lot more on the ST.

You need to hear the motor and the crack-sounds to optimise the racing lines if you want to reach the super division.

Linux & mac.

With bugs fixed and improved performance, like a cache on each processor? I'm in, if it's the same I'm not interested.

That would need a big rewrite, even with the source code avaliable it's a huge task.