Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Michael Ossmann
Yes, that definitely sounds like a hardware failure in a voltage
regulator.  We'll replace your HackRF.


On Fri, May 25, 2018 at 12:25:12AM -0500, Andrew Onyshchuk wrote:
>
> Hi Michael,
> 
> Yep from the hackrf itself.
> 
> Thanks,
> Andrew
> On Fri, May 25, 2018 at 12:17 AM Michael Ossmann  wrote:
> 
> > Andrew,
> 
> > Was that audible noise from the hardware itself (not the attached USB
> > host)?
> 
> > Thanks,
> 
> > Mike
> 
> 
> > On Thu, May 24, 2018 at 11:45:38PM -0500, Andrew Onyshchuk wrote:
> > >
> > > Dominic,
> > >
> > > Not after firmware update - I was using the same firmware (some git
> master
> > > from 6 months ago) for some time.
> > > 2018.01.1 is the result of trying different firmwares after it got
> broken.
> > >
> > > I think(not sure though) I left hackrf connected(but not in rx/tx mode)
> to
> > > my macbook air on that night (for about 14 hours).
> > > Could that have something to do with it?
> > >
> > > Also I remember I heard some high freq noise from the hackrf (after
> running
> > > hackrf_transfer) when I first discovered it was broken.
> > >
> > > Thanks,
> > > Andrew
> > >
> > > On Thu, May 24, 2018 at 11:18 PM Dominic Spill 
> wrote:
> > >
> > > > Hi Andrew,
> > > >
> > > > It certainly sounds like something os going wrong on the board itself.
> > > > Did this start happening after you upgraded your firmware to
> 2018.01.1?
> > > >
> > > > How are you powering the device?  From a laptop/desktop computer?
> > > >
> > > > Thanks,
> > > > Dominic
> > > >
> > > > On 24 May 2018 at 20:33, Andrew Onyshchuk  wrote:
> > > >
> > > >> Hi Dominic,
> > > >>
> > > >> It becomes unresponsive only after I try using hackrf_transfer.
> > > >> After that it is completely unresponsive and only
> rebooting/reconnecting
> > > >> helps.
> > > >>
> > > >> I'm guessing the ARM chip crashes or turns off. Maybe power supply
> issue?
> > > >>
> > > >> Thanks,
> > > >> Andrew
> > > >>
> > > >>
> > > >> On Thu, May 24, 2018 at 7:31 PM Dominic Spill 
> > > >> wrote:
> > > >>
> > > >>> Hi Andrew,
> > > >>>
> > > >>> Is the HackRF permanently in this state?  Or does it switch from
> > > >>> responding to hackrf_info to not responding only after you try using
> > > >>> hackrf_transfer?
> > > >>>
> > > >>> Thanks,
> > > >>>   Dominic
> > > >>>
> > > >>> On 21 May 2018 at 16:43, Andrew Onyshchuk 
> wrote:
> > > >>>
> > >  Hi everyone.
> > > 
> > >  My hackrf one suddenly stopped working.
> > >  When I try rx (or tx) I don't receive any samples and hackrf stops
> > >  responding/ all 6 LED are on.
> > >  Flashing different firmware doesn't help (using DFU as well).
> > >  Same on different computers and different cables.
> > >  The md5 of firmware from the device matches the .bin file.
> > > 
> > >  $ hackrf_info
> > >  hackrf_info version: git-90d3f7f
> > >  libhackrf version: git-90d3f7f (0.5)
> > >  Found HackRF
> > >  Index: 0
> > >  Serial number: 14d463dc2fa077e1
> > >  Board ID Number: 2 (HackRF One)
> > >  Firmware Version: 2018.01.1 (API:1.02)
> > >  Part ID Number: 0xa004cb3c 0x005e4f3e
> > > 
> > >  $ hackrf_transfer -f 41500 -r /dev/null
> > >  call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
> > >  call hackrf_set_freq(41500 Hz/415.000 MHz)
> > >  Stop with Ctrl-C
> > >  0.0 MiB / 1.003 sec = 0.0 MiB/second
> > > 
> > >  Couldn't transfer any bytes for one second.
> > > 
> > >  Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
> > >  Total time: 1.00293 s
> > > 
> > >  $ hackrf_info
> > >  hackrf_info version: git-90d3f7f
> > >  libhackrf version: git-90d3f7f (0.5)
> > >  Found HackRF
> > >  Index: 0
> > >  hackrf_board_id_read() failed: Input/Output Error (-1000)
> > > 
> > >  Looks like a hardware failure?
> > > 
> > >  Thanks in advance for any suggestions/assistance
> > > 
> > >  ___
> > >  HackRF-dev mailing list
> > >  HackRF-dev@greatscottgadgets.com
> > >  https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > 
> > > 
> > > >>>
> > > >
> 
> > > ___
> > > HackRF-dev mailing list
> > > HackRF-dev@greatscottgadgets.com
> > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> 
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Andrew Onyshchuk
Hi Michael,

