Generally, executing in non-executable memory will cause a hardware reset. Anything else, like writing to Flash or protected ports while not in privileged mode, is just ignored without any kind of trap. There are no NMI sources on the 83+/84+(SE).

I assume you're using WikiTI for your hardware info? It's definitely indispensable: http://wikiti.brandonw.net/index.php?title=Category:83Plus:Ports:By_Address

On a side note, the 84+CE actually does trigger NMIs for traps, but at this point there's no easy way to develop an OS for it.

I'm proud to announce the first beta release of SPASM-ng! Alberthrocks forked SPASM (Spencer's Assembler) to make some bug fixes, and I forked his fork to add eZ80 support!

Now you can use the -E option to enable eZ80 mode, with all of the new instructions and opcode suffixes. It assembles in ADL (24-bit) mode by default, but you can change this behavior with the new .ASSUME directive. There are also new .DL and .LONG directives for defining 24-bit data. In addition, the assembler behaves just the same as it always has for z80 code when assembling without the -E option.

Hopefully this assembler will prove useful for the advent of the TI-84+CE. I know it's what I'll be using!

The Wii U gamepad now show ads. Sometimes, it will suddenly turn ON by itself (even with the console turned OFF) then show special offers/promotions on digital games...

Yeah, it's something they added with the Quick Start menu. It was opt-in, but it seems like practically everybody opted in without realizing it, heh. It can be disabled.

Quote from: JWinslow23 on September 01, 2014, 11:56:35 am

If any further clarification is needed, contact me. I'll try not to get everything backwards for you. (*crickets* Seriously, nothing? )

I liked it!

Quick question - is this case sensitive or insensitive?

On a related note, are we supposed to handle characters that aren't parentheses/brackets, and if so, do those also have to produce a palindrome?

For example, (b]o[b)

For TI-BASIC, does it matter if Done is displayed in one case and not the other? If not, then I have a 47-byte program. If so, then it's 48.

Quote from: chickendude on June 28, 2014, 10:20:41 pm

I think the "trick" here is that bit 7 will always be the opposite of the byte you're trying to write (here in b), so if bit 7 of b is 1, bit 7 of (hl) will be 0 (so XORing the two will always give you 1). If it's finished, then you'll get the same bit that's in b, so XORing them will give you 0 (so z will be set). I don't really know how all of it works, that's just what i got from calc84's message.

EDIT: And (hl) doesn't really return the value of (hl) but rather a status byte, so i think you could read from anywhere in flash (like "ld a,($4000) \ xor b") and it would return the same thing until the thing finishes. Also, if you just cp (hl) there's a chance that the status byte has the same value as the byte you're trying to write.

That is how i understood it, too.
2 cases :
1) writing complete, reading will return the effective byte at the address, therefore all bits will match between the write & the read.
2) writing incomplete, reading will return a status byte which bit 7 is the opposite of bit 7 of the byte you asked to write (ugly sentence, i know ).
The thing is, that if bit 7 of the status byte is "guaranteed" to be the opposite, then i don't see how there is a chance to have a match when comparing the 2 bytes.
I mean, comparing byte %1XXXXXXX and byte %0XXXXXXX can never set the zero flag, so why wasting some cycles with that slow BIT instruction ?

Sorry again to bother you with that guyz, but that's important, cause such code can be iterated a lot when writing to flash and highly deserves to be speed-optimized.

According to the documentation, due to some sort of timing/synchronization issue, the first time you get a match in bit 7, the rest of the data is not guaranteed to be correct (it says to read again to get the actual data). But really, the BIT instruction is indeed superfluous; I usually check the sign flag after the XOR instead of doing a BIT followed by checking the zero flag.

Edit: Oh yeah, you also asked what could cause a timeout. Well, I think it just happens if enough time passes without the write succeeding, due to some sort of hardware failure. This prevents it from ever getting stuck in an infinite wait loop.

Now I've uploaded Version 0.40! I've added the fourth scenario, and I believe this means I'm a little over halfway done.

Prepare for MayQueen+Nyan²:


Also, as a PSA, the original Steins;Gate visual novel is now out in English for PC! More information is available at http://steins-gate.us/.

The limited edition is out of stock, but the download edition is available now for $39.95. Alternatively, the standard package edition is coming out within the next couple of weeks, and Rightstuf seems to have the best deal on it at $31.96. Also, the publisher is hoping to eventually publish the game on Steam; negotiations for that are in progress with the Japanese developers currently.

I got the Limited Edition about a month ago, and I can highly recommend it! It's a wild ride, and one of the best time travel adventures I've ever encountered. I've clocked in over 40 hours on it, and I still haven't reached all of the endings. I want this game to sell as well as possible so we can get more localized Science Adventures.

Hi guys! I just installed ndless and nover for my calculator (OS 3.6) and i'm trying to get gpsp and gbc on it, but when i click on the files, it just says that the document format is not supported. Help would be greatly appreciated! 

If that's happening, you may have to reinstall. Ndless on OS 3.6 doesn't stay installed when the calculator fully powers off, I think.