The serial port is J10, on the left of the switch chip, [[#​photos|see photos]]

+

+

| 6 | GND | RX | 5 |

+

| 4 | GND | Vcc (3.3V) ​ | 3 |

+

| 2 | GND | TX | 1 |

+

+

Serial connection parameters are 115200 8N1

+

+

**NB:** A short circuit between pins ''​RX''​ and ''​TX''​ at power up puts the device in a recovery mode with IP ''​192.168.1.1''​ from where a new firmware can be uploaded. ​ OpenWrt binaries are refused, though, because of invalid CRC.

+

+

==== JTAG ====

+

Jtag port is J9 near the SoC and the minipci socket, [[#​photos|see photos]]

+

+

It seems to be a mips e-jtag 14 pin connector with columns swapped (used from the other side?).

+

+

| 14 | DINT ​| ​ VREF | 13 |

+

| 12 | SRST_N ​ ​| ​ GND | 11 |

+

| 10 | TCK | GND | 9 |

+

| 8 | TMS | GND | 7 |

+

| 6 | TDO | GND | 5 |

+

| 4 | TDI | GND | 3 |

+

| 2 | TRST_N ​ ​| ​ GND | 1 |

+

+

CPU Chip ID: 00000110001101011000000101111111 (0635817F)

+

+

I used the JTAG port with [[http://​urjtag.org|urjtag]],​ just use the svn version. Useful info on [[http://​www.neufbox4.org/​wiki/​index.php?​title=Interface_JTAG|"​Neuf Box 4 JTAG" ]]

+

+

You should probably try the [[http://​openocd.berlios.de/​web/​|Open On-Chip Debugger]]

+

+

Install OpenWrt on this router :-)

+

+

===== Requirement to install OpenWrt =====

+

+

To install OpenWrt you have to stop the system loading through the serial console. ​

+

To do that you need a serial adapter/​converter (that convert TTL +3.3V of router serial console to RS232 (+/-12V) or USB).

+

I suggest to use USB serial converter!! Don't even try to go further without a serial adapter!!

**squashfs** is a filesytem that have system files readonly. more stable and less problems. you cannot destroy importan file

+

+

**jffs2** is a file system completly writable. more powerfull but you can destroy system files.

+

+

To start as novice I sugegst to use squasfs firmwares.

+

+

Skip the jffs2 with 64k erase block as the flash use 128k block, anyway using 64k should not give much problem, just some wasted space and some errors messages. Put the chosen image in the right place (see your tftp server configuration),​ and go to the CFE prompt.

Through the serial console and a terminal program (like Hyperterminal,​ Putty portable, Teraterm) setup as 115200, 8 bit data, no parity bit, 1 stop bit, poweron the router and press any key to stop the system loading.

+

+

==== Flash the new firmware via TFTP =====

+

+

__I suggest to rename the firmware file downloaded as **firmware.bin**__

+

+

Now you have to use the //​flashimage//​ command to load the openwrt image, please don't use the //f// command. If you configure (with command //c//) the host ip address you can avoid it in the //​flashimage//​ argument.

+

<​code>​

+

CFE> flashimage

+

+

eg. flashimage [hostip:​]compressed_image_file_name

+

or

+

es: flashimage 192.168.1.100:​firmware.bin

+

or

+

es: flashimage firmware.bin ​

+

</​code>​

+

+

That's all, the device will automatically reboot and openwrt will be there :-)

A226m has a Le88266 VoIP chip onboard providing 2x FXS ports (= 2x ports you can connect analog phones to in order to make calls leveraging VoIP). This functionality is not natively available in OpenWrt, it requires additional drivers. There is an opensource project, called //​bcm63xx-phone//​ [[https://​github.com/​pgid69/​bcm63xx-phone]],​ providing these drivers, and I managed to compile and make it work on this router in combination with Asterisk, tested on both Attitude Adjustment and Barrier Breaker.

+

The developer of the driver directly tested it on a Huawei box, but it also works on A226M. ​

+

There is no ipk package available at the moment, so you need to compile your own .ipk's package or include them in the image of openwrt. Once you do this, you will be able to connect an analog phone to the FXS ports and leverage it in combination with a cheap VoIP service provider.

+

+

If you choose to compile the .ipk's and try to install them on a ready-available openwrt image form repository, be aware that opkg might complain about kernel version not being exaclty the same. Just force installation and it should work.

+

I was able to make phone calls originating from an analog phone connected to the A226M and routed to a VoIP provider using SIP signalling and Asterisk as call manager.