We have divided a new firmware into two parts : DS0201_APP_V2.21 and DS0201_LIB_V2.1_ss .
Burn the DS0201_LIB_V2.1_ss into the DSO first, and go on to download the DS0201_APP_V2.21 in the same way.
This version just a beta test , up to you to decide whether to upgrade the firmware .
If you choose to upgrade it , please feedback the issue that in your use . We do not guarantee that this version of the stability and other problems resulting.
While the transparency is a neat feature, and clearly tries to emulate an analog scope, I quickly downgraded to 2.02. If there were an option to turn it on and off, or even better an adjustment for how aggressive it is, I would keep the upgrade. I certainly hope that we won’t be stuck with the current implementation of it as the versions move forward.
attached is a full backup of my original firmware. But be carefull, it rewrites the bootloader/update thing also.
for me it works, but i can not guarantee that it works for you too. If anything goes wrong your DSO Nano could die and the only way to bring it back to life then is JTAG.
in short: JTAG is a direct connection to the processor, for debugging, monitoring, programming…
If anything goes wrong while flashing the backup file i posted (power loss,…) or it´s simply not compatible to your hardware revision (i think it wold work for all revisions but I DON´T KNOW…) it may be possible that your dso would not start anymore and you won´t be able to flash a new firmware the normal way.
in such a case you could use a jtag interface cable and a piece of software to access the processor directly and so programm it´s internal memory.
I think if if your battery is full, usb cable and power switch stays untouched during flash, the risc is minimal.
but that minimal risc is yours
did a bit of research on JTAG and though I feel technically qualified to use the JTAG programmer I think I can deal with this firmware untill Seeed Studio decides to post the previous rev. I feel like an idiot for not backing it up. I just figured they would have it somewhere.
If anything “flickers” it probably a sign that more is redrawn on the screen then it should/needed and it might be CPU intensive/draw battery. If my suspicions are correct then its bad but it also means the nano has room for improvements and can get even faster when optimised
I agree with the transparent stuff, it just makes the traces harder to see.
The Xposition is backwards, lock on to a square wave and select the T0,
as you press the left/right the trigger marker moves the way you select, but
the square wave moves the wrong direction. The right amount, just the wrong way.
I’m having the same problems as Ben. Triggers don’t work apart from in AUTO mode. NORM and SIGN/SING mostly don’t display the triggered signal at all.
Sometimes in NORM mode, when the R/S button is pressed and HOLD is displayed on the screen, I can see the waveform moving.
Sometimes it does trigger, but only after HOLDing, and possibly only after holding while the signal level is low if you’re looking for a rising edge. It appears to work better at longer time bases.
SIGN mode doesn’t work at all for me, unless I press the R/S button and immediately get a trigger. Could it be that these are triggering further along the horizontal axis and are therefore out of view?
I’m using firmware version 2.21. To test SIGN and NORM modes I was manually triggering the signal level rather than putting a waveform through it.
Hope that helps, and I look forward to the next update!
I’ve been trying to load the firmware on the nano for a while, but it simply does not show itself as a USB device for me…
I’ve tried it on a macbook (W7pro x64 and snow leo) and on a compaq notebook with WXP pro, and the device simply does not register… The screen on the DSO does show “USB” instead of the battery, but DfuSe shows nothing, either…
I’ve also tried holding Down while turning it on. The “Please connect to USB Host” screen appears, but plugging the USB cable yields nothing…
So, any guesses? My DSO is from the first batch, from last year…