Skip to content
This repository was archived by the owner on Mar 18, 2020. It is now read-only.

Prototype measurement ideas

Jump to bottom
spiccinini edited this page May 16, 2019 · 1 revision

Priorities:

Basic requirement does not include dual booting, Marek will take care of the patches for dual booting

bootloader:

  • flash via network/tftp (ap51-flash?)
    • Timeout length to begin network flash ?
    • Flash IP address ?
    • ARP header 'hack' for device identification ?
  • dual partitions
    • Does switching partitions work ?
    • Can both partitions be booted properly ?
    • Can the kernel size be adjusted ?
  • mac address
    • Where is the mac address stored ? uboot env ? ART ?
    • How many mac addresses do we assign per device ? 4 = 1 per radio, and 1 for ethernet (aren't the ethernet ports one device each?)
    • Who supplies the mac addresses ? Dragino ?
    • Does uboot read the mac address correctly ?
    • What does uboot do if the defined destination does not contain a proper mac address (00:00:00:00:00:00 or mac[0] & 0x01) == 0x01) ?

hardware watchdog:

  • Does the device reboot after specified interval (5 min?) after the keep- alive was killed ?
  • Does the device keep running more than 5 mins with the keep-alive working properly ?
  • Can the hardware watchdog ever be disabled via software?
  • Can the hardware watchdog be disabled via hardware? (remove a 0k resistor)

ethernet:

  • link speed negotiation

    • test various links speeds (10/100/1000) with uboot vs Openwrt (see link speed attachment)
    • correct auto-negotiation when connected to various switches
    • test with normal vs passive poe input power

  • VLAN / QinQ tests + ucast/mcast/bcast tests

  • max frame size

  • max throughput (bridge 2 or more ethernet ports)

  • test internal pin headers ?

  • what happens if passive PoE input is plugged into secondary ethernet port (that normally does passthrough)?

    • what happens in this situation if pass through is enabled

  • what about having an SGMII header instead of magnetics and the pin-header for two copper ports?

Wifi:

  • Where is the calibration data stored (one per phy needed) ?
  • Regulatory domain data for Argentina ? (tanzania hacked by default? - ask Pau)
  • Measure max TX power per chain ?
  • Does max TX power vary depending on the channel used?
  • Measure power consumption (see power consumption attachment) ?
  • Max WiFi throughput per phy ?
  • Max WiFi throughput from 5GHz to 5GHz ?
  • Max throughput with all WiFi interfaces running ?
  • Does any part of the board get too hot when TX? (suggesting a problem)

leds:

  • Are all leds software (GPIO) controllable ?
  • Can all software controllable leds be properly turned on/off separately and in combination ?

AR9558 serial console:

  • Attach serial console while using the device normally. Sometimes, the device does not boot with the serial connected or an led might never go off or ... -> tested, works.

passive PoE:

  • Compatible with commercial passive poe injectors / switches (ToughSwitch) ?
  • Max cable length (expected 100m) ?
  • Is passive PoE power input sufficient to power 3 WiFi radios and USB ?

PoE passthrough:

  • is it by default disabled, at all times since the very first stage of boot?
  • test softare control (enable/disable)

reset button:

  • Does the button trigger an event ?

USB:

  • Test reading from USB hard drive
  • Measure power consumption with USB attached ?
  • 0.5A USB out ?
  • Can USB port be deactivated via software to reduce power consumption ?
  • When there's 2.5W being drawn from USB port, and all radios are TX at full power, does the device reboot or hang?

Housing:

  • Waterproof ?
  • UV rating ?

stress test:

  • one wifi client per phy + ethernet attached
  • run: iperf -B 192.168.2.227 -c 224.0.0.1 -t 28800 -u -b 80M <-- this is a multicast test, meant to be done with mcast_rate=1M, so that the radio continuosly transmits, and doesn't carrier sense.
  • Does the device survive this stress for 2+ hours ?
  • Inside the housing ?
  • receiving an iperf over one 5ghz radio and sending another over the other 5ghz radio

XBee expansion socket:

auxiliary module header:

  • Test motherboard power can be controlled through the power line in this header

TVWS pin header:

  • it's only a fallback
  • patch the ath9k driver to make the pin react to packets being sent = gpio line going up and down

GPIO pin header:

  • can you connect all the modules at the same time?

  • can you plug all the cables at the same time?

  • Do all the GPIOs pins work as expected?

  • after all tests, with a lab power supply, check the actual input voltage operating range (12v to 24v). Probably destroy the device.

Calibration partition:

  • Include reasonable tables for regulatory domains [CTL table, Calibration table, ]

Clone this wiki locally