Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu Stuidio 15.10 fails to upgrade firmware using dfu-programmer 0.6.1 #39

Open
CoolGames opened this issue Mar 29, 2016 · 4 comments

Comments

@CoolGames
Copy link

Using Linux to verify ability to update

latest firmware is 1.92 but the docs are not working as written.

dfu programmer 0.6.1 was installed by using synaptic default repositories

$ dfu-programmer --version
dfu-programmer 0.6.1

force is not a valid argument

 dfu-programmer --help
Usage: dfu-programmer target[:usb-bus,usb-addr] command [options] [global-options] [file|data]

global-options:
        --quiet
        --debug level    (level is an integer specifying level of detail)
        Global options can be used with any command and must come
        after the command and before any file or data value

commands:
        configure {BSB|SBV|SSB|EB|HSB} [--suppress-validation] data
        dump
        dump-eeprom
        dump-user
        erase [--suppress-validation]
        flash [--suppress-validation] [--suppress-bootloader-mem]
                     [--serial=hexdigits:offset] {file|STDIN}
        flash-eeprom [--suppress-validation]
                     [--serial=hexdigits:offset] {file|STDIN}
        flash-user   [--suppress-validation]
                     [--serial=hexdigits:offset] {file|STDIN}
        get     {bootloader-version|ID1|ID2|BSB|SBV|SSB|EB|
                 manufacturer|family|product-name|
                 product-revision|HSB}
        getfuse {LOCK|EPFL|BOOTPROT|BODLEVEL|BODHYST|
                 BODEN|ISP_BOD_EN|ISP_IO_COND_EN|
                 ISP_FORCE}
        setfuse {LOCK|EPFL|BOOTPROT|BODLEVEL|BODHYST|
                 BODEN|ISP_BOD_EN|ISP_IO_COND_EN|
                 ISP_FORCE} data
        setsecure
        reset
        start


Entered this command to put the HDK MCU at device ttyACM0 into bootloader mode:
$ screen /dev/ttyACM0 115200
Then entered as per instructions

>#?B1948
where upon screen exited as expected

[screen is terminating]
$ 

But no device was found

dfu-programmer atxmega256a3bu flash  --suppress-bootloader-mem 1-92-OLED.hex
dfu-programmer: no device present.

@rpavlik
Copy link
Member

rpavlik commented Mar 29, 2016

You may need to run with sudo, and/or as the instructions suggest, watch dmesg for the alternate USB device to enumerate first.

@CoolGames
Copy link
Author

Figured out the the distribution is causing the no device so had to git and make from sourceforge.
Still testing so I will report discrepancies next.

@rpavlik
Copy link
Member

rpavlik commented Mar 29, 2016

ah, right, that device was added presumably newer than 0.61 - that's an ancient version to be shipped, why is ubuntu doing that? weird... on Windows, we've used 0.72.

@CoolGames
Copy link
Author

And confirmed after successful build 0.7.2 2015-02-04 from sourceforge
that sudo is required and `--force`` added after distribution version 0.6.1 2013-04-04.
Maybe Ubuntu should be notified as they are approaching Ubuntu 16.04

I checked debian machinekit on Beagle Bone Black as I am trying to connect it
with OSVR HDK 1.3 and it is even older 5.4-1

# dfu-programmer --version
dfu-programmer 0.7.2

I created a shell file to save time.

# cat HDK\ fw1.92.sh 
dfu-programmer atxmega256a3bu flash --force --suppress-bootloader-mem 1-92-OLED.hex
#  ./HDK\ fw1.92.sh 
0%                            100%  Programming 0x1A000 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
0%                            100%  Reading 0x40000 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  Success
Validating...  Success
0x1A000 bytes written into 0x40000 bytes memory (40.62%)

# dfu-programmer atxmega256a3bu launch

Confirmed with screen /dev/ttyACM0 115200
and >#?v

Version 1.92  Mar 24 2016
Tracker:1.8.4.415

When docs reflect these requirements then can be marked closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants