Zerosquare

They're chip-select lines, they only stay asserted during the duration of the memory access. In other words, you can't set them high or low, you only get a very short pulse when you access memory in the memory area associated with the GPIO pin.

This topic is a repository for all files, tools and links that are useful for Jaguar development. Click on the titles to download the files. If you think something is missing, find a broken link, or have a suggestion to improve it, don't hesitate to post. (work in progress, unsorted as of now) Developer documentation (contributed by Starcat and Jon Matthieson) These are scans of the paper documentation which was included in the Jaguar's SDK. They are believed to be the most up-to-date version available. Beware : the archive also includes the Techref v8 file made available by John Mathieson in 2001 ; while it is more convenient to use, it appears to be an older version. JAGUAR.INC JAGUAR.INC is the include file which contains hardware registers and constants definitions. You'll need it to program in assembler or C. This version has a changelog dated 05/16/1995 and is believed to be the latest one. JagView (contributed by dox) JagView is an utility to find and display uncompressed Jaguar pictures embedded in a ROM file (or as separate files). 8-bit, CRY and RGB formats are supported. Beware : it is known to display slightly wrong colors in some circumstances. Lo_inp An updated BJL uploader which works under Windows 2000/XP, as well as Windows 9x and Linux. Sources included. Jaguar Image Converter A modern and more flexible replacement for TGA2CRY. Sources included. bmp_cry, 8bit_to_bmp , view_jag Quick-and-dirty programs to view and convert pictures to and from Jaguar formats. Sources included. Virtual Jaguar 1.0.7 with BIN files support Virtual Jaguar 1.0.7, patched to allow the loading of straight BIN files, and compiled for Windows. Orion's GPU/DSP debugger What it says in the title Sources included. The Removers Library's Q & A Question and answers about the Removers' C library. Mindebug The core of a Jaguar remote debugger using BJL. Can also be used as a basis for reliable bidirectionnal BJL communications. Sources included. Encrypting CDs using the BJL cable How to encrypt CDs if you don't have any JagLink or serial cable. Cartridge dumping tool Allows you to dump Jaguar cartridges, including flash carts. Sources included. Workaround for the UART bug How to use the network without crashes. Sources included. Jagpads, teamtaps, rotaries and other controllers Single topic about the different type of controllers and the way to support them. Jagfiles (contributed by Curt Vendel) Lots of source code from games, mechanical drawings, various Atari documentation, etc. Atari Showroom (Jaguar section) A local mirror of Glenn Bruner's former site. Lots of technical information about Jaguar hardware, both common and rare. Includes schematics, Tom & Jerry netlists, Alpine-related documents, etc. Thanks to Glenn Bruner for providing the files! JagDev A mirror of CTS' former site. A few dev tools there, and some 3D stuff. Some files are unfortunately missing. Universal cartridge header (contributed by Glenn Bruner) The cartridge header that can be added in front of any ROM code to allow it to run on non-modded Jaguars. MPEG cartridge documents (contributed by Glenn Bruner) Technical documents related to the MPEG 1 decoding cartridge that Atari planned (but never released). Adding a rotary on a standard Jagpad Cartridges mechanical drawings / dimensions Fastboot header for carts (contributed by Tursi) A special header for cartridges that speeds up the boot process. The Jaguar Server home page A mirror of Roine Steinberg's Jaguar Server page. (A few images are missing, unfortunately) Flare II Jaguar technical reference manual (pre-Atari, 1992) For archeology buffs, the oldest version of the docs.

Here's a cartridge dumping tool I wrote. It can be used to backup your Jaguar games for various uses : playing in emulators, preserving betas versions and prototypes, etc. It's pretty slow, but very reliable, as there are multiple checks done to be sure that the data isn't corrupted. As well as standard cartridges, Atari Flash carts are supported too. Requirements : - a PC running Windows (95, 98, 2000, XP or Vista : it doesn't matter. Windows 7 not tested, but it probably works too.) - a BJL cable connected to a standard (not USB or PCI/PC Card/ExpressCard) parallel port - a way to upload a Jaguar program with a game cartridge inserted (currently, the only option is a BJL-modded Jaguar) See the included text file for more detailed instructions. For programmers, the sources are included. Unfortunately, they're in French and almost without comments, as they from an older project which wasn't supposed to be publicly released. Planned future developments : - adding support for PCI/PC Card/ExpressCard parallel ports - adding Linux support - adding backup/restore features for the cartridge's EEPROM contents (used for saving states, hiscore lists, etc.) - adding backup/restore features for the Memory Track bjl_dump.zip overridex has been kind enough to port it to Linux : bjl_dump_linux.zip Thanks to him ! The next version will be unified and work with both OSes.

Unfortunately the answer is "no" to each question. But adding support for non-builtin parallel ports is not a lot of work. Which game do you want to dump? Unless it's a previously unknown beta, it's probably been dumped already ; you could download it and save you the trouble.

