Firmware update issue
#1
Hi!

I just received my Pinecil and wanted to update the firmware to IronOS v2.13 NL. Unfortunately this fails with:

    dfu-util: Error during special command "MASS_ERASE" get_status

I'm using dfu-util 0.9-1 from Ubuntu 20.04; dfu-util -l shows

    Found DFU: [28e9:0189] ver=0100, devnum=124, cfg=1, intf=0, path="1-6", alt=0, name="@Internal Flash  /0x08000000/128*001Kg", serial="??"

so according to the https://wiki.pine64.org/wiki/Pinecil it should be safe to update the firmware.

I also tried updating the firmware with https://github.com/pine64/pinecil-firmware-updater/ on a Windows 10 machine but it fails with a similar message:

    Invalid DFU suffix signature A valid DFU suffix signature will be required in a future dfu-util release!!! Error during special command "MASS_ERASE" get_status
    DFU-Util exited with error code 74!
    Flashing failed.

Any ideas what could be wrong here and how to update the firmware on this device?

See https://pastebin.com/wmRE10Bk for a complete log of dfu-util.

Thanks in advance.
  Reply
#2
Just got my pinecil today and I'm seeing the exact same issue on both a fresh build of dfu-util on an ARM SBC, the dfu-util included with pinecil-firmware-updater and the gd32-dfu-utils (https://github.com/riscv-mcu/gd32-dfu-ut...s/tag/v0.9)

All have the same response.

Simple logs attached (and verbose for the ARM SBC):
https://pastebin.com/jLMfMSaM

Thought it might be related to this:
https://github.com/riscv-rust/longan-nano/issues/5

If I remove the mass erase, I was able to update the firmware (there is an erase and download step during the flashing).
dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000
  Reply
#3
(01-20-2021, 04:19 AM)crenn Wrote: Just got my pinecil today and I'm seeing the exact same issue on both a fresh build of dfu-util on an ARM SBC, the dfu-util included with pinecil-firmware-updater and the gd32-dfu-utils (https://github.com/riscv-mcu/gd32-dfu-ut...s/tag/v0.9)

I have successfully updated three Pinecils using dfu-utils, but under Linux, using Debian Stable stock package (which may be a definitively older one).
  Reply
#4
(01-20-2021, 07:20 AM)VaZso Wrote: I have successfully updated three Pinecils using dfu-utils, but under Linux, using Debian Stable stock package (which may be a definitively older one).

Out of curiosity, were all of your Pinecils from the most recent batch or the first batch? I'll try to install dfu-utils from apt and see if I get a different result.
  Reply
#5
(01-20-2021, 06:25 PM)crenn Wrote: Out of curiosity, were all of your Pinecils from the most recent batch or the first batch? I'll try to install dfu-utils from apt and see if I get a different result.

They are from the first batch.
My father has one, one of my friends has one and I have another one. Smile
  Reply
#6
(01-20-2021, 06:25 PM)crenn Wrote:
(01-20-2021, 07:20 AM)VaZso Wrote: I have successfully updated three Pinecils using dfu-utils, but under Linux, using Debian Stable stock package (which may be a definitively older one).

Out of curiosity, were all of your Pinecils from the most recent batch or the first batch? I'll try to install dfu-utils from apt and see if I get a different result.
I am having the same issue, just got mine in the mail today. I am assuming this one is from the 2nd batch.
  Reply
#7
(01-25-2021, 06:02 PM)housinit Wrote:
(01-20-2021, 06:25 PM)crenn Wrote:
(01-20-2021, 07:20 AM)VaZso Wrote: I have successfully updated three Pinecils using dfu-utils, but under Linux, using Debian Stable stock package (which may be a definitively older one).

Out of curiosity, were all of your Pinecils from the most recent batch or the first batch? I'll try to install dfu-utils from apt and see if I get a different result.
I am having the same issue, just got mine in the mail today. I am assuming this one is from the 2nd batch.
Just wanted to add that I am using the Windows installer.
  Reply