Yep from the hackrf itself.

Thanks,
Andrew
On Fri, May 25, 2018 at 12:17 AM Michael Ossmann  wrote:

> Andrew,

> Was that audible noise from the hardware itself (not the attached USB
> host)?

> Thanks,

> Mike


> On Thu, May 24, 2018 at 11:45:38PM -0500, Andrew Onyshchuk wrote:
> >
> > Dominic,
> >
> > Not after firmware update - I was using the same firmware (some git
master
> > from 6 months ago) for some time.
> > 2018.01.1 is the result of trying different firmwares after it got
broken.
> >
> > I think(not sure though) I left hackrf connected(but not in rx/tx mode)
to
> > my macbook air on that night (for about 14 hours).
> > Could that have something to do with it?
> >
> > Also I remember I heard some high freq noise from the hackrf (after
running
> > hackrf_transfer) when I first discovered it was broken.
> >
> > Thanks,
> > Andrew
> >
> > On Thu, May 24, 2018 at 11:18 PM Dominic Spill 
wrote:
> >
> > > Hi Andrew,
> > >
> > > It certainly sounds like something os going wrong on the board itself.
> > > Did this start happening after you upgraded your firmware to
2018.01.1?
> > >
> > > How are you powering the device?  From a laptop/desktop computer?
> > >
> > > Thanks,
> > > Dominic
> > >
> > > On 24 May 2018 at 20:33, Andrew Onyshchuk  wrote:
> > >
> > >> Hi Dominic,
> > >>
> > >> It becomes unresponsive only after I try using hackrf_transfer.
> > >> After that it is completely unresponsive and only
rebooting/reconnecting
> > >> helps.
> > >>
> > >> I'm guessing the ARM chip crashes or turns off. Maybe power supply
issue?
> > >>
> > >> Thanks,
> > >> Andrew
> > >>
> > >>
> > >> On Thu, May 24, 2018 at 7:31 PM Dominic Spill 
> > >> wrote:
> > >>
> > >>> Hi Andrew,
> > >>>
> > >>> Is the HackRF permanently in this state?  Or does it switch from
> > >>> responding to hackrf_info to not responding only after you try using
> > >>> hackrf_transfer?
> > >>>
> > >>> Thanks,
> > >>>   Dominic
> > >>>
> > >>> On 21 May 2018 at 16:43, Andrew Onyshchuk 
wrote:
> > >>>
> >  Hi everyone.
> > 
> >  My hackrf one suddenly stopped working.
> >  When I try rx (or tx) I don't receive any samples and hackrf stops
> >  responding/ all 6 LED are on.
> >  Flashing different firmware doesn't help (using DFU as well).
> >  Same on different computers and different cables.
> >  The md5 of firmware from the device matches the .bin file.
> > 
> >  $ hackrf_info
> >  hackrf_info version: git-90d3f7f
> >  libhackrf version: git-90d3f7f (0.5)
> >  Found HackRF
> >  Index: 0
> >  Serial number: 14d463dc2fa077e1
> >  Board ID Number: 2 (HackRF One)
> >  Firmware Version: 2018.01.1 (API:1.02)
> >  Part ID Number: 0xa004cb3c 0x005e4f3e
> > 
> >  $ hackrf_transfer -f 41500 -r /dev/null
> >  call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
> >  call hackrf_set_freq(41500 Hz/415.000 MHz)
> >  Stop with Ctrl-C
> >  0.0 MiB / 1.003 sec = 0.0 MiB/second
> > 
> >  Couldn't transfer any bytes for one second.
> > 
> >  Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
> >  Total time: 1.00293 s
> > 
> >  $ hackrf_info
> >  hackrf_info version: git-90d3f7f
> >  libhackrf version: git-90d3f7f (0.5)
> >  Found HackRF
> >  Index: 0
> >  hackrf_board_id_read() failed: Input/Output Error (-1000)
> > 
> >  Looks like a hardware failure?
> > 
> >  Thanks in advance for any suggestions/assistance
> > 
> >  ___
> >  HackRF-dev mailing list
> >  HackRF-dev@greatscottgadgets.com
> >  https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > 
> > 
> > >>>
> > >

