June 29, 20242 yr 3 hours ago, naywinthu16 said: Sir. Could I know Upgrade instructions with Flash Thumb. it depends on your inverter and its display if it support USB OTG or not, instructions can be found in this post. Firmware Upload Instructions
June 30, 20242 yr 21 hours ago, Coulomb said: Done. Though I've never done one like this; is there anything else to add? It's my pleasure to pay back for your efforts and help! Nothing else to be added, you covered it perfectly. Try it yourself next time you get to reflash an inverter with a micro-USB port. 21 hours ago, Coulomb said: But then how does it know what reflash command and addresses to use for the DSP reflash? I can't think of a possibility other than it is hard coded in the reflash app, hence making it work for specific models only with the same DSP addresses. I will try flashing my inverter's DSP using the MCU reflash tool while sniffing the serial connection to see what will be going on. I'll try to do it in the next couple of days and post any updates here. Do you think it could overwrite the bootloader by any means?
June 30, 20242 yr 48 minutes ago, Tarek Yag said: Do you think it could overwrite the bootloader by any means? No, I can't see how.
June 30, 20242 yr 8 minutes ago, Coulomb said: No, I can't see how. In the unexpected case of overwriting the bootloader of my VM IV Twin inverter, is there any way to fix it without replacing hardware?
July 1, 20242 yr 11 hours ago, Tarek Yag said: In the unexpected case of overwriting the bootloader of my VM IV Twin inverter, is there any way to fix it without replacing hardware? You'd need a hex file for the bootloader; I don't have one. You'd also need a JTAG programmer for the C2000 family. Edited July 1, 20242 yr by Coulomb
July 14, 20242 yr @Coulomb, I just tried updating my VM IV DSP firmware using the MCU reflash tool and had the update file named "dsp.hex" as required by the tool. It seems like it started writing on MCU addresses as my round display went black while the DSP stayed working normally without any interruptions. So, now I believe: 1- File 'dsp.hex' must be present to enable the tool to work when clicking "Update DSP" button (so clicking it by mistake when trying to update MCU should do no harm) 2- Even if the DSP file is present, it will just brick the display without doing any real damage, because it keeps sending the MCU reflash command without actually writing to the memory (I sniffed the serial connection to see what was going on) 3- Reflashing the appropriate MCU file should get the display working again normally Edited July 14, 20242 yr by Tarek Yag
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.