WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2016-Aug-05 01:48:18

corinai
Member
From: Rice Univ./Boston Univ.
Registered: 2015-Nov-23
Posts: 15

transport_header mismatch

Hi,

I have two WARP boards version 3 and as I was saving the plots of the experiment I just performed.... I noticed two of the LEDs near the antenna port of one of the boards started to flicker: one red and one green. The name written on the boards next to the LEDs is D3 and D4. These are the LEDs next to RF B.

When I checked with the sequence of initialization. The following message showed up "Warning transport header mismatch".

>>clear
N = 2;
nodes = wl_initNodes(N);
wl_nodeCmd(nodes,'identify');
disp(nodes)
Warning: transport_header mismatch: [250 250] [0 0] [1 2]

> In wl_transport_header>wl_transport_header.isReply at 102
  In wl_transport_eth_udp_java>wl_transport_eth_udp_java.send at 313
  In wl_node>wl_node.sendCmd at 693
  In wl_transport_eth_udp_java>wl_transport_eth_udp_java.procCmd at 126
  In wl_node>wl_node.wl_transportCmd at 336
  In wl_node>wl_node.applyConfiguration at 161
  In wl_initNodes at 139
Warning: transport_header mismatch: [250 250] [0 0] [2 3]

> In wl_transport_header>wl_transport_header.isReply at 102
  In wl_transport_eth_udp_java>wl_transport_eth_udp_java.send at 313
  In wl_node>wl_node.sendCmd at 693
  In wl_transport_eth_udp_java>wl_transport_eth_udp_java.procCmd at 155
  In wl_node>wl_node.wl_transportCmd at 336
  In wl_node>wl_node.applyConfiguration at 162
  In wl_initNodes at 139
Warning: transport_header mismatch: [250 250] [0 0] [8 9]

> In wl_transport_header>wl_transport_header.isReply at 102
  In wl_transport_eth_udp_java>wl_transport_eth_udp_java.send at 313
  In wl_node>wl_node.sendCmd at 693
  In wl_node>wl_node.procCmd at 667
  In wl_node>wl_node.wl_nodeCmd at 308
Displaying properties of 2 wl_node objects:
|  ID |  WLVER |  HWVER |    Serial # |  Ethernet MAC Addr |          Address |
-------------------------------------------------------------------------------
|   0 |  7.4.0 |      3 |  W3-a-00355 |  40-D8-55-04-22-C2 |         10.0.0.1 |
-------------------------------------------------------------------------------
|   1 |  7.4.0 |      3 |  W3-a-00308 |  40-D8-55-04-22-6A |         10.0.0.2 |
-------------------------------------------------------------------------------

Is there any way of identifying what is wrong? or what happened to the board?

Thank you so much for your help,
Corina

Last edited by corinai (2016-Aug-05 02:25:05)

Offline

 

#2 2016-Aug-05 14:42:05

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: transport_header mismatch

When you say "flicker" - do you mean the LEDs are off most of the time and turn on briefly? If so this is normal. We use the green LED to indicate Tx mode, red to indicate Rx mode. The WARPLab ref design leaves the radio in standby (both LEDs off) by default.

Offline

 

#3 2016-Aug-05 15:00:26

corinai
Member
From: Rice Univ./Boston Univ.
Registered: 2015-Nov-23
Posts: 15

Re: transport_header mismatch

I know about that part. When they transmit the green LED turns on.

No, what I have observed is both the Red and green ones turn on and off with a very fast frequency.

I changed the SD card as I thought maybe the .bin file got corrupted, but no they continue to flicker non-stop. I use the ofdm reference design 7.4.0 for two RF chains.

Thank you so much for your reply.

Offline

 

#4 2016-Aug-08 09:29:18

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: transport_header mismatch

The blinking Tx/Rx LEDs indicate the MAX2829 PLL did not lock. This occurs when the code misconfigures the PLL or if there's a hardware problem in the RF interface. Do you see this behavior with other designs (802.11 Ref Design or WARPLab Ref Design)?

Offline

 

#5 2016-Aug-08 15:08:32

corinai
Member
From: Rice Univ./Boston Univ.
Registered: 2015-Nov-23
Posts: 15

Re: transport_header mismatch

I have tried the following designs and I have observed the following blinking:

- w3_WARPlab_7.4.0.2RF.bin
    * the LEDs from RF B : D4 and D3 blinking intermittently.

- w3_WARPlab_7.5.0.2RF.bin, w3_WARPlab_7.6.0.2RF.bin and w3_WARPlab_7.6.0.2RF.bin
    * the LEDs from RF B : D4 and D3 blinking intermittently.
    * the LEDs in the User I/O part of the board, that is near the hexadecimal display blink continuously. That is the RED LEDS blink continuously in sets: (D15 with D13) alternatively with  (D14 with D12).

Thank you so much for helping out with this.

Offline

 

#6 2016-Aug-09 11:07:16

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: transport_header mismatch

This LED activity is consistent with damaged or faulty hardware. You can email the serial number to support[at]mangocomm.com to discuss repair options. Alternatively if your application does not required RF B you can bypass the error check of the return value from radio_controller_init() in w3_node_init() in the 802.11 ref design or ifc_init() in WARPLab.

Offline

 

Board footer