We found that the parameter not saving issue was caused by a bug in firmware version -045 and -046. Firmwares earlier did not have the problem. Users can re-flash version -040 to fix it. There is no performance difference among all -04x firmwares.
Our apologies for the mistake!
New kits - 13803/4K - F/W .050
Re: New kits - 13803/4K - F/W .050
Is that issue fixed in 050?
Re: New kits - 13803/4K - F/W .050
I hope it was fixed in 050 as I already purchased one!
I also hope since they know there is a problem in the early firmware, that they issue out o46 with the modification mentioned resolved in the firmware! Is there a list of what the changes have been for each of the updates? I have 045 and don't want to backdate considering something was updated!
JYE- can you respond to our concerns?
I also hope since they know there is a problem in the early firmware, that they issue out o46 with the modification mentioned resolved in the firmware! Is there a list of what the changes have been for each of the updates? I have 045 and don't want to backdate considering something was updated!
JYE- can you respond to our concerns?
Re: New kits - 13803/4K - F/W .050
-050 does not have the problem.
The following are short explanations of the firmware differences.
-041 ---- Added support to TFT controller ILI9325/9328 (-040 and earlier support ILI9341 only). LED will keep blinking if valid TFT controller can not be detected. As a result, VGEN will be disabled in this case.
-045 ---- Internal change to work with new test fixture that can automatically detect shorts/opens on all U1 port pins.
-046 ---- Enable VGEN even when TFT controller is not detected.
The following are short explanations of the firmware differences.
-041 ---- Added support to TFT controller ILI9325/9328 (-040 and earlier support ILI9341 only). LED will keep blinking if valid TFT controller can not be detected. As a result, VGEN will be disabled in this case.
-045 ---- Internal change to work with new test fixture that can automatically detect shorts/opens on all U1 port pins.
-046 ---- Enable VGEN even when TFT controller is not detected.
Re: New kits - 13803/4K - F/W .050
Thank you for responding.
Re: New kits - 13803/4K - F/W .050
JYE1
Is it possible that you might consider fixing the issue with firmware 046 and issue it as an updated firmware so we could at least update our older versions of the dso138?
Thanks again for your efforts to give us a good learning tool.
Don
Is it possible that you might consider fixing the issue with firmware 046 and issue it as an updated firmware so we could at least update our older versions of the dso138?
Thanks again for your efforts to give us a good learning tool.
Don
Re: New kits - 13803/4K - F/W .050
Exactly. Let's say 046a and everybody will be "almost" happy.
JYE1
Is it possible that you might consider fixing the issue with firmware 046 and issue it as an updated firmware so we could at least update our older versions of the dso138?
Thanks again for your efforts to give us a good learning tool.
Don
-
- Posts: 11
- Joined: Sat Apr 25, 2015 8:06 pm
Re: New kits - 13803/4K - F/W .050
Is this topic still active? I posted a question on a different forum section (DSO138 firmwareupdate) and have not received any reply...
Hello.... anybody there?
Hello.... anybody there?
Re: New kits - 13803/4K - F/W .050
They answer on occasion. I have asked several questions and the company only answered the one about selling the second board. I even asked about getting the board with a screen, they never responded to the question but did then offer to sell the kit with a screen!
Re: New kits - 13803/4K - F/W .050
For -046 version please re-flash with version -040. It has the same performance without the bug.
We are sorry for not being able to answer every question. Sometimes this is because it has been answered by other posts. Sometimes it is because we simply do not have enough time to address each question. But we will continue the effort to answer as much questions as we can.
We are sorry for not being able to answer every question. Sometimes this is because it has been answered by other posts. Sometimes it is because we simply do not have enough time to address each question. But we will continue the effort to answer as much questions as we can.