Summary

Details

• Looks like gpio480 can be used to turn off all LEDs?

Helpful documentation

• Exporting LEDs: https://www.emcraft.com/som/vf6/controlling-gpio-from-linux

From here: https://forum.openwrt.org/t/hp-msm-support/82788/13

For this to work, we will need:

• A/B kernel partitions in the .dts
• To find the A/B configuration in one of the existing mtd partitions
• Differing owrt_boot instructions

We want to know how to limit the kernel size in the p1020.mk build definition Makefile for this target.

To do so:

Tasks

• Verify that booting from a compressed kernel fails (past 16M? 32M?)
• Produce the most forgiving boot instructions possible (largest kernel, though bound *that by ~24MB)
• Repeatedly pack the initramfs with crap (just dd from /dev/random into a file in the filesystem under files) until the boot instructions stop working
• Commit back relevant boundary changes to p1020.mk

See this thread for more information.

See also #4.

As it stands

Without A/B partitioning, this is just:

setenv owrt_boot_a='nand read 0x1000000 0x560000 0x2000000\; nand read 0x6000000 0x520000 0x40000\; bootm 0x1000000 - 0x6000000\;'
setenv owrt_boot_b 'nand read 0x1000000 0x560000 0x2000000\; nand read 0x6000000 0x520000 0x40000\; bootm 0x1000000 - 0x6000000\;'

# <do u-boot IP address setup>

tftpboot 0x1000000 openwrt-mpc85xx-p1020-aerohive_hiveap-370-initramfs-kernel.bin;
tftpboot 0x6000000 openwrt-mpc85xx-p1020-aerohive_hiveap-370-squashfs-fdt.bin;

bootm 0x1000000 - 0x6000000;

# ... from Linux:
# copy down the sysupgrade.bin, then
sysupgrade -v /tmp/<sysupgrade.bin>

Problem

By default, the rootfs_data partition does not automount.

Tasks

• Confirm that this fix enables automounting

Synopsis

There were concerns about making platform-wide nand.sh and sysupgrade-tar.sh changes. Since we can afford to patch u-boot now and problems like this can be surmounted, we should try gutting this code.

Tasks

• Verify FIT images are unsupported
  • Attempt to build + boot a fit image
• Build and test dtb + kernel booting
  • Produce correct u-boot command, plus partitioning in dts
• Trace nand sysupgrade code to confirm sysupgrade build process
• Test sysupgrade

Goals

• Patch /dev/mtd1 and /dev/mtd2 so that ggboot boots run_owrt_a and run_owrt_b, respectively
• Idempotent; harmless if run multiple times
• Include as a library file for the mpc85xx target, included with OpenWrt so the initramfs can do its job

TODOs left:

• Organize commit message better
• Trace LED GPIO ordering on the GPIO expander

See https://forum.openwrt.org/t/create-firmware-for-ruckus-r700/133484

Checklist

• Booting
  • How does the OEM device boot?
    • Q: What's the output of help in u-boot?
      • #23 (comment)
    • Q: What's the output of printenv in u-boot? (please scrub MACs and serials, etc.)
      • [Where's the link?]
    • Sounds like from the above, we know the OEM device uses SPI flash -- not memory-mapped on this platform -- and so uses sf to start the SPI flash subsystem and copy stuff out of it into RAM before booting. This, combined with the absence of a bootcmd, strongly suggests we'll find the stock boot commands in the strings in the original flash dump. So:
    • TODO: Dump flash and strings | grep -we sf through it to find the scripts it runs on boot.
    • Do we know of other Ruckus boards that use u-boot? Are there special OpenWrt workarounds for this?
  • Device tree
    • TODO: We'll start by copying another P1010-like from under target/linux/mpc85xx/files/arch/powerpc/boot/dts on the main branch, and beginning to edit the partition list under {lbc:nor@0,0:partitions} (or equivalent -- there is more than one way to create a device tree that the kernel can use to find its rootfs.)
• Wireless
  • Calibration?
    • This board almost certainly uses on-flash calibration data because
      • TODO: Confirm the calibration data is in flash.
    • See https://github.com/rsa9000/atheepmgr for C code which can decode calibration data files.
      • In ath9k world, calibration data sits in a single 0x10000 page, at 0x1000 and 0x5000 for 2.4 and 5GHz, respectively.
      • In ath10k ... not so sure. Worth checking atheepmgr or (more importantly) other ports which must load calibration data to run the ath10k cards.

GPIO

OK, J4 is this:
 1 - GPIO 0 / LED 2 / POWER
 2 - +V / LED
 3 - GPIO 1 / LED 3 / ETHERNET
 4 - +V / LED
 5 - GPIO 2 / LED 4 / WIRELESS 1
 6 - +V / GPS (on prototype)
 7 - GPIO 3 / LED 5 / WIRELESS 2
 8 - +V / GPS (on prototype)
 9 - GPIO 11
10 - GND / GPS (on prototype)
11 - HRESET (Reset Button)
12 - +V / GPS / Reset Button Input
13 - GPIO 12
14 - GND / GPS
15 - GPIO 13
16 - GND / GPS
On J2, what I have verified with tracing so far is this:
 1 - TDO
 3 - TDI
 7 - TCK
 9 - TMS
11 - SRESET
15 - CKSTP_OUT0

See e.g. the same function which patches the AP370.

Other details

• User 'neggles' on #openwrt-devel on OFTC IRC mentions the AP370 u-boot patching process works on the AP330 with some changes.

Hardware needed

• BDI2000/C
  • In-hand
  • Power supply
    • 5v, spliced to a 2x2 pinout; see this diagram:
  • Null-modem serial cable
    • Probably check the eWaste bin at the Lab.
  • 2x8 pin ribbon cable, e.g. this link
    • Glue back together the hacked one I have
    • Continuity-test that it works
    • Test whether the hardware actually pins into the BDI2000/C
  • Re-flashed to 85xx firmware
    • Hardware reflash
    • Logic reflash
      • Stuck on this latter one: not sure how the logic is to be reflashed. Maybe by starting up bdiGDB?
  • Test the BDI2000/C

Software needed

• Compile U-boot for the MSM466
  • Compile U-boot at all
    • See this Dockerfile.
  • Analyze existing NAND to determine U-boot format and positioning
  • Attempt to load onto MSM466
    • What format will this use?
      • See the P1011/P1020 Reference Manual, and or the fohdeesha JTAG page.

ath79 is by default on kernel 5.10 since https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=15aa53d7ee6537d64a32c0d5bd728582f71d5c99.

Tasks

• Test own-built ath79: https://downloads.laboratoryb.org/releases/snapshot/targets/ath79/generic/
• Test OpenWrt-built ath79: https://downloads.openwrt.org/snapshots/targets/ath79/generic/