[USRP-users] GPS data acquisition with the X310

[Florez Manduca, Luz E CIV USARMY (USA) via USRP-users]

Can any of you point me in the right direction in how to collect good GPS data 
with the X310 whether using the X310 internal 10 MHz reference, or external 10 
MHz reference or GPSDO clock, depending on which one will work? How to use the 
PPS port with any of these choices and so on.

Thank you very much.

Sincerely.

Luz Elena (Luchi) Florez Manduca (formerly Roth)
R Electrical Engineer
US Army Armament Research Development & Engineering Center 
Precision Armaments & Intelligent Sensors Division 
Munition Sensors Branch
RDAR-MEF-P, Bldg 407 Buffington Road, Picatinnny Arsenal, NJ 07806-5000 
Desk 973-724-6618 
Cell 267-884-9517 
New Home 267-247-5839
luz.e.florezmanduca@mail.mil



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Carlos Alberto Ruiz Naranjo via USRP-users]

Ok! Thank you :)

El jue., 13 dic. 2018 a las 20:26, Marcus D. Leech ()
escribió:

> On 12/13/2018 02:24 PM, Carlos Alberto Ruiz Naranjo wrote:
> > My problem is that I use the USRPX310 with: default blocks + 1 custom
> > rfnoc blocks.
> >
> > And I am sharing the USRP with a co-worker who uses the python API
> > with defautl blocks.
> >
> > Could we share the same custom FPGA image?
> >
> > Thank you.
> >
> >
> Yes, I think this should work -- the multi_usrp abstraction will only
> use the "default" blocks, and will likely safely ignore any blocks
>that it doesn't "care" about.
>
>
>
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Marcus D. Leech via USRP-users]

On 12/13/2018 02:24 PM, Carlos Alberto Ruiz Naranjo wrote:
My problem is that I use the USRPX310 with: default blocks + 1 custom 
rfnoc blocks.


And I am sharing the USRP with a co-worker who uses the python API 
with defautl blocks.


Could we share the same custom FPGA image?

Thank you.


Yes, I think this should work -- the multi_usrp abstraction will only 
use the "default" blocks, and will likely safely ignore any blocks

  that it doesn't "care" about.



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Carlos Alberto Ruiz Naranjo via USRP-users]

My problem is that I use the USRPX310 with: default blocks + 1 custom rfnoc
blocks.

And I am sharing the USRP with a co-worker who uses the python API with
defautl blocks.

Could we share the same custom FPGA image?

Thank you.
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Marcus D. Leech via USRP-users]

On 12/13/2018 02:04 PM, Carlos Alberto Ruiz Naranjo wrote:

Thanks for the reply.

If I add a rfnoc block but keep the others, could I use UHD python API?
You'd need to use the C++ API--the Python API currently only supports 
the multi_usrp abstraction, and not the

  device3 abstraction (which supports RFNoC).




El jue., 13 dic. 2018 a las 19:37, Marcus D. Leech via USRP-users 
(mailto:usrp-users@lists.ettus.com>>) 
escribió:


On 12/13/2018 01:21 PM, Carlos Alberto Ruiz Naranjo via USRP-users
wrote:
> Hello,
>
> it is posible use UHD python API with a custom USRP X310 image?
>
> Thank you.
>
It very much depends on what type of customization you do.

Obviously, if you remove functionality that UHD expects to be
there, UHD
won't work.

If you add functionality that you want to be accessible to UHD,
you'll
have to modify the host-side UHD libraries to
   "understand" said functionality.

The usual way people do "custom" things with X310 is using RFNoC:

https://kb.ettus.com/Getting_Started_with_RFNoC_Development




___
USRP-users mailing list
USRP-users@lists.ettus.com 
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Carlos Alberto Ruiz Naranjo via USRP-users]

Thanks for the reply.

If I add a rfnoc block but keep the others, could I use UHD python API?

El jue., 13 dic. 2018 a las 19:37, Marcus D. Leech via USRP-users (<
usrp-users@lists.ettus.com>) escribió:

