[Hackrf-dev] DFU

Russell Hande zefie at persona.cc
Wed Aug 7 21:27:05 EDT 2013


Does the flash tool verify writes? Could it be possible his spi flash
nand has a 'bad sector' that isn't updating and corrupting the code?

On Wed, Aug 7, 2013 at 9:25 PM, Michael Ossmann <mike at ossmann.com> wrote:

> I'm very unclear on exactly what you are trying that isn't working. You

> should always be able to perform the recovery steps here:

>

> https://github.com/mossmann/hackrf/wiki/Updating-Firmware#recovering-the-spi-flash-firmware

>

>

> On Thu, Aug 08, 2013 at 10:30:33AM +1000, Graham Cottew wrote:

>>

>> Yes I can do that as well but it doesn't "stick" and as soon as I power off it's back to ground zero.

>> I have to go through DFU again to get the board up able to be recognised by hackrf_info.

>>

>> I have also been running 'make program' from the hackrf_usb directory with the same results.

>> Once after about 50 DFU's it programmed successfully and I started to write a email to this group to announce I had it licked.

>> I used it on another machine and it was powering on and off and booting fine but then after I did a hackrf_spiflash to update to the 2013.07.01 firmware it nuked it back to the present state again and I had to accept defeat.

>>

>> On 08/08/2013, at 3:47 AM, Russell Hande <zefie at persona.cc> wrote:

>>

>> > I think once it is booted in DFU mode, you should be able to re-flash

>> > the rom_to_ram firmware.

>> >

>> > On Wed, Aug 7, 2013 at 3:26 AM, Graham Cottew <gc at zendata.com> wrote:

>> >> With the hackrf_usb.dfu file you sent me and dfu-utils v 0.7 I can do a DFU that appears OK

>> >>

>> >> The Jawbreaker is then found by hackrf_info and works fine with gnuradio on Tx and Rx

>> >> VCCLED, 1V8LED and LED1 are all on when it is idle

>> >>

>> >> Problem is when I power cycle the board the DFU firmware just disappears and I am left with

>> >> VCCLED on

>> >> 1V8LED off

>> >> LED1, LED2, LED3, USB_LED0, USB_LED1 all dimly lit

>> >>

>> >> Can you suggest what I can do to overcome needing to DFU every time I use the Jawbreaker?

>> >>

>> >> DFU:

>> >>

>> >> $ sudo dfu-util --device 1fc9:000c --alt 0 --download hackrf_usb.dfu

>> >> Password:

>> >> dfu-util 0.7

>> >>

>> >> Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.

>> >> Copyright 2010-2012 Tormod Volden and Stefan Schmidt

>> >> This program is Free Software and has ABSOLUTELY NO WARRANTY

>> >> Please report bugs to dfu-util at lists.gnumonks.org

>> >>

>> >> Filter on vendor = 0x1fc9 product = 0x000c

>> >> Opening DFU capable USB device... ID 1fc9:000c

>> >> Run-time device DFU version 0100

>> >> Claiming USB DFU Runtime Interface...

>> >> Determining device status: state = dfuIDLE, status = 0

>> >> WARNING: Runtime device already in DFU state ?!?

>> >> Found Runtime: [1fc9:000c] devnum=0, cfg=1, intf=0, alt=0, name="DFU"

>> >> Claiming USB DFU Interface...

>> >> Setting Alternate Setting #0 ...

>> >> Determining device status: state = dfuIDLE, status = 0

>> >> dfuIDLE, continuing

>> >> DFU mode device DFU version 0100

>> >> Device returned transfer size 2048

>> >> DFU CRC does not match

>> >> Warning: File has no DFU suffix

>> >> bytes_per_hash=346

>> >> Copying data from PC to DFU device

>> >> Starting download: [##################################################] finished!

>> >> unable to read DFU status

>> >>

>> >> HackRF_Info:

>> >>

>> >> $ hackrf_info

>> >> Found HackRF board.

>> >> Board ID Number: 1 (Jawbreaker)

>> >> Firmware Version: git-b056efc

>> >> Part ID Number: 0xbc654755 0xbc654755

>> >> Serial Number: 0x00000000 0x00000000 0x505062c8 0x367b9917

>> >> _______________________________________________

>> >> HackRF-dev mailing list

>> >> HackRF-dev at greatscottgadgets.com

>> >> http://nine.pairlist.net/mailman/listinfo/hackrf-dev

>>



More information about the HackRF-dev mailing list