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:astoria:arcadyan_astoria_easybox_904xdsl_r01 [2018/03/04 10:42] – ↷ Page moved from inbox:arcadyanastoria:arcadyan_astoria_easybox_904xdsl_r01 to toh:astoria:arcadyan_astoria_easybox_904xdsl_r01 bobafetthotmail | toh:astoria:arcadyan_astoria_easybox_904xdsl_r01 [2024/10/25 15:49] – [OpenWrt support] zuzia | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Arcadyan / Astoria Easybox 904xDSL ====== | + | ====== Arcadyan/ |
| - | | {{page> | + | {{page> |
| - | This device is produced by Arcadyan/ | + | This device is produced by Arcadyan/ |
| + | |||
| + | There' | ||
| + | At the time of writing (May/2019) two different HW versions, R01 and R02 exist. Whilst the hardware looks similar, OpenWrt works on both. | ||
| /*****/ | /*****/ | ||
| - | /* How to add images ========> | + | /* How to add images ========> |
| /*****/ | /*****/ | ||
| - | {{:media: | + | {{media: |
| Line 16: | Line 19: | ||
| <color red> | <color red> | ||
| - | Most things work (VDSL vectoring, display, | + | At the moment (October/ |
| + | For the device itself ([[https:// | ||
| + | The device is a little bit outstanding from other lantiq xrx200 devices, for this reason, the development is never over and this page is most of the time not at the current state. | ||
| + | For the current state of developing see this thread: [[https:// | ||
| + | |||
| + | Most things work (VDSL vectoring, display, | ||
| - | Development, | + | The majority |
| - | ===== LEDE support ===== | + | |
| - | Most of things works: | + | |
| * Switch | * Switch | ||
| * USB | * USB | ||
| * ADSL (Annex B and J tested) | * ADSL (Annex B and J tested) | ||
| * VoIP | * VoIP | ||
| - | * WiFi (Basic AP only, connected to vlan 66, needs to be configured through / | + | * Wi-Fi (Basic AP only, connected to VLAN 66, needs to be configured through / |
| * LCD and touchkeys (LCD4Linux is installed as basic status information board). | * LCD and touchkeys (LCD4Linux is installed as basic status information board). | ||
| ===== Supporting activities ===== | ===== Supporting activities ===== | ||
| - | * OpenWrt forum thread(LTE version thread but much helpful information there): https:// | ||
| + | * Old OpenWrt forum thread (LTE version thread but much helpful information there): [[https:// | ||
| + | * New OpenWrt forum thread: [[https:// | ||
| + | * Easybox 904xDSL new build: [[https:// | ||
| + | * Small Recovery images with GUI: [[https:// | ||
| + | * New release OpenWrt version v21.02.07 on GitHub: [[https:// | ||
| - | /*** if info available: uncomment and fill in | ||
| - | ===== Experimental firmware ===== | ||
| - | |||
| - | //List experimental firmware download links here.// | ||
| - | |||
| - | //None at this time.// | ||
| - | |||
| - | * External image (add link) | ||
| - | * trunk image (add link) | ||
| - | * ... | ||
| - | ***/ | ||
| ===== Hardware highlights ===== | ===== Hardware highlights ===== | ||
| - | ^ CPU ^ Ram ^ Flash | + | ^ CPU |
| - | | MIPS32 34Kc @ 500 MHz | + | | MIPS32 34Kc @ 500 MHz |
| - | + | ===== OpenWrt firmware image build ===== | |
| - | ===== Installation | + | |
| - | + | ||
| - | → [[downloads|Obtain firmware]] | + | |
| **Building a new OpenWrt firmware image is possible with few steps:** | **Building a new OpenWrt firmware image is possible with few steps:** | ||
| - | |||
| - | This is mainly taken from the eb904lte forum thread and the description of member stefan-koch. | ||
| < | < | ||
| - | $git clone git://git.openwrt.org/ | + | git clone https://github.com/ |
| - | $cd openwrt | + | ./scripts/feeds update -a |
| - | $wget http://arny.tjps.eu/OpenWrt/EasyBox904xDSL/devel/v0.1-EasyBox904xDSL.patch | + | ./scripts/feeds install -f |
| - | $patch | + | ./scripts/feeds install -a |
| - | $make defconfig | + | cp .config-VPE .config #or .config-SMP |
| - | $make prereq | + | cp -R files-VPE files #or files-SMP |
| - | $make menuconfig | + | make menuconfig |
| - | $make | + | make |
| </ | </ | ||
| - | Then in bin/lantiq/ are two important | + | Then in bin/targets/lantiq/xrx200 |
| - | * '' | + | * '' |
| - | * '' | + | * '' |
| + | ===== Installing OpenWrt 21.02.07 the easy way ===== | ||
| - | → [[doc:howto: | + | **Prerequsites:** |
| + | * PC running TFTP server at 192.168.2.100 | ||
| + | * Easybox 904 xDSL | ||
| + | **Required files with support VPE (VoIP):** | ||
| + | * Recovery system VPE [[https:// | ||
| + | * OpenWrt 21.02.07 VPE [[https:// | ||
| + | **Required files with support SMP (2 Cores CPU):** | ||
| + | * Recovery system SMP [[https:// | ||
| + | * OpenWrt 21.02.07 SMP [[https:// | ||
| - | ==== Installing OpenWrt ==== | + | **This is very important: |
| + | * Copy fullimage.img-VPE or fullimage.img-SMP as fullimage.img to the tftp server (e.g. TFTPD64) which listens on IP address 192.168.2.100. | ||
| - | ---- | ||
| - | |||
| - | **Flashing OpenWrt over opened firmware image** | ||
| - | |||
| - | This is mainly taken from the eb904lte forum thread and the description of member stefan-koch. | ||
| - | |||
| - | * Download the opened vendor Firmware-Image: | ||
| - | * And install it via the rescue mode [[http:// | ||
| - | * Then boot the box with an connected usb stick that includes a 0 byte text file named ' | ||
| - | * Set an password via the web interface (192.168.2.1 | ||
| - | * Then power off the box, remove then the usb stick | ||
| - | * Power on the box again | ||
| - | * Now connect via ssh and the setted password: | ||
| - | |||
| - | < | ||
| - | $ssh root@192.168.2.1 | ||
| - | </ | ||
| - | * connect another usb stick with the rootfs and kernel files and go to these data dir: | ||
| - | < | ||
| - | $cd /tmp/usb/a1 | ||
| - | </ | ||
| - | * Write kernel to nand | ||
| - | < | ||
| - | $flash_eraseall /dev/mtd2 | ||
| - | $nandwrite -p /dev/mtd2 openwrt-lantiq-xrx200-VGV952CJW33-uImage | ||
| - | </ | ||
| - | * write rootfs to nand | ||
| - | < | ||
| - | $umount / | ||
| - | $flash_eraseall /dev/mtd12 | ||
| - | $nandwrite -p /dev/mtd12 openwrt-lantiq-xrx200-VGV952CJW33-squashfs-ubinized.bin | ||
| - | </ | ||
| - | * boot the device again | ||
| - | < | ||
| - | $reboot | ||
| - | </ | ||
| - | |||
| - | |||
| - | ==== Installing LEDE ==== | ||
| - | |||
| - | ---- | ||
| - | |||
| - | **Prerequsites: | ||
| - | * PC running TFTP server at 192.168.2.100 | ||
| - | * Easybox 904 xDSL | ||
| - | |||
| - | **Required files:** | ||
| - | * LEDE fullimage [[https:// | ||
| - | * LEDE sysupgrade.bin [[https:// | ||
| **Steps:** | **Steps:** | ||
| - | - Prepare TFTP server (e.g. TFTPD32) by putting fullimage.img in server directory. | + | - Prepare TFTP server (e.g. TFTPD64) by putting fullimage.img in server directory. |
| - Image must have name " | - Image must have name " | ||
| - Connect device to computer with one of four LAN ports. | - Connect device to computer with one of four LAN ports. | ||
| Line 140: | Line 95: | ||
| - Box will download and flash image. After successfull flash, LCD will show message to shutdown and restart router. | - Box will download and flash image. After successfull flash, LCD will show message to shutdown and restart router. | ||
| - Turn device off and on again. | - Turn device off and on again. | ||
| - | - After some time it will boot to LEDE sysupgrade interface at 192.168.1.1. | + | - After some time it will boot to OpenWrt |
| - | - Using this interface, upload sysupgrade.bin | + | - Using this interface, upload |
| - | - After succesfull flash router will reboot into full LEDE image. | + | - Upgrade firmware via LuCI or command line: \\ < |
| - | - (Optional) install bootloader without password | + | - After succesfull flash router will reboot into full OpenWrt |
| + | - You need to wait about two minutes. Then you can connect to the router either with a browser - http:// | ||
| + | - (Optional) install bootloader without password. | ||
| + | NOTICE: WLAN works in AP mode only. Wi-Fi is active, WPA2+AES is set as encryption. | ||
| + | Network 5 GHz - SSID: EasyBOX-5GHz | ||
| + | Network 2.4 GHz - SSID: EasyBOX-2GHz | ||
| + | Default password: WiFipassword | ||
| + | Change your password (only via the console). | ||
| + | |||
| + | **More information and files:** | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| ===== Installing hacked bootloader ===== | ===== Installing hacked bootloader ===== | ||
| - | |||
| - | ---- | ||
| Default uboot has unknown password. This way we will install uboot with password check removed (it will accept any) | Default uboot has unknown password. This way we will install uboot with password check removed (it will accept any) | ||
| and uboot-env won't be overwritten on each boot (It does this only to increase the recovery value - The firmware reads this value | and uboot-env won't be overwritten on each boot (It does this only to increase the recovery value - The firmware reads this value | ||
| - | and resets it to 0 on each boot if this value is higher than 4, see [[https:// | + | and resets it to 0 on each boot if this value is higher than 4, see [[https:// |
| **Prerequsites: | **Prerequsites: | ||
| - | * Hacked uboot files [[https:// | + | * Hacked uboot files [[https:// |
| + | * Backup link: [[https:// | ||
| **Steps:** | **Steps:** | ||
| - Download hacked uboot file. Extract it to pendrive or upload it to router other way. | - Download hacked uboot file. Extract it to pendrive or upload it to router other way. | ||
| - Double check on router that you have this file accessible. If not, you may brick your device. | - Double check on router that you have this file accessible. If not, you may brick your device. | ||
| - | - Erase flash partition and write new uboot image: | + | - Erase flash partition and write new uboot image\\ < |
| - | < | + | |
| flash_eraseall /dev/mtd0 | flash_eraseall /dev/mtd0 | ||
| nandwrite -p /dev/mtd0 u-boot.lq | nandwrite -p /dev/mtd0 u-boot.lq | ||
| Line 168: | Line 133: | ||
| ===== Debricking ===== | ===== Debricking ===== | ||
| - | -> [[doc:howto: | + | -> [[docs:guide-user: |
| The device can be easily de-bricked. Connect to the device with an serial adapter, shortcut the 2 pins labeled R148 on the backside of the pcb and power on the device to get UART mode. | The device can be easily de-bricked. Connect to the device with an serial adapter, shortcut the 2 pins labeled R148 on the backside of the pcb and power on the device to get UART mode. | ||
| Line 175: | Line 140: | ||
| ---- | ---- | ||
| PCB with R148 marked red with arrow | PCB with R148 marked red with arrow | ||
| - | {{ :media: | + | {{ media: |
| Line 184: | Line 149: | ||
| Download the modified bootloader | Download the modified bootloader | ||
| < | < | ||
| - | $cd | + | cd |
| - | $mkdir tmp | + | mkdir tmp |
| - | $cd tmp | + | cd tmp |
| - | $wget http:// | + | wget http:// |
| - | $unzip 904xdsl-uboot-maybe-no-passwd.zip | + | unzip 904xdsl-uboot-maybe-no-passwd.zip |
| - | $cd 904xdsl-uboot-maybe-no-passwd | + | cd 904xdsl-uboot-maybe-no-passwd |
| </ | </ | ||
| Open another terminal window and connect to serial console. I assume that the adapter is '/ | Open another terminal window and connect to serial console. I assume that the adapter is '/ | ||
| < | < | ||
| - | $screen / | + | screen / |
| </ | </ | ||
| Line 202: | Line 167: | ||
| Now the bootloader has to be copied on the device. This will be done from the first console window. | Now the bootloader has to be copied on the device. This will be done from the first console window. | ||
| < | < | ||
| - | $cat u-boot.asm > / | + | cat u-boot.asm > / |
| </ | </ | ||
| Line 209: | Line 174: | ||
| The best idea in case the device is bricked would be to flash u-boot.lq. Transfer it with tftp to the device. | The best idea in case the device is bricked would be to flash u-boot.lq. Transfer it with tftp to the device. | ||
| - | |||
| - | |||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| ===== Failsafe mode ===== | ===== Failsafe mode ===== | ||
| - | -> [[doc:howto:generic.failsafe]] | + | -> [[docs:guide-user:troubleshooting: |
| ***/ | ***/ | ||
| Line 221: | Line 184: | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| ===== Basic configuration ===== | ===== Basic configuration ===== | ||
| - | After flashing, proceed with [[doc:howto:basic.config|Basic configuration]]: | + | After flashing, proceed with [[docs:guide-user:base-system: |
| ***/ | ***/ | ||
| Line 244: | Line 207: | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| ==== Buttons ==== | ==== Buttons ==== | ||
| - | -> [[doc:howto: | + | -> [[docs:guide-user: |
| Here, we merely name the buttons, so we can use them in the above Howto. | Here, we merely name the buttons, so we can use them in the above Howto. | ||
| Line 263: | Line 226: | ||
| info mainly taken from forum thread and [[http:// | info mainly taken from forum thread and [[http:// | ||
| - | | **Architecture:** | MIPS32 34Kc | | + | ^ Architecture |
| - | | **Vendor:** | Lantiq | + | ^ Vendor |
| - | | **Bootloader:** | U-Boot | + | ^ Bootloader |
| - | | **System-On-Chip:** | Lantiq [[http:// | + | ^ System-On-Chip |
| - | | **CPU/Speed** | 500MHz | + | ^ CPU/ |
| - | | **Flash-Chip:** | Samsung [[http:// | + | ^ Flash-Chip |
| - | | **Flash size:** | 512 MiB | | + | ^ Flash size | 512 MiB | |
| - | | **RAM:** | [[http:// | + | ^ RAM | [[http:// |
| - | | **Wireless:** | [[https:// | + | ^ Wireless |
| - | | **Ethernet:** | [[http:// | + | ^ Ethernet |
| - | | **USB:** | 2x 2.0 | | + | ^ USB | 2x 2.0 | |
| - | | **Serial:** | [[# | + | ^ Serial |
| - | | **JTAG:** | [[# | + | ^ JTAG | [[# |
| * wlan is implemented by own subsystem called " | * wlan is implemented by own subsystem called " | ||
| Line 286: | Line 249: | ||
| ==== Flash Layout ==== | ==== Flash Layout ==== | ||
| <WRAP BOX> | <WRAP BOX> | ||
| - | FIXME // | + | FIXME // |
| - | Please check out the article [[doc:techref:Flash.Layout|Flash layout]]. It contains examples and explanations that describe how to document the flash layout. | + | Please check out the article [[docs:techref:flash.layout|Flash layout]]. It contains examples and explanations that describe how to document the flash layout. |
| </ | </ | ||
| ***/ | ***/ | ||
| Line 299: | Line 262: | ||
| - | {{:media: | + | {{media: |
| - | {{:media: | + | {{media: |
| **Insert photo of backside label** | **Insert photo of backside label** | ||
| Line 311: | Line 274: | ||
| ==== Serial ==== | ==== Serial ==== | ||
| - | -> [[doc: | + | -> [[docs: |
| How to connect to the Serial Port of this specific device:\\ | How to connect to the Serial Port of this specific device:\\ | ||
| - | {{:media: | + | {{media: |
| Line 326: | Line 289: | ||
| ==== JTAG ==== | ==== JTAG ==== | ||
| - | -> [[doc: | + | -> [[docs: |
| How to connect to the JTAG Port of this specific device:\\ | How to connect to the JTAG Port of this specific device:\\ | ||
| Line 1488: | Line 1451: | ||
| </ | </ | ||
| Original Bootlog taken from [[http:// | Original Bootlog taken from [[http:// | ||
| - | ==== OpenWrt | + | ==== QSDK(? |
| <WRAP bootlog> | <WRAP bootlog> | ||
| < | < | ||
| Line 1877: | Line 1840: | ||
| **Helpful Links** | **Helpful Links** | ||
| * [[http:// | * [[http:// | ||
| - | * [[https:// | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| ===== Tags ===== | ===== Tags ===== | ||
| - | |||
| [[meta: | [[meta: | ||
| - | {{tag>128ram 512flash | + | {{tag> |