CartFlasher - Revision history

1BitFeverDreams at 17:33, 29 March 2025

2025-03-29T17:33:44Z

← Older revision		Revision as of 13:33, 29 March 2025
Line 1:		Line 1:
	==== Hardware and memory map for carts ====		=== Hardware and memory map for carts ===
	Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems.		Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems.

Line 8:		Line 8:
	The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.		The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.

	==== Behavior at bootup ====		=== Behavior at bootup ===
	Since an early February 2025 release of a micro-kernel version (classic MMU 6502 mode), DIP switch #1 (see [[DIP switches]]) can be involved to avoid a chicken-and-the-egg scenario.		Since an early February 2025 release of a micro-kernel version (classic MMU 6502 mode), DIP switch #1 (see [[DIP switches]]) can be involved to avoid a chicken-and-the-egg scenario.

Line 27:		Line 27:
	'''Important to note:''' you must use this DIP switch position in order to edit a previously written flash cartridge so that you can access the programs that do perform this operation. The only exception would be if the cartridge itself had been prepared with a boot loader program that includes a flash cartridge writing program.		'''Important to note:''' you must use this DIP switch position in order to edit a previously written flash cartridge so that you can access the programs that do perform this operation. The only exception would be if the cartridge itself had been prepared with a boot loader program that includes a flash cartridge writing program.

	===~~== Getting~~ software on a Flash cartridge =====		=== Tools for getting software on a Flash cartridge ===
	If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:		If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:

Line 51:		Line 51:

	Find instructions for usage, for building in linux or a pre-compiled executable for Windows here: https://github.com/rmsk2/pgz2flash		Find instructions for usage, for building in linux or a pre-compiled executable for Windows here: https://github.com/rmsk2/pgz2flash

			=== Step by step guide to get software on a Flash Cart ===

			# Download fcart.pgz from https://github.com/rmsk2/cartflash/releases
			# Download loader.bin from https://github.com/rmsk2/flashselect/releases
			# Use fcart.pgz to write loader.bin to block 0 of your cartridge
			# Optional: Download cartridge.bin from https://github.com/rmsk2/cartflash/releases and use fcart.pgz to write it to block 31 of your cartridge. Now the software to write on the cartridge is on the cartridge itself
			# Use pgz2flash https://github.com/rmsk2/pgz2flash/releases to convert all the PGZs files you want to KUPs and store them on the cartridge
			# Use your software without load times and without typing any commands. Simply insert the cartridge and turn on the machine.
			# Optional: If you want to type commands you can start all software on the cartridge by typing /progname in BASIC or simply progname in DOS and still have no load times

1BitFeverDreams: new tool, better formatted

2025-03-24T02:38:29Z

new tool, better formatted

