Comments for Coranac

Comment on LOL wordpress by EvallCantee

EvallCantee — Tue, 21 Oct 2008 02:28:11 +0000

Hello,
I am, Steven
there is a ton of stuff on here
look at my site:

http://Z3lKihTh3i.spaces.live.com/

Comment on NDS register overview by Romu

Romu — Sun, 19 Oct 2008 17:39:23 +0000

Hi there
thanks for the namings…
I was wondering, if i wanna send and receive data (I/O interface) from the Slot2, which registers are involved in the process?

thanks anyway

Romu

Comment on Working with bits and bitfields by Ged

Ged — Sun, 12 Oct 2008 18:27:26 +0000

Great article!

Comment on NDS register overview by elwing

elwing — Wed, 01 Oct 2008 13:54:09 +0000

I can’t imagine what visual effect you can make with a R/W vcount :)

Comment on tonc 1.4 official release by cearn

cearn — Tue, 30 Sep 2008 10:56:06 +0000

@ Ealdor: yeah, you’re right. It should be good now.

Comment on links by Good boy

Good boy — Tue, 23 Sep 2008 14:32:23 +0000

Anyway, you help me much.
I like your tonic.

Maybe I have still have a lot of question to ask you in the future. :)
Please don’t be annoyed with me for asking these questions which maybe you think so easy.

Comment on NDS register overview by mml

mml — Tue, 23 Sep 2008 11:34:36 +0000

BG_MAP_RAM and BG_TILE_RAM and friends also have the dubious quality of being memory address macros without a built in cast-to-pointer-type (cf BG_PALETTE, SPRITE_PALETTE and friends), so if you want to copy some data in there you’ve got to cast them yourself. Not a big drama but it looks a bit odd when the palette copy doesn’t need a cast, but then the tiles and map data copies do.

Comment on tonc 1.4 official release by Ealdor

Ealdor — Tue, 23 Sep 2008 09:31:16 +0000

Hi Cearn i got this error when i try to compile the example tmr_demo:

arm-eabi-gcc -MM -I../../tonclib/include -O2 -Wall -fno-strict-aliasing -mthumb- interwork -mthumb -c tmr_demo.c berk.c > tmr_demo.d arm-eabi-gcc -I../../tonclib/include -O2 -Wall -fno-strict-aliasing -mthumb-inte rwork -mthumb -c tmr_demo.c -o tmr_demo.o arm-eabi-gcc -I../../tonclib/include -O2 -Wall -fno-strict-aliasing -mthumb-inte rwork -mthumb -c berk.c -o berk.o berk.c:7: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token berk.c:226: warning: excess elements in struct initializer berk.c:226: warning: (near initialization for 'berkFont') berk.c:227: warning: excess elements in struct initializer berk.c:227: warning: (near initialization for 'berkFont') berk.c:227: error: expected '}' before numeric constant make: *** [berk.o] Error 1

At the file ‘berk.c’ i changed this things:

const u8 *widths;
const u8 *heights;

for this:

const unsigned char *widths;
const unsigned char *heights;

An you forgot a ‘,’ at the line 225 after the second ‘0′

After that all worked fine :).

Comment on links by cearn

cearn — Mon, 22 Sep 2008 17:06:18 +0000

To be honest, I’m not sure what -g does exactly for the object (and ELF) files, but it seems to do something. I do know what effect it has on the generated assembly: it adds .loc directives everywhere. These seem to carry the line number in the source code, presumably to be used for breakpoints. For more details you’ll have to go to the manual I’m afraid.

Comment on links by Good boy

Good boy — Sun, 21 Sep 2008 14:21:38 +0000

Thank Cearn very much! Your answer helps me so much!

But I still have one question. As you said, part of the extra information in the ELF file is debugger information, which could be helpful when running with gdb. I remember that the “-g” option of GCC on Linux platform can produce extra debugging information. What is the different between these two commands “gcc -g -o file file.c” and “gcc -o file file.c” in Linux OS? Does the ELF file contain more debugging information if you add “-g” option when you complie the source codes?

Thank you so much.