Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
wiki:contributors:taylorkline [2024/04/03 02:06] – OKD draft taylorklinewiki:contributors:taylorkline [2024/04/03 15:53] – OKD draft taylorkline
Line 42: Line 42:
   * Hook up your USB to TTL serial adapter to the RT3200 / E8450 **with the power off**   * Hook up your USB to TTL serial adapter to the RT3200 / E8450 **with the power off**
     * remember that tx from router needs to go to rx of uart connector, and rx of router needs to go to tx of uart connector ((thanks forum member smashrvmco for the reminder))     * remember that tx from router needs to go to rx of uart connector, and rx of router needs to go to tx of uart connector ((thanks forum member smashrvmco for the reminder))
-  * Run the mtk_uartboot program with your downloaded files, followed by an **immediate** screen or putty command, e.g.: <code>mtk_uartboot -a -p bl2-for-mtk_uartboot.bin -f *uboot.fip && screen /dev/ttyUSB0 115200</code> or <code>mtk_uartboot -a -p bl2-for-mtk_uartboot.bin -f *uboot.fip && putty.exe -serial COM5 -sercfg 115200,8,n,1,N</code>+  * Run the mtk_uartboot program with your downloaded files, followed by an **immediate** screen or putty command. Below are some examples: 
 +    * Linux, when `mtk_uartboot` automatically recognizes the connected serial device: <code>mtk_uartboot -a -p bl2-for-mtk_uartboot.bin -f *uboot.fip && screen /dev/ttyUSB0 115200</code> 
 +    * macOS, when `mtk_uartboot` would otherwise use the wrong serial device: <code>./mtk_uartboot -a -p bl2-for-debug-snand-issue.bin -f openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip -s /dev/cu.usbserial-B002EI6Z && screen /dev/cu.usbserial-B002EI6Z 115200</code> 
 +    * <code>mtk_uartboot -a -p bl2-for-mtk_uartboot.bin -f *uboot.fip && putty.exe -serial COM5 -sercfg 115200,8,n,1,N</code>
   * Power on the RT3200 / E8450   * Power on the RT3200 / E8450
-  * mtk_uart should trigger a boot and your screen / putty session should present you with a U-Boot menu. If you take no action for a number of seconds, your router will boot. To recover, **you want to immediately press any key (like a down arrow) to interrupt the boot and stay on the boot menu**.+  * mtk_uart should trigger a boot (if you never get past <code>Handshake...</code>, you have the wrong serial device selected, don't have a good serial connection, or - and this is the case for many people - your serial adapter may not be compatible and you should try another if your attempts fail repeatedly) and your screen / putty session should present you with a U-Boot menu. If you take no action for a number of seconds, your router will boot. To recover, **you want to immediately press any key (like a down arrow) to interrupt the boot and stay on the boot menu**.
   * From the boot menu, select the bottom option, U-Boot Console.   * From the boot menu, select the bottom option, U-Boot Console.
-    * {{ :media:openwrt-boot-menu.png?direct&200 | OpenWrt Boot Menu }}+    * {{ :media:openwrt-boot-menu.png?direct&600 | OpenWrt Boot Menu }}
   * Rewrite the flash ("As crazy as it sounds, but literally reading from the flash and writing back the read content fixes the issue."), based on your OpenWrt version   * Rewrite the flash ("As crazy as it sounds, but literally reading from the flash and writing back the read content fixes the issue."), based on your OpenWrt version
     * Did **not** run the v1.1.1 UBI installer (e.g. anyone on OpenWrt 23.05.x or below, or older snapshots)     * Did **not** run the v1.1.1 UBI installer (e.g. anyone on OpenWrt 23.05.x or below, or older snapshots)
  • Last modified: 2024/04/03 16:02
  • by taylorkline