Forum: GNU Radio A rfx2400 is down, which chip on the borad is broken?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
908b26698752d141fda4c93e5ce45d9e?d=identicon&s=25 hanwen (Guest)
on 2007-05-15 05:00
(Received via mailing list)
Hi,
One of our rfx2400 seems not work. I've tested for a while and found:

1. the board can be identified by motherboard
2. when I plugged the db to motherboard and run some scripts, I found
there aren't any samples come to PC through USB cable. (no wave but a
blank
on usrp_oscope.py)
3. the TX doesn't work either

I doubt there is something wrong with the controlling circuit of this db
and
the RF analog part is OK. I'm really a layman in hardware, can you give
me
some idea about which part is possibly broken, so I can exchange them to
repair.

Thanks!
8c9f3dd4874bf514a95f1ef1fc79ba0b?d=identicon&s=25 Lin HUANG (Guest)
on 2007-05-24 13:36
(Received via mailing list)
Hi everybody,

I'm the colleague of Hanwen. Today I checked the broken board. I need
your
help especial Ettus' help.

We can assure that the mother board is OK, because when we plug other
rfx2400, it works well. For this broken rfx2400:

1. The switch control signal, U204 7404
A1 B1 A2 B2 : 0 1 0 1
It seems no problem. And 3.3V voltage is normal.

2. The TX side: For the power supply circuit, U111 ADP3336 has input 6V
and
output 5V and U110 has 5V input and 3.3V output. For the AD8349, VCC=5V,
and
ADF4360 has VCC=3.3V. They all seem normal. But when we run the transmit
program, the graph always stops immediatly and there is no any error
report
on screen. I'm very confused with this.

3. The RX side: the power circuit U6 has 6V input and 5V output, but U5
cannot output 3.3V. So U3 ADF4360 has no power supply. If U5 is the
reason
for board broken, I can try to replace this chip.

But I'm not sure the broken chip is U5. I remember Ettus said that the
TX
and RX path is completely indenpendent. Why our TX path doesn't work
either?
Untill now we have already broke THREE rfx2400s, all with the same
problem.
I worry about other boards will be broken too.

Can anybody give some advice? Thank you very much!

HUANG Lin



2007/5/15, hanwen <kidult.hanwen@gmail.com>:
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2007-05-24 16:35
(Received via mailing list)
On Thu, May 24, 2007 at 07:35:15PM +0800, Lin HUANG wrote:
> A1 B1 A2 B2 : 0 1 0 1
>
> problem.
> I worry about other boards will be broken too.
>
> Can anybody give some advice? Thank you very much!
>
> HUANG Lin

What are you doing to the boards?

What are you connecting them to?

What level signals are you connecting to the inputs?

What are you using for the power supply?  The one that came from Ettus
Research, or something else?

Eric
8c9f3dd4874bf514a95f1ef1fc79ba0b?d=identicon&s=25 Lin HUANG (Guest)
on 2007-05-25 04:15
(Received via mailing list)
What are you doing to the boards?
We are using the rfx2400s to make a 2*2 MIMO-OFDM platform. We also run
some
other programs like usrp-fft, spectrum sensing etc.

What are you connecting them to?
2 common 2.4G antennas, not the PCB antennas from Ettus.

What level signals are you connecting to the inputs?
RF signal from air. According to the received data in PC, I don't think
they
are too high. And we have used them for several weeks with the current
connection.

What are you using for the power supply?  The one that came from Ettus
Research, or something else?
They are exactly the ones from Ettus Research.

The story is like this: We use the platform everyday. Then in someday
morning or afternoon, we started the USRP and found they had no
responses?!
Nobody touched the boards during the period. And when we leave the lab,
we
always shut off the power of the boards. The enclosures are usually open
because we often plug in and out the daughterboard. At that time we are
always very careful.

So we are very confused. What's the reason?

HUANG Lin

2007/5/24, Eric Blossom <eb@comsec.com>:
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2007-05-25 06:22
(Received via mailing list)
On Fri, May 25, 2007 at 10:15:25AM +0800, Lin HUANG wrote:
> What are you doing to the boards?


