Please see template_device to update and finish this wiki.

NOTE: The FCC documentation is available here

→Flash Layout has an example flash layout and all explanations required to understand this. Here the naked hex-values for the WZR-HP-AG300H:

→ cf. oem.installation.using.the.tftp.method with more precise values (4 sec), etc. Merge both to obtain one really good procedure description

NOTE #1: The bootloader of the WZR-HP-AG300H has a very short time frame in which it will accept a new firmware transfer over TFTP: it is about 4 sec long approximately 10-20 sec after powering it on The usable time window gets even shorter when your OS starts negotiating the network connection before it allows you to send data over it. And your OS is going to do that every time, when the other device gets powered on! So to be able to use the entire time span available you need to put a switch between the router and you host machine. In case you do not have a switch, in Windows try turning off Media Sensing and in Linux prefer a static network configuration over the NetworkManager. It is further recommended to make a static ARP entry for the router. Users have found that 'smart' or managed switches sometimes will not allow flashing even with static arp entries sometimes- the simplest switch is the best to use. Here is a link to the console output of the boot process, with all led's in view for reference http://www.youtube.com/watch?v=mAZNTKhpHig. Finally, you must also set your TFTP timeout to something very short (1 second). The default (varies between TFTP clients) is most likely higher than the TFTP window so it will never work. NOTE #2: As the Windows stack can interfere with the process, see forum post, it is recommended to use some Linux to perform the upload! FYI: The OEM version of uboot on the AG300H always uses the IP address 192.168.11.1 and the MAC address 02:aa:bb:cc:dd:20 when listening for a new firmware. It also expects the sending IP address to be 192.168.11.2. Values belong to the bootloader and are independent of the ones used by OEM firmware or OpenWrt! The computer used for the install must be connected to the LAN port on the router closest to the WAN port. On my device this is labeled LAN 4, and it corresponds to port 0 per the information below.

1. Download a suitable OpenWrt firmware image, e.g. Latest Trunk (NOTE: Name must contain "tftp")
2. Install a TFTP client, when running some Linux distribution, do e.g.

   sudo apt-get update
   sudo apt-get install tftp

3. Connect the AG300H with some network switch and that switch with your host machine. Leave the AG300H powered off.
4. Prepare the interface of your PC:

   sudo ifconfig eth0:1 192.168.11.2
   sudo arp -s 192.168.11.1 02:aa:bb:cc:dd:20

5. Now you must be quick. Type in

   tftp -m binary 192.168.11.1 -c put openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-tftp.bin

   and immediately after hitting enter
6. power on the AG300H!
7. If the red "DIAG"-LED begins to flash rapidly then the router has received the image and is currently booting the new firmware.
8. Follow the First Login steps to complete installation.

• Connect to the WebInterface at http://192.168.11.1 and go to "Administration" → "Firmware Upgrade"
• Upload the OpenWrt-Image you want to install, e.g. the latest factory trunk version
• Make your PC obtain a new IP address from OpenWrt (dhclient eth0 or pump -i eth0)
• proceed with basic.config to complete installation

→ generic.sysupgrade

→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

→ generic.failsafe

If you want to trigger a LED as soon as an USB-Device is connected to your USB-Port, add this to /etc/config/system:

This switches on the little red circle of the DIAG-LED everytime you connect something to your USB-Port.

• It's very unlikely that you completely bricked the device, so first try the TFTP Method above. Note that a red diagnostics light blinking twice means your flash failed, but the device is ok and tftp will work (keep trying). If you still get nowhere, more drastic measures:

→ generic.debrick

→ hardware.button on how to use and configure the hardware buttons.

root@OpenWrt:~# lspci -vv
00:11.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)
	Subsystem: Atheros Communications Inc. Device a097
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 168, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 72
	Region 0: Memory at 10000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] <chain broken>
	Kernel driver in use: ath9k

00:12.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)
	Subsystem: Atheros Communications Inc. Device a096
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 168, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 73
	Region 0: Memory at 10010000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: ath9k

A collection of photos on how to open the case, of the PCB and the serial port can be found on https://picasaweb.google.com/111743287730172647732/BuffaloWZRHPAG300HHardwarePhotos .

PCB

→ port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:

1. Open case
2. Locate serial port pads next to the Movie Engine switch
3. Pinouts beginning from the square pad: vcc, gnd, tx, rx
4. Sends at 115200 8N1 as shipped
5. Voltage is 3.3 V

For some Help with the Tags, please have a look here: tags