Gladiator NXT is seen only in bootloader mode

[hiland]

Hello,

I hope to get help with some problems with VKB Gladiator NXT base.

Recently my VKB Gladiator NXT just stopped being recognized by windows or VKBDevCfg. I also have VKB Gladiator NXT EVO base with omni throttle stick, and if I swapp the Evo base to the Gladiator NXT stick - it works just fine. So I know the issue is with the base.

I tried to follows the recommended steps to reflash the firmware, but with actually regression in results.

At first I was able to enter the boot mode by pressing F1+F2+F3 before plugging in the usb cable. I flashed the firmware (_Gladiator_NXT_v2_19_9.vkb), but the device still wouldn't show in VKBDevCfg. Even more, now I can enter the boot mode only by shorting two boot pins. I also tried the oldest firmware I could find (_Gladiator_NXT_v2_05_5.vkb) with no improvement. Not sure what else to try/ check.

[Alex Oz]

Hello,
can you measure the voltage on the BOOT pins?

[hiland]

I'm getting 3.2V

[Alex Oz]

That's OK

Is the firmware process complete and error-free?

What firmware was used before 2_05_5?

[Alex Oz]

Also try this fw

_Gladiator_NXT_v2_19_F.zip

(80.35 KiB) Downloaded 5 times

Do the LEDs on the base or handle light up?

[hiland]

First I tried to flash v2_19_9, then v2_18_2 and v2_05_5. Every time the process was error free, with the only difference in Blocks number. I also tried now _v2_19_F, same thing - device isn't seen in VKBDevCfg in normal mode.
I see the blue LED light up during programming, but that's all I think

[Alex Oz]

So far it looks more like the controller considers the Boot pins to be permanently closed. I need time to do some tests on a live board.
Show a photo of your board (there were three types)

[hiland]

Thanks for your help! To be clear, I still need to shorten two boot pins in order for the device to appear in boot mode. Nothing happens if I just plug in the usb cable

[Alex Oz]

This changes the situation.
It makes sense to try cleaning the registry with USBDeview https://www.nirsoft.net/utils/usb_devices_view.html

PID 0x0200 - right NXT (single) 0x0201 - left

You can also download OTA firmware to check - it will have a different PID and the controller will be installed in the system again.

[hiland]

There were 4 entries with PID 0x0200, I cleared them. Nothing new (with the same VendorID) shows up after the firmware flash which I think makes sense because I also don't hear a USB connected sound unless I connect the board with boot pins shortened.

I also have PID 0x0915 and 0x0916, I guess that's from the Evo base?

[Alex Oz]

So, here we have it.

1. There are no physical problems on the boards - the bootloader starts.

2. There are no problems with flashing the firmware - verification takes place after flashing.
Also, if the firmware was not completely flashed, the bootloader would always start.

3. The firmware is flashed, but does not start. To fully confirm this, you need to measure the voltage of D+
(it should be about 3V). This line is pulled up during startup when trying to connect to USB:

[hiland]

Huh, on D+ and TX2 I get 0. On 5V line I get 5V, on 3.3 line I get 3.25V