Warning: Invalid DFU suffix signature

Meadow Development
1

I cannot connect to F7 v1 anymore. I tried the bootloader and reflashing the OS, and it sort of works, but I get the warning in the end:

meadow flash os
Flashing OS with C:\Users\xxx\AppData\Local\WildernessLabs\Firmware\1.3.0.0\Meadow.OS.bin
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/

Match vendor ID from file: 0000
Match product ID from file: 0000
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
Downloading element to address = 0x08000000, size = 2097152

Erase    done.  [=========================] 100%      2097152 bytes

Download done.  [=========================] 100%      2097152 bytes
File downloaded successfully
Transitioning to dfuMANIFEST state
Warning: Invalid DFU suffix signature                <<<<<<<<< THIS WARNING

Connecting to Meadow on COM3

and then it hangs and never connects to Meadow on COM3,
nor does it connect from Visual Studio 2022, although it shows it in the list of devices as COM3.
I tried different cables and different computers, but since it is able to flash, then the cable should be good.
I am lost here and do not know what to do next, is it dead?

2

Hi Tridy,
if you reboot the device does the command
meadow list ports
show the attached device?

Can you also confirm which operating system you are running these commands on?

3

Found Meadow: COM3
Done!

BUT:

image

4

tried to flash it one more time, and got the same result after the flashing, it could not connect to COM3

image
image906Ă—824 38.7 KB

F7 is on and is on COM3

5

@tridy Which version of Windows OS are you using?

We have seen an issue where certain Win10 or fewer Win11 don’t work with the official Meadow.CLI and for those developer we offer the Meadow.CLI.Classic:

Please follow the installation instructions there and let me know if the Classic version works for you?

6

I got the same result through nuget and v 1.2.2

PowerShell 7.3.6
PS C:\Users\user> dotnet tool uninstall --global WildernessLabs.Meadow.CLI
Tool 'wildernesslabs.meadow.cli' (version '1.3.0') was successfully uninstalled.
PS C:\Users\user> dotnet tool install --global --add-source "E:\NuGets\" WildernessLabs.Meadow.CLI --version 1.3.0
You can invoke the tool using the following command: meadow
Tool 'wildernesslabs.meadow.cli' (version '1.3.0') was successfully installed.
PS C:\Users\user> meadow --version
v1.2.2
Done!
PS C:\Users\user> meadow download os
An update is available. Current Version 1.2.2.0 Latest Version 1.3.0. Run `dotnet tool update WildernessLabs.Meadow.CLI --global` to update
Downloading latest version file

Downloaded 285 bytes
Meadow OS version 1.3.0.0 was previously downloaded to: C:\Users\user\AppData\Local\WildernessLabs\Firmware\1.3.0.0.

Done!
PS C:\Users\user> meadow flash os
Flashing OS with C:\Users\user\AppData\Local\WildernessLabs\Firmware\1.3.0.0\Meadow.OS.bin
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/

Match vendor ID from file: 0000
Match product ID from file: 0000
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
Downloading element to address = 0x08000000, size = 2097152

Erase    done.  [=========================] 100%      2097152 bytes

Download done.  [=========================] 100%      2097152 bytes
File downloaded successfully
Transitioning to dfuMANIFEST state
Warning: Invalid DFU suffix signature

Connecting to Meadow on COM3

stuck after Connecting to Meadow on COM3

The thing is that it used to work and 2 weeks ago or so I was able to deploy the flashing led example without any issues. I remember while keeping the flashing example running and F7 connected to PC, after a couple of hours it would suddenly say that it was not able to recognize the USB device anymore. However, after reconnecting it would be back to normal.

As a result, it can see it on COM3 but cannot work with it on either 1.2.2 or 1.3.0:

PowerShell 7.3.6
PS C:\Users\user> meadow list ports
An update is available. Current Version 1.2.2.0 Latest Version 1.3.0. Run `dotnet tool update WildernessLabs.Meadow.CLI --global` to update
Found Meadow: COM3
Done!
PS C:\Users\user> meadow device name
An update is available. Current Version 1.2.2.0 Latest Version 1.3.0. Run `dotnet tool update WildernessLabs.Meadow.CLI --global` to update

Connecting to Meadow on COM3

Unable to find Meadow.
PS C:\Users\user>

[sad face]

7

The version should say 1.3.0, I’ll fix that today. What timezone are you in, maybe we can jump on a call today, as this is very strange.

8

I have sent a PM to you.

9

PMed you back. I just wanted to point out that in theory the DFU suffix error, isn’t the issue here.

10

Having similar problems as posted here Problem getting started - Meadow Development - Community (wildernesslabs.co)

11

I am discussing that in the support Slack channel:

so far my understanding is that I have managed to deploy an invalid yaml config file it is stuck on the startup error. Reflashing the OS does not erase the deployment of the project, and after os flash, it restarts and locks up with an invalid yaml file. I tried to time meadow mono disable command but was not able to stop mono. So it looks like the board is bricked for now, and I will be waiting for some kind of solution from the team.

1 Like
12

Did you ever get any resolution to how to un-brick your device? I am stuck in the exact same place.

13

Yes, I did manage to get it un-bricked. So, I first flashed to the “special” build 1.3.1.3 and then back to 1.3.0.0, and it removed the settings for the board and it was unbricked. You can find the discussion in Slack.
It was in September, so I am not sure if the build is still there or if they have removed it or if it is still there, but here is what you can try:

meadow download os -v 1.3.1.3
meadow flash os -v 1.3.1.3

then restart, and then you can flash back the 1.3.0.0

the details are in the link to the Slack in my previous post.

14

Thank you! I was able to find that thread and get a bricked CCMv2 I’ve had dead for months working!