|
|
Post by basophilg on Apr 28, 2022 22:15:58 GMT -5
Hi everyone, I have recently bought an LGT Saber from a reseller and am having some issues with trying to update ProffieOS and adding soundfonts that don't seem to have a reasonable answer on any other forum. I should preface this post by saying the Saber works as intended out of the box. When connecting the Proffieboard to the PC the Proffie connects to the PC and the distorted sound of the current font plays which is great. However, from this point there are errors; - Windows will give constant error message prompts stating that "USB is not recognised and the device has malfunctioned" - The Proffieboard seems to stuck in a boot cycle with the above message prompt returning over and over, as well as the "unknown serial bus" disappearing and reappearing in the Device Manager - Attempted to reset the Proffie with the 'reset-boot' manoeuvre, but the "STM32 BOOTLOADER" does not appear no matter how many times or how varied the press in duration is for the hold and release. - By only pressing the reset button, the initial distorted font sound plays so I know that the buttons are being pressed I have used multiple cables, I have tried with and without the battery and I have confirmed my PC knows what a Proffieboard is by connecting one of my other LGT sabers with no issue in recognising it is a Proffie. Each time it enters the cycle as above with the disconnect, reconnect messages saying that the USB is not recognised. The saber has no issues with its functions once everything is back together I am aware of this page: github.com/profezzorn/ProffieOS/wiki/How-to-recover-from-a-bad-programmingSo I know this could be a bad board - just wondering if anyone has had similar experiences or any other ideas that I could try given that the board works out of box but cannot be reset Thanks guys |
|
|
|
Post by nosloppy on Apr 28, 2022 22:30:39 GMT -5
I have a silly question, but you are using the microUSB port ON THE BOARD, not the USB-C charging port they add, right?
I re-read your post and it says you've done other boards successfully so I assume correct USB port then.
Have you just plugged it in without the SD card in? The looping thing sounds like the board was programmed with Mass Storage turned on and the PC is unhappy trying to mount it.
Please be aware that the BOOT and RESET buttons on the board do not just get pressed at the same time.. I mean they can, but the key ingredient to manually entering bootloader is to apply power to the board while the BOOT button is held. The RESET button is just a power interrupt, the same as putting in a kill key or throwing a kill switch. So you need to release the reset button while the boot button is held. That's the trick. For all intent and purposes, and I do this often because it's easier for me, you can hold the boot button down, plug USB into the computer (therefore applying power) then release the BOOT button....never even touching RESET.
|
|
|
|
Post by basophilg on Apr 28, 2022 22:39:36 GMT -5
I have a silly question, but you are using the microUSB port ON THE BOARD, not the USB-C charging port they add, right? Definitely the microUSB on the board itself with multiple cables rated for data transfer. I have been able to use these same cables in the past with my other sabers to flash the board with Arduino - just this current board is giving me issues. Might also be worth mentioning that I have also made a copy of the SD card and have tried the initial steps above with a new SD card in case there were any compatibility issues with the pre-installed SD card. Swapping the SD cards have made no difference, the saber still functions as default with preinstalled fonts (with both the original and back up SD cards). |
|
|
|
Post by basophilg on Apr 28, 2022 22:48:21 GMT -5
I have a silly question, but you are using the microUSB port ON THE BOARD, not the USB-C charging port they add, right? I re-read your post and it says you've done other boards successfully so I assume correct USB port then. Have you just plugged it in without the SD card in? The looping thing sounds like the board was programmed with Mass Storage turned on and the PC is unhappy trying to mount it. Please be aware that the BOOT and RESET buttons on the board do not just get pressed at the same time.. I mean they can, but the key ingredient to manually entering bootloader is to apply power to the board while the BOOT button is held. The RESET button is just a power interrupt, the same as putting in a kill key or throwing a kill switch. So you need to release the reset button while the boot button is held. That's the trick. For all intent and purposes, and I do this often because it's easier for me, you can hold the boot button down, plug USB into the computer (therefore applying power) then release the BOOT button....never even touching RESET. Thanks again mate. I have been actively holding BOOT, pressing RESET, releasing RESET and then releasing BOOT, all with varied timings - but I do continue to get the same message through Windows. The Device Manager can only read it as "Unknown USB Device (Device Descriptor Request Failed)" and not as a Port while my other boards get read as "Proffieboard" as soon as they're connected. |
|
|
|
Post by nosloppy on Apr 28, 2022 22:48:25 GMT -5
I have a silly question, but you are using the microUSB port ON THE BOARD, not the USB-C charging port they add, right? Definitely the microUSB on the board itself with multiple cables rated for data transfer. I have been able to use these same cables in the past with my other sabers to flash the board with Arduino - just this current board is giving me issues. Might also be worth mentioning that I have also made a copy of the SD card and have tried the initial steps above with a new SD card in case there were any compatibility issues with the pre-installed SD card. Swapping the SD cards have made no difference, the saber still functions as default with preinstalled fonts (with both the original and back up SD cards). Ok but plug it into USB with no SD card inserted. It should say "Font directory not found, SD Card not found" You should then look for it under Arduino menu Tools>Port. If it's there, and you've selected it, you can open serial monitor and type RebootDFU instead of the button dance to put it in bootloader. Then check Zadig and see if the drivers are correct and reinstall if not. |
|
|
|
Post by basophilg on Apr 28, 2022 22:54:39 GMT -5
Definitely the microUSB on the board itself with multiple cables rated for data transfer. I have been able to use these same cables in the past with my other sabers to flash the board with Arduino - just this current board is giving me issues. Might also be worth mentioning that I have also made a copy of the SD card and have tried the initial steps above with a new SD card in case there were any compatibility issues with the pre-installed SD card. Swapping the SD cards have made no difference, the saber still functions as default with preinstalled fonts (with both the original and back up SD cards). Ok but plug it into USB with no SD card inserted. It should say "Font directory not found, SD Card not found" You should then look for it under Arduino menu Tools>Port. If it's there, and you've selected it, you can open serial monitor and type RebootDFU instead of the button dance to put it in bootloader. Then check Zadig and see if the drivers are correct and reinstall if not. I have that set up at the moment and do get the "Font directory not found, SD Card not found", but still receive the consistent "USB Device not Recognised. The last USB device you connected to this computer has malfunctioned and Windows does not recognise it". Which I feel is the problem that the PC can't recognise the board as a Proffie so it doesn't show in my Arduino Tools>Port like my other saber. |
|
|
|
Post by nosloppy on Apr 28, 2022 22:56:13 GMT -5
Ok but plug it into USB with no SD card inserted. It should say "Font directory not found, SD Card not found" You should then look for it under Arduino menu Tools>Port. If it's there, and you've selected it, you can open serial monitor and type RebootDFU instead of the button dance to put it in bootloader. Then check Zadig and see if the drivers are correct and reinstall if not. I have that set up at the moment and do get the "Font directory not found, SD Card not found", but still receive the consistent "USB Device not Recognised. The last USB device you connected to this computer has malfunctioned and Windows does not recognise it". Which I feel is the problem that the PC can't recognise the board as a Proffie so it doesn't show in my Arduino Tools>Port like my other saber. Right, but it should show up as STM32BOOTLOADER when you manually do the buttons right. Did you rerun Zadig and look for that under List All Devices? |
|
|
|
Post by basophilg on Apr 28, 2022 23:03:30 GMT -5
I have that set up at the moment and do get the "Font directory not found, SD Card not found", but still receive the consistent "USB Device not Recognised. The last USB device you connected to this computer has malfunctioned and Windows does not recognise it". Which I feel is the problem that the PC can't recognise the board as a Proffie so it doesn't show in my Arduino Tools>Port like my other saber. Right, but it should show up as STM32BOOTLOADER when you manually do the buttons right. Did you rerun Zadig and look for that under List All Devices? That's one of the primary issues - I can't get the board to show up as STM32BOOTLOADER with pressing the manual buttons currently. I attempted what you have mentioned earlier with using the USB as a power interrupt but still could not get it to load as a STM32. It seems to be that since Windows cannot recognise what kind of USB device the Proffieboard is, it won't show up as anything except "Unknown Device" |
|
|
|
Post by nosloppy on Apr 29, 2022 0:17:16 GMT -5
Right, but it should show up as STM32BOOTLOADER when you manually do the buttons right. Did you rerun Zadig and look for that under List All Devices? That's one of the primary issues - I can't get the board to show up as STM32BOOTLOADER with pressing the manual buttons currently. I attempted what you have mentioned earlier with using the USB as a power interrupt but still could not get it to load as a STM32. It seems to be that since Windows cannot recognise what kind of USB device the Proffieboard is, it won't show up as anything except "Unknown Device" Did you uninstall delete driver and reinstall, like this? |
|
|
|
Post by nosloppy on Apr 29, 2022 0:22:32 GMT -5
Actually that's when the composite device "Proffieboard" gets the wrong driver installed.
You would want remove device including delete driver for "Unknown Device"
|
|
|
|
Post by basophilg on Apr 29, 2022 3:10:10 GMT -5
Actually that's when the composite device "Proffieboard" gets the wrong driver installed. You would want remove device including delete driver for "Unknown Device" Yeah I had a look at that video too but unfortunately as you mentioned - its not so much a Proffieboard with the wrong driver, it's just an unknown device to the PC. I have tried to remove the unknown device multiple times and there have been multiple permutations that haven't seemed to work - Delete driver for unknown device and the device reconnects before I can remove it from the USB - Delete driver, disconnect device, wait a few minutes and reinsert but still unknown - Delete driver, disconnect device, turn off PC (as well as unplug PC), wait 5 mins, turn it all on and reconnect Proffie and get unknown device - Attempt the above steps on both USB 3.0 and 2.0 ports around the PC. I'm just curious if there is a way to override the PCs "unknown device" flag and allocate the drive as "Proffieboard" or even "STM32BOOTLOADER" Thanks for all your help though! It is appreciated |
|
|
|
Post by basophilg on Apr 29, 2022 21:24:29 GMT -5
So I have revisited this today - whenever plug the board in initially or I try and reset the board with the RESET + BOOT dance - I get the message that the "USB device is not recognised" and that the device has "Malfunctioned and Windows does not recognise it"
Could this be an issue if the initial manufacturer flashed the board from MacOS and now I am trying to flash the board from a PC?
It just seems strange to me that the PC won't recognise it at all and the board doesn't seem to reset with the RESET + BOOT issues even though something is happening that allows the PC to "reassess" there is an unknown device attached.
|
|
|
|
Post by nosloppy on Apr 29, 2022 22:33:02 GMT -5
So I have revisited this today - whenever plug the board in initially or I try and reset the board with the RESET + BOOT dance - I get the message that the "USB device is not recognised" and that the device has "Malfunctioned and Windows does not recognise it" Could this be an issue if the initial manufacturer flashed the board from MacOS and now I am trying to flash the board from a PC? It just seems strange to me that the PC won't recognise it at all and the board doesn't seem to reset with the RESET + BOOT issues even though something is happening that allows the PC to "reassess" there is an unknown device attached. Mac vs PC is irrelevant. Your dealing with the hardcoded onboard STM32BOOTLADER and that's all it should show up as. Did you simply try on another computer? |
|
|
|
Post by basophilg on Apr 30, 2022 1:15:31 GMT -5
So I have revisited this today - whenever plug the board in initially or I try and reset the board with the RESET + BOOT dance - I get the message that the "USB device is not recognised" and that the device has "Malfunctioned and Windows does not recognise it" Could this be an issue if the initial manufacturer flashed the board from MacOS and now I am trying to flash the board from a PC? It just seems strange to me that the PC won't recognise it at all and the board doesn't seem to reset with the RESET + BOOT issues even though something is happening that allows the PC to "reassess" there is an unknown device attached. Mac vs PC is irrelevant. Your dealing with the hardcoded onboard STM32BOOTLADER and that's all it should show up as. Did you simply try on another computer? I have and I get the same issue with Device Manager showing it only as an unknown USB Device - code 43. |
|
|
|
Post by basophilg on Apr 30, 2022 4:29:48 GMT -5
Just a thought I've had - unsure if it's a good idea/even possible.
Given that I can access the "Unknown USB Device (Device Descriptor Request Failed" properties through Device Manager - is it possible to directly install drivers though this and add the STM32BOOTLOADER directly onto the board so the PC can recognise it?
Posting my thoughts here because I can't find any issue like this on what appears to be a perfectly working board with no hot components.
|
|
|
|
Post by nosloppy on Apr 30, 2022 6:47:46 GMT -5
I don't think you can flash the board like that. profezzorn might have some additional ideas here but unfortunately I'm stumped. I'm not a Windows guy even. |
|
|
|
Post by basophilg on Apr 30, 2022 19:31:05 GMT -5
I don't think you can flash the board like that. profezzorn might have some additional ideas here but unfortunately I'm stumped. I'm not a Windows guy even. Thanks mate. Appreciate the effort to help me. I'm very stumped too. I don't really have any other strategies so hopefully someone can help me out. It's very frustrating. |
|
|
|
Post by profezzorn on May 2, 2022 0:22:55 GMT -5
I think this board is busted.
I do have one more thing you could try, but I don't expect it to yield a different result:
* Make sure the board has no power.
* hold BOOT
* insert USB
This should do the same thing as the BOOT+RESET, but bypasses the boot-loop stage, which could potentially make windows happier, although as I said, I don't think it will make any difference.
|
|
|
|
Post by basophilg on May 2, 2022 8:10:24 GMT -5
I think this board is busted. I do have one more thing you could try, but I don't expect it to yield a different result: * Make sure the board has no power. * hold BOOT * insert USB This should do the same thing as the BOOT+RESET, but bypasses the boot-loop stage, which could potentially make windows happier, although as I said, I don't think it will make any difference. Thanks mate - appreciate it. Unfortunately that didn't work for me either so I'll have to assume it is a bad board. |
|
|
|
Post by basophilg on May 2, 2022 17:26:46 GMT -5
Well, I can finalise this post unfortunately. I discussed with the seller and he asked me to take a video of the disconnect/reconnect issue I was having to submit it for a warranty claim and the microUSB port popped clean off the board. Luckily I was able to get it on video, but now it appears that since the beginning there may have been some loose connections from the microUSB to the board which is why it wasn't reading well. So unfortunately if anyone else is experiencing this issue - please try the above advice from nosloppy and profezzorn. If that still doesn't work, it is probably worth reaching out to the manufacturer for a warranty claim. Thanks everyone for the help. |
|
