Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:aerohive:hiveap-330 [2022/02/16 21:49] – [Photos] added PCB Top and Bottom Side chunkeey | toh:aerohive:hiveap-330 [2022/02/19 18:32] – [Snapshot Releases] new method chunkeey | ||
|---|---|---|---|
| Line 83: | Line 83: | ||
| * This entry will be updated once the device boots with the 5.10 snapshots again. | * This entry will be updated once the device boots with the 5.10 snapshots again. | ||
| - | Connect your PC's ethernet port to the RJ45 port labeled " | ||
| - | Open the serial connection (9600, 8N1) and power on the AP121. | + | |
| + | 1. setup a network with a tftp server | ||
| + | |||
| + | Start a tftp server at serverip (192.168.1.101) with the initramfs image in the servers root tftp directory. Having a dhcp server is advantageous. However static IPv4s can be set in the uboot environment later on. | ||
| + | |||
| + | 2. setup console port and pass uboot login challenge | ||
| + | |||
| + | The AP has a serial port on the RJ45 port labeled " | ||
| When you see '' | When you see '' | ||
| - | Now is a good time to confirm your bootloader version. Issue the command | + | 3. confirm uboot is supported |
| + | |||
| + | confirm your bootloader version. Issue the command | ||
| < | < | ||
| version | version | ||
| </ | </ | ||
| - | ... | + | Check if the version listed there matches one of the supported uboot version. |
| + | |||
| + | 4. setup IPv4 connection | ||
| + | |||
| + | If you are using dhcp, you can just enter '' | ||
| + | set you up with an ipv4. | ||
| + | |||
| + | If you are going the static assignment route. You have to set your IPv4 Address by | ||
| + | entering: '' | ||
| + | this IP isn't already taken by another device). | ||
| + | |||
| + | 5. upload initramfs firmware | ||
| + | |||
| + | The next step is to transfer the OpenWrt binary to the HiveAP-330' | ||
| + | The method depends on what release you want to install. | ||
| + | |||
| + | ==== Snapshot Releases ==== | ||
| + | |||
| + | If you start out fresh you can preemptively set the new openwrt boot command. | ||
| + | For this to work, the uboot has to be modified (which we do in a later step). | ||
| + | Otherwise, the stock uboot will always use a internal bootcmd that can't be | ||
| + | overwritten and it won't boot the sysupgraded'/ | ||
| + | |||
| + | < | ||
| + | setenv owrt_boot ' | ||
| + | save | ||
| + | </ | ||
| + | |||
| + | To boot the initramfs, enter the following commands into uboot' | ||
| + | < | ||
| + | setenv bootargs console=ttyS0, | ||
| + | tftpboot 1000000 192.168.1.101: | ||
| + | bootm | ||
| + | </ | ||
| + | |||
| + | 6. Once OpenWrt booted: | ||
| + | carefully copy and paste this into the root shell. One step at a time. | ||
| + | |||
| + | 6.1 install kmod-mtd-rw from the internet and load it | ||
| + | |||
| + | opkg update; opkg install kmod-mtd-rw | ||
| + | insmod mtd-rw i_want_a_brick=y | ||
| + | |||
| + | 6.2 create scripts that modifies uboot | ||
| + | |||
| + | cat <<- " | ||
| + | . / | ||
| + | cp "/ | ||
| + | cp /tmp/uboot / | ||
| + | ofs=$(strings -n80 -td < /tmp/uboot | grep '^ [0-9]* setenv bootargs.*cp\.l' | ||
| + | for off in $ofs; do | ||
| + | printf "run owrt_boot; | ||
| + | done | ||
| + | md5sum / | ||
| + | EOF | ||
| + | |||
| + | 6.2 run the script to generated a patched uboot | ||
| + | |||
| + | sh / | ||
| + | |||
| + | The script will print out three md5sums to verify that /tmp/uboot and / | ||
| + | |||
| + | For reference: my md5sum looked like this | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | 6.3 flash the patched uboot | ||
| + | |||
| + | mtd write / | ||
| + | |||
| + | This uboot runs the bootcommand in the // | ||
| + | editing this uboot environment variable. | ||
| + | |||
| + | 7. permanent installation | ||
| + | |||
| + | If you have LuCI (included in Releases), you can now load up LuCI at 192.168.1.1, | ||
| + | |||
| + | If you don't have LuCI, you have to copy over the sysupgrade file via SFTP/ | ||
| + | ==== (Downgrade) to Releases older or equal to 21.02 ==== | ||
| + | |||
| + | If you are downgrading from a later snapshot release: You need to set and save the original boot command parameters that were used before the re-partitioning of the device: | ||
| + | < | ||
| + | setenv owrt_boot " | ||
| + | save | ||
| + | </ | ||
| + | |||
| + | To run the installation enter the following commands in uboot: | ||
| + | < | ||
| + | tftpboot 0x1000000 192.168.1.101: | ||
| + | tftpboot 0x6000000 192.168.1.101: | ||
| + | bootm 0x1000000 - 0x6000000; | ||
| + | </ | ||
| + | |||
| + | Once OpenWrt boots and you have LuCI (included in Releases), you can now load up LuCI at 192.168.1.1, | ||
| + | If you don't have LuCI, you have to copy over the sysupgrade file via SFTP/ | ||
| ===== Troubleshooting/ | ===== Troubleshooting/ | ||