SpritesMind.Net

Thanks a lot for the links!

I don't like inline assembly too much. I rather prefer having a separate assembly file with C callable routines. I usually only use inline assembly for extremely simple routines that fit inside a C macro, and doesn't make sense wasting time calling them/returning.

I want to code some routines in 68k ASM using the GNU toolchain. I'm interested both in inline assembly and also in making "C" callable ASM routines. This is not the first time I do this, but this is the first time I do it with GCC and a 68000 CPU (previously I coded some "C" callable ASM routines f...

I got some more time to play with this and finally got it to work! Grabbed SGDK "windows only" makefile and started modifying it to work with GNU/Linux. At first, object files were built, but failed when linking: m68k-elf-gcc -n -T /opt/toolchains/gen/ldscripts/md.ld -nostdlib out/sega.o @out/cmd_ /...

The included Makefile is driving me nuts :? I'm trying to modify it. First I commented out the ARCHIVES variable. Now I want to know why each time I make the project, all the .o and .elf files are deleted just after the final dd that copies and pads the ROM. It's a complete mistery. The only rm in t...

I just copied the Makefile inside /opt/toolchains/gen/skeleton, and didn't modify a single line. Isn't this supposed to be the SGDK Makefile? I'm a bit confused. The linker step in the Makefile is exactly this one: %.elf: $(OBJS) $(BOOT_RESOURCES) $(CC) -o $@ $(LINKFLAGS) $(BOOT_RESOURCES) $(ARCHIVE...

I have just tried building the rotating cube sample, without success. It looks like the toolchain doesn't generate correct roms, dgen complains about "no valid ROM found", and it looks like the ROM header is not OK: $ cp -r /opt/toolchains/gen/skeleton/* ./ $ make m68k-elf-gcc -m68000 -Wall -O2 -c -...

Thanks for the info. Unfortunately, although I would like learning 68k asm (I already know asm for some architectures like 6502, some TI DSPs, and a tiny bit of ARM, and I really enjoy coding in ASM), I don't have the time required to properly do it .

I have just successfully built the toolchain on a 64 bit Arch distro using this script. Thanks @kubilus1 and @Chilly Willy. I had some problems because Arch uses texinfo version 5.1, and this version fails while building documentation from .texi files (I have suffered this problem also building e.g....

Genesis software manual?

Is that some kind of leaked document? Sounds interesting

Thanks a lot for the info. It's a pity the port isn't full duplex and has no Tx interrupt :( If I want to use controller port 1, then registers are 0xA1000F (TxData), 0xA10011 (RxData) and 0xA10013 (S-Ctrl), right? What's the pinout for TX and RX pins? Does it use standard DB-9 pinout (e.g. pins 2 a...

Nice hack!

I'm also interested on how to set up the MD ports to use them as UARTs. 2400 bps is a very low baud rate (that's around 4 bytes per frame), but can be enough for some simple input/output devices.

Great! Thanks a whole lot!

I was talking about this or this . They are 600 MIPS (really 600 MMACs) devices, with 32/64 kiB internal dual port RAM. The internal ROM is read only. It has the bootloader and some utilities (like a sine LUT). The bootloader is pretty flexible. It can boot from external memory (via parallel or SPI ...

TI DSPs are really easy to use. They can be coded using C/C++ and there are free libraries available to use their peripherals. You'll need to learn assembly language if you want to extract all the juice of the DSPs, but I suppose C is enough for most tasks. It would be useful to know an estimation a...