DSOQuadV2.6 RESOURCE(Update 2012/04/12)

APP(V2.32) sourcecode released:
SYS(V1.34) sourcecode released:
APP(V2.35) sourcecode released:
FPGA(V2.5) sourcecode released:

and , for some reason, the sourcecode git change
from:
github.com/Seeed-Studio/DSOQuad … SourceCode
to :
github.com/Seeed-Studio/DSOQuad_SourceCode

Is there new firmware? :blush:

Can we know what SYS1.34 and APP2.32 change to the previous version?

A change log would be usefull when upgrading Firmware so we know what to expect :slight_smile:

I can not upgrade on a Mac, if I boot the device in upgrade mode it continually resets itself so that disk is disappearing faster than I can copy to it. Is there another way, DFU-util or dfuse that I can use.

So I found a Windoze box and it is clear now what the problem is, and it should be simple to fix. Are you interested in fixing it or should I go off and do it myself? I hate seeing forked pools, but this is very annoying. We got the dfuse tool working for the previous mode, not I but others did that which gave us the ability to update from many different platforms. I am not excited by going backwards here.

The DSOQuad HWv2.6 need to upgrade the app/sys/FPGA as the way in the manual because of the BIOS that embeded in the STM32 when Quad was produced . So, DFU-util or dfuse can not be used unless you embeded the related BIOS to the STM32.
as on the Mac, it will be grateful for you sharing your experience that we really lacked .I expececd your detailed introduction

Please tell me what you need to know and I will write it up. On Linux or a Mac the upgrade disk disappears completely every time it checks for new files. (about every second or two) This interrupts copies, or truncates them, and umounts the drive about as fast as the OS can mount it. This makes it so that you can’t copy anything reliably. I even tried to write a script to detect the disk had reappears and then did an ordered copy of the files, but that failed as well. Windows seems to tolerate the disk disappearing for a moment, but Linux and Mac os treat it as if the drive was unplugged while active. So the experience on Windows is good, but it is unusable on Mac os or Linux, even from a program trying to interact with it.

Is this what you need or is it something else? I am willing to help, but it is hard to know what someone doesn’t know. If I were going to fix it, I would change the embedded code to wait for a button press before disconnecting to check for new/changed files. That way you could succeed on copying the files on, before the system sees the disk go away as it now does.

Hi

We just received our engineering sample today.
As suggested by the developers, we upgraded the APP to 2.33 and the other SYS f/w updates.

However, now the CALIBRATE button does not work.

Please advice.

you may need to pressed this button about 2s…

Thanks.
Was it faster in 2.32? I recalled that we only need to press it briefly before going into that mode.

yes , this is a little change .

When I attach 2.6 in “upgrade” mode on Linux I see that there are no partitions (just the disk) and it don’t mount, when I connect it to mac osx it ignores it and when I connect it on windows I cannot click on my computer any more as it is trying to mount the disk …

any ideas?

EDIT:
I finally managed to solve the problem, 2win machines were not working just like the linux and mac, third win machine worked with it without a problem … weird

Any idea on when the changes for 2.33 are going to be pushed out to the repository on github?

There is a topic already opened on that problem http://www.seeedstudio.com/forum/viewtopic.php?f=22&t=1934
but no solution for the moment.

I’ve added information on the wiki for upgrading firmware:
garden.seeedstudio.com/index.php … g_firmware

Feel free to make improvements. The process is very complicated and I tried to explain it as clearly as I could.

HugeMan;

You may want to edit your original post in this thread in 3 ways

First, you may want to change your sentence about which software to use because it is too vague. You could list the latest file version number for V2.2 hardware, and also show the first file version numbers for V2.6 hardware. For example, only use verAA or lower for hardware v2.2 and only use verBB and above for hardware v2.6.

Second, explain front end compensation is different from the 10x probe compensation, and that these are both different from Quad calibration (input range scale calibration).

Third, you may want to post only attachments of the most current versions of all files here, and remove obsolete versions to reduce confusion.

The filename for the probe compensation attachment should probably be renamed to “front-end compensation and 10x probe compensation.zip” (or words to that effect) for better clarity.

This is just a suggestion on my part. Keep up the good work. :smiley:

What I don’t understand is why those informations are not put on the garden.
As stated on the home page of the garden it is a place where to find “A collection of product info pages” and “Includes datasheet, source files, application notes and related application info”

On the product page there is a version tracker (with no information at the moment) no link to any source file or binary file. As we already ask when we download a new version we have no idea of what this version try to correct or add.

Hi,

I updated to the latest version, and found a few errors in ‘DSOQuadV2.6Manual0.91B.pdf’. I’d like to report here just to make sure.

DSOQuadV2.6Manual0.91B.png

I’m sorry if this is a false alarm.

Best,
Shigeru

to kotobuki:
thanks for your remind. the manual will be updated .

Please Please PLEASE make it clear what files have changed and need to be installed onto the quads, if any, in this release. All i see is a list of update with NO IDEA which it the most current. THis request has been made several times now, so much for listening to customer suggestions etc …