WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2015-May-05 05:32:07

FoufiDoumi
Member
Registered: 2014-May-05
Posts: 14

Unable to configure WARP v3 with WARPLab 7.5.0 or 7.5.1

Hi there!

I will be brief:

2 WARP v3 with 4RFs
2 SD cards

- SD cards slots work just fine because I tried re-configuring both our WARPs from slot 1 or 2 with the 7.4.0 that already works and they succesfully showed the dwo dashes on the 7 segment.
- So, I tried writting 7.5.0 and 7.5.1 in slot 0 and tried to reconfigure, but it will just not happen. The 7 segment stays to 00 (zero zero) and nothing blinks.
- At the same time, now that I have 7.4.0 in slot0, 7.5.0 in slot1 and 7.5.1 in slot2, trying any of slots 1 and 2 again does not configure the WARPs, while slot 0 does and again I see the two dashes.
So the WARPs are currently still configured with 7.4.0. after a total of 3 succesfull reconfigurations.

So, clearly I set up the SD card correctly, I also do the dynamic configuration process correctly, but the 7.5.0 and 7.5.1 just will not configure the boards.

Ofcourse I use the right ones, for v3 and for 4RFs, and the .bin files.

What could be wrong? Here we'd like to take advantage of the extra memory on the boards so that we can receive many more samples.

I hope that I am not the only one having this issue and that there is a solution.

So, any help would be appreciated and thank you in advance.

Offline

 

#2 2015-May-05 09:11:24

welsh
Administrator
From: Mango Communications
Registered: 2013-May-15
Posts: 612

Re: Unable to configure WARP v3 with WARPLab 7.5.0 or 7.5.1

I was able to download the WARPLab 7.5.1, write the design to slot 0 of an SD and use the card to successfully boot a WARP v3 4RF node. 

Can you please post the UART output of the boot process so we can understand where the board is getting stuck.  This will allow us to further isolate where the issue might be.

Offline

 

#3 2015-May-06 04:48:02

FoufiDoumi
Member
Registered: 2014-May-05
Posts: 14

Re: Unable to configure WARP v3 with WARPLab 7.5.0 or 7.5.1

Oh! Never thought of doing that. Ok!

...

Several trials passed. The message I was receiving was

Code:

     ***** WARP v3 Clock Config Core *****
      Program Assembly Date: 24 Jan 2015

No config data in EEPROM - Using Defaults
Detected CM-MMCX Module
Loading configuration B
Clock Config Complete - Continuing Boot Process

Even though it says that no config data was detected in the first line, I figured out it was the enabled MM-CX module to blame. Even if I tried to configure the clock master on its own it needed to keep the MM-CX module disabled (both switces to zero). Then, I disabled the MM-CX from the clock slave too and was able to succesfully configure it with 7.5.1 from slot 2.

Yay! ^_^

7.4.0 doesn't have a problem like that. Even with the MM-CX enabled, in both warps, clock master and slave, I succesfully reconfigured them back with 7.4.0.

Well now both of them have 7.5.1. PuTTY log as follows:

_________________Clock master ______________________
     

Code:

WARPLab v7.5.1 (compiled Mar 12 2015 11:13:49)
Configured for 4 RF Interfaces - FMC-RF-2X245 FMC module must be installed
No clock module detected - selecting on-board clocks

NODE: W3-a-00474 using Node ID: 65535
DRAM SODIMM detected ...
  Contents not cleared
Configuring baseband ...
  Using DDR for buffers
  Rx samples:       32768 (  67108864 max)
  Tx samples:       32768 (  58720256 max)
Configuring transport ...
  ETH A MAC Address: 40:D8:55:04:23:A0
  ETH A IP  Address: 10.0.0.0
  Configuring ETH A for AXI DMA mode with 9024 byte buffers (2 receive, 1 send)
  ETH A speed 1000 Mbps (default)
  Listening on UDP ports 9000 (unicast) and 10000 (broadcast)

Waiting for Ethernet link ...

Initialization Successful - Waiting for Commands from MATLAB

!!! Waiting for Network Configuration via Matlab !!!

____________________Clock Slave __________________
     

Code:

WARPLab v7.5.1 (compiled Mar 12 2015 11:13:49)
Configured for 4 RF Interfaces - FMC-RF-2X245 FMC module must be installed
No clock module detected - selecting on-board clocks

NODE: W3-a-00364 using Node ID: 65535
DRAM SODIMM detected ...
  Contents not cleared
Configuring baseband ...
  Using DDR for buffers
  Rx samples:       32768 (  67108864 max)
  Tx samples:       32768 (  58720256 max)
Configuring transport ...
  ETH A MAC Address: 40:D8:55:04:22:DC
  ETH A IP  Address: 10.0.0.0
  Configuring ETH A for AXI DMA mode with 9024 byte buffers (2 receive, 1 send)
  ETH A speed 1000 Mbps (default)
  Listening on UDP ports 9000 (unicast) and 10000 (broadcast)

Waiting for Ethernet link ...

Initialization Successful - Waiting for Commands from MATLAB

!!! Waiting for Network Configuration via Matlab !!!

And now I get this nice message in MATLAB:

Code:

Displaying properties of 2 wl_node objects:
|  ID |  WLVER |  HWVER |    Serial # |  Ethernet MAC Addr |          Address | 
-------------------------------------------------------------------------------
|   0 |  7.5.1 |      3 |  W3-a-00364 |  40-D8-55-04-22-DC |         10.0.0.1 |
-------------------------------------------------------------------------------
|   1 |  7.5.1 |      3 |  W3-a-00474 |  40-D8-55-04-23-A0 |         10.0.0.2 |
-------------------------------------------------------------------------------

When I try to sync them though, the 7segment stays at 00 on both of them and MATLAB can't communicate with them. Well then I suppose I will revise the examples to see how to sync them now under 7.5.1, I'll also try to implement the MEX UDP transport since it is considered much faster, and I hope I won't have any more problems in the future.

Thank you very much!

Offline

 

#4 2015-May-06 09:00:39

welsh
Administrator
From: Mango Communications
Registered: 2013-May-15
Posts: 612

Re: Unable to configure WARP v3 with WARPLab 7.5.0 or 7.5.1

I'm glad you were able to get it working.  If you look at the Change Log for WARPLab, you can see that we upgraded the clock controller to be able to use the new CM-PLL clock modules.  The SIP settings for the CM-MMCX have changed between WARPLab 7.4.0 and WARPLab 7.5.x, so please take a look at the documentation to understand the new configuration options.

Offline

 

Board footer