MASS_ERASE get_status fail on Flash
DariusHutchison opened this issue · 14 comments
I am unable to flash my new Pinecil.
Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! Error during special command "MASS_ERASE" get_status
I also attempted to load to with the GD MCU 32 tool, but it was not listing any device available.
Windows 10 Pro using the loaded WinUSB adapter.
GD32 MCU Tool need another driver, not WinUSB.
About the problem, can you please in directory with pinecil updater execute dfu-util.exe -l and send response here?
Thanks
Cannot open DFU device 0a5c:21e8
Found DFU: [28e9:0189] ver=0100, devnum=100, cfg=1, intf=0, path="2-3", alt=1, name="@option Bytes /0x1FFFF800/01016Be", serial="??"
Found DFU: [28e9:0189] ver=0100, devnum=100, cfg=1, intf=0, path="2-3", alt=0, name="@internal Flash /0x08000000/128001Kg", serial="??"
I also loaded the GD MCU 32 drivers and it flashed fine with that tool.
Then it's not Flash Size error problem. Well, I found one person having same problem, but he probably didn't found solution.
Can be issue with dfu-util, since it works for you with GD MCU Tool. Will take look. Thanks for reporting.
Here is the screenshot from the MCU tool if it helps:
I'm having the same problem with the Pinecil I received today from the January batch. My output from dfu-util.exe -i is
C:\Users\bcombee\Downloads\pinecil_firmware_updater_win64_1.2>dfu-util.exe -l
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Cannot open DFU device 17e9:6006
Cannot open DFU device 17e9:6006
Found DFU: [28e9:0189] ver=0100, devnum=56, cfg=1, intf=0, path="1-2", alt=1, name="@Option Bytes /0x1FFFF800/01*016Be", serial="??"
Found DFU: [28e9:0189] ver=0100, devnum=56, cfg=1, intf=0, path="1-2", alt=0, name="@Internal Flash /0x08000000/128*001Kg", serial="??"
Like @RyanHutchison, I was able to use the gd32 dfu-util to flash the device after installing their driver.
Also not working for me.
`dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Found DFU: [28e9:0189] ver=0100, devnum=62, cfg=1, intf=0, path="3-14", alt=1, name="@option Bytes /0x1FFFF800/01016Be", serial="??"
Found DFU: [28e9:0189] ver=0100, devnum=62, cfg=1, intf=0, path="3-14", alt=0, name="@internal Flash /0x08000000/128001Kg", serial="??"`
Success with "GD32 MCU DFU Tool" version 3.8.2.9056 using "GD DFU Drivers" version 3.6.6.6167 -- GD32 DFU Tool set to Verify and Erase All
(http://www.gd32mcu.com/en/download/7?kw=)
Unit indicated settings reset on reboot as expected. Device functions as expected.
Manually installing driver provided with Pinecil Firmware Updater v1.2 and attempting to flash over successfully flashed IronOS 2.14.1 from GD32 MCU DFU Tool -- same result.
@codefaux so even GD32 tool doesn't work for you?
It should be fixed in 1.3. Please let me know if it still persists.
@gamelaster GD32 Tool worked; just indicating that using GD32 Tool did not 'repair' the inability to use the Pinecil Updater - it's just a workaround. (Mostly for clarification/documentation.)
@codefaux yes, I know, that's why I made some changes and it should work in 1.3 without issues
Tested and seems to be functioning now.
@RyanHutchison Great, thank you very much for letting me know.