This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - calc84maniac
Pages: 1 ... 148 149 [150] 151 152 ... 197
2236
« on: April 01, 2010, 05:37:59 pm »
:{GDB1}+1->GDB1
:GDB1+1->GDB1
:GDB1+1->{GDB1} What would these three do? *Ztrumpet is curious... 
The first two are illegal because GDB1 is a constant pointer. The third one will add one to the constant and store it to {GDB1}
2237
« on: April 01, 2010, 11:26:55 am »
Tell me something.
Why can't anyone confirm the speed of the TI-Nspire processor?
The speed is changeable. The TI-Nspire OS generally runs at 90MHz, while the CPU is clockable to a maximum of 150MHz.
2238
« on: April 01, 2010, 11:25:17 am »
Hmm...
Are you able to do mathematical operations with hexadecimal?
The only thing that is hexadecimal about it is how you type it in. It's just a number.
2239
« on: April 01, 2010, 08:11:03 am »
Never mind, I wasn't paying much attention to what I was writing.
So, does it make that a 10 or a 0A?
EDIT:
Actually, it is:
:[09]->GDB1
:{GDB1}+1->GDB1 That shouldn't even be a legal operation...
2240
« on: April 01, 2010, 08:01:00 am »
Do you mean that when you do this:
:[09]->GDB1
:GDB+1->GDBGDB1 becomes a 10 and not a 0A?
No, it is actually: :[09]->GDB1
:{GDB1}+1->{GDB1}
2241
« on: March 30, 2010, 07:12:44 pm »
nice to hear!
First time I hear of "volatile unsigned", though. I heard about short signed/unsigned, long signed/unsigned, etc, but not that
Yeah, using "volatile" tells the compiler that it's not normal memory and it must always read/write when told to, rather than optimizing like for normal memory access. Edit: For example, with code while (*timer) { };that waits for a timer register to count down to zero, if "timer" is not specified as volatile, it will only be read once and the read value would be checked against z80 over and over. On the other hand, if it is volatile, it will actually read the register every loop.
2242
« on: March 30, 2010, 07:54:04 am »
Hmm, that is odd about the clock speed. I've never actually set it using C... maybe you need "volatile unsigned" since they are memory-mapped ports.
2243
« on: March 29, 2010, 11:46:28 am »
I think its a good idea, but how would it be smaller or faster?
Because the z80 is an 8-bit processor, and by nature doing 16-bit operations is slower and produces larger code.
2244
« on: March 28, 2010, 03:07:36 pm »
@Sir I meant the entire code actually, including Axe. I now understand what {A} does, though, after a talk with Quigibo. {A} == LA(1), {A+1} == LA(2), etc, or something similar. I don't get the lenght thing, though.
Length just means how big the appvar is. Make sure not to use data outside the appvar, or you might corrupt other things.
2245
« on: March 28, 2010, 02:55:50 pm »
2246
« on: March 27, 2010, 03:37:11 pm »
Good idea, I'll add the maximum distance code.
calc84: how do you change the CPU clock speed in C?
To set 150MHz, do this: *(unsigned*)0x900B0000 = 0x00000002;
*(unsigned*)0x900B000C = 4;To set 90MHz, do this: *(unsigned*)0x900B0000 = 0x00141002;
*(unsigned*)0x900B000C = 4;
2247
« on: March 27, 2010, 03:26:37 pm »
Here's the thing. I don't even check the "diagonal" keys at all. Checking up/down/left/right is enough.
2248
« on: March 25, 2010, 01:26:19 pm »
I actually got a Bad Address error today, when trying to unarchive Sam Heald's Mario, of all things. It gave a large memory leak, too. I had to manually create a new program, copy the data to it, and delete the old one. Calcsys is awesome that way 
2249
« on: March 25, 2010, 01:23:29 pm »
My guess is that each memory sector is 65536 bytes, right?
(such array would most likely be 76800 bytes large, unless I am wrong, right?)
I have no idea how the flash memory on the Nspire works, actually. Though, we are talking about RAM here, which isn't really in "sectors". And the array would actually be 38400 bytes, since there are 2 pixels per byte.
2250
« on: March 25, 2010, 08:05:21 am »
Would the array work if I made it 8 times smaller? Do you guys think its crashing because of lack of memory?
I am not sure exactly what method you are using. But trying to copy an extra-large array to the LCD ram would probably overflow to other sensitive memory.
Pages: 1 ... 148 149 [150] 151 152 ... 197
|
Show Posts