SpritesMind.Net

Is it possible to generate 68k interrupts by driving any cartridge line? Which line/lines?

Having a quick look here, it looks like you can interrupt the Z80, but not the 68k...

I'm now using m68k-elf-gcc, sdcc, zasm and sjasm built using ArchLinux recipes, but I still find this project very useful for building SGDK and the remaining tools.

Keep up the good work!

Also did you build SGDK (and your program) with debug information? It doesn't look like, but could your problem be related to the first I had about not being able to single step through SGDK functions?

It would be nice having a separate window that lets you watch an entire background (or several backgrounds with enable/disable buttons). But if this is too much trouble to implement, just adding some shortcuts to enable/disable backgrounds (A, B, Window) and also the sprite layer would do the trick....

Great news you continue improving BlastEm!

Are you planning to, at some point, add capabilities to display VRAM tiles, backgrounds and sprites?

@Stef: Yes, I built GDB for Linux. I can't recall the version exactly, but I think it was the latest (7.7), and it built nicely on 64-bit ArchLinux. I didn't have the problem you mention about single stepping getting you into VInt code. But I also had problems clearing breakpoints. Unfortunately I h...

I have no access to my files right now, but IIRC, I'm not directly building the assembly files with as, but with gcc instead. Also I think I'm only passing -m68000 to it right now, but I have to verify it. Gotta try repeating your test (moving the VINT handler to a separate file) when I get some spa...

I have tried modifying an assembly file, using the default syntax with the '%' to name registers. Then I built it without using the --register-prefix-optional switch and tried to debug the file. Result: FAIL. I still get the same error ("No source file named <asm_file>."), but the file is there for ...

Of course the .s files are present and readable at the path specified by GDB (that was the first thing I checked).

I'll try generating the SGDK library again, compiling with -g to test if adding debug info helps.

Thanks!

I have built m68k-elf-gdb and I have integrated it with Code::Blocks IDE. It works with BlastEm!, but I have some problems.

I have opened a new thread to deal with these problems here.

I have started experimenting with the debugging capabilities of the promising BlastEm! (Many thanks Mask of Destiny!). As I'm not a CLI debugging fan, I have integrated GDB with Code::Blocks IDE, for easy breakpoint and watches management. It somehow works: I can set breakpoints, step through code a...

Thanks for the quick reply. I hope I can get some time to try setting up the debugger!

Hum... that might be the problem, I can't remember if I added the load resistors, thanks a lot for the info!

Unfortunately I don't know when I'll be able to resume this project, I'm extra busy lately (gotta finish writing my Ph.D. once and for all!).

I'm trying to build v0.2.0 (6b7a96d0eda8) under 64-bit ArchLinux without success. It spits this error at first: stateview.c: In function 'main': stateview.c:89:2: error: too few arguments to function 'render_init' render_init(width, height, "GST State Viewer", 60, 0); ^ In file included from statevi...

Great news!!!

I NEED to get some time to test this, GDB support is something I've been awaiting for a long time. Too bad I'm extremely busy ATM.