@@ Line 1: / Line 1: @@
-Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.
+==== Hardware and memory map for carts ====
-When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (KUP, see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the cartridge. Or in other words if there is at least one KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:
+The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.
 * F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart
 * fcart: https://github.com/rmsk2/cartflash
-Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as a KUP which can be run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.
+Both do run on your Foenix machine.
-The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.
+Find instructions for usage, for building in linux or a pre-compiled executable for Windows here: https://github.com/rmsk2/pgz2flash

Mgr42 at 18:25, 10 January 2025

2025-01-10T18:25:14Z

← Older revision		Revision as of 14:25, 10 January 2025
Line 6:		Line 6:
	* fcart: https://github.com/rmsk2/cartflash		* fcart: https://github.com/rmsk2/cartflash

	Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as KUP which can run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.		Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as a KUP which can be run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.

	The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.		The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.

Mgr42: Cosmetics

2025-01-10T17:59:15Z

Cosmetics

← Older revision		Revision as of 13:59, 10 January 2025
Line 1:		Line 1:
	Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.		Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.

	When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (KUP, see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the cartridge. Or in other words if there is a KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:		When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (KUP, see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the cartridge. Or in other words if there is at least one KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:

	* F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart		* F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart
	* fcart https://github.com/rmsk2/cartflash		* fcart: https://github.com/rmsk2/cartflash

	Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as KUP which can run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.		Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as KUP which can run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.

	The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.		The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.

Mgr42: Add information on how to run the mentioned programs

2025-01-10T17:56:46Z

Add information on how to run the mentioned programs

← Older revision		Revision as of 13:56, 10 January 2025
Line 1:		Line 1:
	Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.		Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.

	When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical ~~system~~ configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the ~~flash expansion~~ cartridge. Or in other words if there is a KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose		When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (KUP, see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the cartridge. Or in other words if there is a KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose:

	* F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart		* F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart
	* fcart https://github.com/rmsk2/cartflash		* fcart https://github.com/rmsk2/cartflash

	Both do run on your Foenix machine. F256_FlashCart always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite.		Both do run on your Foenix machine. F256_FlashCart is written in BASIC and always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite. Additionally it can be built in three versions. First as a pgz file (see [[File Formats]]) which can be run py [[Pexec]], then as a KUP which expects to be run from on-board flash and finally as KUP which can run from the last block of the flash cartridge itself. This allows the cartridge to be self contained in such a way that no additional software is needed to store data on it.

	The 256K flash chip is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.		The 256K flash chip in the cartridge is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.

Mgr42: Add more information about the flash expansion cartridge

2025-01-10T16:49:52Z

Add more information about the flash expansion cartridge

← Older revision		Revision as of 12:49, 10 January 2025
Line 1:		Line 1:
	https://~~discord~~.com/~~channels~~/~~691915291721990194~~/~~1054250056703815680~~/~~1228540690691260416~~		Apart from the 256K RAM expansion cartridge there is also [https://c256foenix.com/product/flashcart256k/?v=5f02f0889301 256K flash expansion cartridge] for the F256 K/Jr. available from Foenix Retro Systems. This cartridge contains extra flash memory which can be used to store software and data in a non volatile fashion. The extra memory is visible at 24 bit address $100000. The MMU (see [[Memory Management]]) can map the 32 8K blocks on the cartridge as blocks $80 to $9F into the 64K base memory.

	~~Link~~ to the ~~project~~ on ~~github: https://github~~.~~com/Red-Fool/F256_FlashCart~~		When booting your Foenix the [[MicroKernel]] looks for a Kernel User Program (see [[File Formats]]) to start in the flash cartridge, in the on-board flash memory and (depending on the position of your [[DIP switches]]) also in the on-board RAM. In a typical system configuration on a system with a flash expansion cartridge the first memory region to be searched is the memory occupied by the flash expansion cartridge. Or in other words if there is a KUP in your flash cartridge the first one found will be started automatically after power on and after each reset. If you want to write data on your flash expansion cartridge then there are two programs which can be used for this purpose

	~~According to [~~https://~~discord~~.com/~~channels~~/~~691915291721990194~~/~~1225217740998971413 this info]~~ the flash chip in the ~~cartridge~~ is a [https://www.microchip.com/ Microchip]		* F256_FlashCart: https://github.com/Red-Fool/F256_FlashCart
	~~Sst39vf040~~. ~~The~~ data sheet ~~of this chip~~ can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The ~~cartFlasher program is not~~		* fcart https://github.com/rmsk2/cartflash
	~~understandable without this~~ data sheet ~~as commands which are to be sent~~ to the ~~chip have to be encoded as reads and writes to and from specific addresses~~
	~~in a specific sequence~~.		Both do run on your Foenix machine. F256_FlashCart always erases the whole flash chip before writing new data to it. fcart allows to incrementally write data to a flash cartridge by only erasing the flash blocks which it is told to overwrite.

			The 256K flash chip is a SST39LF/VF020 by [https://www.microchip.com/ Microchip]. Its data sheet can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The data sheet is necessary if one wants to understand what both of the programs linked above actually do. The flash cartridge is also compatible with the K2/JrJr.

91.17.29.58 at 18:40, 9 December 2024

2024-12-09T18:40:58Z

← Older revision		Revision as of 14:40, 9 December 2024
Line 5:		Line 5:
	According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a [https://www.microchip.com/ Microchip]		According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a [https://www.microchip.com/ Microchip]
	Sst39vf040. The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The cartFlasher program is not		Sst39vf040. The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The cartFlasher program is not
	understandable without this data sheet as commands which are to be sent to the chip ~~are~~ encoded as reads and writes to and from specific addresses		understandable without this data sheet as commands which are to be sent to the chip have to be encoded as reads and writes to and from specific addresses
	in a specific sequence.		in a specific sequence.

91.17.29.58 at 18:28, 9 December 2024

2024-12-09T18:28:40Z

← Older revision		Revision as of 14:28, 9 December 2024
Line 3:		Line 3:
	Link to the project on github: https://github.com/Red-Fool/F256_FlashCart		Link to the project on github: https://github.com/Red-Fool/F256_FlashCart

	According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a Sst39vf040.		According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a [https://www.microchip.com/ Microchip]
	The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The cartFlasher program is not		Sst39vf040. The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The cartFlasher program is not
	understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses		understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses
	in a specific sequence.		in a specific sequence.

91.17.29.58 at 18:20, 9 December 2024

2024-12-09T18:20:04Z

← Older revision		Revision as of 14:20, 9 December 2024
Line 4:		Line 4:

	According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a Sst39vf040.		According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a Sst39vf040.
	The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The ~~BASIC~~ program is not		The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The cartFlasher program is not
	understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses		understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses
	in a specific sequence.		in a specific sequence.

91.17.29.58 at 18:19, 9 December 2024

2024-12-09T18:19:00Z

← Older revision		Revision as of 14:19, 9 December 2024
Line 3:		Line 3:
	Link to the project on github: https://github.com/Red-Fool/F256_FlashCart		Link to the project on github: https://github.com/Red-Fool/F256_FlashCart

	According to [[https://discord.com/channels/691915291721990194/1225217740998971413 this info]] the flash chip in the cartridge is a Sst39vf040.		According to [https://discord.com/channels/691915291721990194/1225217740998971413 this info] the flash chip in the cartridge is a Sst39vf040.
	The data sheet of this chip can be found [[https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]]. The BASIC program is not		The data sheet of this chip can be found [https://ww1.microchip.com/downloads/en/DeviceDoc/20005023B.pdf here]. The BASIC program is not
	understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses		understandable without this data sheet as commands which are to be sent to the chip are encoded as reads and writes to and from specific addresses
	in a specific sequence.		in a specific sequence.