clrion / dsonano

Automatically exported from code.google.com/p/dsonano
0 stars 0 forks source link

Problem upgrading to different APP #10

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. When trying to upgrade APP and LIB 
2.
3.

What is the expected output? What do you see instead?
Power up holding down button screen says "copy hex or bin file to DFU virtual 
disk (just like the quad), I copy the new files APP and LIB and the nano shows 
files as RDY,  all ok so far, turn nano off and on and it still has previous 
APP running. This  nano was supplied with LIB 2.26, APP 2.60, after contacting 
my supplier LIB 2.25 and APP 2.60 were e-mailed to me from  guojun Ding, the 
nano accepted this LIB file and APP file so I now have LIB 2.25 APP 2.60, so 
this method appears to work for these files but I cannot change to benf APP 
3.64 with LIB 3.53

What version of the product are you using? On what operating system?
 Nano with the square button for up,down,left,right selection, e-design device firmware upgrade V3.20A,  LIB ver 2.25, APP ver 2.60

Please provide any additional information below.
When turned on with down button DFU demo can't find nano but it appears in 
windows explorer as DFU V3_11_A and the new hex files can be copied to this and 
it behaves as the quad scope, marks the files as RDY but when turned off and on 
returns to the existing APP (2.60)

Original issue reported on code.google.com by thelogic...@googlemail.com on 10 May 2012 at 2:03

GoogleCodeExporter commented 8 years ago
I had the exact same problem with DFU files for the /BenF 3.4 firmware then I 
found the information below. On loading the .hex files instead, it upgraded 
just fine. 

"Most recent DSO Nano 201 coming from China are having a different firmware 
upgrade function that can't be used with DfuSe. Instead, it goes much easier

Just copy first each of the files to the “removable storage” Nano. After a 
few seconds, the explorer window should close automatically, then, after 2-3 
seconds, reopen. The file should still be there, but renamed; if it has a .rdy
extension now, everything is fine. If it has a .err extension, something is 
wrong (most likely the .hex file is broken).

If you try to copy a .dfu file instead a .hex file, the window is closing, but 
not reopening again, and you will get an error message that the target is not 
available"

Original comment by djdavey...@gmail.com on 11 Aug 2012 at 9:09

GoogleCodeExporter commented 8 years ago
I just received a new DSO201 and have exactly the same problem. I copy the hex 
files to the DFU V3_11_A virtual drive, the window closes and reopens with the 
*.RDY files, but when I turn the DSO201 off on then on, the previous version of 
the firmware is still loaded. What am I doing wrong? I need a solution to this 
problem or I will be forced to return the DSO for a refund.  

Original comment by rick.hen...@gmail.com on 16 Aug 2012 at 2:56

GoogleCodeExporter commented 8 years ago
I finally found a solution to my problem. See the following link:
http://www.seeedstudio.com/forum/viewtopic.php?f=12&t=3195&start=40

Basically, the hex files I was using were incompatible with the latest DSO201 
hardware. See the 5th post in the above link and download the zip file which 
contain the BenF firmware hex files in the correct format. 

Original comment by rick.hen...@gmail.com on 17 Aug 2012 at 8:08