> > ___
> > HackRF-dev mailing list
> > HackRF-dev@greatscottgadgets.com
> > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Michael Ossmann
Andrew,

Was that audible noise from the hardware itself (not the attached USB
host)?

Thanks,

Mike


On Thu, May 24, 2018 at 11:45:38PM -0500, Andrew Onyshchuk wrote:
>
> Dominic,
> 
> Not after firmware update - I was using the same firmware (some git master
> from 6 months ago) for some time.
> 2018.01.1 is the result of trying different firmwares after it got broken.
> 
> I think(not sure though) I left hackrf connected(but not in rx/tx mode) to
> my macbook air on that night (for about 14 hours).
> Could that have something to do with it?
> 
> Also I remember I heard some high freq noise from the hackrf (after running
> hackrf_transfer) when I first discovered it was broken.
> 
> Thanks,
> Andrew
> 
> On Thu, May 24, 2018 at 11:18 PM Dominic Spill  wrote:
> 
> > Hi Andrew,
> >
> > It certainly sounds like something os going wrong on the board itself.
> > Did this start happening after you upgraded your firmware to 2018.01.1?
> >
> > How are you powering the device?  From a laptop/desktop computer?
> >
> > Thanks,
> > Dominic
> >
> > On 24 May 2018 at 20:33, Andrew Onyshchuk  wrote:
> >
> >> Hi Dominic,
> >>
> >> It becomes unresponsive only after I try using hackrf_transfer.
> >> After that it is completely unresponsive and only rebooting/reconnecting
> >> helps.
> >>
> >> I'm guessing the ARM chip crashes or turns off. Maybe power supply issue?
> >>
> >> Thanks,
> >> Andrew
> >>
> >>
> >> On Thu, May 24, 2018 at 7:31 PM Dominic Spill 
> >> wrote:
> >>
> >>> Hi Andrew,
> >>>
> >>> Is the HackRF permanently in this state?  Or does it switch from
> >>> responding to hackrf_info to not responding only after you try using
> >>> hackrf_transfer?
> >>>
> >>> Thanks,
> >>>   Dominic
> >>>
> >>> On 21 May 2018 at 16:43, Andrew Onyshchuk  wrote:
> >>>
>  Hi everyone.
> 
>  My hackrf one suddenly stopped working.
>  When I try rx (or tx) I don't receive any samples and hackrf stops
>  responding/ all 6 LED are on.
>  Flashing different firmware doesn't help (using DFU as well).
>  Same on different computers and different cables.
>  The md5 of firmware from the device matches the .bin file.
> 
>  $ hackrf_info
>  hackrf_info version: git-90d3f7f
>  libhackrf version: git-90d3f7f (0.5)
>  Found HackRF
>  Index: 0
>  Serial number: 14d463dc2fa077e1
>  Board ID Number: 2 (HackRF One)
>  Firmware Version: 2018.01.1 (API:1.02)
>  Part ID Number: 0xa004cb3c 0x005e4f3e
> 
>  $ hackrf_transfer -f 41500 -r /dev/null
>  call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
>  call hackrf_set_freq(41500 Hz/415.000 MHz)
>  Stop with Ctrl-C
>  0.0 MiB / 1.003 sec = 0.0 MiB/second
> 
>  Couldn't transfer any bytes for one second.
> 
>  Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
>  Total time: 1.00293 s
> 
>  $ hackrf_info
>  hackrf_info version: git-90d3f7f
>  libhackrf version: git-90d3f7f (0.5)
>  Found HackRF
>  Index: 0
>  hackrf_board_id_read() failed: Input/Output Error (-1000)
> 
>  Looks like a hardware failure?
> 
>  Thanks in advance for any suggestions/assistance
> 
>  ___
>  HackRF-dev mailing list
>  HackRF-dev@greatscottgadgets.com
>  https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> 
> 
> >>>
> >

> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Andrew Onyshchuk
Dominic,

Not after firmware update - I was using the same firmware (some git master
from 6 months ago) for some time.
2018.01.1 is the result of trying different firmwares after it got broken.

I think(not sure though) I left hackrf connected(but not in rx/tx mode) to
my macbook air on that night (for about 14 hours).
Could that have something to do with it?

Also I remember I heard some high freq noise from the hackrf (after running
hackrf_transfer) when I first discovered it was broken.

Thanks,
Andrew

On Thu, May 24, 2018 at 11:18 PM Dominic Spill  wrote:

> Hi Andrew,
>
> It certainly sounds like something os going wrong on the board itself.
> Did this start happening after you upgraded your firmware to 2018.01.1?
>
> How are you powering the device?  From a laptop/desktop computer?
>
> Thanks,
> Dominic
>
> On 24 May 2018 at 20:33, Andrew Onyshchuk  wrote:
>
>> Hi Dominic,
>>
>> It becomes unresponsive only after I try using hackrf_transfer.
>> After that it is completely unresponsive and only rebooting/reconnecting
>> helps.
>>
>> I'm guessing the ARM chip crashes or turns off. Maybe power supply issue?
>>
>> Thanks,
>> Andrew
>>
>>
>> On Thu, May 24, 2018 at 7:31 PM Dominic Spill 
>> wrote:
>>
>>> Hi Andrew,
>>>
>>> Is the HackRF permanently in this state?  Or does it switch from
>>> responding to hackrf_info to not responding only after you try using
>>> hackrf_transfer?
>>>
>>> Thanks,
>>>   Dominic
>>>
>>> On 21 May 2018 at 16:43, Andrew Onyshchuk  wrote:
>>>
 Hi everyone.

 My hackrf one suddenly stopped working.
 When I try rx (or tx) I don't receive any samples and hackrf stops
 responding/ all 6 LED are on.
 Flashing different firmware doesn't help (using DFU as well).
 Same on different computers and different cables.
 The md5 of firmware from the device matches the .bin file.

 $ hackrf_info
 hackrf_info version: git-90d3f7f
 libhackrf version: git-90d3f7f (0.5)
 Found HackRF
 Index: 0
 Serial number: 14d463dc2fa077e1
 Board ID Number: 2 (HackRF One)
 Firmware Version: 2018.01.1 (API:1.02)
 Part ID Number: 0xa004cb3c 0x005e4f3e

 $ hackrf_transfer -f 41500 -r /dev/null
 call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
 call hackrf_set_freq(41500 Hz/415.000 MHz)
 Stop with Ctrl-C
 0.0 MiB / 1.003 sec = 0.0 MiB/second

 Couldn't transfer any bytes for one second.

 Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
 Total time: 1.00293 s

 $ hackrf_info
 hackrf_info version: git-90d3f7f
 libhackrf version: git-90d3f7f (0.5)
 Found HackRF
 Index: 0
 hackrf_board_id_read() failed: Input/Output Error (-1000)

 Looks like a hardware failure?

 Thanks in advance for any suggestions/assistance

 ___
 HackRF-dev mailing list
 HackRF-dev@greatscottgadgets.com
 https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


>>>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Dominic Spill
Hi Andrew,

It certainly sounds like something os going wrong on the board itself.  Did
this start happening after you upgraded your firmware to 2018.01.1?

How are you powering the device?  From a laptop/desktop computer?

Thanks,
Dominic

On 24 May 2018 at 20:33, Andrew Onyshchuk  wrote:

