doc:appunti:hardware:technicolor_tg789vac_v2
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
doc:appunti:hardware:technicolor_tg789vac_v2 [2020/03/18 15:58] – [Router Bircked] niccolo | doc:appunti:hardware:technicolor_tg789vac_v2 [2020/03/23 17:31] – [Router Bircked] niccolo | ||
---|---|---|---|
Line 78: | Line 78: | ||
</ | </ | ||
- | ===== Router | + | ===== Router |
I succeeded in bricking this router, may be after I installed the **openvpn** package, which required the **kmod-tun** one. I mixed packages from different architectures and sources, so probably I got some unworkable mix. It is probable that my customization went into the overlay partition and the boot partition is still good, but unfortunately I don't know any method to clean or format the overlay. | I succeeded in bricking this router, may be after I installed the **openvpn** package, which required the **kmod-tun** one. I mixed packages from different architectures and sources, so probably I got some unworkable mix. It is probable that my customization went into the overlay partition and the boot partition is still good, but unfortunately I don't know any method to clean or format the overlay. | ||
Line 94: | Line 94: | ||
=== Accessing the serial line === | === Accessing the serial line === | ||
- | I tried also to connect | + | I connected |
+ | |||
+ | < | ||
+ | Technicolor Gateway | ||
+ | (c) 2015, All rights reserved | ||
+ | |||
+ | Decompressing Bootloader................................ | ||
+ | Gateway initialization sequence started | ||
+ | Boot Loader Version : 2.0.85 | ||
+ | CPU : BCM63168-D0 | ||
+ | RAM : 256MB | ||
+ | Flash : 128MB NAND, blocksize=128KB, | ||
+ | Board Mnemonic | ||
+ | Market ID : FFFCExternal switch id = 53125 | ||
+ | |||
+ | Booting | ||
+ | Magic packet | ||
+ | SW Version | ||
+ | Starting the Linux kernel | ||
+ | |||
+ | [ 0.000000] Initializing cgroup subsys cpu | ||
+ | [ 0.000000] Linux version 3.4.11-rt19 (repowrt-builder@d0b3de64c70c) | ||
+ | (gcc version 4.6.4 (OpenWrt/ | ||
+ | [ 0.000000] VANT-6 prom init | ||
+ | [ 0.000000] CPU revision is: 0002a080 (Broadcom BMIPS4350) | ||
+ | </ | ||
=== Forcing a bank switch === | === Forcing a bank switch === | ||
Line 101: | Line 126: | ||
* In normal condition, the router boot from bank_1. | * In normal condition, the router boot from bank_1. | ||
- | * Flashing via **TFTP** will write to **bank_1** only. | + | * Flashing via **TFTP** will write to **bank_1** only. It will do so even if the active bank is currently bank_2. It will never set bank_1 as active. |
- | * If something goes bad during the kernel | + | * You can see what is the **active bank** by reading **/ |
- | * FIXME Is there a software | + | * Whenever |
+ | * To **force the switchover** from one bank to the other, you have to run a command | ||
So I immagine at least two methods to force the router to boot from the other bank: | So I immagine at least two methods to force the router to boot from the other bank: | ||
Line 117: | Line 143: | ||
* **[[https:// | * **[[https:// | ||
* **[[https:// | * **[[https:// | ||
+ | * **[[https:// | ||
* **[[https:// | * **[[https:// | ||
* **[[https:// | * **[[https:// |
doc/appunti/hardware/technicolor_tg789vac_v2.txt · Last modified: 2020/03/23 17:52 by niccolo