FPGA - AP's And SM's


Can someone explain to me what the FPGA is please. Does the FPGA version for all sm’s looking at an AP have to be the same (or is it good practice for them all to be the same)?

Do all AP’s on a cluster have to run the same FPGA version?

The reason I ask is that I am experiencing some problems at a particular cluster, which is populated with 3 AP’s serving about 115 sm’s. It seems that one AP which is particularly affected has a greater mix of FPGA versions that anywhere else on my deployment. Frequently the SM’s take so long to respond to pings, that it would indicate that they are down. However, they never lose registration to the AP. One of my staff members lives within this community and has reported that he can see other SM’s, but at the times that I see, from our noc, that the kit is down, he gets very long ping responses, possibly indicating congestion.

The FPGA question was something that we do not hold hopes on, but something to eliminate nonetheless.

We are also investigating control slots as another avenue of thought, and also considering a bad SM, but have no real way to discover where a bad SM could be. Does anyone have any thoughts / experience on how to discover a bad SM, without getting customers to unplug the SM?



FPGA… here is get from google :slight_smile:

“Short for Field-Programmable Gate Array, a type of logic chip that can be programmed. An FPGA is similar to a PLD, but whereas PLDs are generally limited to hundreds of gates, FPGAs support thousands of gates. They are especially popular for prototyping integrated circuit designs. Once the design is set, hardwired chips are produced for faster performance.”


There are some combinations of FPGA versions, between AP and SM, that won’t work. That is, they won’t connect at all. I’m not aware of combinations that work, but may be unreliable.

Motorola recommends an AP and all its registered SMs have the same versions of software, boot code, and FPGA. All same-band APs in a cluster must be synchronized and have identical DataDown and MaximumRange settings. The ControlSlots should only be an issue at extended distances.

Thanks for the info.

I was under the impression that the control slots were to be changed to address contention issues?

I think that we may be closer to addressing the problem. The event log for two of the three AP’s showing the following entry:

File C:/ISIPPC/pssppc.250/bsps/devices/whisp/session.c : Line 3701 Drop session, unexpected luid. ESN = 00-00-00-00-00-00

- which I am assuming means that there are dead nic’s in the field.

We also have an entry on the remaining AP showing:

File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1584 Ranging Diff : FE61

- which maybe to do with the mixed FPGA versions?

To further complicate matters, we seem to have a stack dump from two of the AP’s:

TASK TASK Percent RunTime TASK Total S T A C K
NAME PRI RunTime MAX usec Preemption TaskSwitches Current High Low OVFL
IDLE 0 0 0l 0l 0l 00EFFD28 00EFFE00 00EFFA00
ROOT 175 0 0l 0l 0l 00EFEFF0 00EFF600 00EFD600
FECT 190 0 0l 0l 0l 00EFD300 00EFD400 00EFC400
PNAD 187 0 0l 0l 0l 00EFC0E0 00EFC200 00EFAE00
pshd 180 0 0l 0l 0l 00CFA510 00CFA800 00CF9E00
tnpd 181 0 0l 0l 0l 00CF9908 00CF9C00 00CF9200
TFD$ 177 0 0l 0l 0l 00CF0A90 00CF0E00 00CECE00
TFD0 177 0 0l 0l 0l 00CECAE0 00CECC00 00CE8C00
TFD1 177 0 0l 0l 0l 00CE88E0 00CE8A00 00CE4A00
TFD2 177 0 0l 0l 0l 00CE46E0 00CE4800 00CE0800
TFD3 177 0 0l 0l 0l 00CE04E0 00CE0600 00CDC600
ftpd 179 0 0l 0l 0l 00CCFD08 00CD0000 00CCF600
LEDT 199 0 54l 0l 6l 00CCF318 00CCF400 00CCE400
IDLA 76 0 0l 0l 0l 00CCE120 00CCE200 00CCD200
SESS 194 0 0l 0l 0l 00CCCF08 00CCD000 00CCB000
UPDT 79 0 0l 0l 0l 00CCACD8 00CCAE00 00CC9E00
VLAN 191 0 0l 0l 0l 00CC9B18 00CC9C00 00CC8C00
BDMT 184 0 0l 0l 0l 00CC8820 00CC8A00 00CC7A00
SOCK 193 0 0l 0l 0l 00CC74A8 00CC7800 00CC5800
COMM 192 0 0l 0l 0l 00CC5518 00CC5600 00CC3600
HTTP 77 0 0l 0l 0l 00CC30C0 00CC3400 00CC1400
SYNC 200 0 0l 0l 0l 00CC1108 00CC1200 00CC0200 X
DIAG 196 0 0l 0l 0l 00CBFF10 00CC0000 00CBF000
DOWN 198 99 329963l 6l 6l 00CBECA0 00CBEE00 00CBDE00
UPLK 197 0 0l 0l 0l 00CBDB08 00CBDC00 00CBCC00
SNMP 182 0 0l 0l 0l 00CBC488 00CBCA00 00CACA00
NTP 176 0 0l 0l 0l 00CAC700 00CAC800 00CAB800
GPSI 177 0 0l 0l 0l 00CAB510 00CAB600 00CAA600

Ay ideas where I can get this deciphered?



You should contact Motorola Canopy Technical Support. Email all the info to them, and then post the resolution on this thread. They’ll very likely have you start by upgrading all software.