> We are using the rfx2400s to make a 2*2 MIMO-OFDM platform. We also run
> some
> other programs like usrp-fft, spectrum sensing etc.

to != with ;)

> What are you connecting them to?
> 2 common 2.4G antennas, not the PCB antennas from Ettus.


> The story is like this: We use the platform everyday. Then in someday
> morning or afternoon, we started the USRP and found they had no
> responses?!
> Nobody touched the boards during the period. And when we leave the lab,
> we
> always shut off the power of the boards. The enclosures are usually open
> because we often plug in and out the daughterboard. At that time we are
> always very careful.
>
> So we are very confused. What's the reason?

Changing daughter boards while the power is applied could
cause a problem.

Not having the daughterboards seated properly on the stand offs could
cause a problem.

Dropping wires, connectors, tools or any other conductors onto the
USRP could cause a problem.

Writing your own verilog code could kill the main and/or
daughterboard.

Calling the u._write_oe method could kill the main and/or
daughterboard.

As far as I know, you are the only people who have been killing RFX-*
boards, and you've managed to kill a lot of them.  I suspect that
someone in your lab is mistreating the boards somehow.


Eric
A4fa617c43498846cb4770f049b53cc7?d=identicon&s=25 Nikhil (Guest)
on 2007-05-26 20:43
(Received via mailing list)
On 5/24/07, Lin HUANG <huanglin.bupt@gmail.com> wrote:

> Hi everybody,
>
>

Hello,




>
> 2. The TX side: For the power supply circuit, U111 ADP3336 has input 6V
> and output 5V and U110 has 5V input and 3.3V output. For the
> AD8349, VCC=5V, and ADF4360 has VCC=3.3V. They all seem normal. But when
> we run the transmit program, the graph always stops immediatly and there is
> no any error report on screen. I'm very confused with this.
>


You said you were using your own antennas.  What is the input impedance
of your Tx antennas?
8c9f3dd4874bf514a95f1ef1fc79ba0b?d=identicon&s=25 Lin HUANG (Guest)
on 2007-09-25 23:04
(Received via mailing list)
I'd like to report to all of you our investigation results. At least,
the TX
side works now. But for the RX side, I think it is absolutely broken and
I
give up to repair it.
I changed the resistors R40, R42, R46, R130, R132, R136 to be 1k ohms.
This
prevents the RX side influencing the TX side. And I connected the 6V
power
of TX side with the power pin of the control part (U203), because the
power
of RX is not normal. Then the TX side can work.

Thanks a lot for Ettus's help.~
HUANG Lin


2007/5/30, Lin HUANG <huanglin.bupt@gmail.com>:
8c9f3dd4874bf514a95f1ef1fc79ba0b?d=identicon&s=25 Lin HUANG (Guest)
on 2007-09-25 23:06
(Received via mailing list)
>
> I continued checking these broken boards recent days. I found for the TX
> side, the graph stops as soon as it starts. It seems the daughter board
> gives some signal to stop the motherboard to load data from PC. I read the
> .sch file in the subversion repository and the defination of the interface
> between db and mb.
>

IOUTN_B IOUTP_B IOUTP_A IOUTN_A   ---- the analog IF signal   mb-->db
clock ---- the db is synchronous with mb   mb-->db
I2C_A0 I2C_A1 ---- TX/RX RX1/RX switch control signal  mb-->db
SCLK SDA ---- R/W interface to E2PROM  mb<-->db
IO0~IO15 ---- for debug usage. mb<-->db

Which pin will give a wrong signal to motherboard and disable the board?
IO?
We never used u_write_oe. So it may be as a input?

Thanks for Eric and Nikhil's help before. Hope you are continously
interested in my bug investigation. Thank you. :)

HUANG Lin
8c9f3dd4874bf514a95f1ef1fc79ba0b?d=identicon&s=25 Lin HUANG (Guest)
on 2007-09-25 23:07
(Received via mailing list)
Hello all,

Just update the status of our broken boards. Now they are fixed up. :)
We
replaced the amplifier chip, U4 MGA82563, with a new one. Then
everything
works now.

Good luck
HUANG Lin


2007/6/6, Lin HUANG <huanglin.bupt@gmail.com>:
This topic is locked and can not be replied to.