Jump to content
Jagware

Tursi

Members
  • Content count

    76
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tursi

  • Rank
    Great giana sister
  • Birthday 11/29/1971

Contact Methods

  • Website URL
    http://harmlesslion.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    SFO
  • Interests
    Software, games, classic systems

Previous Fields

  • Skills - Comp├ętences
    Languages: English, Franglais? ;) Current on: Embedded code, asm, BASIC (visual or not, whatever), C/C++, system, server, network, console, pc. CPUs: 6502, 6509, Z80, 9900, Atmel, Jaguar RISC, x86, 68k, PPC, TI DSP Systems: Apple2, Atari800XL, Atari ST, Amiga OCS, Vectrex, TI-99/4A, GB, GBA, DS, PS1, Ruputer, Dreamcast, GP2X, STIX, PC
  1. Added. makefastboot.zip
  2. Would you be willing to add my fastboot header for carts? I had it at JS2, but since that's down... It has just 2 blocks to decrypt instead of 10 so starts in 1 second instead of 5. I also had a tool to replace the boot header on any ROM image with it. (It was originally one block, but that's not compatible with the JagCD). Downside of it is that it doesn't verify the entire cartridge, but, neither does the common universal header, so I figured that might be okay.
  3. A Jaguar in a FPGA

    That's very cool
  4. Software reset?

    I was actually looking at this problem myself while playing with the GDB stub. At any rate, 2 won't even work for the 68k, because after MEMCON1 is written, there's no ROM at address 0 so no vector available (and it's unclear to me whether you can read the BIOS ROM again without changing MEMCON1 even if you get the right address...? It didn't look like it in the debugger (because it's 8 bits wide).) Solution 1 is curious, didn't know that one. (Of course as Zero mentioned, not useful here anyway.) Also worth noting that 3 doesn't reset the 68k, only the hardware attached to the 68k's reset line. Regarding the risk of writing the OPL from the 68k... I found the OP could lock up in some bad address cases, but I never had it happen just writing from the 68k, so I'm not sure if it only happens if it's allowed to scribble through memory for a longer time or if it's just really, really rare.
  5. Interupt timing with the PIT (68k)

    Are you sure you aren't just running into trouble with the speed of printing? I would first try measuring for a full second before output (or even just half a second), and see whether that makes any difference.
  6. Cartridge dumping tool

    The software would also have to switch out the CD BIOS in order to see the cartridge ROM, I believe. Otherwise you'll just get a dump of the CD BIOS. Though for one reason or another, hot swap doesn't seem safe on the Jag, but my experience was due to power issues. I wonder if it'd be different through the CD unit - especially whether it powers down its cartridge port when it's not mapped in?
  7. Linker behaviour (alignment bug)

    Just add -m to your linker flags, IIRC. (Check aln docs if that doesn't work). I think that only dumps it to the console, I seem to have captured the console output to file (with >) when I needed to review it. You could probably use a perl script to quickly break it into multiple lines, if you needed that, though.
  8. Linker behaviour (alignment bug)

    Have you tried generating a map file and looking at where your objects and data structures are actually being placed, just to be sure?
  9. Skunkboards are behind due to parts issues, but we have a promised delivery date for them. GOAT should be updating on that shortly - please don't quote me on it, but I figured since you are making long term plans you should know. As for the friendliness, you can definately find it, but just be aware that the Jag community tends to sometimes be a little cliquish and volatile. Just stay honest and keep a thick skin, and it can work pretty well for you! I've been fortunate enough to avoid most of the messes over the years. I hope you'll stick around and have fun with it - the Jag is an unusual machine but it can be quite rewarding.
  10. If you have any skill with a soldering iron, you could install a BJL ROM and build a cable to do uploads to the real Jag. Doing this will not prevent the Skunkboard from working when it's released, and gets you going on hardware quicker. (You do have to be willing to open the Jag and solder into it, as well as burn or beg an EPROM and cut a trace on the existing ROM).
  11. BJL Source Code?

    Yeah. I found I do have source code to the '97 version, which covers at least the basics of 4 bit protocol. While changing the protocol to be more reliable is trivial, it's the fact that it's already established which makes it useful. So, no big deal. I dropped the project today (although I did get the switch working -- that part is also bizarre - sending 2 bits at a time starting with bit 1 (instead of bit 0)). I just moved on and picked up an old XP PC for my needs.
  12. BJL Source Code?

    Made some progress last night. My original theory was that the protocol was not strictly synchronous as documented, but included undocumented timeouts. That seems to be confirmed, I can now get the Jag to switch into receiver mode. But it's still not taking the program properly. Unfortunately I don't have a working BJL setup or I would just sniff the lines to get the correct timing. Thanks for your reply at least, Zero. Seems like nobody understands the protocol. The more I learn about it, the less I like it. There's not much wrong with the cable (some electrical glitching the way they did it, at least on my Jag, but not critical), but the implementation feels quite arbitrary (at least by looking at the client source code). Due to the fact that the protocol seems not to be truly synchronous, my USB->BJL chain can not work.. latency on the PC and the USB bus is always going to kill it. I verified this experimentally by moving the handshake fully to the uC, only once it was there and the timing was tuned way down did the Jag start switching into receiver mode.
  13. BJL Source Code?

    That's just the version that I burned into my Jag years ago. I have a working serial->parallel adapter (which I then use through USB->serial), but it's not working against BJL (which is what I made it for), and the signals from the Jaguar are NOT responding in the way that the documentation says that they should. I wanted to look at the code and see why that is, and then maybe I can make some special cases for it. Since parallel ports are becoming very rare, this seemed like a good thing. But if the author isn't going to allow people to work with the protocol, maybe it's better to let it die and use something else.
  14. BJL Source Code?

    Anyone have the actual source for the BJL ROM version (specifically 1.05.01 on mine). I have a couple of loose source codes but they look incomplete and don't match the behaviour I am seeing. Specifically I am seeing the Jaguar pulsing the busy line when I hold strobe low, rather than waiting for me to release Strobe. I want to see if that is in the software or if there is something else going on. Unfortunately I don't have a parallel port anymore so I can't compare to a real BJL setup. But if someone has one and an analyzer, I would also appreciate a sniff of the initial handshake and a byte or two so I can see what should be going on. My adapter is not giving me the results that I expect to see. Thanks!
  15. Happy Birthday

    Hehe, I knew I better pop in today, because somehow you guys always remember, even if all I've done in the year is been grumpy. Thank you! I like the pic, Zero
×