#8
Meetoo on this error--my Pinecil also reboots when you turn the heat on, and when I tried to reflash firmware I got the same error:


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

DFU-Util exited with error code 74!
Flashing failed.


[font=Tahoma, Verdana, Arial, sans-serif]Any suggestions would be appreciated.[/font]
  Reply
#9
(01-16-2021, 07:36 AM)admar Wrote: Hi!

I just received my Pinecil and wanted to update the firmware to IronOS v2.13 NL. Unfortunately this fails with:

    dfu-util: Error during special command "MASS_ERASE" get_status

I'm using dfu-util 0.9-1 from Ubuntu 20.04; dfu-util -l shows

    Found DFU: [28e9:0189] ver=0100, devnum=124, cfg=1, intf=0, path="1-6", alt=0, name="@Internal Flash  /0x08000000/128*001Kg", serial="??"

so according to the https://wiki.pine64.org/wiki/Pinecil it should be safe to update the firmware.

I also tried updating the firmware with https://github.com/pine64/pinecil-firmware-updater/ on a Windows 10 machine but it fails with a similar message:

    Invalid DFU suffix signature A valid DFU suffix signature will be required in a future dfu-util release!!! Error during special command "MASS_ERASE" get_status
    DFU-Util exited with error code 74!
    Flashing failed.

Any ideas what could be wrong here and how to update the firmware on this device?

See https://pastebin.com/wmRE10Bk for a complete log of dfu-util.

Thanks in advance.

Please refer to this thread: https://github.com/Ralim/IronOS/issues/820
  Reply
#10
(01-27-2021, 05:26 PM)tllim Wrote:
(01-16-2021, 07:36 AM)admar Wrote: Hi!

I just received my Pinecil and wanted to update the firmware to IronOS v2.13 NL. Unfortunately this fails with:

    dfu-util: Error during special command "MASS_ERASE" get_status

I'm using dfu-util 0.9-1 from Ubuntu 20.04; dfu-util -l shows

    Found DFU: [28e9:0189] ver=0100, devnum=124, cfg=1, intf=0, path="1-6", alt=0, name="@Internal Flash  /0x08000000/128*001Kg", serial="??"

so according to the https://wiki.pine64.org/wiki/Pinecil it should be safe to update the firmware.

I also tried updating the firmware with https://github.com/pine64/pinecil-firmware-updater/ on a Windows 10 machine but it fails with a similar message:

    Invalid DFU suffix signature A valid DFU suffix signature will be required in a future dfu-util release!!! Error during special command "MASS_ERASE" get_status
    DFU-Util exited with error code 74!
    Flashing failed.

Any ideas what could be wrong here and how to update the firmware on this device?

See https://pastebin.com/wmRE10Bk for a complete log of dfu-util.

Thanks in advance.

Please refer to this thread: https://github.com/Ralim/IronOS/issues/820
I'm having the same issue with a batch #2 pinecil on both Win10 and Debian.

On Win10, I'm using the Pinecil Updater Utility, and I've run it stock, with dfu-util updated to v0.10, with it automatically downloading the firmware, and going through the "custom firmware" option and giving it the firmware directly, all resulting in:

Code:
Pinecil Firmware Updater v1.2
Looking for firmwares and latest version...
Flashing...
dfu-util 0.10

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2020 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/


Opening DFU capable USB device...
ID 28e9:0189
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048

Warning: Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! Error: File ID 0000:0000 does not match device (28e9:0189 or 28e9:0189)
DFU-Util exited with error code 74!
Flashing failed.

Debian I'm doing it on the command line with dfu-util 0.10 as sudo, trying to back up the firmware, and get:

Code:
dfu-util: Cannot open DFU device 28e9:0189 found on devnum 24 (LIBUSB_ERROR_ACCESS)
dfu-util: No DFU capable USB device available.
 
I get failed notifications both with and without the ":mass-erase:force" option when flashing.

Any ideas?
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)