Some devices do not have an external way to activate tftp boot (like
tp-link). You must interact with bootloader in order to
ask it to download a new firmware. Other routers, that might be your case,
have some kind of "konami code" to start a
firmware recovery mode, like pressing reset while you turn on your device.
Also, some bootloaders allows you to upload a new firmware though the
serial itself (i.e. via kermit). This allows a reflash
even for devices that do not have a working ethernet interface. Generally,
this is not recomended as it is much slower than
tftp. As I my pc has only one ethernet, I used kermit in order to keep my
internet online while flashing my device.
Regards,
---
Luiz Angelo Daros de Luca, Me.
luizl...@gmail.com
2013/8/12 Martin T <m4rtn...@gmail.com>
> Hi,
>
> there are few guides in OpenWRT wiki which explain how to configure IP
> settings and download(using TFTP) an OpenWRT firmware file in
> bootloader(for example CFE) CLI. For example, I have following commands
> available in my CFE:
>
> CFE> help
> Available commands:
>
> rndis Broadcom USB RNDIS utility.
> et Broadcom Ethernet utility.
> nvram NVRAM utility.
> reboot Reboot.
> printdefault Display the environment default variables embeded in
> the bootloader
> flash Update a flash memory device
> autoboot Automatic system bootstrap.
> batch Load a batch file into memory and execute it
> go Verify and boot OS image.
> boot Load an executable file into memory and execute it
> load Load an executable file into memory without executing
> it
> write Write a region of memory to a remote file via TFTP
> read Read a region of memory to a remote file via TFTP
> save Save a region of memory to a remote file via TFTP
> ping Ping a remote IP host.
> arp Display or modify the ARP Table
> ifconfig Configure the Ethernet interface
> unsetenv Delete an environment variable.
> printenv Display the environment variables
> setenv Set an environment variable.
> help Obtain help for CFE commands
>
> For more information about a command, enter 'help command-name'
> *** command status = 0
> CFE>
>
>
> As far as I know, in order to access the bootloader CLI, a working
> bootloader and serial connection is required. This means that one can not
> repair bootloader itself over serial port. And in case the OpenWRT
> installation is broken and one can not even access the failsafe mode, then
> OpenWRT can be easily flashed by uploading the OpenWRT firmware from TFTP
> client in PC without initiating this on bootloader CLI.
>
> In which situation it's useful to be able to start the TFTP client on
> bootloader CLI? Are there situations where router bootloader will not start
> the TFTP server and one is not able to upload the firmware from TFTP client
> running in PC? Or are there some other clever maintenance tasks usually
> carried out from bootloader CLI?
>
>
>
> regards,
> Martin
>
>
> _______________________________________________
> openwrt-users mailing list
> openwrt-users@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>
>
_______________________________________________
openwrt-users mailing list
openwrt-users@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