Here's an adapter to use Atari ST (or compatible) joysticks/joypads on the Jaguar. The four directions of the joystick map to the Jaguar's D-pad, and the joystick button maps to the Jaguar's B button. This is not a standalone device, it is meant to be added inside a standard controller (it can probably work on a Pro controller with minor modifications, but I don't have one so I can't test it). All buttons of the controller remain functional whether or not there's a joystick plugged in. The circuit taps signals from the controller's 74HC244 chip ("Axx" arrows) and from the controller's cable ("Bxx" arrows). The dot on the 74HC244 package is next to pin #1 ; pins are numbered counter-clockwise. To identify the correct wires on the cable, use a continuity tester, since wire colors may be different from controller to controller. The parts you need are: - One 74HC244 or 74HCT244 integrated circuit - Five 10 kΩ ±5 % 0.25 W resistors - Five 1N4148 diodes - One 100 nF 25 V X7R capacitor - One 9 pin male D-sub connector

irc.worldnet.net

Added a very old (1992) version of the docs from Flare II, for curious people :)

I have no experience with this since I don't own a JagCD, but have you looked at this guide?

Fredifredo told me he had two hard drives crashes since then, so he isn't sure he still has a copy of the file, and can't look into it right now. Sorry

It shows 138 MB for me too, so the file must have been corrupted on the server for some reason. Unfortunately I don't have a copy of this file, but I've asked Fredifredo to send it to me if he can.

Original

I've added a "convert to BMP" feature to my picture viewer: http://www.jagware.org/index.php?showtopic=259&p=12902

Nice

To switch back from interlaced to non-interlaced mode: Blindly restoring the values from the boot ROM into the video registers doesn't work reliably. Both HC and VC must be reset immediately before doing so, otherwise you have a chance of ending up in a state where you don't get VBLANK interrupts anymore. Here's the code: InitNonInterlacedMode: move.w CONFIG, d0 andi.w #16, d0 bne InitNonInterlacedMode_60Hz InitNonInterlacedMode_50Hz: move.w #0, HC move.w #0, VC move.w #$026F, VP move.w #$0265, VEB move.w #$026A, VS move.w #$0006, VEE move.w #$0022, VBE move.w #$0258, VBB move.w #$0352, HP move.w #$06D5, HS move.w #$0313, HEQ move.w #$0259, HVS move.w #$06AF, HBB move.w #$009E, HBE move.w #$06A0, HDE move.w #$00A6, HDB1 move.w #$00A6, HDB2 move.w #$002E, VDB move.w #$020E, VDE bra InitNonInterlacedMode_End InitNonInterlacedMode_60Hz: move.w #0, HC move.w #0, VC move.w #$020B, VP move.w #$01FF, VEB move.w #$0205, VS move.w #$0006, VEE move.w #$0018, VBE move.w #$01F4, VBB move.w #$034C, HP move.w #$06CD, HS move.w #$0310, HEQ move.w #$028B, HVS move.w #$06B1, HBB move.w #$007D, HBE move.w #$06A0, HDE move.w #$00A6, HDB1 move.w #$00A6, HDB2 move.w #$002E, VDB move.w #$01F0, VDE InitNonInterlacedMode_End: For safety, you should disable 68K interrupts before running this code, to make sure it doesn't get interrupted. This code resets all video registers, so you should rerun your video init code afterwards to set VI, HDB1, HDB2, HDE, VDB and VDE properly for your game. VI is especially important: make sure its value is odd, otherwise you won't get any VBLANK interrupts anymore.

It's never too late

Happy new year

As a Christmas present, Reboot has released a Jaguar invitro to the Sommarhack 2016, using the now-famous Raptor Basic+. It can be downloaded here, and the Pouët.net page is there.

As a nice example of what can be done with Reboot's Raptor Basic+, sh3 released a demo at the Outline party called "Cloudy with a chance of metaballs". It can be downloaded here. If you can't run it, here's a video:

I just thought of something: Most CD homebrews are pretty small, so there's unused space on the disc. Even the largest ones are large mostly because of audio tracks, not code/gfx. What about filling the unused space with copies of the code/gfx? It could work that way: - there are N copies of your code/gfx on the disc - if a sector read fails, retry it a few times - if the error persists, seek to the next copy and try to read the sector from there - if it succeeds, continue loading from that copy (don't seek back to the original copy) - if it still fails after a few retries, go to the next copy (or back to the first one if you reached the last one) Maybe each copy could be in its own track or session. Padding could be used between copies to make sure they are spread far enough on the disc. I don't know if it can actually improve the reliability of JagCD loadings, but I think it could use a test

It works

Ah, you're right, I didn't even notice. I must be really tired...

It doesn't display here. Oh well

Too bad there's no "like" button on this forum

I could, but nobody could afford it. This is not the NeoGeo scene