# 1.202 Update Problem on QA403 **URL:** \ **Category:** Uncategorized\ **Created:** [December 13, 2024, 5:01am UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645 "2024-12-13T05:01:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ScottRichardson](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.quantasylum.com/scottrichardson/32/1423_2.png) [@ScottRichardson](https://forum.quantasylum.com/u/ScottRichardson)\ **Post date:** [December 13, 2024, 5:01am UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/1 "2024-12-13T05:01:51Z")
I am trying to update my QA403 to version 1.202. I downloaded the software package and installed it, but, when I try to open it, it says I need to update the firmware. I tell it to do so, but then I get the message: “An exception was caught. Was the HW in IPS mode? One or more errors occurred.” (I have absolutely no idea what his means because I’m not a computer engineer or programmer). I then click “OK” and it says: “Finished updating the flash. Please unplug the hardware, wait one second and then re-plug the hardware.” I then quickly follow the instructions and unplug the QA403 from the USB hub and plug it back in. When I do this, the Link and Atten lights come one and it loops back to the first message that the firmware must be updated. The Link and Atten lights stay on. I can’t get past this. HELP! ---
**Author:** ![Claudio](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@Claudio](https://forum.quantasylum.com/u/Claudio)\ **Post date:** [December 13, 2024, 4:20pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/2 "2024-12-13T16:20:35Z")
Hi @ScottRichardson. This may be of no use, but have you tried looking at these posts? > [@Fail Firmware update](https://forum.quantasylum.com/t/fail-firmware-update/561/8): > > I tried to update to 1.142 from 1.132 on a QA403 and it gives me a fail see picture [qaprobl] Any ideas ? ---
**Author:** ![ScottRichardson](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.quantasylum.com/scottrichardson/32/1423_2.png) [@ScottRichardson](https://forum.quantasylum.com/u/ScottRichardson)\ **Post date:** [December 13, 2024, 4:45pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/3 "2024-12-13T16:45:42Z")
Not really. I am not a software person; I’m a vacuum tube audio unit repair person and a point-and-click user of computers (Macintosh, although I use a PC only for the QA403). I don’t have a clue regarding programming, modes, coding, firmware, commands, etc. If I can get a set-by-step guide on how to fix this, I’ll be a happy camper. ---
**Author:** ![Claudio](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@Claudio](https://forum.quantasylum.com/u/Claudio)\ **Post date:** [December 13, 2024, 4:59pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/4 "2024-12-13T16:59:12Z")
Perhaps the to-do list in the following post is what you are looking for: > [@Fail Firmware update](https://forum.quantasylum.com/t/fail-firmware-update/561/6): > > Hi @jli, there are a few possibilities, and all should be recoverable without sending the unit back. The way the flash programming works on the QA402 and QA403 is as follows: When you need to re-flash an image, the QA40x application puts the hardware into an “ISP” mode, and the processor inside the QA40x attaches to your PC with the VID:PID of 0x1FC9:0x022. The QA40x app then opens the “new” device as a HID device, and an image is sent to the QA40x. You then power cycle and the new ima… ---
**Author:** ![ScottRichardson](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.quantasylum.com/scottrichardson/32/1423_2.png) [@ScottRichardson](https://forum.quantasylum.com/u/ScottRichardson)\ **Post date:** [December 13, 2024, 8:07pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/5 "2024-12-13T20:07:27Z")
It is assuming I am well-versed in programming and overall software usage, which I am not: 1. Try on a Win10 PC if possible. But if not, it’s worth a shot on Linux **[Understood. I’m using a Windows 11 PC]** 2. Unplug the QA403 hardware **[Understood]** 3. Start the QA40x application **[Understood]** 4. Once the app is up, click on the title bar of the app (to make sure it has focus) and type ‘QA40x’ (no quotes). You should hear a beep or similar. **[There is no place to type anything in the title bar]** 5. Notice there is a new menu called “DEBUG” just after the HELP menu **[I see the DEBUG menu]** 6. Plug in your QA40x hardware, and verify a device with VID:PID 0x1FC9: 0x0022 is connected to your machine via HW manager or lsusb, etc. **[I have no idea how to verify if “a device with VID:PID 0x1FC9: 0x0022 is connected.” I don’t know what the “HW Manager or lsusb” are]** 7. From the DEBUG menu, select `Load Default Secure Image (must in be HID mode)` **[I have no idea how to make sure it is in HID mode or even what that means]** 8. Get ready to watch the status at the bottom. It will go really fast and you might not see it. But it should reflash **[Understood]** 9. Unplug the QA40x, wait 2-3 second, and re-plug. It should be connected. The cycling front-panel LEDs indicate the flash was successful. **[Understood]** ---
**Author:** ![ScottRichardson](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.quantasylum.com/scottrichardson/32/1423_2.png) [@ScottRichardson](https://forum.quantasylum.com/u/ScottRichardson)\ **Post date:** [December 13, 2024, 8:12pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/6 "2024-12-13T20:12:07Z")
My computer flashed a message that there had been a problem updating Windows, so I told it to retry the update (must have happened in the past). The computer then restarted and now the version 1.202 seems to be working. ---
**Author:** ![Claudio](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@Claudio](https://forum.quantasylum.com/u/Claudio)\ **Post date:** [December 13, 2024, 9:19pm UTC](https://forum.quantasylum.com/t/1-202-update-problem-on-qa403/1645/7 "2024-12-13T21:19:20Z")
> [@ScottRichardson](#): > > The computer then restarted and now the version 1.202 seems to be working. If “QA40x v.1.202” appears in the pricipal window and the program works, then it’s probably okay!