I'm recerived another ISR9024D-M that works good...
At first I'm connect to corrupted 9024D-M to new one then run the command
update remote-command and finished successfully.
But console was not return.
There isn't update remote-software command.......
I'm find reason for console problem.
It's a cleard configuration and software on flash bank....
Below is normal printenv result via console
-----------------------------------------------------------------------------
| In: | serial |
Out: serial
Err: serial
Net: EMAC0, EMAC1
BEDBUG:ready
Hit any key to stop autoboot: 0
=> printenv
loads_echo=1
serial#=9998
ecc=on
pci_enum=on
pci_listing=short
ethaddr=00.80.f9.69.23.26
eth1addr=00.80.f9.69.a3.26
gatewayip=0.0.0.0
bootfile=path/file.bin
baudrate=38400
filesize=235
netmask=255.255.0.0
ipaddr=192.168.1.2
serverip=192.168.1.100
loadaddr=800000
hostname=0.0.0.0
bootdelay=2
bootargs=console=ttyS0,38400 root=/dev/ram0 rw
addip=setenv bootargs $(bootargs) ip=$(ipaddr):::$(netmask):$(hostname):eth1:none
sec=echo booting secondary, press ^c to abort; sleep 5; echo booting...; bootm d0a00000
prim=echo booting prim...; bootm d3500000
bootcmd=run addip sec prim
stdin=serial
stdout=serial
stderr=serial
Environment size: 619/2556 bytes
---------------------------------------------------------------------------------------------------------------------------------------
Below is last console log of corrupted 9024D-M
*****************************************************************************
BEDBUG:ready
=> printenv
baudrate=38400
filesize=235
bootargs=console=ttyS0,38400 root=/dev/ram0 rw
addip=setenv bootargs $(bootargs) ip=$(ipaddr):::$(netmask):$(hostname):eth1:non
e
sec=echo booting secondary, press ^c to abort; sleep 5; echo booting...; bootm d0a00000
prim=echo booting prim...; bootm d3500000
serial#=0
ecc=on
pci_enum=on
pci_listing=short
eth1addr=00.80.f9.69.17c.18
bootcmd=tftpboot;go
bootdelay=-1
loadaddr=80000
stdin=serial
stdout=serial
stderr=serial
Environment size: 451/2556 bytes
=> setenv baudrate=38400
=> setenv filesize=235
Unknown command 'setenv' - try 'help'
=> saveenv
Saving Enviroment to EEPROM...
=> setenv addip=setenv bootargs $(bootargs) ip=$(ipaddr):::$(netmask):$(hostname):eth1:non
=> e
Unknown command 'e' - try 'help'
=> setenv addip=setenv bootargs $(bootargs) ip=$(ipaddr):::$(netmask):$(hostname):eth1:non
=> saveenv
Saving Enviroment to EEPROM...
******************************************************************************
When switch was reboot then all was gone...
(If I run the initenv command before reboot the switch there is no problem exists...)
setenv usage is very confused to me.....
I find that => setenv baudrate=38400 command delete baudrate value.
Correct usage is setenv baudrate 38400.......
Also another value was deleted........
It's a correct that configuration is located on EEPROM.
But there is nothing to correct the problem on user level.
If you have a solution via normal switch or etc, can you explain to me?
If initial configuration on EEPROM recover then can I re-install SM software on NAND Flash again?