# B\_rand new N200 Not working

**URL:** <https://www.ruby-forum.com/t/b-rand-new-n200-not-working/214424>\
**Category:** GNU Radio\
**Created:** [December 1, 2011, 6:02pm UTC](https://www.ruby-forum.com/t/b-rand-new-n200-not-working/214424 "2011-12-01T18:02:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [December 1, 2011, 6:02pm UTC](https://www.ruby-forum.com/t/b-rand-new-n200-not-working/214424/1 "2011-12-01T18:02:39Z")

</div>

Dear All,

I am getting towards the end of my tether with this Ettus stuff - having  
had so much trouble I really don’t know why I did, I was stupid, but I  
did recommend USRPs to a colleague for a radar project.

So,my colleagues new N200 has now arrived and I have to get it working  
or questions will be asked.

It is connected up to the same PC the USRP2 was connected to, on the  
same port, with the same software setup. With the same cables. With the  
same everything basically. It should at least respond to ping on  
192.168.10.2. Does it respond to PING? No.

OK - perhaps something happened to the firmware in shipping, S2 should  
recover this. Does anything happen when s2 is pressed on power cycle no.  
I have pressed S2 until my finger is sore with no results. Are Ettus  
shipping faulty hardware? I think not. So why am I yet again to wasting  
so much time just trying to make things that should work, work? Last  
time it was because things were changed and not documented. This time I  
have no idea. Perhaps the default IP address was changed?

Frustratedly  
Mike

---

<div class="post-metadata">

**Author:** ![vh1](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/278dde/32.png) [@vh1](https://www.ruby-forum.com/u/vh1)\
**Post date:** [December 2, 2011, 7:51pm UTC](https://www.ruby-forum.com/t/b-rand-new-n200-not-working/214424/2 "2011-12-02T19:51:07Z")

</div>

Well nobody cares I suppose - everyone is too busy with their own  
issues.

To follow up, it seem like Ettus shipped us a dud after all because  
after several different PCs have all failed to talk to it and because  
the LEDs are not doing what they should. specifically the CLPD LED  
lights but the firmware one does not, while the Ethernet lights and  
remains orange, I have concluded that it is most likely that it has been  
shipped without any default firmware or with incorrect or corrupted  
firmware.

---

<div class="post-metadata">

**Author:** ![vh1](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/278dde/32.png) [@vh1](https://www.ruby-forum.com/u/vh1)\
**Post date:** [January 6, 2012, 4:06pm UTC](https://www.ruby-forum.com/t/b-rand-new-n200-not-working/214424/3 "2012-01-06T16:06:48Z")

</div>

Update - Yes they had shipped us a dud. Pity about the wasted day of  
effort.

Now trying to build gnuradio but keep getting stuck on the firmware.  
Doing that manually, with the latest firmware still gives:

Expected FPGA compatibility number 8, but got 7:  
The FPGA build is not compatible with the host code build.

But at least the N200 appears to be working this time.