> On 12/13/2018 01:21 PM, Carlos Alberto Ruiz Naranjo via USRP-users wrote:
> > Hello,
> >
> > it is posible use UHD python API with a custom USRP X310 image?
> >
> > Thank you.
> >
> It very much depends on what type of customization you do.
>
> Obviously, if you remove functionality that UHD expects to be there, UHD
> won't work.
>
> If you add functionality that you want to be accessible to UHD, you'll
> have to modify the host-side UHD libraries to
>"understand" said functionality.
>
> The usual way people do "custom" things with X310 is using RFNoC:
>
> https://kb.ettus.com/Getting_Started_with_RFNoC_Development
>
>
>
>
> ___
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] UHD Python API with custom FPGA image

[Marcus D. Leech via USRP-users]

On 12/13/2018 01:21 PM, Carlos Alberto Ruiz Naranjo via USRP-users wrote:

Hello,

it is posible use UHD python API with a custom USRP X310 image?

Thank you.


It very much depends on what type of customization you do.

Obviously, if you remove functionality that UHD expects to be there, UHD 
won't work.


If you add functionality that you want to be accessible to UHD, you'll 
have to modify the host-side UHD libraries to

  "understand" said functionality.

The usual way people do "custom" things with X310 is using RFNoC:

https://kb.ettus.com/Getting_Started_with_RFNoC_Development




___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] UHD Python API with custom FPGA image

[Carlos Alberto Ruiz Naranjo via USRP-users]

Hello,

it is posible use UHD python API with a custom USRP X310 image?

Thank you.
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] USRP1 support: "unknown" daughterboard

[Carlos Alberto Ruiz Naranjo via USRP-users]

Thank you!!! :)

El mié., 12 dic. 2018 a las 15:42, Robin Coxe ()
escribió:

> You may have multiple versions of GNU Radio and/or UHD libraries still
> installed on your PC.  Try navigating to the wherever you installed them
> (e.g., /usr/local/lib) and deleting the ones you don’t want by hand.
>
>
>
> Robin Coxe | Chief R Program Manager, SDR | Santa Clara, CA |
> 408.610.6363
>
> --
> *From:* USRP-users  on behalf of
> Carlos Alberto Ruiz Naranjo via USRP-users 
> *Sent:* Wednesday, December 12, 2018 4:17 AM
> *To:* patchvonbr...@gmail.com
> *Cc:* USRP-users@lists.ettus.com
> *Subject:* Re: [USRP-users] USRP1 support: "unknown" daughterboard
>
> Hi Marcus,
>
> I have changed the version to UHD-3.9.LTS. With *uhd_usrp_probe
> --args="type=usrp1" *I haven't erros. But I don't know why the GNURadio
> version hasn't changed... I have, with the previous errors :
>
> *GNU C++ version 7.3.0; Boost_106501; UHD_4.0.0.rfnoc-devel-702-*
> *geec24d7b*
>
> Any idea?
>
> Thank you.
>
> El mar., 11 dic. 2018 a las 22:42, Marcus D. Leech via USRP-users (<
> usrp-users@lists.ettus.com>) escribió:
>
>> On 12/11/2018 04:36 PM, Carlos Alberto Ruiz Naranjo via USRP-users wrote:
>> > Hello,
>> >
>> > I have found a USRP1 and I am playing with it. I have this error:
>> >
>> > carlos@carlos-pc:~$ sudo uhd_usrp_probe --args="type=usrp1"
>> > [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501;
>> > UHD_4.0.0.rfnoc-devel-702-geec24d7b
>> > [INFO] [USRP1] Opening a USRP1 device...
>> > [INFO] [USRP1] Using FPGA clock rate of 64.00MHz...
>> > [ERROR] [DBMGR] The daughterboard manager encountered a recoverable
>> > error in init.
>> > Loading the "unknown" daughterboard implementations to continue.
>> > The daughterboard cannot operate until this error is resolved.
>> > AssertionError: m and ref_clock/m >= 1e6 and ref_clock/m <= 2.5e6
>> >   in double dbsrx::set_lo_freq(double)
>> >   at /home/carlos/rfnoc/uhd/host/lib/usrp/dboard/db_dbsrx.cpp:305
>> >
>> > _
>> >  /
>> > |   Device: USRP1 Device
>> > | _
>> > |/
>> > |   |   Mboard: USRP1
>> > |   |   serial: 479b9db3
>> > |   |
>> > |   |   Time sources:  none
>> > |   |   Clock sources: internal
>> > |   |   Sensors:
>> > |   | _
>> > |   |/
>> > |   |   |   RX DSP: 0
>> > |   |   |
>> > |   |   |   Freq range: -32.000 to 32.000 MHz
>> > |   | _
>> > |   |/
>> > |   |   |   RX DSP: 1
>> > |   |   |
>> > |   |   |   Freq range: -32.000 to 32.000 MHz
>> > |   | _
>> > |   |/
>> > |   |   |   RX Dboard: A
>> > |   |   |   ID: DBSRX (0x0002)
>> > |   |   | _
>> > |   |   |/
>> > |   |   |   |   RX Frontend: 0
>> > |   |   |   |   Name: Unknown (0x) - 0
>> > |   |   |   |   Antennas:
>> > |   |   |   |   Sensors:
>> > |   |   |   |   Freq range: 0.000 to 0.000 MHz
>> > |   |   |   |   Gain Elements: None
>> > |   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz
>> > |   |   |   |   Connection Type: IQ
>> > |   |   |   |   Uses LO offset: No
>> > |   |   | _
>> > |   |   |/
>> > |   |   |   |   RX Codec: A
>> > |   |   |   |   Name: ad9522
>> > |   |   |   |   Gain range pga: 0.0 to 20.0 step 1.0 dB
>> > |   | _
>> > |   |/
>> > |   |   |   RX Dboard: B
>> > |   |   | _
>> > |   |   |/
>> > |   |   |   |   RX Frontend: 0
>> > |   |   |   |   Name: Unknown (0x) - 0
>> > |   |   |   |   Antennas:
>> > |   |   |   |   Sensors:
>> > |   |   |   |   Freq range: 0.000 to 0.000 MHz
>> > |   |   |   |   Gain Elements: None
>> > |   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz
>> > |   |   |   |   Connection Type: IQ
>> > |   |   |   |   Uses LO offset: No
>> > |   |   | _
>> > |   |   |/
>> > |   |   |   |   RX Codec: B
>> > |   |   |   |   Name: ad9522
>> > |   |   |   |   Gain range pga: 0.0 to 20.0 step 1.0 dB
>> > |   | _
>> > |   |/
>> > |   |   |   TX DSP: 0
>> > |   |   |
>> > |   |   |   Freq range: -44.000 to 44.000 MHz
>> > |   | _
>> > |   |/
>> > |   |   |   TX DSP: 1
>> > |   |   |
>> > |   |   |   Freq range: -44.000 to 44.000 MHz
>> > |   | _
>> > |   |/
>> > |   |   |   TX Dboard: A
>> > |   |   | _
>> > |   |   |/
>> > |   |   |   |   TX Frontend: 0
>> > |   |   |   |   Name: Unknown (0x) - 0
>> > | 

Re: [USRP-users] E310 Kernel Sources

[Philip Balister via USRP-users]

On 12/13/2018 11:06 AM, Philip Balister via USRP-users wrote:
> On 12/13/2018 08:26 AM, Said Uçar wrote:
>> Hi Philip,
>>
>>
>> Thank you for your effort, you help a lot! Last image you provided
>> worked without trouble and I managed to run batman in e310. I didn't
>> test the toolchain yet but I think it will work too. Besides, I tried to
>> build whole image on my own and it worked also. At this point I have
>> some questions;
>>
>> 1. Although the batman works without trouble, to trace batman logs, I
>> need debugfs. When I tried to use batctl (since batman-adv implemented
>> as kernel module, to control batman they provide batctl application), I
>> given an error;
>>
>>                 "Error - can't mount or find debugfs"
>>
>> How could I add debugfs to image?
> 
> Do this:
> 
> https://github.com/balister/meta-ettus-1/commit/5be7f1ef6c47315cc7fac7c957ed399ef7726ab1
> 
> and this:
> 
> https://github.com/balister/sdr-build/commit/e90faa63e79843f5193e6344d4bc30d8721fdeed

Or look on the dropbox later, I am going to kick a build with that in it.

Philip

> 
> You don't really need to bump the submodule hash until the image is
> tested. I do it because the machine that builds the images for dropbox
> uses it.
> 
>>
>> 2. I tried to build image on a computer that has 128 Core processor and
>> 128GB RAM. It took almost 4 hours to complete. And I only built dev
>> image, not demo image. Can I remove some packages from image (if so,
>> how?) to reduce built time? It builds too many packages and I think we
>> don't need all of them.
>>
> 
> How fast is the internet connection? the first time it is going to
> download a lot of source. It is saved for future builds (be careful no
> to delete the downloads directory) I do the build on 4+HT and like 16GB
> and 4 images + 2 sdks is like 6 hours.
> 
> Review the image recipes here:
> 
> https://github.com/balister/meta-sdr/tree/master/recipes-images/images
> 
> If you are using gnuradio, you can use he PACKAGECONFIG variable to turn
> off unused features like qtgui. See:
> http://opensdr.com/posts/building-small-gnuradio-images/
> 
> 
>> 3. I believe at some point in future, we need to configure kernel for
>> our image, how can I tweak the kernel image before build? (I used 'make
>> menuconfig' for another device's kernel build once, but it wasn't built
>> with bitbake)
>>
> 
> I sort of hinted how I do this above. I find config fraqments work work
> better than copying around the entire config file. Easier to move kernel
> version etc.
> 
> The Yocto Project Mega Manual is very useful:
> 
> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
> 
>>
>> Thank you again,
>>
>> Best Regards,
>>
>> Said U.
>>
>>
>> On 12/13/18 5:24 AM, Philip Balister wrote:
>>> OK Dropbox updated:
>>>
>>> https://www.dropbox.com/sh/6qfjjqlfzmyegyd/AABu45Ney1xRoen-NyJim5dGa?dl=0
>>>
>>> Thanks for testing.
>>>
>>> Philip
>>>
>>> On 12/12/2018 07:16 AM, Philip Balister via USRP-users wrote:
 On 12/12/2018 05:42 AM, Said Uçar via USRP-users wrote:
> Hi Philip,
>
>
> I write the image you provided and it booted without trouble. I set the
> KERNELPATH to /usr/src/kernel. Then, I tried to build batman-adv module
> but failed at first, as expected. I given an error;
>
>              /bin/sh: scripts/basic/fixdep: No such file or directory
>
> Then I built all modules in kernel sources using the following
> commands;
>
>          cd /usr/src/kernel
>
>          make modules_prepare
>
>          make modules
>
>          make modules_install
>
> That took some time, but at the end I can manage to build batman
> without
> error. However, I couldn't use the build batman-adv.ko. When I tried to
> insmod the module, I given an error;
>
>          modprobe: ERROR: could not insert 'batman_adv': Unknown
> symbol in module, or unknown parameter (see dmesg)
>
> And the kernel log was;
>
>          [ 1896.210237] batman_adv: Unknown symbol crc32c (err 0)
 I think there is another kernel option needed:

 https://cateee.net/lkddb/web-lkddb/LIBCRC32C.html

 I'll make the change and kick off the sausage machine. Unfortunately it
 is set to do a clean build (to avoid a certain class of failures) so the
 build takes along time to create all the images and sdks, then another
 few hours to upload. Doing incremental builds locally would save you a
 lot of time:

 I think the README here will walk you through the process:

 https://github.com/balister/sdr-build/tree/rocko-e300

 I'll let you know when the upload is done.

>
> The output of  'cat /proc/kallsyms | grep crc'  command;
>
>          c02cd8d8 t crc32c_cra_init
>          c0303250 t crc32_generic_shift
>          c03032d8 T crc32_le_shift
>          c03032e4 T 

Re: [USRP-users] E310 Kernel Sources

[Philip Balister via USRP-users]

On 12/13/2018 08:26 AM, Said Uçar wrote:
> Hi Philip,
> 
> 
> Thank you for your effort, you help a lot! Last image you provided
> worked without trouble and I managed to run batman in e310. I didn't
> test the toolchain yet but I think it will work too. Besides, I tried to
> build whole image on my own and it worked also. At this point I have
> some questions;
> 
> 1. Although the batman works without trouble, to trace batman logs, I
> need debugfs. When I tried to use batctl (since batman-adv implemented
> as kernel module, to control batman they provide batctl application), I
> given an error;
> 
>                 "Error - can't mount or find debugfs"
> 
> How could I add debugfs to image?

Do this:

https://github.com/balister/meta-ettus-1/commit/5be7f1ef6c47315cc7fac7c957ed399ef7726ab1

and this:

https://github.com/balister/sdr-build/commit/e90faa63e79843f5193e6344d4bc30d8721fdeed

You don't really need to bump the submodule hash until the image is
tested. I do it because the machine that builds the images for dropbox
uses it.

> 
> 2. I tried to build image on a computer that has 128 Core processor and
> 128GB RAM. It took almost 4 hours to complete. And I only built dev
> image, not demo image. Can I remove some packages from image (if so,
> how?) to reduce built time? It builds too many packages and I think we
> don't need all of them.
> 

How fast is the internet connection? the first time it is going to
download a lot of source. It is saved for future builds (be careful no
to delete the downloads directory) I do the build on 4+HT and like 16GB
and 4 images + 2 sdks is like 6 hours.

Review the image recipes here:

https://github.com/balister/meta-sdr/tree/master/recipes-images/images

If you are using gnuradio, you can use he PACKAGECONFIG variable to turn
off unused features like qtgui. See:
http://opensdr.com/posts/building-small-gnuradio-images/


> 3. I believe at some point in future, we need to configure kernel for
> our image, how can I tweak the kernel image before build? (I used 'make
> menuconfig' for another device's kernel build once, but it wasn't built
> with bitbake)
> 

I sort of hinted how I do this above. I find config fraqments work work
better than copying around the entire config file. Easier to move kernel
version etc.

The Yocto Project Mega Manual is very useful:

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html

> 
> Thank you again,
> 
> Best Regards,
> 
> Said U.
> 
> 
> On 12/13/18 5:24 AM, Philip Balister wrote:
>> OK Dropbox updated:
>>
>> https://www.dropbox.com/sh/6qfjjqlfzmyegyd/AABu45Ney1xRoen-NyJim5dGa?dl=0
>>
>> Thanks for testing.
>>
>> Philip
>>
>> On 12/12/2018 07:16 AM, Philip Balister via USRP-users wrote:
>>> On 12/12/2018 05:42 AM, Said Uçar via USRP-users wrote:
 Hi Philip,


 I write the image you provided and it booted without trouble. I set the
 KERNELPATH to /usr/src/kernel. Then, I tried to build batman-adv module
 but failed at first, as expected. I given an error;

              /bin/sh: scripts/basic/fixdep: No such file or directory

 Then I built all modules in kernel sources using the following
 commands;

          cd /usr/src/kernel

          make modules_prepare

          make modules

          make modules_install

 That took some time, but at the end I can manage to build batman
 without
 error. However, I couldn't use the build batman-adv.ko. When I tried to
 insmod the module, I given an error;

          modprobe: ERROR: could not insert 'batman_adv': Unknown
 symbol in module, or unknown parameter (see dmesg)

 And the kernel log was;

          [ 1896.210237] batman_adv: Unknown symbol crc32c (err 0)
>>> I think there is another kernel option needed:
>>>
>>> https://cateee.net/lkddb/web-lkddb/LIBCRC32C.html
>>>
>>> I'll make the change and kick off the sausage machine. Unfortunately it
>>> is set to do a clean build (to avoid a certain class of failures) so the
>>> build takes along time to create all the images and sdks, then another
>>> few hours to upload. Doing incremental builds locally would save you a
>>> lot of time:
>>>
>>> I think the README here will walk you through the process:
>>>
>>> https://github.com/balister/sdr-build/tree/rocko-e300
>>>
>>> I'll let you know when the upload is done.
>>>

 The output of  'cat /proc/kallsyms | grep crc'  command;

          c02cd8d8 t crc32c_cra_init
          c0303250 t crc32_generic_shift
          c03032d8 T crc32_le_shift
          c03032e4 T __crc32c_le_shift
          c03032f0 T crc32_le
          c0303438 T __crc32c_le
          c0303580 T crc32_be
          c030a2f0 t crc32_validate
          c091364c t crc32c_mod_init

 And I assume that crc32c module is exists? I stuck at this point, and
 googling didn't 

Re: [USRP-users] E310 Kernel Sources

[Said Uçar via USRP-users]

Hi Philip,


Thank you for your effort, you help a lot! Last image you provided 
worked without trouble and I managed to run batman in e310. I didn't 
test the toolchain yet but I think it will work too. Besides, I tried to 
build whole image on my own and it worked also. At this point I have 
some questions;


1. Although the batman works without trouble, to trace batman logs, I 
need debugfs. When I tried to use batctl (since batman-adv implemented 
as kernel module, to control batman they provide batctl application), I 
given an error;


                "Error - can't mount or find debugfs"

How could I add debugfs to image?

2. I tried to build image on a computer that has 128 Core processor and 
128GB RAM. It took almost 4 hours to complete. And I only built dev 
image, not demo image. Can I remove some packages from image (if so, 
how?) to reduce built time? It builds too many packages and I think we 
don't need all of them.


3. I believe at some point in future, we need to configure kernel for 
our image, how can I tweak the kernel image before build? (I used 'make 
menuconfig' for another device's kernel build once, but it wasn't built 
with bitbake)



Thank you again,

Best Regards,

Said U.


On 12/13/18 5:24 AM, Philip Balister wrote:

OK Dropbox updated:

https://www.dropbox.com/sh/6qfjjqlfzmyegyd/AABu45Ney1xRoen-NyJim5dGa?dl=0

Thanks for testing.

Philip

On 12/12/2018 07:16 AM, Philip Balister via USRP-users wrote:

On 12/12/2018 05:42 AM, Said Uçar via USRP-users wrote:

Hi Philip,


I write the image you provided and it booted without trouble. I set the
KERNELPATH to /usr/src/kernel. Then, I tried to build batman-adv module
but failed at first, as expected. I given an error;

             /bin/sh: scripts/basic/fixdep: No such file or directory

Then I built all modules in kernel sources using the following commands;

             cd /usr/src/kernel

             make modules_prepare

             make modules

             make modules_install

That took some time, but at the end I can manage to build batman without
error. However, I couldn't use the build batman-adv.ko. When I tried to
insmod the module, I given an error;

             modprobe: ERROR: could not insert 'batman_adv': Unknown
symbol in module, or unknown parameter (see dmesg)

And the kernel log was;

             [ 1896.210237] batman_adv: Unknown symbol crc32c (err 0)

I think there is another kernel option needed:

https://cateee.net/lkddb/web-lkddb/LIBCRC32C.html

I'll make the change and kick off the sausage machine. Unfortunately it
is set to do a clean build (to avoid a certain class of failures) so the
build takes along time to create all the images and sdks, then another
few hours to upload. Doing incremental builds locally would save you a
lot of time:

I think the README here will walk you through the process:

https://github.com/balister/sdr-build/tree/rocko-e300

I'll let you know when the upload is done.



The output of  'cat /proc/kallsyms | grep crc'  command;

             c02cd8d8 t crc32c_cra_init
             c0303250 t crc32_generic_shift
             c03032d8 T crc32_le_shift
             c03032e4 T __crc32c_le_shift
             c03032f0 T crc32_le
             c0303438 T __crc32c_le
             c0303580 T crc32_be
             c030a2f0 t crc32_validate
             c091364c t crc32c_mod_init

And I assume that crc32c module is exists? I stuck at this point, and
googling didn't helped.


There is one more thing, I asked the kernel upgrade process to the ETTUS
Support, they replied with the following;

             "Upgrading the kernel would require you to port our drivers.
That probably isn't feasible."

Um, clearly that isn't an accurate statement. I've seen it done a few
times, and Kurt Kiefer published his work which I built on to make these
images.

Philip




Regarding that answer, how could you managed to build image with kernel
4.9 for e310 devices?


Thank you again,

Best Regards,

Said U.


On 12/12/18 12:58 AM, Philip Balister wrote:

On 12/10/2018 04:20 PM, Philip Balister via USRP-users wrote:

On 12/10/2018 03:03 AM, Said Uçar via USRP-users wrote:

Hi Philip,


Thank you for your answer. I believe the first option is simpler than
the second. However, I'm not familiar to building and tweaking kernel.
Is there a documentation for building and tweaking kernel for E300
series? You are definitely right about the kernel version issue (batman
did most of its features after kernel 4), I would like to test older
version because it may be sufficient for us.

I don't have any docs that would help and don't know of any on the Ettus
site. I've had an idea that might help. I have a more recent build based
on the OpenEmbedded rocko branches that use a 4.9 kernel, I am adding
the kernel-devsrc package to the image. That should let you build the
kernel module on the device. No warranty though. The builder is running
now and it is a long job, I'll post a link to the updated images when
they are