Troubleshooting - Revision history

WF: /* FNX4N4S issues */

2026-08-16T10:04:29Z

FNX4N4S issues

← Older revision		Revision as of 06:04, 16 August 2026
Line 8:		Line 8:

	* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''		* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''
	* After the first batch of these in 2023, the cable changed to use a different wire color mapping, but were still wired by the same colors inside the FNX4N4S case. If you have a newer unit that matches the original wire color arrangement below, rewire them to match the later one.		* After the first batch of these in 2023, the cable changed to use a different wire color mapping, but were still wired by the same colors inside the FNX4N4S case. If you have a newer unit that matches the original wire color arrangement below, you might need to rewire them to match the later one. Continuity check the DIN9 vs CN1 connections to be sure.

	{\| class="wikitable"		{\| class="wikitable"

WF: /* FNX4N4S issues */

2026-08-16T06:48:12Z

FNX4N4S issues

← Older revision		Revision as of 02:48, 16 August 2026
Line 8:		Line 8:

	* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''		* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''
	* After the first batch of these in 2023, the ~~cabling~~ changed ~~and~~ the ~~differing wire~~ colors ~~induced some errors in the wiring~~ inside the FNX4N4S case. ~~The solution is~~ to ~~follow @Cibee's work and make sure you tie these 2 sets of pins~~ the ~~right way:~~		* After the first batch of these in 2023, the cable changed to use a different wire color mapping, but were still wired by the same colors inside the FNX4N4S case. If you have a newer unit that matches the original wire color arrangement below, rewire them to match the later one.

	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+@Cibee's wiring solution
	!FNX4N4S pins inside,		!FNX4N4S pins inside,
	marked CN1		marked CN1

WF: /* FNX4N4S issues */

2026-08-16T04:25:49Z

FNX4N4S issues

← Older revision		Revision as of 00:25, 16 August 2026
Line 18:		Line 18:
	!original 2023 run wire colors		!original 2023 run wire colors
	!latest 2024-5 run wire colors		!latest 2024-5 run wire colors
	~~!Changed?~~
	\|-		\|-
	\|1		\|1
Line 24:		Line 23:
	\|blue		\|blue
	\|blue		\|blue
	\|
	\|-		\|-
	\|2		\|2
Line 30:		Line 28:
	\|red		\|red
	\|red		\|red
	\|
	\|-		\|-
	\|3		\|3
	\|2		\|2
	\|white		\|'''white'''
	\|green		\|'''green'''
	\|X
	\|-		\|-
	\|4		\|4
Line 42:		Line 38:
	\|brown		\|brown
	\|brown		\|brown
	\|
	\|-		\|-
	\|5		\|5
	\|3		\|3
	\|green		\|'''green'''
	\|orange		\|'''orange'''
	\|X
	\|-		\|-
	\|6		\|6
Line 54:		Line 48:
	\|purple		\|purple
	\|purple		\|purple
	\|
	\|-		\|-
	\|7		\|7
	\|4		\|4
	\|orange		\|'''orange'''
	\|yellow		\|'''yellow'''
	\|X
	\|-		\|-
	\|8		\|8
Line 66:		Line 58:
	\|black		\|black
	\|black		\|black
	\|
	\|-		\|-
	\|9		\|9
	\|5		\|5
	\|yellow		\|'''yellow'''
	\|white		\|'''white'''
	\|X
	\|}		\|}
	[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]		[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]
	[[File:Fnx4n4s realcable.png\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]		[[File:Fnx4n4s realcable.png\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]
	*		*

WF: /* FNX4N4S issues */

2026-08-16T04:24:11Z

FNX4N4S issues

← Older revision		Revision as of 00:24, 16 August 2026
Line 34:		Line 34:
	\|3		\|3
	\|2		\|2
	\|white *		\|white
	\|green		\|green
	\|X		\|X
Line 46:		Line 46:
	\|5		\|5
	\|3		\|3
	\|green *		\|green
	\|orange *		\|orange
	\|X		\|X
	\|-		\|-
Line 58:		Line 58:
	\|7		\|7
	\|4		\|4
	\|orange *		\|orange
	\|yellow *		\|yellow
	\|X		\|X
	\|-		\|-

WF: /* FNX4N4S issues */

2026-08-16T04:23:50Z

FNX4N4S issues

← Older revision		Revision as of 00:23, 16 August 2026
Line 18:		Line 18:
	!original 2023 run wire colors		!original 2023 run wire colors
	!latest 2024-5 run wire colors		!latest 2024-5 run wire colors
			!Changed?
	\|-		\|-
	\|1		\|1
Line 23:		Line 24:
	\|blue		\|blue
	\|blue		\|blue
			\|
	\|-		\|-
	\|2		\|2
Line 28:		Line 30:
	\|red		\|red
	\|red		\|red
			\|
	\|-		\|-
	\|3		\|3
	\|2		\|2
	\|white		\|white *
	\|green		\|green
			\|X
	\|-		\|-
	\|4		\|4
Line 38:		Line 42:
	\|brown		\|brown
	\|brown		\|brown
			\|
	\|-		\|-
	\|5		\|5
	\|3		\|3
	\|green		\|green *
	\|orange		\|orange *
			\|X
	\|-		\|-
	\|6		\|6
Line 48:		Line 54:
	\|purple		\|purple
	\|purple		\|purple
			\|
	\|-		\|-
	\|7		\|7
	\|4		\|4
	\|orange		\|orange *
	\|yellow		\|yellow *
			\|X
	\|-		\|-
	\|8		\|8
Line 58:		Line 66:
	\|black		\|black
	\|black		\|black
			\|
	\|-		\|-
	\|9		\|9
	\|5		\|5
	\|yellow		\|yellow
	\|white		\|white
			\|X
	\|}		\|}
	[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]		[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]
	[[File:Fnx4n4s realcable.png\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]		[[File:Fnx4n4s realcable.png\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]
	*		*

1BitFeverDreams at 20:22, 1 February 2026

2026-02-01T20:22:18Z

← Older revision		Revision as of 16:22, 1 February 2026
Line 1:		Line 1:
			== TroubleShooting ==

	=== General issues ===		=== General issues ===
	* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''[[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]		* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''[[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]
	* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.		* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.

	==== FNX4N4S issues ====		=== FNX4N4S issues ===

	* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''		* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''

1BitFeverDreams: fixed DIN9 image

2026-02-01T20:19:35Z

fixed DIN9 image

← Older revision		Revision as of 16:19, 1 February 2026
Line 63:		Line 63:
	\|}		\|}
	[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]		[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]
	[[File:Fnx4n4s ~~cable~~.~~jpg~~\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]		[[File:Fnx4n4s realcable.png\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]

	*		*

1BitFeverDreams: FNX4N4S issue added, work by Cibee and Aleskey

2026-02-01T20:16:22Z

FNX4N4S issue added, work by Cibee and Aleskey

← Older revision		Revision as of 16:16, 1 February 2026
Line 1:		Line 1:
			=== General issues ===
	* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''[[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]		* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''[[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]
	* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.		* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.

			==== FNX4N4S issues ====

			* '''Can't seem to make the gamepad work reliably, or one button press affects multiple buttons and triggers at once'''
			* After the first batch of these in 2023, the cabling changed and the differing wire colors induced some errors in the wiring inside the FNX4N4S case. The solution is to follow @Cibee's work and make sure you tie these 2 sets of pins the right way:

			{\| class="wikitable"
			\|+
			!FNX4N4S pins inside,
			marked CN1
			!DIN9 pins outside the cable,
			while facing the pins
			!original 2023 run wire colors
			!latest 2024-5 run wire colors
			\|-
			\|1
			\|1
			\|blue
			\|blue
			\|-
			\|2
			\|6
			\|red
			\|red
			\|-
			\|3
			\|2
			\|white
			\|green
			\|-
			\|4
			\|7
			\|brown
			\|brown
			\|-
			\|5
			\|3
			\|green
			\|orange
			\|-
			\|6
			\|8
			\|purple
			\|purple
			\|-
			\|7
			\|4
			\|orange
			\|yellow
			\|-
			\|8
			\|9
			\|black
			\|black
			\|-
			\|9
			\|5
			\|yellow
			\|white
			\|}
			[[File:Fnx4n4s inside.png\|thumb\|Inside the FNX4N4S adapter box with the top cover removed. CN1 is where the cable is soldered directly on the PCB.]]
			[[File:Fnx4n4s cable.jpg\|thumb\|Facing the pins of the DIN9 cable of the FNX4N4S adapter box, from the outside.]]

			*

1BitFeverDreams at 12:37, 14 June 2024

2024-06-14T12:37:47Z

← Older revision		Revision as of 08:37, 14 June 2024
Line 1:		Line 1:
	* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''		* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''[[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]
	* [[File:Microkernel boot screen.png\|thumb\|Microkernel boot screen]]
	* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.		* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.

1BitFeverDreams: Created page with "* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?''' * Microkernel boot screen * Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the r..."

2024-06-14T12:37:35Z

Created page with "* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?''' * thumb|Microkernel boot screen * Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the r..."

New page

* '''Sometimes, when turning on the F256K/Jr, I get greeted with this screen, from which nothing can happen. How do you resolve this and why does this happen?'''
* [[File:Microkernel boot screen.png|thumb|Microkernel boot screen]]
* Every time you are powering off and on your unit, the FPGA needs to reprogram itself and that takes time (i.e. Not Instantaneous). It's possible to have faulty loading because the power supply is not quite stable; the RTC that generates the reset is not aligned with the rest of the system. If you are doing a quick on and off, the capacitors are not empty enough to create a rising power rail so the reset can do its things. Unfortunately those are not ASICs, so nothing is instantaneous.