discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] GRC 3.7.11 on Windows crashes python.exe


From: Cinaed Simson
Subject: Re: [Discuss-gnuradio] GRC 3.7.11 on Windows crashes python.exe
Date: Fri, 14 Apr 2017 16:31:21 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

You should post this on

   https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

mailing list.

Indicate the color of the LED and it's position relative to the antenna,
post the output of

  hackrf_info

and a copy of your flowchart - the XML file with the

  .GRC

extension.

I know next to nothing about Windows 10 but there were some problems
with the drivers - possibly the Windows USB driver - but I thought they
were resolved. I'm assuming you installed the Windows 10 USB driver.

And try different USB ports - there's a rumor that the Windows driver
may only work on a single port - but then I know next to nothing.

-- Cinaed


On 04/14/2017 09:40 AM, Marcus Müller wrote:
> Hi Martijn,
> 
> "Illegal Instruction" is actually a proper processor fault (ie. your
> processor noticed a problem, and jumped to an interrupt routine telling
> your OS that hey, things need to be handled) that happens when one tries
> to execute code that isn't actually code or uses an instruction that
> your CPU doesn't have.
> 
> I'm pretty optimistic that hackrf.dll wasn't compiled for a CPU that's
> incompatible to yours, so this might essentially be a bug – either in
> the hackrf driver dll (which might be jumping into machine code that
> isn't code), or in the way the windows DLL loader is used. Hm. Maybe
> even a compiler bug.
> 
> Now, I have to admit that under Unixes, I'd know how to debug this, but
> under Windows, I'm out of my depth. So if you happen to be more capable
> than I am with that, you could try to run "python
> C:\path\to\your\flow_graph_python_file.py" in a debugger and see where
> it crashes. But even then, I don't know if things would be easy to
> figure out.
> 
> Best regards,
> Marcus
> On 14.04.2017 16:34, Martijn Scale wrote:
>>
>> Trying to use a HackRF One with GNU Radio on Windows 10 (64-bits),
>> installed from gnuradio_3.7.11_win64.msi.
>>
>> When using osmocom Source and executing the flow graph, execution
>> halts with message: python.exe has stopped working. GRC remains alive.
>>
>> Crashes happen both with WX and QT. The HackRF One module is put into
>> Receive mode (Rx Led of HackRF One is on).
>>
>>  
>>
>> GNU Radio, GRC, Hack RF and computer do work as expected with the
>> GNURadioLiveDVD <https://wiki.gnuradio.org/index.php/GNURadioLiveDVD>.
>>
>>  
>>
>> Debugging shows: Unhandled exception at 0x00007FFCCDDD3CCB
>> (hackrf.dll) in python.exe: 0xC000001D: Illegal Instruction.
>>
>> Additional info from Event Viewer:
>>
>> Faulting application path: C:\Program
>> Files\GNURadio-3.7\gr-python27\python.exe
>>
>> Faulting module path: C:\Program Files\GNURadio-3.7\bin\hackrf.dll
>>
>> And info from Console Panel in GRC:
>>
>> Win32; Microsoft Visual C++ version 14.0; Boost_106000;
>> UHD_003.010.001.001-0-unknown
>>
>>  
>>
>> hackrf.dll info: 2017-03-03, 66.560 Bytes
>>
>>  
>>
>> gr-osmosdr ae686c46 (0.1.5git) gnuradio 3.7.11
>>
>> built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf bladerf
>> airspy redpitaya
>>
>> Number of USB devices: 17
>>
>> USB device 1d50:xxxx: 0000000000000000a06063c82xxxxxxx match
>>
>> Using HackRF One with firmware 2017.02.1
>>
>>  
>>
>> Hardware:
>>
>> Processor           Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz,
>> 2794 Mhz, 4 Core(s), 8 Logical Processor(s)
>>
>> Display adapter                AMD Radeon HD 5700 Series
>>
>>  
>>
>> Your support is highly appreciated (I tried building GNU Radio from
>> sources, which failed as “gr-newmod/CMakeLists.txt was not found and
>> is required”, but I decided not to pursue the building path any
>> further as it exceeds my knowledge).
>>
>>  
>>
>>  
>>
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]