> Hi Dominic,
>
> It becomes unresponsive only after I try using hackrf_transfer.
> After that it is completely unresponsive and only rebooting/reconnecting
> helps.
>
> I'm guessing the ARM chip crashes or turns off. Maybe power supply issue?
>
> Thanks,
> Andrew
>
>
> On Thu, May 24, 2018 at 7:31 PM Dominic Spill  wrote:
>
>> Hi Andrew,
>>
>> Is the HackRF permanently in this state?  Or does it switch from
>> responding to hackrf_info to not responding only after you try using
>> hackrf_transfer?
>>
>> Thanks,
>>   Dominic
>>
>> On 21 May 2018 at 16:43, Andrew Onyshchuk  wrote:
>>
>>> Hi everyone.
>>>
>>> My hackrf one suddenly stopped working.
>>> When I try rx (or tx) I don't receive any samples and hackrf stops
>>> responding/ all 6 LED are on.
>>> Flashing different firmware doesn't help (using DFU as well).
>>> Same on different computers and different cables.
>>> The md5 of firmware from the device matches the .bin file.
>>>
>>> $ hackrf_info
>>> hackrf_info version: git-90d3f7f
>>> libhackrf version: git-90d3f7f (0.5)
>>> Found HackRF
>>> Index: 0
>>> Serial number: 14d463dc2fa077e1
>>> Board ID Number: 2 (HackRF One)
>>> Firmware Version: 2018.01.1 (API:1.02)
>>> Part ID Number: 0xa004cb3c 0x005e4f3e
>>>
>>> $ hackrf_transfer -f 41500 -r /dev/null
>>> call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
>>> call hackrf_set_freq(41500 Hz/415.000 MHz)
>>> Stop with Ctrl-C
>>> 0.0 MiB / 1.003 sec = 0.0 MiB/second
>>>
>>> Couldn't transfer any bytes for one second.
>>>
>>> Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
>>> Total time: 1.00293 s
>>>
>>> $ hackrf_info
>>> hackrf_info version: git-90d3f7f
>>> libhackrf version: git-90d3f7f (0.5)
>>> Found HackRF
>>> Index: 0
>>> hackrf_board_id_read() failed: Input/Output Error (-1000)
>>>
>>> Looks like a hardware failure?
>>>
>>> Thanks in advance for any suggestions/assistance
>>>
>>> ___
>>> HackRF-dev mailing list
>>> HackRF-dev@greatscottgadgets.com
>>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>>
>>>
>>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Andrew Onyshchuk
Hi Dominic,

It becomes unresponsive only after I try using hackrf_transfer.
After that it is completely unresponsive and only rebooting/reconnecting
helps.

I'm guessing the ARM chip crashes or turns off. Maybe power supply issue?

Thanks,
Andrew


On Thu, May 24, 2018 at 7:31 PM Dominic Spill  wrote:

> Hi Andrew,
>
> Is the HackRF permanently in this state?  Or does it switch from
> responding to hackrf_info to not responding only after you try using
> hackrf_transfer?
>
> Thanks,
>   Dominic
>
> On 21 May 2018 at 16:43, Andrew Onyshchuk  wrote:
>
>> Hi everyone.
>>
>> My hackrf one suddenly stopped working.
>> When I try rx (or tx) I don't receive any samples and hackrf stops
>> responding/ all 6 LED are on.
>> Flashing different firmware doesn't help (using DFU as well).
>> Same on different computers and different cables.
>> The md5 of firmware from the device matches the .bin file.
>>
>> $ hackrf_info
>> hackrf_info version: git-90d3f7f
>> libhackrf version: git-90d3f7f (0.5)
>> Found HackRF
>> Index: 0
>> Serial number: 14d463dc2fa077e1
>> Board ID Number: 2 (HackRF One)
>> Firmware Version: 2018.01.1 (API:1.02)
>> Part ID Number: 0xa004cb3c 0x005e4f3e
>>
>> $ hackrf_transfer -f 41500 -r /dev/null
>> call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
>> call hackrf_set_freq(41500 Hz/415.000 MHz)
>> Stop with Ctrl-C
>> 0.0 MiB / 1.003 sec = 0.0 MiB/second
>>
>> Couldn't transfer any bytes for one second.
>>
>> Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
>> Total time: 1.00293 s
>>
>> $ hackrf_info
>> hackrf_info version: git-90d3f7f
>> libhackrf version: git-90d3f7f (0.5)
>> Found HackRF
>> Index: 0
>> hackrf_board_id_read() failed: Input/Output Error (-1000)
>>
>> Looks like a hardware failure?
>>
>> Thanks in advance for any suggestions/assistance
>>
>> ___
>> HackRF-dev mailing list
>> HackRF-dev@greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
>>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one

2018-05-24 Thread Dominic Spill
Hi Andrew,

Is the HackRF permanently in this state?  Or does it switch from responding
to hackrf_info to not responding only after you try using hackrf_transfer?

Thanks,
  Dominic

On 21 May 2018 at 16:43, Andrew Onyshchuk  wrote:

