dfu-util | dfu-util with statically linked libusb for mac | Networking library

by PeachyPrinter C Version: Current License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | dfu-util Summary

dfu-util is a C library typically used in Networking applications. dfu-util has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

This specically formulated version of dfu-utils designed with the intent of statically linking libusb to create standalone operation on mac computers. ******** Not Working ... yet *********. Dfu-util - Device Firmware Upgrade Utilities. Dfu-util is the host side implementation of the DFU 1.0 [1] and DFU 1.1 [2] specification of the USB forum. DFU is intended to download and upload firmware to devices connected over USB. It ranges from small devices like micro-controller boards up to mobile phones. With dfu-util you are able to download firmware to your device or upload firmware from it. dfu-util has been tested with Openmoko Neo1973 and Freerunner and many other devices. [1] DFU 1.0 spec: [2] DFU 1.1 spec:

Support

Quality

Security

License

Reuse

Support

dfu-util has a low active ecosystem.

It has 5 star(s) with 8 fork(s). There are 5 watchers for this library.

It had no major release in the last 6 months.

dfu-util has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of dfu-util is current.

Quality

dfu-util has no bugs reported.

Security

dfu-util has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

dfu-util is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

dfu-util releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dfu-util

Get all kandi verified functions for this library.

dfu-util Key Features

No Key Features are available at this moment for dfu-util.

dfu-util Examples and Code Snippets

No Code Snippets are available at this moment for dfu-util.

Community Discussions

Trending Discussions on dfu-util

STM32 DFU upload fails and GCC optimisations

How to determin size of internal flash for target?

Can't Flash Code to Particle Photon

QUESTION

STM32 DFU upload fails and GCC optimisations

Asked 2019-Apr-23 at 06:54

Edit : Problem circuvented by generating a Makefile project but I'd still like to know what is going on.

This question echoes my unresolved problem mentioned here (STM32 app not running sometimes, remains in DFU).

I have a custom board STM32L486 based and I am using the built-in DFU mode to upload new firmware over USB using dfu-util on Linux.

Sometimes, for unknown reasons, the app won't start after leaving the DFU mode. A slight change in code can make it work or break it. (see link above for details).
Examples of changes that can reverse the problem :

Adding / removing a HAL_Delay or a LED Blink
+1 or -1 on an array size
Adding / removing a sprintf format

What seems to work is building the binary with Og optimisation (or using the STLink tool and debug mode).

I have tried to increase the heap and stack (up to 20x the default), it doesn't change anything. Checking the prepare dead code/data removal options in Atollic seem make build fail more than other times.

What could be causing the issue of the app not starting, not even the init steps ? How can I track down the culprit flags that may cause this ?
Can this be linked to a memory alignment problem ?

Any ideas / insights / comments on how to check is welcome.

I have been able to reproduce the same issues (from here and my other link) on a Nucleo board.
I tried to generate a Makefile project from CubeMX and the problem does not happen. I guess this is a bug in either the binary generated by Atollic or the compiler/linker settings that the IDE.
Note that my Makefile uses the exact same toolchain as Atollic so this cannot be a toolchain issue.
This issue is hereby circumvented by this, but I'd still like to understand what may happen.

...

ANSWER

Answered 2019-Apr-23 at 06:54

As far as I've tried, this DFU issue and app not rebooting is caused when building from Atollic (TrueStudio).

Generating a Makefile project from CubeMX solved this issue though I still cannot explain why.

Source https://stackoverflow.com/questions/55759042

QUESTION

How to determin size of internal flash for target?

Asked 2019-Feb-01 at 20:03

I want to upload the device firmware to a file using dfu-util. How can I determine the correct size of flash memory?

After booting the device into DFU it can be found using:

...

ANSWER

Answered 2019-Feb-01 at 13:04

Please see UM0290 in which we find:

Each Alternate setting string descriptor must follow this memory mapping else the PC Host Software would be able to decode the right mapping for the selected device:

@: To detect that this is a special mapping descriptor (to avoid decoding standard descriptor)

/: for separator between zones

Maximum 8 digits per address starting by “0x”

/: for separator between zones

Maximum of 2 digits for the number of sectors

* : For separator between number of sectors and sector size

Maximum 3 digits for sector size between 0 and 999

1 digit for the sector size multiplier. Valid entries are: B (byte), K (Kilo), M (Mega)

1 digit for the sector type as follows:

a (0x41): Readable

b (0x42): Erasable

c (0x43): Readable and Erasable

d (0x44): Writeable

e (0x45): Readable and Writeable

f (0x46): Erasable and Writeable

g (0x47): Readable, Erasable and Writeable

So your string really does mean that the internal flash is 64 sectors of 2 KB, and that they are "readable, erasable and writable" (i.e. flash). Are you sure about your expectations of the device's flash layout?

Source https://stackoverflow.com/questions/54469520

QUESTION

Can't Flash Code to Particle Photon

Asked 2018-Jan-05 at 07:54

I have a Particle Photon which I'm trying to setup. I've tried flashing code both from the web IDE, and locally and it always times out. The device is connecting as it can be seen in these pictures:

The web IDE does not give me much information. It only says "Request Timed Out". This is what I get when I try to flash an .ino code

...

ANSWER

Answered 2017-Jun-22 at 15:46

You won't be able to flash a Core firmware to a Photon (they have different architecture and firmware layout). To compile the code for photon you can also use the CLI:

Source https://stackoverflow.com/questions/44460336

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install dfu-util

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: