On Mon, Apr 5, 2010 at 4:40 PM, Stefan Fehrle wrote:
>
> Tom Rondeau schrieb:
>>> Now I can build the firmware.
>>>
>>> When I copy "txrx.bin" from the subfolder apps to the sd-card. I can't
>>> connect to the USRP2. The led e and f burns. The GNU Radio Companion
>>> (GRC)
>>> stops the program wi
Tom Rondeau schrieb:
>> Now I can build the firmware.
>>
>> When I copy "txrx.bin" from the subfolder apps to the sd-card. I can't
>> connect to the USRP2. The led e and f burns. The GNU Radio Companion
>> (GRC)
>> stops the program with the error message "RuntimeError: No USRPs found
>> on
>> int
> Now I can build the firmware.
>
> When I copy "txrx.bin" from the subfolder apps to the sd-card. I can't
> connect to the USRP2. The led e and f burns. The GNU Radio Companion (GRC)
> stops the program with the error message "RuntimeError: No USRPs found on
> interface eth1".
>
> When I copy "txr
Eric Blossom schrieb:
> On Tue, Mar 30, 2010 at 12:05:25PM +0200, Stefan Fehrle wrote:
>>
>> Eric Blossom schrieb:
>> > On Tue, Mar 30, 2010 at 08:38:08AM +0200, Stefan Fehrle wrote:
>> >>
>> >> I wanted to build the USRP2 firmware to enable the testclk at J503,
>> but
>> >> I
>> >> have some erro
On Tue, Mar 30, 2010 at 12:05:25PM +0200, Stefan Fehrle wrote:
>
> Eric Blossom schrieb:
> > On Tue, Mar 30, 2010 at 08:38:08AM +0200, Stefan Fehrle wrote:
> >>
> >> I wanted to build the USRP2 firmware to enable the testclk at J503, but
> >> I
> >> have some errors. I download the source with the
Eric Blossom schrieb:
> On Tue, Mar 30, 2010 at 08:38:08AM +0200, Stefan Fehrle wrote:
>>
>> I wanted to build the USRP2 firmware to enable the testclk at J503, but
>> I
>> have some errors. I download the source with the command "git clone
>> git://gnuradio.org/gnuradio
>> " and the mb-gcc from h
On Tue, Mar 30, 2010 at 08:38:08AM +0200, Stefan Fehrle wrote:
>
> I wanted to build the USRP2 firmware to enable the testclk at J503, but I
> have some errors. I download the source with the command "git clone
> git://gnuradio.org/gnuradio
> " and the mb-gcc from http://gnuradio.org/tools/
>
> T
I wanted to build the USRP2 firmware to enable the testclk at J503, but I
have some errors. I download the source with the command "git clone
git://gnuradio.org/gnuradio
" and the mb-gcc from http://gnuradio.org/tools/
Then I execute the commands "./bootstrap" and "./configure.gnu
MB_GCC=/usr/loc
On Sat, Oct 04, 2008 at 03:22:52PM -0400, Jeff Long wrote:
>>
>> Right now __moddi3, __umoddi3, __divdi3 and __udivdi3 contain inlined
>> versions of __udivmoddi4. Un-inlining them should save about 5KB in
>> the worst case, 4KB typical. I'm working on it. (These routines
>> implement signed an
Right now __moddi3, __umoddi3, __divdi3 and __udivdi3 contain inlined
versions of __udivmoddi4. Un-inlining them should save about 5KB in
the worst case, 4KB typical. I'm working on it. (These routines
implement signed and unsigned 64-bit divides and mods. We use these
in dealing with our 64
On Fri, Oct 03, 2008 at 11:10:36PM -0700, Matt Ettus wrote:
> Jeff Long wrote:
>> Generated a new txrx.bin using EDK101 and put it on the SD
>> card. Works! I'm assuming that's the correct app, based on
>> strings on the provided SD. BTW, is any of this documented
>> yet?
>
> Yes, txrx is the co
Jeff Long wrote:
Generated a new txrx.bin using EDK101 and put it on the SD
card. Works! I'm assuming that's the correct app, based on
strings on the provided SD. BTW, is any of this documented
yet?
Yes, txrx is the correct app to use, and is the one which is on the SD
card which I ship out
Generated a new txrx.bin using EDK101 and put it on the SD
card. Works! I'm assuming that's the correct app, based on
strings on the provided SD. BTW, is any of this documented
yet?
Where do printf's go to?
Using -Os vs. -O2 shaves off another 500 bytes if you ever
need the space. Takes txrx
On Fri, Oct 03, 2008 at 01:58:02PM -0400, Jeff Long wrote:
> Trying out the firmware build ...
>
> - had to comment out apps/rx_only_v2.c, line 104
> (static volatile bool link_is_up = false) to avoid
> multiple definitions ... does not appear to be used
> in this file and is declared static
On Fri, Oct 03, 2008 at 01:58:02PM -0400, Jeff Long wrote:
> Trying out the firmware build ...
>
> - had to comment out apps/rx_only_v2.c, line 104
> (static volatile bool link_is_up = false) to avoid
> multiple definitions ... does not appear to be used
> in this file and is declared static
On Fri, Oct 03, 2008 at 01:58:02PM -0400, Jeff Long wrote:
> Trying out the firmware build ...
>
> - had to comment out apps/rx_only_v2.c, line 104
> (static volatile bool link_is_up = false) to avoid
> multiple definitions ... does not appear to be used
> in this file and is declared static
Trying out the firmware build ...
- had to comment out apps/rx_only_v2.c, line 104
(static volatile bool link_is_up = false) to avoid
multiple definitions ... does not appear to be used
in this file and is declared static
- build exceeds size of flatmem (0x8000) ... bumped to
0xa000 and
17 matches
Mail list logo