> Hi everyone.
>
> My hackrf one suddenly stopped working.
> When I try rx (or tx) I don't receive any samples and hackrf stops
> responding/ all 6 LED are on.
> Flashing different firmware doesn't help (using DFU as well).
> Same on different computers and different cables.
> The md5 of firmware from the device matches the .bin file.
>
> $ hackrf_info
> hackrf_info version: git-90d3f7f
> libhackrf version: git-90d3f7f (0.5)
> Found HackRF
> Index: 0
> Serial number: 14d463dc2fa077e1
> Board ID Number: 2 (HackRF One)
> Firmware Version: 2018.01.1 (API:1.02)
> Part ID Number: 0xa004cb3c 0x005e4f3e
>
> $ hackrf_transfer -f 41500 -r /dev/null
> call hackrf_set_sample_rate(1000 Hz/10.000 MHz)
> call hackrf_set_freq(41500 Hz/415.000 MHz)
> Stop with Ctrl-C
> 0.0 MiB / 1.003 sec = 0.0 MiB/second
>
> Couldn't transfer any bytes for one second.
>
> Exiting... hackrf_is_streaming() result: HACKRF_TRUE (1)
> Total time: 1.00293 s
>
> $ hackrf_info
> hackrf_info version: git-90d3f7f
> libhackrf version: git-90d3f7f (0.5)
> Found HackRF
> Index: 0
> hackrf_board_id_read() failed: Input/Output Error (-1000)
>
> Looks like a hardware failure?
>
> Thanks in advance for any suggestions/assistance
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


Re: [Hackrf-dev] Broken hackrf one after firmware update.

2014-12-20 Thread Michael Ossmann
You should also update the CPLD:

https://github.com/mossmann/hackrf/wiki/Updating-Firmware

With new firmware and old CPLD I would expect the spectrum to be
inverted in some cases.  A fixed frequency offset would be puzzling
unless it is a misinterpretation of inverted spectrum (which could be an
easy mistake to make).

Mike


On Sat, Dec 20, 2014 at 09:19:21AM +0100, Ulf Bertilsson wrote:

 Old firmware(that worked and came with my unit)
 
 ~/src/hackrf/firmware/hackrf_usb/build$ cat hackrf_info.txt
 Found HackRF board.
 Board ID Number: 2 (HackRF One)
 Firmware Version: git-44df9d1
 Part ID Number: 0xa000cb3c 0x005e4f54
 
 new build yesterday:
 
 ~/src/hackrf/firmware/hackrf_usb/build$ cat hackrf_info2.txt
 Found HackRF board.
 Board ID Number: 2 (HackRF One)
 Firmware Version: git-4e98bc6
 Part ID Number: 0xa000cb3c 0x005e4f54
 Serial Number: 0x 0x 0x457863c8 0x2f21441f
 
 Currently running:
 
 Found HackRF board.
 Board ID Number: 2 (HackRF One)
 Firmware Version: 2014.08.1
 Part ID Number: 0xa000cb3c 0x005e4f54
 Serial Number: 0x 0x 0x457863c8 0x2f21441f
 
 Gcc toolchain:
 
 gcc-arm-none-eabi-4_9-2014q4
 
 uname -a:
 
 Linux hack 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux
 
 gqrx
 gr-osmosdr v0.1.4-2-g8d9e6b58 (0.1.5git) gnuradio 3.7.6git-188-gf60cd24f
 built-in source types: file fcd rtl_tcp hackrf rfspace
 
 ..
 cmake .. -DBOARD=HACKRF_ONE
 ..
 
 2014-12-20 9:06 GMT+01:00 Ulf Bertilsson ulf.daniel.bertils...@gmail.com:
 
  Oh dear, my hackrf is not feeling well.
 
  I setup the gcc tool chains and stuff and compiled the firmware from got.
 
  I followed the readme and it went well.
 
  I then flashed it with hackrf_one_usb.bin file.
 
  All seemed well, and I reset it.
 
  All, well until I started up gqrx and noticed all my bookmarks are about
  5mhz off !?
 
  I also recompiled gqrx, reflashed with rebuild official firmware.
 
  Still all my freq are off and need ~5mhz lo to be correct.
 
  What have I broken ?! :/
 
  --
  Ulf

 ___
 HackRF-dev mailing list
 HackRF-dev@greatscottgadgets.com
 https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev