Category:84PCE:OS Information - Revision history

MateoConLechuga at 17:45, 25 June 2017

2017-06-25T17:45:07Z

2017-06-25T17:44:51Z

2017-06-25T17:44:30Z

2017-06-25T17:44:15Z

2017-06-25T17:44:03Z

2016-03-06T07:45:28Z

2015-10-12T20:19:27Z

2015-08-13T20:27:06Z

2015-08-13T20:26:28Z

2015-08-05T22:22:01Z

Revised and clarified language

@@ Line 12: / Line 12: @@
 * The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself, or disable interrupts, you can't change MBASE to get a full 64 K of Z80 mode code and data in whatever location suits your program. (However, you can still simply place your Z80 mode code in 'safeRAM' locations in the first 64 K of RAM.)
 * The boot code interrupt handler also disables mixed-memory-mode, so you can't run code in Z80 mode without disabling interrupts or handling them yourself.
 [[Category:84PCE]]

← Older revision		Revision as of 17:44, 25 June 2017
Line 14:		Line 14:

	[[Category:84PCE]]		[[Category:84PCE]]
−	[[Category:83PCE]]	+	* [[:Category:83PCE:OS_Information\|TI-83 Premium CE OS information]]

← Older revision		Revision as of 17:44, 25 June 2017
Line 14:		Line 14:

	[[Category:84PCE]]		[[Category:84PCE]]
−	[[Category:83PCE~~:OS_Information\|TI-83 Premium CE OS information~~]]	+	[[Category:83PCE]]

← Older revision		Revision as of 17:44, 25 June 2017
Line 14:		Line 14:

	[[Category:84PCE]]		[[Category:84PCE]]
−	[[:Category:83PCE:OS_Information\|TI-83 Premium CE OS information]]	+	[[Category:83PCE:OS_Information\|TI-83 Premium CE OS information]]

← Older revision		Revision as of 17:44, 25 June 2017
Line 14:		Line 14:

	[[Category:84PCE]]		[[Category:84PCE]]
		+	[[:Category:83PCE:OS_Information\|TI-83 Premium CE OS information]]

@@ Line 8: / Line 8: @@
 * Because the eZ80 doesn't need paging, apps are no longer limited to being allocated in 16 K increments, and they contain a relocations table like TI-89 apps
 ** The app signing key is now 2048 bits
-** TI can now develop apps using C; and we can do programs.
+** TI can now develop apps using C; and we can do programs using the C Development SDK: https://github.com/CE-Programming/toolchain/releases
 * The interrupt handler now saves and restores IY, so you can use IY depending on what OS routines you want that may depend on IY.
 * The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself, or disable interrupts, you can't change MBASE to get a full 64 K of Z80 mode code and data in whatever location suits your program. (However, you can still simply place your Z80 mode code in 'safeRAM' locations in the first 64 K of RAM.)

← Older revision		Revision as of 20:19, 12 October 2015
Line 12:		Line 12:
	* The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself, or disable interrupts, you can't change MBASE to get a full 64 K of Z80 mode code and data in whatever location suits your program. (However, you can still simply place your Z80 mode code in 'safeRAM' locations in the first 64 K of RAM.)		* The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself, or disable interrupts, you can't change MBASE to get a full 64 K of Z80 mode code and data in whatever location suits your program. (However, you can still simply place your Z80 mode code in 'safeRAM' locations in the first 64 K of RAM.)
	* The boot code interrupt handler also disables mixed-memory-mode, so you can't run code in Z80 mode without disabling interrupts or handling them yourself.		* The boot code interrupt handler also disables mixed-memory-mode, so you can't run code in Z80 mode without disabling interrupts or handling them yourself.
		+
		+	[[Category:84PCE]]

@@ Line 10: / Line 10: @@
 ** TI can now develop apps using C
 * The interrupt handler now saves and restores IY, so you can use IY depending on what OS routines you want that may depend on IY.
-* The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself (which, you'll recall, you're not allowed to do), '''you can't change MBASE''' to get 64 K of Z80 mode code and data in whatever location suits your program. Unless you copy your intterupt and code to the empty safeRAM locations...
+* The boot code interrupt handler checks that MBASE is set to D0 before passing interrupt handling control to OS. If it's not D0, the boot code jumps to some kind of error handler that basically resets the calculator. So unless you're handing interrupts yourself, or disable interrupts, you can't change MBASE to get a full 64 K of Z80 mode code and data in whatever location suits your program. (However, you can still simply place your Z80 mode code in safe RAM locations in the first 64 K of RAM.)