Kernel & SuperBASIC Updates - Revision history

Agurtovoy: /* Kernel and/or SuperBASIC Releases */

2026-04-27T15:31:04Z

Kernel and/or SuperBASIC Releases

← Older revision		Revision as of 11:31, 27 April 2026
Line 3:		Line 3:
	Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published at https://github.com/wildbitscomputing/firmware.		Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published at https://github.com/wildbitscomputing/firmware.

	If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, ~~which~~ available from the corresponding Github repos:		If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, available from the corresponding Github repos:
	* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]		* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
	* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]		* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]

Agurtovoy: /* Kernel and/or SuperBASIC Releases */

2026-04-27T15:16:15Z

Kernel and/or SuperBASIC Releases

← Older revision		Revision as of 11:16, 27 April 2026
Line 1:		Line 1:
	== Kernel and/or SuperBASIC Releases ==		== Kernel and/or SuperBASIC Releases ==

	Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published ~~on [~~https://~~discord~~.gg/~~K63fav2qHc Discord]~~.		Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published at https://github.com/wildbitscomputing/firmware.

	If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:		If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:

Agurtovoy: /* Kernel and/or SuperBASIC Update Links */

2026-04-27T15:10:54Z

Kernel and/or SuperBASIC Update Links

← Older revision		Revision as of 11:10, 27 April 2026
Line 1:		Line 1:
	== Kernel and/or SuperBASIC ~~Update Links~~ ==		== Kernel and/or SuperBASIC Releases ==

	Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published on [https://discord.gg/K63fav2qHc Discord].		Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published on [https://discord.gg/K63fav2qHc Discord].

Agurtovoy: /* Kernel and/or SuperBASIC Update Links */

2026-04-27T15:10:00Z

Kernel and/or SuperBASIC Update Links

← Older revision		Revision as of 11:10, 27 April 2026
Line 1:		Line 1:
	== Kernel and/or SuperBASIC Update Links ==		== Kernel and/or SuperBASIC Update Links ==

	~~Most people will prefer to rely on curated, prepared firmware collection to flash the whole flash memory blocks all at once, using a community driven~~ firmware ~~release~~ that ~~will~~ routinely ~~also~~ improve ~~superbasic~~ and ~~the Micro~~-~~Kernal~~, ~~among other things~~. ~~This is what most people will prefer to use~~.		Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published on [https://discord.gg/K63fav2qHc Discord].

	~~Here is a complete package of both latest instances (Scripts & bulk.csv files included as well as the foenixmgr utilities to perform the flash), check the '''Releases''' page of the following link:~~		If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:
			* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
	~~[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]~~		* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]


	If~~, for some reason,~~ you ~~really~~ want to ~~modify certain parts of the firmware in flash~~, you could do so piecewise by replacing only the ~~superbasic~~ or only the ~~Micro-Kernel~~ flash blocks~~. For the vast majority of users~~, ~~this is NOT needed.~~

	~~Here are~~ the ~~GitHub Links where you will find the latest F256K / F256Jr Micro-Kernel load and/or SuperBASIC~~:

	[https://github.com/~~ghackwrench~~/~~F256_MicroKernel F256x Micro-Kernel Github Link~~]

	[https://github.com/~~paulscottrobson~~/superbasic/releases ~~F256x~~ SuperBASIC ~~Github Link~~]

	== USB Port ==		== USB Port ==

1BitFeverDreams: better instructions with gen2

2026-02-01T20:38:30Z

better instructions with gen2

← Older revision		Revision as of 16:38, 1 February 2026
Line 1:		Line 1:
	== Kernel and/or SuperBASIC Update Links ==		== Kernel and/or SuperBASIC Update Links ==

			Most people will prefer to rely on curated, prepared firmware collection to flash the whole flash memory blocks all at once, using a community driven firmware release that will routinely also improve superbasic and the Micro-Kernal, among other things. This is what most people will prefer to use.

			Here is a complete package of both latest instances (Scripts & bulk.csv files included as well as the foenixmgr utilities to perform the flash), check the '''Releases''' page of the following link:

			[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]


			If, for some reason, you really want to modify certain parts of the firmware in flash, you could do so piecewise by replacing only the superbasic or only the Micro-Kernel flash blocks. For the vast majority of users, this is NOT needed.

	Here are the GitHub Links where you will find the latest F256K / F256Jr Micro-Kernel load and/or SuperBASIC:		Here are the GitHub Links where you will find the latest F256K / F256Jr Micro-Kernel load and/or SuperBASIC:

Line 6:		Line 15:

	[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]		[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]

	~~Here is a complete package of both latest instances (Scripts & bulk.csv files included)~~

	~~[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]~~

	== USB Port ==		== USB Port ==
Line 18:		Line 23:

	=== F256K2 ===		=== F256K2 ===
	On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART.		On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART. This means that you only use a data supporting USB-C cable running from a modern computer to the back of the K2, no need for a specialty cable, nor a specialty adapter.

	Therefore, on a F256K2 you want to select the second COM port that gets added to your system. ~~On my~~ Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.		Therefore, on a F256K2 you want to select the second COM port that gets added to your system. As an example, on one Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

	=== Update batch file to point at correct port ===		=== Update batch file to point at correct port ===
Line 42:		Line 47:

	<youtube>Zgyhy_cBsM8</youtube>		<youtube>Zgyhy_cBsM8</youtube>

			==== How to Update your F256 Jr2 / F256K2 Video ====
			<youtube>pOab0ocKqac</youtube>
			Starting at 6:46, this video dives into updating the firmware for a specific core (each core have their pocket of 512K of flash memory, not shared).

Edwin: Clean up section on usb driver for gen1 and for both, how to select port.

2025-10-14T21:29:23Z

Clean up section on usb driver for gen1 and for both, how to select port.

← Older revision		Revision as of 17:29, 14 October 2025
Line 11:		Line 11:
	[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]		[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]

	== ~~Link to~~ USB ~~Driver for XR21B1411 (Not needed for F256K2)~~ ==		== USB Port ==
	XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
			=== F256 Jr. / F256K ===
			You will need to have the XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
	[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]		[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

	On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the ~~Rasberry~~ PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port and the ~~Third~~ one is the system UART.		=== F256K2 ===
			On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART.

	Therefore on a F256K2 you want to select the second COM port that gets added to your system. On my Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.		Therefore, on a F256K2 you want to select the second COM port that gets added to your system. On my Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

	To perform a full Kernel & ~~SuperVASIC~~ update, I simply downloaded the Complete Package (above), and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).		=== Update batch file to point at correct port ===
			To perform a full Kernel & SuperBASIC update, I simply downloaded the Complete Package (above) and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

	== Links to Software needed to do update with FoenixMgr (Python Script) ==		== Links to Software needed to do update with FoenixMgr (Python Script) ==

KoolKiwi: /* Updated for the differing COM Port instructions for updating the F256K2 */

2025-02-13T01:28:32Z

Updated for the differing COM Port instructions for updating the F256K2

← Older revision		Revision as of 21:28, 12 February 2025
Line 11:		Line 11:
	[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]		[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]

	== ~~Links~~ to ~~driver & softwares~~ needed ~~to do an update with the FoenixMgr (Python Script~~) ==		== Link to USB Driver for XR21B1411 (Not needed for F256K2) ==
	XR21B1411 USB Driver ~~(For~~ PC/Linux/ The MAC is outdated)		XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
	[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]		[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

			On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Rasberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port and the Third one is the system UART.

			Therefore on a F256K2 you want to select the second COM port that gets added to your system. On my Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

			To perform a full Kernel & SuperVASIC update, I simply downloaded the Complete Package (above), and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

			== Links to Software needed to do update with FoenixMgr (Python Script) ==
	Python		Python
	[https://www.python.org/]		[https://www.python.org/]

1BitFeverDreams: The MicroKernel link leads to an older page that tried to provide both the microkernel and DOS together. This is now deprecated as of Dec 28th 2023 as seen on the readme page of https://github.com/ghackwrench/F256_Jr_Kernel_DOS. the new repo for just the kernel is at: https://github.com/ghackwrench/F256_MicroKernel

2023-12-29T01:16:07Z

The MicroKernel link leads to an older page that tried to provide both the microkernel and DOS together. This is now deprecated as of Dec 28th 2023 as seen on the readme page of https://github.com/ghackwrench/F256_Jr_Kernel_DOS. the new repo for just the kernel is at: https://github.com/ghackwrench/F256_MicroKernel

← Older revision		Revision as of 21:16, 28 December 2023
Line 3:		Line 3:
	Here are the GitHub Links where you will find the latest F256K / F256Jr Micro-Kernel load and/or SuperBASIC:		Here are the GitHub Links where you will find the latest F256K / F256Jr Micro-Kernel load and/or SuperBASIC:

	[https://github.com/ghackwrench/~~F256_Jr_Kernel_DOS/tree/main/kernel~~ F256x Micro-Kernel Github Link]		[https://github.com/ghackwrench/F256_MicroKernel F256x Micro-Kernel Github Link]

	[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]		[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]

Foenix: /* Kernel and/or SuperBASIC Update Links */

2023-12-16T06:25:25Z

Kernel and/or SuperBASIC Update Links

← Older revision		Revision as of 02:25, 16 December 2023
Line 7:		Line 7:
	[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]		[https://github.com/paulscottrobson/superbasic/releases F256x SuperBASIC Github Link]

	Here is a complete package of both latest instances (~~Scipts~~ & bulk.csv files included)		Here is a complete package of both latest instances (Scripts & bulk.csv files included)

	[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]		[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]

Foenix: /* Kernel and/or SuperBASIC Update Links */

2023-12-16T06:25:10Z

Kernel and/or SuperBASIC Update Links

← Older revision		Revision as of 02:25, 16 December 2023
Line 9:		Line 9:
	Here is a complete package of both latest instances (Scipts & bulk.csv files included)		Here is a complete package of both latest instances (Scipts & bulk.csv files included)

	[https://github.com/FoenixRetro/f256-firmware]		[https://github.com/FoenixRetro/f256-firmware Complete Package Kernal+SuperBASIC+Apps Link]

	== Links to driver & softwares needed to do an update with the FoenixMgr (Python Script) ==		== Links to driver & softwares needed to do an update with the FoenixMgr (Python Script) ==