OpenWrt Forum Archive

Topic: [SOLVED]Zyxel P-2612HNU-F1 v3.11(BLT1) BBv3.05 issue

The content of this topic has been archived on 25 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello,

may anyone know's how to switch on the keyboard on CLI using Tera Term to stop the autoboot on this router and get the ZyU console?

Other problem that i have, is the bootbase or Z-loader.
After some update(that start automatically from self)the router become slow so i downgraded it successfull back to v3.10 but the bootbase was still the new v3.05 and some option was lost.
By mistake i tried to upgrade the router with a firmware v3.11(BLT0) previously was v3.11(BLT1)and since this it's failed to load the firmware.

The problem is that the Bootbase v3.05 incl FW 3.11 is built-in a Zyxel ExpressTool as .EXE and can't get each file separately.
May someone know how get it from the ExpressTool this will also solve my problem.

I think if i can change back(upload over CLI) the FW v3.10 the router will be start again.

Anyone know's maybe what is the "amazon_s Switch"?

ROM VER: 1.1.3
CFG 06
NAND
NAND Read OK

ROM VER: 1.1.3
CFG 06
NAND
NAND Read OK

ROM VER: 1.1.3
CFG 06
NAND
NAND Read OK
DDR Access auto data-eye tuning Rev 0.3a
DDR size from 0xa0000000 - 0xa7ffffff
Start DDR tuning [\]
Read DQS Delay Slice0     :00000017
Read DQS Delay Slice1     :00000016
Write DQS Setting         :00000045
Fix DQS Out Shift         :00000068


ZyU-F01-301-01AA004-V3.05|12/27|2011(BLT)

Boot from NAND flash
AR9 BOARD
CLOCK CPU 393M RAM 196M
DRAM:  128 MB

 relocate_code start
 relocate_code finish.
128 MiB
=>new DDR param:88888888-00000345-00001738-00001616-00000068-00000203
=>old DDR param:00000000-00000000-00000000-00000000-00000000-00000000


  ZyXEL: DDR parameter is changed, but we ignore it!!

*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Net:
switch chip id=0000ffff

switch chip id=0000ffff
"

set voltage

Hit any key to stop autoboot:  0

NAND read: device 0 offset 112640, size 65536 ...  65536 bytes read: OK
## Starting application at 0x85A00000 ...


Z-LOADER 3.0(Dec 27 2011)

NAND flash block size: 0x20000
Dual image: Both OK! upgcnt1=6 upgcnt2=5
Select 1st zboot image...
go 0x85a10000
## Starting application at 0x85A10000 ...


Z-Boot 3.0.0(Nov  3 2011)

we get zloader version:
get mrd failed
initialize working buffer failed

Thanks.


EDIT:
Keyboard issue on CLI are solved- just need to hold the "z" key immediately after power on the router and you will be get "ZLO>" command line

(Last edited by roadstar234 on 26 Jul 2014, 03:25)

With a "help" or "?" on ZLO>
I got four options:

ZLO> ?
ZLGO              boot up the whole system
ZLGU              go back to U-Boot command line
ZLUA    x         upgrade ras image (whole image)
ZLUP    x         upgrade ras image (zboot+kernel+rootfs)

type ZLGU and you will go to the U-Boot command line, which is AMAZON_S#
"?" or "help" command show the options, which are:

=>## Application terminated, rc = 0x0
AMAZON_S # ?
?       - alias for 'help'
askenv  - get environment variables from stdin
bootm   - boot application image from memory
cp      - memory copy
echo    - echo args to console
go      - start application at address 'addr'
help    - print online help
imls    - list all images found in flash
md      - memory display
mm      - memory modify (auto-incrementing)
mtest   - simple RAM test
mw      - memory write (fill)
nand    - NAND sub-system
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
tftpboot- boot image via network using TFTP protocol
upgrade - forward/backward copy memory to pre-defined flash location
AMAZON_S #

Anyone know something more about "AMAZON_S" environment?

The Exprees Upgrade Tool - ExpressBootSrv also show the checksums for:

RootFS Checksum: 000022c8
Kernel Checksum: 0000bd1d
RomFile Checksum: 00005b42

http://i61.tinypic.com/5xndhv.jpg

(Last edited by roadstar234 on 20 Jul 2014, 04:41)

I got finally a separate v3.11BLT1 FW .bin file from Zyxel.

Hello roadstar234,

I've got the same problem and wish to upgrade my P-2612HNU-F1 from V3.10 (BLT.1) to V3.11 (BLT.1) with the hope to fix one instability problems. The Zyxel provided upgrade tool exe file regularly failed and I found no way to extract the bin file. Don't you mind share with me the v3.11BLT1 FW .bin file you have received from Zyxel? Thanks.

Hi,

there is no problem to share the file, but check first the version of installed bootbase on your device.

Because the file are not included of the new bootbase and you can't use it, if the bootbase are still v3.04.

Let me know what kind of instability issue you have, may i can help.

The discussion might have continued from here.